@alex @curtis

> Also, a DID needs a resolver that can find information about you based on the DID alone. With the keypair example you're likely hitting MIT's keyserver to try to resolve it, or Keybase or whatever.

I'd argue that's a separate concern. different task. whatever. onion, GNS, DNS, and a keyserver are all different solutions to it

>The good thing about ActivityPub IDs is that you can easily resolve them from the ID alone, since they're URLs.

:02_laugh: nigga please. that's just using an ICANT sanctioned URL and pretending it's suitable as an ID. the "real" ID is the server key. much grief has come of these two things being hopelessly conflated by current AP implementations

> Most other solutions have us depending on centralized servers, or reinventing DNS.

... fedi is hopeless dependent on ICANT DNS at present. if your domain gets pulled what are you going to do?

> IPFS seems like it would work well for this, if it wasn't extremely slow.

exactly, what does DID do that an IPNS record doesn't? that combines keypair with decentralized name resolution. of course tor .onion also do the exact same thing ...