According to Rimu Atkinson, the main developer of PieFed, all PieFed instances come with a 3000-long block list of resources that cannot be linked to. These include all sorts of right-wing outlets. There is no easy opt-out, forcing existing instances to follow the blocklist.
The flagship PieFed instance also rolled out a feature marking various other sorts of outlets - among them, resources considered AI slop and Marxist outlets. These are specific to piefed.social.
Related discussion: https://piefed.social/comment/11254679
Why YSK: Many users have hard time choosing between Lemmy, PieFed, and Kbin/Mbin. Users that prefer a more curated and politically uniform experience might prefer PieFed over the alternatives. Users that are right-wing, Marxist, or generally concerned about global censorship of the Fedi-/Threadiverse, might opt for other options instead.
Note: The post is only meant to inform users of the potentially important differences between Threadiverse platforms. Any ideologically charged discussions are better left in the respective topic.
I literally installed it the day before yesterday, the first page of logs was applied x blocklist, applied x blocklist… Unless the pyfedi repo is unofficial?
PEBCAC. this is a skill issue not a statement of fact. you not knowing how to operate the software is different from the software mandating things. maybe you should go find the code and understand how it works before making wild claims that are a result of your incompetence.
Fun fact: since someone did provide receipts and I did look at the code. its trivial to remove both domain blocklist and the instance block list in about 40s of work.
Okay? Just because it’s possible does not mean the avg instance will bother, much less avg person
the average person isnt running their own software stack. your complaint was its hard coded. it isnt. your complaint was that it couldnt be changed. it can. you were simply wrong on all counts and are now moving the goal post to make yourself feel better.
Ok, but the only reason for there to be default blocks with no env var to disable, no command flag to disable, and no setting to disable is to want them to be applied to every instance
or 99% of the people running instances will want those defaults and its not worth the effort to deal with people like you to bother making it brain dead to disable.
trust me adding friction to a codebase is the a easy way to not have to deal with you.
for example imagine having ti field nonsense feature requests from people who cant even be assed to do basic research on how to remove the blocking configuration. that’d be infuriating.