Semperverus

Why would you call closed source client apps “open”?

Do note though that MeshCore is proprietary and has a licensing cost to unlock all of its features whereas Meshtastic is open source and free as in freedom.

Yep, just make sure to set the permissions so you’re not sending notifications to the other phone (if it’s someone else’s) or allowing remote control of yours. Just enable file sharing or whatever you want, and maybe allow them to do the find my phone ring thing.

When you and your wife send pics over KDE Connect instead is a powerful moment. Still requires one phone to connect to the other over hotspot or be on the same network at home, but its slick otherwise.

I dunno if you know this but SMS support got removed from Signal a few years ago

Its still better than any new chat protocol thats been made in the last decade. You’ll have to pry my family XMPP server out of my cold dead hands.

Great! Now I can listen to my PinePods on my PineBuds which I store in my PinePod that they came with.

Meshcore also has a paid license to use the full feature set and if Plex has taught us anything, it’s to stay away from garbage like that. I’ll stick to Meshtastic, thank you.

The fossify apps are legit, I use them daily.

This is the same or similar situation as OpenOffice → LibreOffice or OwnCloud → NextCloud (and to a lesser extent but more similar scenario, Audacity → Tenacity or various other forks).

This is what true open source looks like in action.

People are always angry and confused when i call MIT a grifter license

I wish we would all start switching over to JSON for configuration files. It’s so much easier to parse, and you can’t screw it up with too many spaces or not enough.

This makes it make so much more sense…

Its not really insanity, just a lot of hidden function calls

Two thumbs

MIT is allow to be closed, so it’s free but not libre. I know its pedantic, but it’s a very important distinction.

Are you using Pipelines in either github or another upstream source management platform? I don’t know if they have a free build plan or not, but you can have an entire pipeline that just spits out an executable for one or more platforms every time you commit to your main branch, depending on how you have compilation set up (you can have it use both a Linux and a Windows VM for different steps in the pipeline too). It can even handle publishing them to a website if youre handy with bash and/or powershell scripts (or python or JS or whatever you can call from the pipeline).

I use the Azure DevOps version at work and its amazingly useful, but very confusing to learn at first.

Looking forward to seeing your work - it’s always good to have competitors, and gpt4all is also very crashy. If you have a lead in stability, I’d definitely use yours over theirs.

Some other areas you could probably look into if you want to differentiate are:

• Getting Started experience - recommend some high quality models and update the list as time goes on. Maybe include a good default one as part of the package.

• Convenience - include a way to do what the modern chat interfaces do where asking it to do something other than text will call a different AI model built for that purpose and return the result (image generation, etc)

• Voice conversations - Can we actually talk to the dang thing?

• Assistant module - piggybacking off of the last one, can we invoke it with a wake-word or a button press and have it “always available” (similar to HomeAssistant with a Whisper plugin, but on-device).

Anyway, I wish you well in your endeavor and will keep an eye out.

EDIT: looks like the conversational bits are on your roadmap, and you do have some basic suggestions on startup.

As for voice, the OpenWhisper module might fit your project’s theme a bit closer than elevenlabs.

Bro this is Gpt4All

Its just whatever is built into copilot.

You can do a quick and dirty test by opening copilot chat and asking it something like “outline the vulnerabilities found in the following code, with the vulnerabilities listed underneath it. Outline any other issues you notice that are not listed here.” and then paste the code and the discovered vulns.

That seems to be the direction the industry is headed in. GHAzDO and competitors all seem to be converging on using AI as a force-multiplier on top of the existing solutions, and it works surprisingly well.

Having actually worked with AI in this context alongside github/azure devops advanced security, I can tell you that this is wrong. As much as we hate AI, and as much as people like to (validly) point out issues with hallucinations, overall it’s been very on-point.