I wish #Mastodon would just implement FEP-8b32 instead of the LD Signatures which is obsolete.

[beaware@social.beaware.live]

@hongminhee they could. Though, with it already being an FEP and possibly directly implemented into AP at some point in the future, they'd just be undermining AP again instead of supporting the protocol that Mastodon is built on.‍️(they could probably do the work for AP directly instead of only for Mastodon)

They don't seem to have a problem doing that, so it might happen!

[julian]

This post is deleted!

[liaizon@social.wake.st]

@hongminhee where did this w3id fep short url come from? first time I am seeing it

[hongminhee@fosstodon.org]

@liaizon I have no idea either, but I learned it from @tesaguri (if I recall correctly).

[saschanaz@sekai.social]

@[email protected] @[email protected] @[email protected] probably coming from https://github.com/perma-id/w3id.org/tree/master/fep

[silverpill@mitra.social]

@saschanaz @liaizon @tesaguri @hongminhee this namespace was proposed in FEP-888d

[julian]

@[email protected] have you implemented it? I'd love to see it, since it's confusing for me. I'd rather take an existing implementation if possible.

[hongminhee@fosstodon.org]

@julian Yes, Fedify implements it. Here's the implementation:

fedify/src/sig/proof.ts at 0.14.4 · fedify-dev/fedify

ActivityPub server framework in TypeScript. Contribute to fedify-dev/fedify development by creating an account on GitHub.

GitHub (github.com)

[silverpill@mitra.social]

@julian @hongminhee What parts of it you find confusing? I can edit the text

[julian]

@[email protected] I don't think much in the FEP is confusing, it's mostly the technical implementation, calculation of proofs, etc.

As I have absolutely zero background in cryptography, I feel like this is one of those "hard problems" that should be outsourced to a common library, and not hand rolled.