mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

351K
active users

#willowprotocol

0 posts0 participants0 posts today
Zicklag<p><span class="h-card" translate="no"><a href="https://writing.exchange/@erlend" class="u-url mention">@<span>erlend</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@cwebber" class="u-url mention">@<span>cwebber</span></a></span> This is actually the one thing that I hadn&#39;t figured out how to do on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> yet. but I really want to find a way to do it eventually. I think it&#39;s tricky so we&#39;d need a good protocol / algorithm for it I think.</p><p>Currently we&#39;re just using public keys as identity which can be resolved through domains.</p><p>The rest of it is all stuff we&#39;ve already got or that we&#39;re working on, other than the fact that we aren&#39;t using OCaps exactly because Willow has Meadowcap.</p>
Zicklag<p>For the last several months I&#39;ve been working on making a federated app.</p><p>I just finished migrating it to use the latest iteration of our new <a href="https://mastodon.social/tags/leafprotocol" class="mention hashtag" rel="tag">#<span>leafprotocol</span></a> data format on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> and so far it&#39;s going really well.</p><p>In this post I share some of the concepts and rational behind the Leaf Protocol:</p><p><a href="https://zicklag.katharos.group/blog/introducing-leaf-protocol/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">zicklag.katharos.group/blog/in</span><span class="invisible">troducing-leaf-protocol/</span></a></p><p><a href="https://mastodon.social/tags/fediverse" class="mention hashtag" rel="tag">#<span>fediverse</span></a> <a href="https://mastodon.social/tags/protocol" class="mention hashtag" rel="tag">#<span>protocol</span></a> <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="tag">#<span>iroh</span></a></p>
Zicklag<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@RookieNerd" class="u-url mention">@<span>RookieNerd</span></a></span> <span class="h-card" translate="no"><a href="https://writing.exchange/@erlend" class="u-url mention">@<span>erlend</span></a></span> Excellent post.</p><p>I&#39;m less sure about the third shift &quot;Interfaces become queries&quot;, but it&#39;s just an idea anyway and it&#39;s not bad.</p><p>The direction I&#39;ve taken is to try and start designing a simple entity-component type data model that apps can read and write on top of whatever distribution protocol ( starting with the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a>, but it might work with other similar options, too ).</p><p>I&#39;ve face similar inter-operability challenges in video game scripting interfaces.</p><p>🧵</p>
Zicklag<p>I&#39;ve just finished the first draft of the Leaf Protocol!</p><p><a href="https://github.com/commune-os/agentic-fediverse/blob/4ab05ac7cbbc6f5fed185d051b9293ff2db49219/leaf-protocol-draft.md#leaf-protocol-draft" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/commune-os/agentic-</span><span class="invisible">fediverse/blob/4ab05ac7cbbc6f5fed185d051b9293ff2db49219/leaf-protocol-draft.md#leaf-protocol-draft</span></a></p><p>It&#39;s a data layer on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> seeking help build a &quot;Web of Data&quot; for the <a href="https://mastodon.social/tags/agenticfediverse" class="mention hashtag" rel="tag">#<span>agenticfediverse</span></a>.</p><p>I&#39;m going to be working on a prototype very soon, built on <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="tag">#<span>iroh</span></a> for use in the Weird project:</p><p><a href="https://github.com/commune-os/weird/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">github.com/commune-os/weird/</span><span class="invisible"></span></a></p>
Zicklag<p><span class="h-card" translate="no"><a href="https://mastodon.mauve.moe/@mauve" class="u-url mention">@<span>mauve</span></a></span> <span class="h-card" translate="no"><a href="https://mitra.social/users/silverpill" class="u-url mention">@<span>silverpill</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@smallcircles" class="u-url mention">@<span>smallcircles</span></a></span> Something important that I don&#39;t think I&#39;ve made very clear in my posts so far:</p><p>The &quot;protocol&quot; that I am describing is merely a minimal serialization format and schema standard on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> and nothing more.</p><p>Even the serialization format is just <a href="https://mastodon.social/tags/borsh" class="mention hashtag" rel="tag">#<span>borsh</span></a>. It&#39;s not custom.</p><p>We aren&#39;t making a totally new protocol, we&#39;re describing a more organized way to store data on the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a>.</p><p>Granted the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> is new and isn&#39;t <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="tag">#<span>activitypub</span></a>.</p>
Zicklag<p><span class="h-card" translate="no"><a href="https://mastodon.mauve.moe/@mauve" class="u-url mention">@<span>mauve</span></a></span> <span class="h-card" translate="no"><a href="https://mitra.social/users/silverpill" class="u-url mention">@<span>silverpill</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@smallcircles" class="u-url mention">@<span>smallcircles</span></a></span> <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="tag">#<span>iroh</span></a> is working on support for the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> and because I don&#39;t need meadowcap features just yet, it&#39;s safe enough for me to build on Iroh and just adapt when they come out with the willow update.</p><p>We&#39;re pretty partial to <a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="tag">#<span>rust</span></a> so that&#39;s a big motivation to use Iroh.</p>
Zicklag<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@happyborg" class="u-url mention">@<span>happyborg</span></a></span> <span class="h-card" translate="no"><a href="https://mitra.social/users/silverpill" class="u-url mention">@<span>silverpill</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@smallcircles" class="u-url mention">@<span>smallcircles</span></a></span> One thing I like about the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="tag">#<span>willowprotocol</span></a> is that it doesn&#39;t create an infinitely growing append-only log with a permanent record of every change. Sometimes you want to be able to delete revisions and clean stuff up to save on storage.</p><p>The idea is instead to let you track versions with maybe something like a `Revisions` component that has a list of the immutable entity snapshots of older revisions.</p>