New

GitHub

GitHub - fiatjaf/nak: a command line tool for doing all things nostr

a command line tool for doing all things nostr. Contribute to fiatjaf/nak development by creating an account on GitHub.

release (v0.17.0) has: - `nak git` commands that allow cloning, setting up a new nip34/grasp repository, pushing, fetching and pulling (just call "nak git push", for example, instead of "git push") - `nak req --only-missing` flag that takes a jsonl file with events and does negentropy with a target relay to only download the events that are not in that file (finally @Kieran -- this was ready 2 weeks ago, but I had to make a ton of git stuff before I was able to publish it) - `nak serve --negentropy --blossom --grasp` new flags that make hosting these things of servers locally much easier for debugging - you can finally use npubs/nprofiles/nevents/naddrs directly as arguments to `nak event`, `nak req` and others (they will be parsed and included in the event or filter as proper hex)

Finally browsing code from others can be done properly: using a local filesystem with a local editor, not an unsearchable unindexed clanky unscrollable cantshowthisfilebecauseitistoobig laggy githubby garbage browser UI. View quoted note → Also it's incredible how smooth and fast it is. A testament to what our computer experiences could be.

Vibecoding turned open-source software projects into a spam attack vector. Before that you could expect high quality projects from a huge percentage of all apps, so acting on a message like "hey, I made this app, please try" was often a good use of your time. These days there are at least 10x more of such apps, so assuming rationality the default reaction to "hey, I made this app, please try" will eventually become to not even look, or people will only look at apps from well-known creators. Considering this it might be that rather than "democratizing" the creation of software vibecoding made it harder for a newcomer without reputation or reach to get their app in front of the eyes of others.

New website for nostr-web-components, now with simpler usage instructions and live demos for each component:

Nostr Web Components - Documentation

I forgot to add a caching layer and

nostr.wine Relay

The most reliable paid relay on nostr.

was ratelimiting me, but now it should be working fine. You can even use crazy filters if you want. View quoted note →

Here's a relay for the people who love a little bit of global "trending" notes: wss://trending.relays.land/ No need for a custom HTTP integration and is immediately usable if your client can view relay feeds, like Jumble, Yakihonne, Nosotros, Nostur and others. It is based on the

nostr.wine Relay

The most reliable paid relay on nostr.

trending API (could also be based on the https://nostr.band/ trending API, but that one is currently down) until @Mazin doesn't expose it in a relay interface himself.

@DanConwayDev my "nak git push" command (that I just made) was able to successfully push to relay.ngit.dev and gitnostr.com yesterday, but now when calling "git push" directly (nak calls it underneath) it fails with "fatal: unable to access 'https://relay.ngit.dev/npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/nostrlib.git/': The requested URL returned error: 500". ngit is still unable to push. Did you abandon this issue entirely or are you cooking something? How can I help you more?