Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.coop/users/bnewbold/statuses/112146650520103588">bryan newbold (bnewbold@social.coop)'s status on Sunday, 24-Mar-2024 05:38:21 JST</a><a href="https://social.coop/@bnewbold" title="bnewbold@social.coop"><img src="https://gnusocial.jp/avatar/97159-48-20230210230859.webp" width="48" height="48" alt="bryan newbold" style="position: absolute; left: 0; top: 0;">bryan newbold</a><div><a href="https://mitra.social/objects/018e574c-de23-e787-3669-b2e09971729c" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/85321" title="silverpill@mitra.social">silverpill</a></li><li><a href="https://gnusocial.jp/user/111327" title="erlend@writing.exchange">Erlend Sogge Heggen</a></li></ul></div></section><article><p><a href="https://mitra.social/users/silverpill">@silverpill</a> <a href="https://writing.exchange/@erlend">@erlend</a> <a href="https://hachyderm.io/@cmdrmoto">@cmdrmoto</a> PLC today works with centralized servers for convenience, but it doesn't have to stay that way. the core of the method is self-certifying identities, and that info could be distributed any number of ways.</p><p>I gave a talk recently about PLC and ways to de-centralize it more while staying backwards compatible (video, transcript, slides):<br><a href="https://fission.codes/blog/fission-tech-talks-bluesky-and-plc/" rel="nofollow noreferrer">https://fission.codes/blog/fission-tech-talks-bluesky-and-plc/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2837944#notice-5674975">In conversation</a><time datetime="2024-03-24T05:38:21+09:00" title="Sunday, 24-Mar-2024 05:38:21 JST">about 8 months ago</time> <span>from <span><a href="https://social.coop/@bnewbold/112146650520103588" rel="external" title="Sent from social.coop via ActivityPub">social.coop</a></span></span><a href="https://social.coop/@bnewbold/112146650520103588">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: fission.codes</div><h5><a href="https://fission.codes/blog/fission-tech-talks-bluesky-and-plc/">Fission Tech Talks: Bluesky and PLC – Fission</a></h5><div> from <span>https://ghost.fission.codes/</span></div></header><div>Bryan Newbold, protocol engineer for Bluesky, joins us to discuss DID PLC, a self-authenticating decentralized identifier that is key to account portability on the Bluesky social network.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
bryan newbold (bnewbold@social.coop)'s status on Sunday, 24-Mar-2024 05:38:21 JSTbryan newbold
in reply to
@silverpill @erlend @cmdrmoto PLC today works with centralized servers for convenience, but it doesn't have to stay that way. the core of the method is self-certifying identities, and that info could be distributed any number of ways.
I gave a talk recently about PLC and ways to de-centralize it more while staying backwards compatible (video, transcript, slides):
https://fission.codes/blog/fission-tech-talks-bluesky-and-plc/
In conversationabout 8 months ago from social.cooppermalink
Attachments
1. Domain not in remote thumbnail source whitelist: fission.codes
  Fission Tech Talks: Bluesky and PLC – Fission
  from https://ghost.fission.codes/
  Bryan Newbold, protocol engineer for Bluesky, joins us to discuss DID PLC, a self-authenticating decentralized identifier that is key to account portability on the Bluesky social network.

Public

Embed Notice

HTML Code

Corresponding Notice