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:
- 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
In the vast majority of cases, one can support variation in admin preferences by exposing a configuration parameter. Your downvote example is perfect because Beehaw doesn't run a customized lemmy codebase. There is a checkbox exposed to lemmy admins that enables/disabled downvotes.
Running a custom-codebase is generally the highest-hassle method of achieving some custom-config goal. The absence of communities around this approach isn't an accident, the people who develop customizations generally try to work with the upstream unless the devs give them good reason not to.
You're absolutely right, now that I think about it. My bad. But yeah, it makes more sense to upstream and make the features toggle-able.