3 ms·
The potential for division in the fediverse as a whole is worse. On twitter, there were McCarthyesque, opaquely curated user blacklists to worry about. A conglo
by subdivisions 8y ago
The potential for division in the fediverse as a whole is worse. On twitter, there were McCarthyesque, opaquely curated user blacklists to worry about. A conglomerated instance could enforce this kind of arbitrary censorship across entire communities by imposing rules on who their federation partners can federate with, and control network disruption by refusing to federate with new, <100 user instances under the excuse of "preventing spam". Centralized social networks have already isolated people into information bubbles bad enough as it is.
- intothemild 8y agoThe blocklists are equally as McCarthyesque.. I remember being on mastodon when the second wave of users hit (pawoo.net). Suddenly overnight we had to worry about what was on our servers cache.. suddenly there was lolicon porn, which might be legal in japan, but outside it could be illegal. So naturally blocklist's appeared, blocking all the new wave of Japanese servers. I remember there was a disagreement between those in favor of block list's and the creator of Mastodon. Who didn't want any form of blocking, back at that time the tools to do any form of blocking was either non-existent or very raw. I had an instance at this stage, and the thought about having some kind of childporn drawings in my servers cache scared the living shit out of me. Enough to shut it down. But the blocklists weren't vetted back then, and I don't think there was a central list that I can remember.
- deleted 8y ago[deleted]
- rainbowmverse 8y agoI think this is what led to instance muting. Now admins can mute an instance, but people can still opt in to following someone there, probably without caching.