@FediTips @FediGarden I mean, here's goblin.technology, run by Tobi who basically started GoToSocial.

https://goblin.technology/

It allows signups. So I'm not sure if that's public or not.

ALL GoToSocial instances require manual review for signups however.

@FediTips @FediGarden Things like Fediverse Observer and FediDB started dropping many GoToSocial instances, after GTS started messing with scrapers ignoring the robots.txt by permitting admins to create ridiculous stats. This messed with the overall stats of the fediverse, so essentially a lot of GTS instances got wholly blacklisted from public directories, regardless of whether they enabled the 'spoof' setting or not.

Which....I guess stopped those places from scraping GTS server endpoints.

Some people are really mad at the authors over it, but all it's really done is take GTS off the official statistics board entirely.

@FediTips @jonny @elduvelle Yeah, it doesn't have to worry about the problems of running thousands on the same instance because it's not really designed for that. Although, if there was a large instance like that, they could just prevent it entirely by turning off backdated post imports at the server level in the config yaml.

It's not so much that it can't handle large volume or large amounts of members migrating posts.... it probably can?

It's just that no one has ever tested it. I'm not aware of anything I'd consider a "large" GTS instance, for one. I'm not aware of anyone with, say, 20k followers migrating to a GTS instance, or importing a massive archive to it.

@FediTips @jonny @elduvelle

This is a solved problem with GoToSocial.

First, they allowed backdating statuses.

Which allowed importing old statuses.

One of the devs created a tool, Slurp, for this purpose. It uses your existing Mastodon archive.

At this time, GoToSocial is the only platform I'm aware of that can handle not just account migration, but post migration as well.

This page talks about migrating to GoToSocial and using Slurp to migrate posts.