They have a16z. We have f7z.
We are on the winning team.
GN
Listening to the conversation of nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgmwaehxw309aex2mrp0yhxy6t5vdhkjmnsv9exktnrdaksz8rhwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdaks9hhj2c and nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt at #nostriga
Bangers!
Nostr does not need a marketing department because real people using it will drive adoption.
Until we don't even realize we are using nostr.
We will just login with the same identity in every app and that's gonna be normal. And we will talk about the old days when things were quite rough around the edges and many of us still used legacy "unsigned and unrelayed" web apps.
On second thought nip51 might be an overkill. We have to fundamentally rely on ppl not deleting their kind 10002 relays from the whole network.
If you have those redundantly disseminated then you just query those and then the announcement events for repos, wallets, blossom servers etc. with the relay hints if applicable.
Guess we could argue to also have this for nutsack wallets, DM-s and others?
Or just use nip51
I announced SatShoot with #ngit as a nip34 repo and pushed the code to Gitworkshop.dev .
The feeling of freedom from github is indescribable.
Thanks to nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd for making this possible. I encourage every nostr dev to do the same!
That's great to hear!
So you're familiar with nix.
This is the way :)
The best would be to package ngit and git-remote-nostr with nix and publish it to github. [Hydra](https://github.com/NixOS/hydra) can help with CI too.
This way it will be available on nixos.org and easily searchable and be included in a nix config.
Also publishing something nix-bitcoin does like a configurable, modularized template helps a lot. It's a lot of work though.
My lord it's fixed!
Thanks for the hints!
Actually what was wrong is that I added git-remote-nostr to path with a tilde like
'~/.cargo/bin'
What worked was
'$HOME/.cargo/bin'
I don't actually know why but in the shell everything seemed fine I could invoke the command but git could not access it the first way.
I'll zap your Offer in SatShoot!
Thanks for the help amd for your great project!
I feel blessed!
You might be right... I setup the binary cargo installed in the devshell flake not in the configuration.nix where the git package is defined on the nixOS level.
Let me try sth and update you with result. Then if it doesn't help I'll share my nix setup!
Done. No success yet :/
Same error:
```
git: 'remote-nostr' is not a git command. See git --help'.
```
Reading the [git-scm docs](https://git-scm.com/docs/gitremote-helpers) it says sth about
"git remote-
I guess that should be the mechanism git-remote-nostr is using but I haven’t checked your code.
If I try to invoke the binary cargo installed it is auto-completed and in its place on my PATH.
Could not say what I'm doing wrong :(
Thanks will try as soon as I get home!
nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd I'm tagging from amethyst, SatShoot tagging still needs some work it seems :)
Hey Nostr and npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr !
Please help me with this issue and I can pay sats for your time:
## Native git commands failing with git-remote-nostr
I was able to make ngit work and the SatShoot repo was pushed to Gitworkshop.dev.
However, when I try to use git fetch or push or clone native commands with the remote that is configured with the nostr:// URL, git complains with "git: 'remote-nostr' is not a git command. See 'git --help'. " error message.
Other details:
- I installed ngit and git-remote-nostr with cargo and they are recognized on $PATH
- I am using a nix devshell setup with the 'GIT_REMOTE_HELPERS' env variable exported correctly with the 'nostr' string added next to other built-in transfer protocols.
What could be wrong and how to make this work?
Make an offer on this URL:
#satshoot #asknostr #git #ngit #git-remote-nostr #nix_os #nix
I inspected the naddr listed on https://git.fiatjaf.com/nostrapps.com/+/master/ with njump :)
This worked! Huge thanks!
"nostr://npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/nostrapps.com"
Hey nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd I am trying to submit [SatShoot](https://SatShoot.com) to nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8g2lcy6q 's nostrapps.com project via #ngit.
I installed ngit and cloned the repo with fiatjaf's https URL but then set the remote url to nostr://[repo-details] .
Then created my new pr branch and committed my app's details.
The problem is when I try to submit the PR with 'ngit send'. You most likely are not using the relay defined in the repo's 30617 event (wss://git.fiatjaf.com) and the result is:
'Error, no repo events at specified coordinates' .
I am basing this on the fact that I see the relays it tries to fetch the repo event from and neither of them is the correct one.
I am not entirely sure I do everything right but this seems to be the problem. Can you help me out here?
After this I want to push SatShoot with ngit as well.
#asknostr