Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/zicklag/statuses/112803984968314577">Zicklag (zicklag@mastodon.social)'s status on Thursday, 18-Jul-2024 07:10:10 JST</a><a href="https://mastodon.social/@zicklag" title="zicklag@mastodon.social"><img src="https://gnusocial.jp/avatar/266139-48-20240620204714.webp" width="48" height="48" alt="Zicklag" style="position: absolute; left: 0; top: 0;">Zicklag</a><div><a href="https://mastodon.social/@zicklag/112803963156027559" 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></ul></div></section><article><p><a href="https://mitra.social/users/silverpill">@silverpill</a> <a href="https://social.coop/@smallcircles">@smallcircles</a> <a href="https://mastodon.social/tags/iroh" rel="tag">#iroh</a> which is implementing the <a href="https://willowprotocol.org/" rel="nofollow noreferrer">https://willowprotocol.org/</a> does all those things I want from a storage, connectivity, and replication standpoint.</p><p>If I were to implement the network that I'm imagining, I think I would probably still need Iroh, even if I supported ActivityPub.</p><p>But instead of supporting ActivityPub immediately, I'm trying to understand the smallest specification that I need to accomplish my goals.</p><p>2/3</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3383950#notice-6669474">In conversation</a><time datetime="2024-07-18T07:10:10+09:00" title="Thursday, 18-Jul-2024 07:10:10 JST">about 4 months ago</time> <span>from <span><a href="https://mastodon.social/@zicklag/112803984968314577" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@zicklag/112803984968314577">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: willowprotocol.org</div><h5><a href="https://willowprotocol.org/">Willow Specifications - Willow</a></h5><div></div></header><div>A protocol for peer-to-peer data stores. The best parts? Fine-grained permissions, a keen approach to privacy, destructive edits, and a dainty bandwidth and memory footprint.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Zicklag (zicklag@mastodon.social)'s status on Thursday, 18-Jul-2024 07:10:10 JSTZicklag
in reply to
- smallcircles (Humanity Now 🕊)
- silverpill
@silverpill @smallcircles #iroh which is implementing the https://willowprotocol.org/ does all those things I want from a storage, connectivity, and replication standpoint.
If I were to implement the network that I'm imagining, I think I would probably still need Iroh, even if I supported ActivityPub.
But instead of supporting ActivityPub immediately, I'm trying to understand the smallest specification that I need to accomplish my goals.
2/3
In conversationabout 4 months ago from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: willowprotocol.org
  Willow Specifications - Willow
  A protocol for peer-to-peer data stores. The best parts? Fine-grained permissions, a keen approach to privacy, destructive edits, and a dainty bandwidth and memory footprint.

Public

Embed Notice

HTML Code

Corresponding Notice