I have returned, with tea

[cwebber@social.coop]

The infrastructure we build reflects our social dynamics, and our social dynamics are made possible by our infrastructure.

This thread has been long, and I have said everything I have to say. Thanks for listening. I hope we can build a good future for each other.

[damon@social.wedistribute.org]

@serapath Interesting that you come at someone that actually knows the people, politics and technologies on both sides. Also, very interesting to put Mastodon and Nostr in the same sentence as vast majority of Nostr stakeholders would tell you that Mastodon is not in fact decentralised

[erlend@writing.exchange]

@cwebber

> 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

Zicklag (@[email protected])

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: https://blog.muni.town/leaf-atproto-activitypub/

Mastodon (mastodon.social)

[lutindiscret@mastodon.libre-entreprise.com]

@cwebber now refill that cup of tea now and do nostr 🥺

Joke aside, thanks for this thread I think the whole debate is spoiled by the lack of vocabulary, we should stop using "decentralized" and coin some more strictly defined terms

[zicklag@mastodon.social]

@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.

[nextgraph@fosstodon.org]

@zicklag @erlend @cwebber

Erlend and Zicklag, you both know already that @nextgraph is implementing just that (Decentralized identity on top of ~mutable CAS storage) among other things, and will be compatible with ActivityPub thanks to the collab with @activitypods .
So at some point it would be nice to recognise the efforts done by others, specially since I am trying to reach out to everyone in the field and build cooperation and collaboration (and I am mostly ignored so far)

[erlend@writing.exchange]

@nextgraph @zicklag certainly!

Zick is currently in the process of drafting a blog post in response to Christine’s ‘Correct Fediverse’ outline in the context of Leaf.

You’re in a great position to do the same for NextGraph, with the added bonus of being innately AP compatible!

Nomadic Identity is complicated and many separate ventures are saying ‘we do this’. Such statements need to be accompanied with explanations of the flows and trade offs involved, as that makes all the difference.

[fanf42@social.treehouse.systems]

@cwebber I read to the end and e2ee is not touched again (totally OK, the subject massively hard in a decentralized context, and the thread is, hum, not short already).
I suppose you're aware of that, but just in case, and for other readers : @soatok gave himself the challenge to deliver that, up to the federated key management protocol spec : https://soatok.blog/2024/10/12/ambition-the-fediverse-and-technology-freedom/
(Independently from w3c and, it seems, with strong view about how it should be done)

[cwebber@social.coop]

@fanf42 @soatok It's linked in the blogpost!

[dmitri@social.coop]

@cwebber Hey, for what it's worth. @bengo and i are working on exactly that for the Fediverse! We've got the FEPs written, a content-addressed zCap powered storage backend MVPd, and are now working on fedi integrations!