Tbh I'm not enthusiastic about a #Mastodon#hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
@:mima_rule: Mima-sama My first thoughts when I read about the hard-fork plans were just this. If you want stuff in the Fediverse that Mastodon doesn't have, why not use something that already has that stuff? After all, my most popular post by far was about just this.
But by reading how @tallship and @The Nexus of Privacy explained their motivation, it looks like this won't be another "Mastodon + xyz" project by people who don't know the Fediverse beyond Mastodon. I mean, @tallship is on Hubzilla himself. @tallship is on Misskey as well. He's on almost everything.
If anything, it's likely that a hard fork will do away with lock-in measures and open what's essentially Mastodon up to the rest of the Fediverse. The idea is to have something that looks like Mastodon and feels like Mastodon and maybe even has Mastodon in its name, but without Mastodon's product politics and without Mastodon's "We're the Fediverse, full stop" attitude.
As first steps, I've already proposed an indicator for the instance type a post came from (Friendica has it, and I think at least one *key has it) and built-in migration on at least Sharkey's level to facilitate moving away from the original woolly mammoth.