A reply to @cwebber's recent "recipe for the fediverse" and an overview of how we plan on handling identity for Weird on the
#leafprotocol. Just finished a new blog post!
A reply to @cwebber's recent "recipe for the fediverse" and an overview of how we plan on handling identity for Weird on the
#leafprotocol. Just finished a new blog post!
> Decentralized identity on top of ~mutable CAS storage
Is there anything like a spec stub for that somewhere? I think we stand a good chance of checking all these boxes in #leafprotocol by @zicklag
Slowly while working on our #leafprotocol we've realized that it shares a lot of similarities with both #activitypub and #atproto.
We just finished a blog post that explains how Leaf compares with its alternatives:
Curious what thoughts you have on this @zicklag
There’s something quite ‘web of data’ about Hixie’s idea, but you’ve arguably come up with something far more backwards web-compatible in #leafprotocol
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/