The creators of Lemmy are tankies and have some pretty despicable views, maybe we shouldn’t advertise giving them money.
I like the software, it feels cozy outside some communities from lemmy.ml, and I hope someone forks it eventually, but for now removing the link should be easy to do.
Relevant thread: https://mstdn.social/@feditips/106835057054633379
From taking a look through the feditips post and just idly browsing lemmy.ml, there’s an alarming amount of toxicity and strange moderation decisions that seem to be weirdly tankie… sigh
I’m unsure if I’ll be able to maintain a fork myself given everything else, but I’d be more than happy to swap to one that removes those links and references. As well, I’m going to look at defederating from lemmygrad.ml which seems to be one of the more prominent sources.
I did see Feditips recommend an alternative: https://kbin.pub/en – but, I’m unsure if anything that’s already been set up would be cross-transferable.
Haven’t looked at it yet, but patching out the button should be relatively simple even in production as the frontend is in typescript. Not sure about the licensing aspect, since it’s AGPL, which means source code has to be provided.
I have a test instance up because I’m experimenting with lemmy as a blog backend, so I’ll try it out and let you know!
For transparency, we’re using the ansible playbook to deploy it, so we’d end up needing it dockerized, but yeah.
I’m not very familiar with docker and whether it’s possible to just patch files in the image, if yes the you could probably make a script to apply it in case of an update (client.js is the file that needs to be changed), if not it should be possible to make a theme with some CSS that removes it.
With the license, I think stating the exact change in the sidebar would be enough, but obviosuly not a lawyer and AGPL is funky.
Think of Docker as just an .exe, the compiled version of the code in a neat bundle. We’d just need to set up a pipeline to run that, but since it’s AGPL, we should be fine.