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
Where do you get that from? I have no love for tankies, but from what I've seen, they've built a product that's free of their biases, opensourced it and thrown it over the wall with no strings attached.
If you want to make a rooten-tooten white supremacist nazi instance with Lemmy, you can do exactly that. Nobody has to federate with you, and you don't have to federate with them.
Strange take.
Not for folks who have been following the development. It’s one thing if it’s just a couple of devs working on the project and trying their best, it’s an entirely different thing when a couple of devs are shutting out large numbers of contributors (frequently subject matter experts which they desperately need at this point) over relatively trivial issues. It's become a pattern and will almost certainly continue. At this point a significant number of users have been lost because the devs have been largely unable to capitalize on previous waves on growth due to slow development. Because of all this Lemmy has an awful reputation even among the rest of the fediverse and particularly among people who have tried to contribute. A fork would probably be a significant improvement as far as brand perception goes.
Sounds like you should fork it.
I would love to contribute but I don't have the experience for a fork. This is kind of the essence of the whole problem though. Plenty of unutilized contributors who could be driving this project forward but are having a hard time getting involved.
This sort of thing happens in every opensource project; the maintainer(s) have a vision for the product and whatever amount of time they can use to review contributions and PRs. Some PRs are utter messes, some are good but complex, others are good but either are not going to be supportable with the current manpower or will be superceded by codebase changes in the future. And then these contributors get upset their PRs aren't being taken seriously. They as well are welcome to fork it and they could even use patches from the original branch as they develop their forks, and presumably implement them in production. But more often than not, they just move on because they don't have much invested.
It's every maintainers balance that has to be determined, and not everyone is going to be happy. They might want a slow development pace because fast paces require a lot of work to maintain. Simplistically saying "we need faster development to take advantage of surges in interest" is pointless if there's nobody that's willing to stand behind the extra QC and support those patches introduce. Drive-by patching is a huge issue because the contributors rarely stick around to fix bugs.