@stefan frankly I don't think that migrating from URLs to DIDs as identifiers would still qualify as the same protocol in the case of ActivityPub.

So, if ActivityPub is the main component of the Fediverse - which it is for me - I don't think we'll be able to reproduce _all_ the functionality ATProto has.

@_elena @benroyce @mat

@mariusor @stefan @_elena @mat

mastodon was playing around with DIDs at some point

you can find references to it in the documentation (deprecated now for a long time)

example:

https://docs.joinmastodon.org/entities/IdentityProof/

not sure why they abandoned it

maybe because DID just isn't there yet

@benroyce I wasn't speaking of Mastodon because they barely do any effort into being a spec compliant ActivityPub service...

@stefan @_elena @mat

@mariusor @stefan @_elena @mat

not in an effort to start a fight but just divulging my honest views on the topic:

so fucking what

just build shit

the spec can follow behind later

waiting for perfect spec structuring before doing anything is an exercise in inertia

@benroyce maybe you want to look through my post history before giving me advice to build shit. I'm not speaking from a point of ignorance.

The reason why some of us are trying to stick to the specification is to maximize compatibility between implementations. Each project adding their little flavour of functionality before even bothering to have a solid common foundation is detrimental to the health of the ecosystem as a whole.

@stefan @_elena @mat