22
Customised Lemmy Instances?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Aug 2023
22 points (92.3% liked)
Selfhosted
61207 readers
201 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
founded 3 years ago
MODERATORS
If one had developed code to do these things, why would one not upstream it so it's released in core lemmy and all instances can benefit from that capability?
Speed of development. It could take months for a PR to get into Lemmy core and then a new release.
Things that get into Lemmy core have to be well thought out and the core Devs have to want them in there.
Running custom code is a way to make changes without having to get their approval, and if it proves popular enough, then maybe they'll implement it upstream.
Not all instance owners may want all those features implemented. Not the same but kind of like how Beehaw doesn't allow downvotes while other lemmy instances do.
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.
No downvotes is a feature toggle by the way.