So good, thanks for doing this!

Hi, I want to know what benefit Nostr is providing here, since Git is inherently designed to work with repos hosted anywhere and already supports cryptographic identities for commit authors. My first and most pressing question is: where are the repos hosted?

In the permissions from the connect request you are sending get_pubic_key instead of get_public_key

Go have a play folks… View quoted note →

Gotta protect chastity.

Congrats on the rewrite! For those shipping Android apps from a NIP-34 repo to @Zapstore What's the current best practice? As far as I can tell `zsp` doesn't auto-detect `nostr://` / gitworkshop URLs yet, so the options seem to be: point `repository:` at the underlying git server (Gitea/Forgejo/Codeberg) or just hand `release_source:` a direct APK URL. Is that the right path? Any plans to make nostr-native repos a first-class source? 👀

Not the repos, but the patches and issues are nostr events. For repos there is GRASP, which use Nostr to check if the push authorized or not, instead of ssh keys in regular git server. So you create a single nostr event called Repository State Announcement, and push your repo to 5 GRASP server, they will not ask you for an account, they will just check that the repo state match the nostr one.

Amazing!

congrats dan!

Give it a try @Pete Sparrow View quoted note →

Nice, thanks for the info, very helpful! I don't currently know anything about Grasp, but I would expect that it handles authentication simply by allowing anyone to upload any commts anywhere, but checking whether branches, tags, and other such labels are authored by authorised persons, depending on the specific repo owner and repo name that those labels are pushed under? If it's done in that way, then forking would be very straightforward as far as backend implementation is concerned: just create a new set of labels pointing to the same commit-ishes/tree-ishes under a different owner name and/or repo name.

🥰🥰🥰🥰Greatfull beyond words 🙏! My $5k trade is now $34k thank you ma’am👇👇👇

Telegram

FX_EVA_DAVID

11+ Years stocks&crypto Trading Guru i Help investors & Traders Earn💰

Rather than authenticating users, GRASP servers reject pushes that don't match the repository state published to nostr. This state is just a list of the git refs ie. a list of branches, tags, etc and the commit id of their tip. The backend is actually really simple, a standard git server with custom authentication. The core of the protocol fits on one page:

gitworkshop - Decentralized Git

Decentralized GitHub alternative over Nostr

I think I'm guilty as charged for having a preference for really small text and low contrast. I should do a review to comply with accessability standards relating to size and contrast.

I created an issue for it nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy2hwumn8ghj7un9d3shjtnwva5hgtnyv4mz7qgnwaehxw309ankjarwdaehgu3wvdhk6tcqyzx428e33rvplprdq9gecku5hv8eez9kj9xwwrmsaxfmpcqcu6stqvltkjv