Code for people interested
app/admin/routes.py#L373 (removed since posting), app/cli.py#L1026
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.
Jesus that’s a lot of spaghetti code, and why are they hardcoding a bunch of terms? Is this just for a public facing site, or does every deployed instance effectively filter these out?
It’s hardcoded in the PieFed source code, so every instance does this by default unless you patch it like I did.
The combined swearwords + excluded communities list seems to appear at least 3 times in the codebase (not referenced, copied verbatim).
Let’s just say that it wouldn’t pass my code review if I saw this at work
EDIT: It has been removed from 2/3 places in the codebase.
Help them clean it up!
I’ve made a PR
Atta boy!
The piefed.world instance has some of these edited out but I don’t think they all are.
I think the communities were added manually
How do you manually add communities?
You go to
https://INSTANCE_DOMAIN/c/COMMUNITY_NAME@COMMUNITY_DOMAINand press JoinYou just try to go to the community from that instance, and it’ll say “community not found” and you just click it. Then someone local needs to subscribe to it for new content from there to federate.
Yeah. The list should be in the site config. Go ahead and include those as defaults to block, but allow sites to override that.
OP, are you saying that the federation is blocked on the OUTGOING side? Because then that just seems bass ackwards.
No, it’s incoming. When you first set up an instance you have to kickstart the federation process by adding communities to federate. The linked code excludes those specified communities from that. Once federated, they won’t be blocked AFAIK.