Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://furry.engineer/users/soatok/statuses/115808824039697697">Soatok Dreamseeker (soatok@furry.engineer)'s status on Tuesday, 30-Dec-2025 22:47:10 JST</a><a href="https://furry.engineer/@soatok" title="soatok@furry.engineer"><img src="https://gnusocial.jp/avatar/34725-48-20230823231406.webp" width="48" height="48" alt="Soatok Dreamseeker" style="position: absolute; left: 0; top: 0;">Soatok Dreamseeker</a><div><a href="https://fosstodon.org/@pemensik/115808818905030742" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://fosstodon.org/@pemensik" rel="nofollow">@pemensik</a> </p><p>wouldn't it be enough to propose RFC for secure email handling by email clients?</p><p>No. The problems with encrypted email are unsolvable by RFCs.</p><p>Creating completely new protocol might hit problems solved already in existing protocols.</p><p>This is why <a href="https://github.com/soatok/awoo-specification" rel="nofollow">https://github.com/soatok/awoo-specification</a> is still an empty repo: It's work I planned to do after I solved key transparency for Fedi and E2EE happens.</p><p>For example user friendly, decentralized key distribution has no great solution, if it should be secure at the same time?</p><p>Literally, <a href="https://soatok.blog/2025/12/15/announcing-key-transparency-fediverse/" rel="nofollow">https://soatok.blog/2025/12/15/announcing-key-transparency-fediverse/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/6005024#notice-11816738">In conversation</a><time datetime="2025-12-30T22:47:10+09:00" title="Tuesday, 30-Dec-2025 22:47:10 JST">about 6 months ago</time> <span>from <span><a href="https://furry.engineer/@soatok/115808824039697697" rel="external" title="Sent from furry.engineer via ActivityPub">furry.engineer</a></span></span><a href="https://furry.engineer/@soatok/115808824039697697">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: soatok.blog</div><h5><a href="https://soatok.blog/2025/12/15/announcing-key-transparency-fediverse/">Announcing Key Transparency for the Fediverse</a></h5><div> from <span>Soatok</span></div></header><div>I’m pleased to announce the immediate availability of a reference implementation for the Public Key Directory server. This software implements the Key Transparency specification I’ve be…</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/soatok/awoo-specification">soatok/awoo-specification</a></h5><div></div></header><div>Asynchronous Web Opaque Objects. Contribute to soatok/awoo-specification development by creating an account on GitHub.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Soatok Dreamseeker (soatok@furry.engineer)'s status on Tuesday, 30-Dec-2025 22:47:10 JSTSoatok Dreamseeker
in reply to
- Petr Menšík :fedora:
@pemensik
wouldn't it be enough to propose RFC for secure email handling by email clients?
No. The problems with encrypted email are unsolvable by RFCs.
Creating completely new protocol might hit problems solved already in existing protocols.
This is why https://github.com/soatok/awoo-specification is still an empty repo: It's work I planned to do after I solved key transparency for Fedi and E2EE happens.
For example user friendly, decentralized key distribution has no great solution, if it should be secure at the same time?
Literally, https://soatok.blog/2025/12/15/announcing-key-transparency-fediverse/
In conversationabout 6 months ago from furry.engineerpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: soatok.blog
  Announcing Key Transparency for the Fediverse
  from Soatok
  I’m pleased to announce the immediate availability of a reference implementation for the Public Key Directory server. This software implements the Key Transparency specification I’ve be…
2. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  soatok/awoo-specification
  Asynchronous Web Opaque Objects. Contribute to soatok/awoo-specification development by creating an account on GitHub.