Our friends from the #WillowProtocol have released Ufotofu: an alternative to #RustLang streams, sinks, AsyncRead & AsyncWrite. They rather think of it as producers and consumers. Check it out! It's a very principled and consistent design.
@erlend @cwebber This is actually the one thing that I hadn't figured out how to do on top of the #willowprotocol 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.
For 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 #leafprotocol data format on top of the #willowprotocol and so far it's going really well.
In this post I share some of the concepts and rational behind the Leaf Protocol:
https://zicklag.katharos.group/blog/introducing-leaf-protocol/
@RookieNerd @erlend 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 #willowprotocol, but it might work with other similar options, too ).
I've face similar inter-operability challenges in video game scripting interfaces.
🧵
I've just finished the first draft of the Leaf Protocol!
It's a data layer on top of the #willowprotocol seeking help build a "Web of Data" for the #agenticfediverse.
I'm going to be working on a prototype very soon, built on #iroh for use in the Weird project:
@mauve @silverpill @smallcircles 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 #willowprotocol and nothing more.
Even the serialization format is just #borsh. It's not custom.
We aren't making a totally new protocol, we're describing a more organized way to store data on the #willowprotocol.
Granted the #willowprotocol is new and isn't #activitypub.
@mauve @silverpill @smallcircles #iroh is working on support for the #willowprotocol 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 #rust so that's a big motivation to use Iroh.
@happyborg @silverpill @smallcircles One thing I like about the #willowprotocol 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.
very normal person
iroh
Zicklag