Notices by Rusty Corgi (rusty@cubhub.social), page 2

@NeonPurpleStar .cofe files :blobcatgooglycofecup:

Users: I'm worried about picking the right instance. What if I want to post stuff that doesn't work with the instance I'm on?

The dumb CubHub admin: HEY LOOK, I'm a bondage dog bark bark! Now I'm a piggo let's talk about fatty stuff!! Now I'm gonna go on a big Linux rant!! Wait what was this place supposed to be about again? :blobfoxthinkgoogly:

I think what bothers me most about #TheBadSpace discourse is how disingenuous the response to the criticism has been. Blocklists propagate too quickly and universally lack proper vetting. They're too often a tool to silence queer and kink-positive voices. In the case of our server, we've been on blocklists simply because of our name, despite the first paragraph of our About page clarifying what types of content we allow. Yet, without any vetting, we were blocked (and continue to be blocked) by other instances that used a blocklist.

TheBadSpace uses instances that we're blocked by due to the admins being extremely kink-averse, yet they look at those instances as trusted sources.

Ad hoc moderation has universally not been an issue for servers to do. Blocklists are simply oppressive tools wielded by people who want to police everyone else.

@ocdtrekkie Websites can implement API calls to Mastodon instances without being Mastodon themselves. Adding them to the domain blocks ensures they can't use the API endpoints to scrape data.

I understand being a work in progress, but making a domain block list with zero checks in place is wholly irresponsible. Whatever underlying AI/logical infrastructure they have in place here is clearly contradicting itself and hurting a lot of smaller instances. The behavior of this blocklist really could make or break hundreds, if not thousands of users trying to be a part of the Fediverse. It's a flat-out irresponsible behavior.