I am forever grateful to him for building & popularizing Mastodon, but I don't think @Gargron should be working on features at all right now.

Instead, he and the Mastodon non-profit (and a whole bunch of others) should be figuring out governance for collectively making decisions about Mastodon. Features in the Fediverse shouldn't be up to one guy, or even one company.

That's the whole point of the Fediverse. We do this together, or not at all.

@blaine @Gargron this was already solved.

ActivityPub is a W3C standard and WebFinger is an IETF standard.

I think betting it all on Mastodon is a bigger issue IMO, it's like saying that Chromium should have better governance instead of promoting browser engine diversity.

My only concern right now is the lack of a standardized REST API for clients (preferably something that uses OpenID Connect instead of just OAuth).

@lucid00 @blaine @Gargron Yeah, an API standards process is going to be critical. If all the 3rd party apps target @Gargron's Mastodon API, then that becomes the de-facto standard. Meanwhile, misskey development withers because it has its own incomatible API.

I could imagine something like how XMPP has XEPs to define protocol extensions; some kind of formal process for API modifications where other backends can weigh in.

@Andres4NY @blaine @Gargron

Yeah @tcit just pointed out that ActivityPub has an official client API but almost nothing out uses it.

I completely forgot about it myself for that reason.

Someone at the W3C should look into bringing energy back to that part of the project.