Also not that it matters but I am continuing to use "Mastodon" to describe the particular bit of the Fediverse visible from Mastodon Dot Social and "Fediverse" for the whole disconnected graph of federatable software. (Although tbh part of that is the word "Fediverse" rubs me the wrong way for some reason. Also considering how widely blocked it is, perhaps "Mastodon" shouldn't include Mastodon Dot Social.)
@mcc It's really been a pain for me finding an instance that's 1) Not toxic itself, 2) Run by an admin who's not overzealous in blocking instances over high school cafeteria drama, and 3) Not blocked by a bunch of other major instances. I really get sick of trying to follow a journalist who's migrated from Birdsite, and finding their instance is blocked. The proper approach IMO is to limit instance blocking to instances that have really toxic cultures as a whole -- like fascist, MRA, TERF, &c -- and otherwise just block offending individuals. Either that, or come up with some way to override your instance admin's block if you want to follow an individual on a blocked instance.
@KevinCarson1 I absolutely agree, although it's complex because I *do* want instances to get blocked over systemic racism and although I feel I am very confident I can tell the difference between high school cafeteria drama and legitimate concerns about homophobia/transphobia I do not think I can trust myself to do the same with racism.
But it barely matters because I picked an instance in 2016 and I can't switch now without losing my post history!
@mcc @KevinCarson1 I feel like "losing your post history" shouldn't be one of the problems with this medium. so much for "own your own data" 🙃🙃🙃
