What PieFed blocks out of the box - and how to unblock it
-
PieFed has a dizzying array of settings and options that instance admins can tweak. Most of them have obvious and sensible default values but some of those have been a bit controversial, especially to do with what gets blocked by default. In this post I explain what those are and how they can be configured.
-
PieFed has a dizzying array of settings and options that instance admins can tweak. Most of them have obvious and sensible default values but some of those have been a bit controversial, especially to do with what gets blocked by default. In this post I explain what those are and how they can be configured.
Appreciate the Piefed Devs are continuing the series on explaining their design choices and letting admins/users know how they can enable/disable select features.
Hope to see more entries in the series to come
-
PieFed has a dizzying array of settings and options that instance admins can tweak. Most of them have obvious and sensible default values but some of those have been a bit controversial, especially to do with what gets blocked by default. In this post I explain what those are and how they can be configured.
It’s a pretty blunt instrument and using it risks bringing in a lot of weird stuff you didn’t expect so there is a keyword filter to screen out some of the more jarring communities. The keywords are: ‘shit’, ‘piss’, ‘fuck’, ‘cunt’, ‘cocksucker’, ‘motherfucker’, ‘tits’, ‘greentext’, ‘4chan’, ‘fauxbait’. Any community with those words in it cannot be accidentally added while pulling in dozens or hundreds of others. View source code.
You can still manually add any community, including ones with those words in them (like “shitposts@piefed.world” or “4chan@sh.itjust.works”. Do this by going to the main Communities page and clicking on ‘Add remote community’.
While no communities I’d be interested in are affected by the filtered word list, requiring instance owners to know about and manually import each community affected by it still amounts to a built-in, non-optional block on most impacted communities (given that most communities realistically won’t be manually imported); ideally the word list should be configurable as the other settings are.
-
It’s a pretty blunt instrument and using it risks bringing in a lot of weird stuff you didn’t expect so there is a keyword filter to screen out some of the more jarring communities. The keywords are: ‘shit’, ‘piss’, ‘fuck’, ‘cunt’, ‘cocksucker’, ‘motherfucker’, ‘tits’, ‘greentext’, ‘4chan’, ‘fauxbait’. Any community with those words in it cannot be accidentally added while pulling in dozens or hundreds of others. View source code.
You can still manually add any community, including ones with those words in them (like “shitposts@piefed.world” or “4chan@sh.itjust.works”. Do this by going to the main Communities page and clicking on ‘Add remote community’.
While no communities I’d be interested in are affected by the filtered word list, requiring instance owners to know about and manually import each community affected by it still amounts to a built-in, non-optional block on most impacted communities (given that most communities realistically won’t be manually imported); ideally the word list should be configurable as the other settings are.
Before we created the bulk community import feature, all communities were manually imported.
Back then it happened by people importing their profile settings from Lemmy, which includes their community subscriptions. As soon as a dozen people joined piefed.social and imported their settings, 80% of the popular communities were added, including ones with ‘shit’ in their name.
So this anti-shock filter on the bulk import isn’t a big hurdle, at all. Shitposts abound, regardless.
