Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.online/users/laurin/statuses/112156384940234671">Laurin (laurin@mastodon.online)'s status on Monday, 25-Mar-2024 22:57:38 JST</a><a href="https://mastodon.online/@laurin" title="laurin@mastodon.online"><img src="https://gnusocial.jp/avatar/251770-48-20240325135738.webp" width="48" height="48" alt="Laurin" style="position: absolute; left: 0; top: 0;">Laurin</a><div><ul><li><li><a href="https://gnusocial.jp/user/85321" title="silverpill@mitra.social">silverpill</a></li><li><a href="https://gnusocial.jp/user/91788" title="steve@social.technoetic.com">Steve Bate</a></li><li><a href="https://gnusocial.jp/user/238890" title="fentiger@zotum.net">FenTiger</a></li></ul></div></section><article><p><a href="https://social.technoetic.com/@steve">@steve</a> <a href="https://mymath.rocks/timeline/">@helge</a> <a href="https://zotum.net/channel/fentiger">@fentiger</a> <a href="https://social.coop/@smallcircles">@smallcircles</a> </p><p>Why is the client-side signing FEP (<a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md" rel="nofollow noreferrer">https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md</a>) using the jcs and not the rdfc crypto suite (<a href="https://www.w3.org/TR/vc-di-eddsa/#eddsa-rdfc-2022" rel="nofollow noreferrer">https://www.w3.org/TR/vc-di-eddsa/#eddsa-rdfc-2022</a>)?<br>This would solve the whole problem I suppose, since it will convert the activity to rdf, to sign.</p><p><a href="https://mitra.social/users/silverpill">@silverpill</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2862615#notice-5686174">In conversation</a><time datetime="2024-03-25T22:57:38+09:00" title="Monday, 25-Mar-2024 22:57:38 JST">about 10 months ago</time> <span>from <span><a href="https://mastodon.online/@laurin/112156384940234671" rel="external" title="Sent from mastodon.online via ActivityPub">mastodon.online</a></span></span><a href="https://mastodon.online/@laurin/112156384940234671">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: codeberg.org</div><h5><a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md">fep</a></h5><div> from <span>fediverse</span></div></header><div>Fediverse Enhancement Proposals</div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.w3.org/TR/vc-di-eddsa/#eddsa-rdfc-2022">Data Integrity EdDSA Cryptosuites v1.0</a></h5><div></div></header><div>This specification describes a Data Integrity cryptographic suite for use when
creating or verifying a digital signature using the twisted Edwards Curve
Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Laurin (laurin@mastodon.online)'s status on Monday, 25-Mar-2024 22:57:38 JSTLaurin
@steve @helge @fentiger @smallcircles
Why is the client-side signing FEP (https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md) using the jcs and not the rdfc crypto suite (https://www.w3.org/TR/vc-di-eddsa/#eddsa-rdfc-2022)?
This would solve the whole problem I suppose, since it will convert the activity to rdf, to sign.
@silverpill
In conversationabout 10 months ago from mastodon.onlinepermalink
Attachments
1. Domain not in remote thumbnail source whitelist: codeberg.org
  fep
  from fediverse
  Fediverse Enhancement Proposals
2. No result found on File_thumbnail lookup.
  Data Integrity EdDSA Cryptosuites v1.0
  This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).

Public

Embed Notice

HTML Code

Corresponding Notice