Snub sacrifices backwards compatibility with git. Git is highly evolved tech’ years beyond Nostr.

The goal of GitNestr is to broadcast the Commits, Issues, and Pull Requests of GitHub as #Nostr notes — then store the git folder as a Merkle DAG on relays. The root of the Merkle DAG is signed like a Nostr note, authenticating the repo.

This allows people to pull their repos straight off GitHub and upload it to Nostr relays.

Sacrificing git is a grave mistake given how advanced the technology it is — abandoning git also creates switching costs for users.

Reply to this note

Please Login to reply.

Discussion

Ahh I see it does interface with git actually, but where is the repo stored?

If the repo isn’t decentralized across relays, then how is this censorship resistant?…

it's like i said somewhere - maybe in this thread - it's not got enough thought about the protocol. and like you say, why reinvent the wheel, git just needs a filesystem, and an fs is a much easier thing to make a protocol for.

it is possible to concurrently mutate a git repository, but only when it's a different branch, if the mutations are both on the same node. with that attended to either order of applying the change yields an atomic result.

I've changed the architecture of snub but haven't updated the readme. Other projects more important at the moment.

👍