Which are only blocked if the admin specifically asks for them to be.
In other words not hard-coded at all.
PieFed is quite opinionated, and the instance picker even more so, but the “hard-coded” arguments have long since been debunked (though last I checked, without being acknowledged by those who initially spread the story).
Also the flagship instance PieFed.social does block a lot, but that’s as different as an instance is from software. Btw Lemmy.ml rather famously blocks a lot of content as well.
Whatever software you use, pick good instance admins that you feel reflect your values (or even self-host your own), and you’ll enjoy your experience on the Threadiverse much better than being at odds with them.
piefed has hardcoded blocks for instances the dev doesn’t like
Which are only blocked if the admin specifically asks for them to be.
In other words not hard-coded at all.
PieFed is quite opinionated, and the instance picker even more so, but the “hard-coded” arguments have long since been debunked (though last I checked, without being acknowledged by those who initially spread the story).
Also the flagship instance PieFed.social does block a lot, but that’s as different as an instance is from software. Btw Lemmy.ml rather famously blocks a lot of content as well.
Whatever software you use, pick good instance admins that you feel reflect your values (or even self-host your own), and you’ll enjoy your experience on the Threadiverse much better than being at odds with them.
I follow along a lot in the chats and run the software. They did move everything to configuration a long time ago.