social.coop

0 posts0 participants0 posts today

Zicklag<a href="https://writing.exchange/@erlend" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@erlend</a> <a href="https://social.coop/@cwebber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cwebber</a> This is actually the one thing that I hadn't figured out how to do on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> yet. but I really want to find a way to do it eventually. I think it's tricky so we'd need a good protocol / algorithm for it I think.Currently we're just using public keys as identity which can be resolved through domains.The rest of it is all stuff we've already got or that we're working on, other than the fact that we aren't using OCaps exactly because Willow has Meadowcap.

ZicklagFor the last several months I've been working on making a federated app.I just finished migrating it to use the latest iteration of our new <a href="https://mastodon.social/tags/leafprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#leafprotocol</a> data format on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> and so far it's going really well.In this post I share some of the concepts and rational behind the Leaf Protocol:<a href="https://zicklag.katharos.group/blog/introducing-leaf-protocol/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://zicklag.katharos.group/blog/introducing-leaf-protocol/</a><a href="https://mastodon.social/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://mastodon.social/tags/protocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocol</a> <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iroh</a>

Zicklag<a href="https://hachyderm.io/@RookieNerd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@RookieNerd</a> <a href="https://writing.exchange/@erlend" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@erlend</a> Excellent post.I'm less sure about the third shift "Interfaces become queries", but it's just an idea anyway and it's not bad.The direction I'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="nofollow noopener noreferrer" target="_blank">#willowprotocol</a>, but it might work with other similar options, too ).I've face similar inter-operability challenges in video game scripting interfaces.🧵

ZicklagI've just finished the first draft of the Leaf Protocol!<a href="https://github.com/commune-os/agentic-fediverse/blob/4ab05ac7cbbc6f5fed185d051b9293ff2db49219/leaf-protocol-draft.md#leaf-protocol-draft" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/commune-os/agentic-fediverse/blob/4ab05ac7cbbc6f5fed185d051b9293ff2db49219/leaf-protocol-draft.md#leaf-protocol-draft</a>It's a data layer on top of the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> seeking help build a "Web of Data" for the <a href="https://mastodon.social/tags/agenticfediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agenticfediverse</a>.I'm going to be working on a prototype very soon, built on <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iroh</a> for use in the Weird project:<a href="https://github.com/commune-os/weird/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/commune-os/weird/</a>

Zicklag<a href="https://mastodon.mauve.moe/@mauve" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mauve</a> <a href="https://mitra.social/users/silverpill" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@silverpill</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a> Something important that I don't think I've made very clear in my posts so far:The "protocol" 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="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> and nothing more.Even the serialization format is just <a href="https://mastodon.social/tags/borsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#borsh</a>. It's not custom.We aren't making a totally new protocol, we're describing a more organized way to store data on the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a>.Granted the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> is new and isn't <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#activitypub</a>.

Zicklag<a href="https://mastodon.mauve.moe/@mauve" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mauve</a> <a href="https://mitra.social/users/silverpill" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@silverpill</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a> <a href="https://mastodon.social/tags/iroh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iroh</a> is working on support for the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> and because I don't need meadowcap features just yet, it's safe enough for me to build on Iroh and just adapt when they come out with the willow update.We're pretty partial to <a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> so that's a big motivation to use Iroh.

Zicklag<a href="https://fosstodon.org/@happyborg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@happyborg</a> <a href="https://mitra.social/users/silverpill" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@silverpill</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a> One thing I like about the <a href="https://mastodon.social/tags/willowprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#willowprotocol</a> is that it doesn'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.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.

Recent searches

Search options

Administered by:

Server stats:

#WillowProtocol