view the rest of the comments
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!
They promised at least that's not how they're going to do this, at least. But in the end, it's easy to backpaddle on these promises.
Still: you can always fork the project.
I don't think it's possible to make this project proprietary because FUTO does not own the rights to the code that were made by random contributors on git. Part of the promise was that they won't change their CLA so it should be fine.
Who is? That's the problem with forks. They always divide the community into slices
I don't think that there'll be a community for a project that turned proprietary.
Why not? There are some popular examples, like mysql --> mariadb or elasticsearch --> opensearch
I meant for the propietary branch.
Ok, makes sense