Code for people interested https://codeberg.org/rimu/pyfedi/src/branch/main/app/admin/routes.py#L373
I commented it out, rebuild the Docker containers and it works now 👍
EDIT: People seem to misunderstand what it does. It prevents it from federating automatically when populating the community search, importing from another instance or from Lemmyverse. It’s not a full block, and you can still add it manually. Not only that, but it’s also already partially removed since I posted this.
List of blocked words in community names:
shit piss fuck cunt cocksucker motherfucker tits memes piracy 196 greentext usauthoritarianism enoughmuskspam political_weirdos 4chanSeems 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.
People were rallying on piefed on resentment from tankie Lemmy devs. But this explains where the piefed devs bias is.
Seems like the intentions are to limit the reach of content critical of a certain country. Hmm…
I’m not okay with them filtering profanity, who the fuck are they to define what is or is not acceptable?
The stupid thing is that all those words are only in English. No “merda”, “scheisse”, “joder”, “merde”, …
You can contribute to the codebase by offering to add them in…
I don’t think it’s a good idea either, but it’s less egregious than filtering specific communities.
I probably agree, but frankly I find neither acceptable
Or they like it and e.g. want just one strong 196 community.
That nobody is federated to.
That could be the point. No such community on a new instance can be found by others so the original community receives all the attention.
That doesn’t make any sense because it doesn’t block the new 196 community because it uses letters
What do you mean? 196 is part of the list in degenerate_neutron_matter’s comment so a new 196 channel would be blocked.
Do you mean that the official 196 channel uses words and if somebody copies that it is not blocked? True but who would do that?
What is a “196” community? I tried looking it up and there’s only astrology stuff coming up.
To add to the other responses, it was the very first community I blocked upon moving from Kbin.social (when it died) to Lemmy, since while the content is not so much “bad” it is just so… MUCH.
And I’ve heard the same story from so many others. It makes browsing All - particularly by New - very difficult by overwhelming the space.
As already mentioned, it moves around a lot - there are at least three communities here now, and also on Reddit before there was a r/196 there was a r/195, so it moving and splitting and continuing on is kinda its thing - sorta exactly like the Fediverse itself!:-)
It’s a meme community with a special rule (see the sidebar).
https://www.reddit.com/r/196/ (the original)
https://lemmy.blahaj.zone/c/onehundredninetysix
Aha. My gratitude for the links.
This isn’t the first time I’ve encountered an extremely pointed line of code in piefed meant to fuck over one person specifically. It’s very concerning now that it’s a pattern.
Got any other specific examples?
Yeah, check out this dick move. This changeset exists just to fuck over one specific well-known community member who has never been accused of any kind of misconduct.
That’s hilarious
It is, but it’s not funny enough to make up for how shitty it is.
I do, from the piefed repository, but it’s buried in my history. I really want to remember, I’ll reply again if I do.
Damn this should honestly be spread and talked about more. I don’t think many people know this is a thing?
Considering PieFed users won’t shut the fuck up about how much better and less politically opinionated it is, yeah we should probably shout this from the rooftops.
Reminds me of Brave browser users a bit
Absolutely! Oh wait, we aren’t talking about Rust debate bros here?
“Ours is not biased and less opinionated, because it agrees with my bias and opinions.”
This is every single Lemmy v PieFed argument. No matter what platform you host or use, its just this on the grand scale of things.
One of PyFed’s selling points was that it was easier to work with than Lemmy. It’s going to be amusing when that takes a 180 turn and people start complaining.
Python is great for prototyping and iterating on small projects or as glue for modules written in C and C++. What it isn’t great at is linearly scaling on a single node. When the day that throwing more powerful hardware at the problem stops being an option, Kubernetes is going to walk through that door and fuck any semblance of simplicity up.
People are already complaining (see: this very thread:-), but also note that people are complaining about Lemmy too - e.g. slrpnk.net about to switch to PieFed, due to frustrations with long-standing bugs.
People always complain, the important thing is to move forward with something that is going to work. Personally I think Lemmy will not, though I would be happy to be proven wrong, and I am pinning all hopes on PieFed - worst case there is that they both succeed, which would be fantastic 😍.
Yes I hear what you are saying about resources and complexity (learning Rust is somewhat complicated as well though…), but right now the subscriber counts across the entire Threadiverse are dropping not rising, so that will be a wonderful problem to have to solve one day, if we ever get to that point.
I would agree with that sentiment, but seems like peoples’ actual experiences are a bit different: https://jeena.net/lemmy-switch-to-piefed
Possibly a testament of how software architecture can be more important than any lower level technical decisions.
I think Lemmy has some in-memory data structures that limit the backend to a single node, too. Also postgres is great, but Lemmy really fucked up their database performance somehow.
But yeah large python codebases turn into spaghetti really quickly.
I can confirm this statement.
Hard-coded filters, here we go again.
https://github.com/LemmyNet/lemmy/issues/622
I think a regex to filter out common slurs isn’t really the same
The regex:
Link to code
That can’t be common enough to be included lmao. Also censoring “bitching” is kind hard, now I can’t tell everyone about my bitching ride
thanks for pointing to that issue. i dont know how piefed devs reacted to this. so i will give them the benefit of the doubt: it could very well be a quick and dirty solution, never meant to last long.
as the lemmy devs showed, it does not have to be like this at all. but i haven’t seen that much oppinionsted and defensive actions from the piefed devs.
What are the words in the harcoded Lemmy filter?
Isn’t there a Java based Lemmy compatible thing too? I forgot what it was called but I think there is one.
Sublinks. It’s currently in a hiatus, I think.
They also put “memes” and “enoughmuskspam.”
The latter I guess could be used to stop Musk spam (since the community is literally nothing but Elon Musk news) but not allowing the word “memes” in a community name?
Utterly stupid.
But they do appear to be fans of Carlin based on the first 7 banned words.
There’s no racial slurs in there either. I might have assumed this was merely an example an operator is meant to edit themselves, but these are some weird ass choices for even that.
Well, it seems specifically 196 just got removed: https://codeberg.org/rimu/pyfedi/commit/b7a9ea0eea3a80f710e0b5b63cf0bbecde60f8bf
Actually, they only removed it from 2 places. It’s still there https://codeberg.org/rimu/pyfedi/src/branch/main/app/cli.py#L1026
I wonder why the dev had an issue with 196
Because it’s an enormous flood of content that overwhelms trying to browse All otherwise, especially by New. Or at least that was the case a couple years ago, maybe it’s changed now that the community has split up into 3 parts.
It was particularly a concern back before Lemmy had implemented the Scaled sort function and changed how Hot worked. Perhaps PieFed, back upon tinkering with its own sort functions, similarly tried to make that process easier to see content other than from 196 and memes?
If I had to guess, 196 is more queer positive.
I don’t think that’s the reason. The code mentions it filtering out “low-effort” communities so the devs probably didn’t like seeing so many posts from it on their frontpage.
You’re wrong. Rimu has never expressed any objection to pro-LGBT sentiment and has even done interviews in regards to that. I have seen him ban people for anti-LGBT bigotry. This particular ruleset looks like a copy and paste from the retention rules that piefed.social currently has that doesn’t save data from communities after 6 months. (RImu doesn’t have a high opinion of meme-themed content and believes it to be a drain on server storage).
I agree all of it should be optional, and I believe it currently is anyway as instance owners can revert this.
That still makes no sense
It does if your a bigoted shit face.
Let’s not make those assumptions based on an old filter list
Correct, it doesn’t. But some people find a way to be bothered by it.
So if I started a piefed instance and wanted to host a 196 community I’d have to edit the list, but would every single other instance also have to or no?
Or you could pull it in manually. It’s just that the automated startup would not do it for you, for communities with these keywords. Nothing prevents anyone from pulling in the communities manually though.
Yes, every other instance would also refuse to federate unless they also changed their code. Because the blocklist is baked right into the code, so anyone just pulling and running it as-is will fail to federate.
It’s odd that communities with those names load if they’re hosted on Lemmy, tho. Or maybe I’ve just only been on Piefed Instances that undid the list.
George Carlin would be amused.
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 don’t host any so as I understand it:
The problem with PieFed is the initial filter list is not opt-in, but can be modified freely.
The problem with Lemmy is changes like those will be hardcoded.
The thing with PieFed… I don’t know if it’s in the setup guide and OP didn’t read it or if it must be pointed out in the guide.
Anyway, it should be opt-in, not opt-out.
But trying to frame it as if it was as terrible as lemmy… Lemmy defenders sure love the ragebait.