"starting from your next commit, when you `git push` to a remote that uses your nostr url, it will store your repository state on nostr and update the state of the git server(s) you just listed."
Technical feedback: from nostrudel if I press "open on gitworkshop.dev", it tries to open nevent1qvzqqqqx2ypzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqqs9cv8pajach39wg4dfxj3wz2w50e2mpfqwlykh4cmffec5hfxknngf2ef2k there, which shows an error.
2. I'm fine by doing an MVP, let's not touch the 30317 for now. I think increasing UX is more important here. Especially that by the authorities taking the DNS they achieve nothing a.) it's a news flash for the project b.) somebody trusted will point a new nip05 to the project c.) educating the public it's a dependency d.) still being able to use the npub/naddr remote, which ngit could support out of the box (as all the info is cached in a checked out repo)
2. I called "repo relays" the "relays" tag value in the 30317 event, and "relay hint" the relay in the nostr remote URL, like: nostr://nip05/relay.hint/identifier
How will gitworkshop.dev find out which URL to show in the green "clone" dropdown? (nostr://nip05/relay.hint/identifier, or nostr://nip05/identifier? - or one of the npub / nevent / naddr variant?)
3. Fine, but then we need to add an "identifier: Option" member, too. Because we can't store it anywhere else until we haven't resolved the nip05 to a pubkey.
this is how to access nostrudel, and you bet that sooner or later we are going to have our own naming system protocol and fuck that shit... install some extension and who cares about iana, microsoft, and mozilla inc
Just a reminder, many people on Nostr believe that solving the decentralized naming problem perfectly is impossible - so we should not even try to come up with an almost perfect.
I think we need names, we need to break free of IANA, even if it's imperfect and SOME trust is involved. Handshake.org did it, although there is a shitcoin involved in it. There must be other ways.
Caching the pubkey for the nip05 makes sense. Config is a good place for it.
A couple of questions:
- RepoRef is used to directly map the 30617 event into a rust object?
- Should we add the nostr remote URL into the gitrepo event? It would reflect the choice of the repo owner how he wants to use it. For example, if my nip05 relays intersect with the repo relays, I will omit the relay hint. If they are distinct, I'll include. But it would be easier to just store the URL and use later, than to do the intersection repeatedly. And it's a problem for not cors-enabled nip05s on the web.
- Do you think it would make sense to further refactor the `coordinate` member of `NostrUrlDecoded`? If we could include the Coordinate members (identifier, pubkey, kind, relays) direct members of the `NostrUrlDecoded`, we could change pubkey to Option, and NostrUrlDecoded could hold the URL value after parsing but before looking up NIP05. Also, the duplication of the `identifier` wouldn't be needed. I duplicated that previously because I couln't instantiate Coordinate from a NIP05 nostr:// remote URL.
It's critical to catch it early. Now is the time when you can make it shorter and milder. What I usually do these times is taking Vitamin D and Vitamin A. It helps a lot. If you have the clean form (oily drops), take 50000 of each now, in the evening, and tomorrow morning, 3 times in sum. And take loads (50mg) of zinc, too. Make the room warm. Get better soon!
Végülis igen. Használni, feature-öket requestelni, bugokat reportolni (ehhez még túl korai, van jópár). Azt hallottam, hogy a fejlesztőket motiválja, ha kapnak feedbacket.