"Committed developers, deep knowledge of the code, community outreach, a coherent product vision, and having a designer all go a long way towards making this successful. Making it easy for communities to switch over is important, too."
@deadsuperhero Those are all good points, can I quote them? I'm updating my article, and will also include a quote from and link to your article in the section on "It's not as easy as it sounds"> "For me, a big concern involves trying to run a fork that actively competes with Mastodon, to the point of trying to replace it. This is what I see when people make calls for a hard fork"
That might say more about what you're seeing than what people are saying. The way I phrased it was
"It's worth highlighting that a new hard fork complements the official Mastodon fork, which is likely to remain a better alternative for large, Threads-friendly instances like mastodon.social."