"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.
https://bengo.is/blogging/2024-10-03-the-challenge-of-activitypub-data-portability/
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 ⁂
@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 that ap
URLs are easier to work with. They also better fit into origin-based security model used in vanilla ActivityPub.
@silverpill @ilja Yes, and FEP-ef61 is not the only way of doing that. You'll notice I don't mention *any* FEPs in here. The point was to describe the problem, not any solutions other than what was already in the ActivityPub CR in 2017, which is to use what became DataIntegrityProofs.
I think it's cool that FEP-ef61 uses W3C DataIntegrityProofs. gj
@silverpill @ilja what's a good client i can download to create posts/URIs that conform to FEP-ef61?
@silverpill @ilja @mikedev nice. I tried out the client and created a user woot.