I think @boyter is pretty cool, but @cloy seems to be on the wrong track. The response to both, though, demonstrates to me that instance admins here are going to be absolutely blown away when state-level actors and professional trolling outfits show up here.

Instance what-a-mole shared via hashtag isn't going to be effective in 2023.

@ocdtrekkie @boyter @cloy admins have been asking website boy for allowlist based federation, for "review new servers" like the "review trending" admin tools, for any kind of collaborative blocklist tooling. Eugen has been very resistant to even admitting that there's a problem.

@eqe @boyter @cloy@techhub.social People need to stop asking Eugen for things and just build forks.

I am fine with Eugen running his software project the way he sees fit. But the fediverse needs to be more than just Eugen.

If that means we didn't different cute animal logos due to trademark policy, so be it.

@ocdtrekkie @eqe @boyter Uhm ... you're aware of the fact, that mastodon is _just_ one of _MANY_ UIs you can have?

The #FediVerse is _WAY_ bigger. I'm actually astounded that one obviously needs you to tell that ... seen that you're already with the #Fediverse since april 2018!

@hackbyte @eqe @boyter I would assume eqe knows that, but one of the real challenges is it's very hard for an existing community to switch to a different piece of software.

So more than likely, for an existing Mastodon instance, their only choice is to transition to a fork of Mastodon which, at least initially, is database-compatible.

@ocdtrekkie the nice thing about building on a protocol like this is that the cost to switch should be negligible, if you run your own server.

Sure you lose data potentially, but migration scripts can be made. It should be as easy to switch as it was when you could host your own email.