Why Nostr? What is Njump?
2024-06-27 19:22:57
in reply to

ManiMe on Nostr: > “because it avoids creating yet another isolated patch of weeds” Pitching in to ...

> “because it avoids creating yet another isolated patch of weeds”

Pitching in to existing projects actually brings MORE people into MORE and different and DEEPER weed patches BECAUSE each project has their “own way” to see the “problem” and to implement a “solution”.

Code repos are ALL about implementation. There is ZERO room in a repo to back out and discuss the bigger problem BECAUSE it only ends up in YA issue, pr delegation, forked project, or abandoned #wontfix thread.

ALSO, because these siloed “repo discussions” are all happening on GitHub, then there’s even less opportunity for the rest of Nostr to contribute to maybe keeping them alive and connecting dots for us developers who ARE “in the weeds”.

may be onto something when she pitches bringing these repo convos into Nostr. This may help, but still … we need time and space for dev realignment. Nostr doesn’t have this.
If you want to clone a git repo, just use 'git clone'. Also, pulling and pushing to origin is still over git, not ngit.

You make a local commit and type 'ngit send' and it sends that commit (you can select multiple commits) to the relays as a proposal linked to the repo event.
Anyone else can comment on it and then anyone can pull it into their local clone and then merge it to origin (if they have access to origin). You can also have the commits in branches.

init is like this
Author Public Key
npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn