Nostr Web Client

OK, now I see the reason for the existence of the feature. I guess it's exactly the same for the protocol feature. (/ssh/https/)

For me it feels that this preference of the user belongs to the git config of the user instead of the remote URL.

This way the user could specify his githost-specific settings once in global git config, and use it automatically for new clones, too.

DanConwayDev 1y ago

I can see that argument but some users are very used to setting the protocol in the git url. eg:

```

git remote set-url origin nostr://dan@gitworkshop.dev/identifier

git remote set-url --push origin nostr://nym1@ssh/npub/identifier

````

Reply to this note

Please Login to reply.

Discussion

Lez 1y ago

But in this case the user and protocol doesn't belong to the rest of the URL, it belongs to the invisible underlying clone URL(s).

So when there are multiple underlying URL's, how can we prevent repeated errors on the console, if the username or protocol are different for each clone URL?

I'll tag nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c as I understand he might be using this feature on a daily basis.

DanConwayDev 1y ago

You are right, in that the same protocol (and ssh user) will get used for every git server. I'd be surprised if a different ssh user is used for different git servers thatnhave the same repository.