@evan Thanks for your response. @silverpill already mentioned the "main-key" fragment. Is that documented somewhere?

I had an implementation that returned just an object of type "PublicKey" if the "./key" endpoint is called.

I checked what I get back from Mastodon if I call my profile with the "main-key" fragment. The result is the full profile.

So should I either refer to the profile url with the fragment and return the full "Person" OR [...]

[...] use a dedicated url (i.e. mine with an appended ./key) and just return an object of type "PublicKey"?

@evan @silverpill

@achim @silverpill yes, it's documented in my book.

@achim @silverpill I'm rereading the book section on public keys, and it looks good. Do it like that!

@evan I read that section and implemented the preferred version, not the Mastodon one. That did not work, but I might got confused by other mistakes I made. Will give it another try. Thanks for your help!

@silverpill

@achim @silverpill So, here's a minimal example of a key object:

A minimal key object for ActivityPub

A minimal key object for ActivityPub. GitHub Gist: instantly share code, notes, and snippets.

Gist (gist.github.com)

@achim @silverpill And here's the corresponding person object:

A minimal user with a public key

A minimal user with a public key. GitHub Gist: instantly share code, notes, and snippets.

Gist (gist.github.com)

@achim @silverpill Some things to note:

- They have to point to each other
- I think the "publicKey" object in the person has to be an embedded object for Mastodon; it won't accept an URL as the property value.

@achim @silverpill OK. Try the samples I gave!

@achim @evan The fragment ID could be different but it needs to be embedded in your actor document. Here's a JSON schema:

Cookie monster!

(codeberg.org)