Yeah, but that's after the fact, and after their content has federated to other instances.
It doesn't solve the bot problem, but just plays whack a mole with them, whilst creating an ever large amount of moderation work, due to it federating to multiple instances.
Solving the bot problem means stopping the content from federating, which either means stopping the bot accounts from registering, or stopping them from federating until they're known to be legit.
I mean, approving users, you just let your regular established users approve instance applications. All they need to do is stop the egregious bots from getting through. And if there is enough of them, the applications will be processed really quickly. If there is any doubt about an application, let them through, because they can be caught afterwards. And historical applications are already visible, and easily checked if someone has a complaint.
And if you don't like the idea of trusted users being able to moderate new accounts, you can tinker with that idea. Let accounts start posting before their application has been approved, but stop their content from federating outwards until an instance staff member approves them. It would let people post right away without requiring approval, and still get some interaction, but it would mitigate the damage that bots can do, by containing them to a single instance.
My point is, there are options that could be implemented. The status quo of open sign ups, with a growing number of bots doesn't have to be the unquestioned approach going forward.
How do you figure that? There's nothing centralised about it
Make sign ups require approval and create a "trusted user" permission level that lets the regular trusted users on the instance see and process pending sign up requests and suspend/delete brand new spam accounts (say under 24 hours old) that slip through the cracks. You can have dozens of people across all timezones capable of approving requests as the are made, and capable of shutting down the bots that slip through.
Boom, bot problem solved
It sounds like depersonalisation to me. A form of dissociation.
Lots of trans people deal with it when they're closeted. I know I did.
I don't understand. Why not do whatever you normally do to edit and post videos?
Make a video telling people you've moved
Time travel/alternate dimension stories that don't just use infinite dimensions as a cheap way of avoiding complexity. Once you have infinite timelines, it's all meaningless, because whatever story you're trying to tell loses all sense of importance, because whatever didn't happen in one version still happens in another. Who cares if the character saves their family, when there are an infinite variety of worlds where they're not saved.
It's possible to tell stories about infinite timelines, where the weirdness of having infinite duplicates is an important part of the story (Dark Matter).
It's possible to tell stories where there are alternate timelines, but only a finite number (The Peripheral/Counterpart/Alice)
And it's possible to tell stories where there is only one timeline, and gracefully navigate the paradox (The Pern Series/All You Zombies/11.22.63)
I can't get enough of stories that handle it well!
Who said it would be entirely men?
First hand experience
'cause I know I feel welcome, and not completely othered and invalidated when I'm forced to play on a team that is otherwise entirely men, whom have athletic advantage over me
I think it's a good thing, because it discourages centralisation. If we end up with a bunch of specialist instances, then diversity suffers, because everyone looking for a specific area will end up on the one single specialist instance dedicated to it.
And I say that as the admin of an instance focused on the trans and gender diverse folk. There is a reason that we don't enforce specialisation on those topics in our instance communities though. Even so, we still tend to be "the trans instance", when I'd much prefer it if we were just one of many, like we are on the microblog part of the fediverse.
It's using the existing tool, but making a small portion of them (approving applications) available to a much larger pool of people
If the instance that hosts it doesn't think it's a bot, then it stays, but is blocked by the instance that does think its a bot.
And if the instance that thinks its a bot also hosts it, it gets shut down.
That is regular fediverse moderation