Skip to content

Comment on Gitworkshop.dev – Collaborate on code over Nostrparent

Comments

Both technologies (cryptocurrency and nostr) are very cipherpunk—I'm not particularly surprised that they draw overlapping crowds.

Another take on decentralized source control with more of an emphasis on "federated" and less of one on "censorship resistant": https://tangled.org/

To me ATProto has not proven yet to be really distributed / decentralized. In terms of "censorship resistant" you can also think of a 100% uptime of your code / work (your repository). Or always available for anyone with a internet connection. In the context of a federated network (aka fediverse), that's often not the case (if a federated instance is unavailable, many assets will be missing leading to a unuseable application or service).

Thx for sharing, didn't know that one.

After reading https://radicle.xyz/guides/protocol my first impression it's the same as how it works with Nostr with one key difference in the conceptual model. Nostr uses relays to distribute the data and Radicle is using a gossip model to distribute the data peer-to-peer (the bittorrent model).

They do explain the difference with a federated model. I miss the explainer compared to a relay model.

So regarding the peer-to-peer modal, here are some thoughts: How IPFS is broken: https://fiatjaf.com/d5031e5b.html Why IPFS cannot work, again: https://fiatjaf.com/b8e2f959.html

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.