There are no instances in ActivityPub either. There's only actors.

The instance'ification came outside of the work on the spec, though it did start with the particular shape of how sharedInbox was defined. I wish I had pushed harder for sharedInbox to retain the actor-like properties I believed were important, rather than the implicit-routing that Mastodon pushed for. My biggest regret.

Nonetheless, even then, there's still no "instance" in AP, in terms of the spec. In terms of the fediverse, the way it became, that's a different story.

That said, "instance" has become several things on the fediverse, and even though it's not how I have argued things should be, it encompasses several things, including often a kind of community, and also including participatory infrastructure.

I'm not interested in playing the comparison game too much, but there is where we are: ATproto allows for movement across the network, but still does rely on server-oriented sources of authority (and looks like it will get more of it in the upcoming versions of their authorization systems, from what I have read), and the fediverse has developed into a strong sense of server-oriented sources of authority, but is more participatory.

Directed delivery remains an important part of how the fediverse manages to achieve participatory involvement that is still lacking from the ATmosphere's hub-and-spoke-in-practice ecosystem at present. It is how you scale down and wide.

Both could learn from each other, though. Even combined is not the full answer.

Overall I remain *mostly* disinterested in the fediverse-vs-atmosphere debates, because I am not interested in squabbles over the present but building towards a future. It's hard not to make a bit of side commentary though, I guess.