Are there instances that run modified versions of the base Lemmy software? For example, that use their own sorting algorithms, or provide users ways to block instances or specific users, etc?
Are there communities that talk about this kind of thing? Like a LemmyForInstanceOwners community? I don’t really want to trawl through GitHub for this sort of discussion.
Are there instances that run modified versions of the base Lemmy software? For example, that use their own sorting algorithms, or provide users ways to block instances or specific users, etc?
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?
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.
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.
The instances that have been developing custom features (IIRC lemm.ee and a couple others) have been contributing them back into the main Lemmy project, so everyone else ends up eventually getting them.
Edit: I’ve seen a community for instance owners and devs somewhere but don’t remember the name, hopefully someone else remembers
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
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?
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.
No downvotes is a feature toggle by the way.
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.
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.
The NSFW instances use a modified front end to allow for automatic picture expansion (and probably other things).
The instances that have been developing custom features (IIRC lemm.ee and a couple others) have been contributing them back into the main Lemmy project, so everyone else ends up eventually getting them.
Edit: I’ve seen a community for instance owners and devs somewhere but don’t remember the name, hopefully someone else remembers
Lemmynsfw uses a custom version that that removes the blur for nsfw images but that’s it I think.
Yes, Hexbear is highly customized. Beehaw is o believe. Not sure what else