If you dont like it, fork it. Stop bothering us about it
-devs of PieFed
Oh wait no, that’s the devs of Lemmy when asked the same request. (edit: ‘asking’ to ‘asked’)
Hopefully Rimu will be more accommodating when you ask him? (codeberg issue creation prefered)
It might be time to move this away from a hard-coded list now, if the expectations that someone installing an instance is going to read through the code is lower now than previously.
Eventually, but only reluctantly and after first telling the userbase to simply piss off and stop asking.
In contrast, the PieFed devs seem to have edited their codebase within mere minutes of this discussion having started to have already started changing things in highly positive directions, even prior to being officially asked on codeberg.
The contrast there is eye-opening, and I hope indicative of what the future holds for the Threadiverse. There are far too many LONG-STANDING issues remaining in Lemmy that only continue to get ignored as the years drag on… Lemmy is their codebase, you exist at their leisure, whereas PieFed is ours, able to be modified in ways that we collectively want it to. Obviously I mean on the spectrum, aka “PieFed has highly responsive devs”, who not only receive but even outright ask for advice on things like prioritization (see e.g. last year’s !piefed_2025@piefed.social, although nowadays they are doing that via codeberg issue tickets).
These aren’t specific community *blocks (they’re not blocks as such). They’re keywords. It jus so happens that “196” was a community as well, although that has now been removed.
At least PieFed allows you to edit the list. I still agree that it should not have been hard-coded, but this is not a case where Lemmy is a shining beacon of all goodness and PieFed is pure shit - both have their flaws, and Lemmy’s is MAJOR (and unchangeable) whereas by comparison, PieFed’s is fairly minor as these things go.
Plus haven’t the PieFed devs already changed the code in response to this very thread? (In 2 of the 3 places, but I haven’t taken time to actually look directly myself, and the 3rd place should also be changed too, if it hasn’t been already, to remove the list from being hard-coded.) The PieFed devs, instead of telling the userbase to piss off and only reluctantly change things after a large outcry, are (especially by comparison, but also very much objectively too?) VERY responsive to feedback? I bet you will even be thanked for bringing this to their attention… though in the future you could also try submitting a codeberg ticket:-).
Anyway, you are helping make the installation experience more streamlined and smooth for future users, so (while I have nothing whatsoever to do with the devs), I will say thank you just by myself!:-)
-devs of PieFed
Oh wait no, that’s the devs of Lemmy when asked the same request. (edit: ‘asking’ to ‘asked’)
Hopefully Rimu will be more accommodating when you ask him? (codeberg issue creation prefered)
It might be time to move this away from a hard-coded list now, if the expectations that someone installing an instance is going to read through the code is lower now than previously.
I mean, if I read the thread correctly they did end up making it optional…
No clicking the link to show it was about removing racial slurs! Only out of context snippets!
Eventually, but only reluctantly and after first telling the userbase to simply piss off and stop asking.
In contrast, the PieFed devs seem to have edited their codebase within mere minutes of this discussion having started to have already started changing things in highly positive directions, even prior to being officially asked on codeberg.
The contrast there is eye-opening, and I hope indicative of what the future holds for the Threadiverse. There are far too many LONG-STANDING issues remaining in Lemmy that only continue to get ignored as the years drag on… Lemmy is their codebase, you exist at their leisure, whereas PieFed is ours, able to be modified in ways that we collectively want it to. Obviously I mean on the spectrum, aka “PieFed has highly responsive devs”, who not only receive but even outright ask for advice on things like prioritization (see e.g. last year’s !piefed_2025@piefed.social, although nowadays they are doing that via codeberg issue tickets).
tankies btfo
wow. blocking slurs. oh no thats terrible lmfao
maybe they should expand that list
Wasn’t that only blocking slurs and not specific communities?
These aren’t specific community *blocks (they’re not blocks as such). They’re keywords. It jus so happens that “196” was a community as well, although that has now been removed.
Yes they’re keywords, but they also happen to be the exact names of threadiverse 8 communities, so that’s pretty specific to me.
Wait until you see what is coming up next in Lemmy:
(Edit: I forgot to add the link to source)
At least PieFed allows you to edit the list. I still agree that it should not have been hard-coded, but this is not a case where Lemmy is a shining beacon of all goodness and PieFed is pure shit - both have their flaws, and Lemmy’s is MAJOR (and unchangeable) whereas by comparison, PieFed’s is fairly minor as these things go.
Plus haven’t the PieFed devs already changed the code in response to this very thread? (In 2 of the 3 places, but I haven’t taken time to actually look directly myself, and the 3rd place should also be changed too, if it hasn’t been already, to remove the list from being hard-coded.) The PieFed devs, instead of telling the userbase to piss off and only reluctantly change things after a large outcry, are (especially by comparison, but also very much objectively too?) VERY responsive to feedback? I bet you will even be thanked for bringing this to their attention… though in the future you could also try submitting a codeberg ticket:-).
Anyway, you are helping make the installation experience more streamlined and smooth for future users, so (while I have nothing whatsoever to do with the devs), I will say thank you just by myself!:-)