Replying to Avatar daniele

I'm cooking something for nostr:nprofile1qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6vuxagm

Hey git loversdev, does this make any sense to you?

#nostrdesign #dev

Avatar
DanConwayDev 1y ago

I liked this so much I have already implemented some of it.

Just need a `search` and clone command in ngit.

Reply to this note

Please Login to reply.

Discussion

Avatar
daniele 1y ago

I'm thinking if the clone command make really sense. We can force it via the search workflow, so the user can double check the repo trustworthiness (via the mantainer npub + WoT indicator).

This should avoid easy fraud attempts using well known names.

Avatar
DanConwayDev 1y ago

I like it. We could even force it via `git clone nostr://amethyst` with a git remote-helper.

Avatar
daniele 1y ago

But this also exposes to scams.

Adding a NIP-05 to the mix could solve the problem, but a good format is not easy to spot:

nostr://_@vitorpamplona.com@amethyst

?? haha

I would use ngit to search the repos, and let git the usual clone command (or invoke it from the search)

Avatar
DanConwayDev 1y ago

Either `git clone nostr://naddr123...` which clones. Or `git clone nostr://amehtyst` which searches and clones the selected repo.

Avatar
daniele 1y ago

But nostr://amehtyst cannot be unambiguous, so it is open to scams.

The naddr1 is fine.

Avatar
DanConwayDev 1y ago

nostr://amethyst would search for events that have amethyst as an identifier and present the options to the user to decide which one, if any to choose (using description, WoT, etc).

Avatar
daniele 1y ago

Ok, so it would works like I imagined the search command.

Avatar
Laeserin 1y ago

Would rather have search, with results ordered by my WoT.

39
purple.co 1y ago

how about ngit clone naddrs ? this will add an .git folder with just config set to git remote, and use later git pull/fetch/....

39
purple.co 1y ago

I see 2 flows:

1. start with git, and later add ngit / nostr collaboration (init/clone) .

2. start with ngit collaboration (init/clone) and later add git/scm.

In 5-10 years, an AI will read comments / issues / proposals and generate the app and upload to git repo, so, the idea of ngit working independent in the beginning will make sense in the future .

PS: SCM is more than git, ( #fossilscm , #jj, #pijul, #radiclescm, ... )