Instances choosing to implement their own blocks for their instance is different than a front end developer sneaking a block list in an obscure way that impacts multiple instances.
Comment on Tesseract Dev (AdmiralPatrick) RageQuits Lemmy with Final Goodbye Message
pelespirit@sh.itjust.works 3 hours agoOther instances do this, he’s not the only one. There is a github program that you can use. Also, cloudflare (cloudfare?) probably does a bit of that too.
snooggums@piefed.world 3 hours ago
pelespirit@sh.itjust.works 3 hours ago
No it’s not. If I have an instance that blocks any mention of lgbtq+, or trump, or biden, or whatever, that wouldn’t be cool at all. It would be fine if they told you up front, but not if it’s a secret.
snooggums@piefed.world 3 hours ago
You can’t see the difference between one instance making a decision for themselves and a dev making a secret decision that affects multiple instances?
pelespirit@sh.itjust.works 3 hours ago
So you can’t see that shadow banning and curating other’s content is bad?
unemployedclaquer@sopuli.xyz 3 hours ago
Yah we’re getting it from every angle. Oooh where do you get secure DNS?
Trampampoline@sh.itjust.works 55 seconds ago
unbound raspberrypi next to the router
our dns doesn’t exist, fam
unemployedclaquer@sopuli.xyz 2 hours ago
Is this a hard comparison to ongoing controversy? I’m on a mobile but can come back on a desktop. Although yeah cloudflare, hmmm, never heard of it, but my neighbor is yelling at their dog
Trampampoline@sh.itjust.works 2 minutes ago
Gotosocial and Jabber(XMPP) have blocklists too. Optional ones.