Conversation

Notices

1. Raphael Lullis (raphael@mastodon.communick.com)'s status on Friday, 17-May-2024 22:14:42 JST Raphael Lullis

   From the W3C spec: all objects distributed by the ActivityPub protocol MUST have unique global identifiers (...) must fall into one of the following groups:

   - Publicly dereferencable URIs, such as HTTPS URIs, with their authority belonging to that of their originating server. (Publicly facing content SHOULD use HTTPS URIs).
   - null

   Does this mean an Actor ID can be resolvable through some protocol other than http? E.g, DNS?

   • silverpill (silverpill@mitra.social)'s status on Friday, 17-May-2024 22:14:41 JST silverpill

     in reply to

     @raphael Yes, that's correct.

     The proposed data portability extension is based on a liberal interpretation of this part of the spec.

     https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

     It defines a new URL type where "authority" part is a DID, not a DNS name:

     ap://did:example:123456/path/to/object?name=value#key-id
   • silverpill (silverpill@mitra.social)'s status on Friday, 17-May-2024 23:04:29 JST silverpill

     in reply to

     @raphael Regarding your other post,

     >...a different approach for ActivityPub software, putting the client at the center of everything and making the servers just specialized relays of ActivityStream messages

     This is possible with FEP-ef61. Portable messages are self-authenticating, so it doesn't matter where they are generated, on the server or on the client.

     However, I think the traditional (server-centered) approach also has its merits. There is a place for both in Fediverse

     https://mastodon.communick.com/users/raphael/statuses/112453788068689232