Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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.
I could be off the mark here, but I think it's a little more complicated than that. I believe Meshtastic has trademarks on the name and logo, and they went so far as to shut down a project that was attempting to allow a device to switch between Meshtastic and Meshcore firmwares.
On the other hand, Meshcore is all open, however the client apps are closed source and on a sort of fremium model aimed at supporting the developer. Mobile apps have a 10 second wait to admin router nodes, which can be removed by a one time fee ($9, I think?). And then there's a more feature rich firmware for the LilyGo T-Deck (cool standalone Blackberry-like device) which has a paid option.
I'd like to see open source community developed apps, and I don't think there's anything to stop anyone from writing new ones, other than the fact that the existing ones work well and the paid features make for a cheap an easy way to support the project.
If I'm wrong about any of that, I hope someone else with a better understanding can chime in.
Why would you call closed source client apps "open"?
I suppose I worded that poorly. I meant that the firmware and protocol are open while the Android/iOS apps are not. My intent was to clarify what was open/closed, not obfuscate.
Directly from MeshCore's docs:
Like I said, I'd prefer to see those closed bits also being developed openly and as a community, and there's nothing to stop anyone from that endeavor. I also get that the mobile app dev has put in a lot of work on both the closed and open source pieces of the project, and he's gotta eat.