New

GitHub

Release v0.17.2 · fiatjaf/nak

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

with: - `nak gift wrap`: takes an event on stdin and wraps it; - `nak gift unwrap`: the opposite of `nak gift wrap`; - `nak sync`: takes two relay URLs and does a wild negentropy hack to cause both to get synced with each other (let me know how it goes), blame @Alex Gleason if it doesn't work; - many fixes to `nak git`; - `nak nip` lists NIPs, prints them in the terminal or opens them in a browser, courtesy of @npub18373...cgnm. View quoted note →

vnak is now widely available:

GitHub

GitHub - fiatjaf/vnak: visual nostr army knife with qt

visual nostr army knife with qt. Contribute to fiatjaf/vnak development by creating an account on GitHub.

View quoted note → Grab a binary from

GitHub

Release v0.1.0 · fiatjaf/vnak

visual nostr army knife with qt. Contribute to fiatjaf/vnak development by creating an account on GitHub.

and let me know how it goes.

Here's a demo of how you can setup a pyramid relay for you in very few steps: View quoted note →

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.