silverpill, 1 month ago to random

FEP-ef61 update, as promised: https://codeberg.org/fediverse/fep/pulls/304

Introducing ap:// URLs

#fep_ef61

silverpill, 1 month ago to random

Changes in my FEP-ef61 implementation: the resolver endpoint was replaced with gateway, and did:ap URLs were replaced with ap:// URLs

https://mitra.social/.well-known/apgateway/did:key:z6MkjtdL1hhAtJDRTti4JZtjGVkMiqbrQWhLQjK8wV4neCvS/actor

Also found a way to use existing URL library to parse ap:// URLs. A massive FEP-ef61 update is coming.

#fep_ef61

silverpill, 1 month ago to random

Recommendations for working with nested signed objects (FEP-8b32):

https://codeberg.org/fediverse/fep/pulls/292/files

FEP-ae97 and FEP-ef61 require embedding signed objects into other signed objects (example: Create activity), but Data Integrity specification doesn't say how to do that correctly.

Looks like we have two options:

1. Use RDF canonicalization instead of JCS, double down on JSON-LD and RDF
2. Use JCS, but break compatibility with some JSON-LD processors

The proposed change represents option 2 (discussion on SocialHub: https://socialhub.activitypub.rocks/t/use-cases-of-fep-8b32-object-integrity-proofs/3249/18).

#fep_ef61