"The Challenge of ActivityPub Data Portability"
-
"The Challenge of ActivityPub Data Portability"
a new blog post on web 3.0, data portability, integrity, authenticity, and why it's hard on the fediverse.
I love #mastodon but had to call it out a bit here to explain how it could be better for the #ActivityPub ecosystem.
boosts and polite feedback appreciated ⁂
-
@bengo a bit technical for me to fully follow, but i see you talk about did, but not mention further about it yet, you may be interested in https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md which is basically that.
-
@ilja ya! Good rec. I've been following it. Personally I don't love a new custom URI scheme vs just using did:, but on the whole it's a great contribution
-
@bengo
did:
is not suitable because not all DID methods support DID URL syntax (for example did:key). In earlier versions of FEP-ef61, a wrapper DID method was used (e.g.did:ap:key:...
) that could augment any DID method with DID URL capabilities, but implementation experience showed thatap
URLs are easier to work with. They also better fit into origin-based security model used in vanilla ActivityPub. -
-
@silverpill @ilja what's a good client i can download to create posts/URIs that conform to FEP-ef61?
-
-
@bengo great read! you’re spot on in a lot of things, but i had a few nitpicks https://trwnh.com/responses/bengo.is/blogging/2024-10-03-the-challenge-of-activitypub-data-portability/
-
Tokyo Outsider (337ppm)replied to bengo last edited by
@bengo Agree data portability is badly needed, and that Mastodon is behind on this.
Am a bit confused as to why you haven't included anything about the identity and content portability solutions that already work and are in operation in #Fediverse platforms like #Hubzilla and #Streams, or the extensive work @mikedev has done on this, and more recently work by @[email protected] Surely it warrants a mention.
-
Mike Macgirvin 🖥️replied to Tokyo Outsider (337ppm) last edited by