Permanently Deleted
this post was submitted on 01 Jan 2026
384 points (97.5% liked)
memes
21023 readers
1361 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
List of blocked words in community names:
Seems like one of the PieFed devs has some opinions about the kind of content they dislike, and are unilaterally forcing that on every PieFed instance. I can somewhat understand filtering out curse words, but specific communities should not blocked by default, and definitely not hidden in a hardcoded list in the source code.
Edit: Important context here: https://lemmy.world/comment/21323475 Seems this blocklist is more limited in scope; it's not blocking federation entirely, just blocking (from what I can tell) their appearance in search and automatically federating with them when adding an instance. Still problematic to exclude specific communities in a non-configurable way with little justification IMO.
They're pretty explicit about what they don't like when you sign up. That's why I joined it
Each instance should be free to set their own rules. Individual instances blocking those communities is fine, but the PieFed devs hardcoding a blocklist that applies to all instances (especially one as opinionated and arbitrary as this) is absolutely not.
They... are though? Maybe I am dumb, but I do not understand why each instance setting its own rules would apply to all other instances? Say if you made your own instance, you would set your own rules, but the other instances are free to set theirs as well? Like if you want to allow communities such as "4chan", then go ahead, but if others want to block that, then why shouldn't they be allowed to?
Definitely agree that this issue should be made much more transparent and easier to change, like not hard-coding it.
This filter is not part of any specific instance, it's hardcoded into PieFed's code. That means it applies to every PieFed instance unless the instance admin explicitly patches the code to remove it.
As mentioned elsewhere, it's just a convenience function - anytime after starting up the instance, the admins can always pull in those communities manually. Or change this part of the code beforehand. So it's not a hard-coded "block", just slightly less convenient for it to not automatically pull in those communities during the one-time initial setup for an instance.
But anyway you are right that this should not be a hard-coded list.
Edit: it's also worth mentioning that the way that Lemmy does this is via a direct pull of communities from Lemmy.ml. What I am reacting to here is not so much to say that PieFed's method is perfect, but that both suffer from flaws, and that PieFed's is relatively benign, at least in comparison to Lemmy's. Lemmy uses an extremely authoritarian approach whereby Lemmy.ml is the sole and invariant arbiter of what communities are allowed vs. not during that initial one-time setup, and there is no way to change that, whereas PieFed uses a list that the instance admin is capable of changing. On the spectrum of authoritarian control, PieFed's level here is like a 1 out of 100, whereas Lemmy's is... well, it's still not much in this exact situation, but it's definitely way more. Sorry for being confusing initially in the way I worded that.
I presume that it was a simple misunderstanding, but in any case it has lead to some... interesting, and ultimately quite fruitful discussion, so there's that to have enjoyed:-).
And it really shouldn't have been hard-coded like that. A minor issue imho, and one not really a problem until now, but at least it's already now well on its way to being resolved. In contrast, Lemmy's own hard-coding of Lemmy.ml into the equivalent function I doubt will ever be changed, certainly not without strong reluctance (and likely along with public outcry, as before with the filter list).
One point: I would argue that opt-in vs. -out doesn't fully apply here, as this automated convenience function will only ever be run once upon initial setup for an instance, after which the instance admin can add any communities they desire, manually (I'm not sure why OP phrased it then as needing to be "debugged", that seems an odd term for such routine instance maintenance tasks that do not need any modification of any code at all, anywhere?). In short, it's not actually a "block" at all, as the wording in the meme seems to me to strongly imply by using "federate"). The phrase "opt-out" usually referrs to something harsh but that isn't all the way fully forced, but this issue of not pulling in (initially) of communities is so extremely gentle than on the spectrum it is adjacent to "opt-in" already? Still, ultimately you are probably correct, I am just not sure of the wording there, so wanted to help by offering those additional nuances.