The most recent #nak version has things that you may have not heard about: - "nak nsite" command for downloading and publishing nsites from a directory - most commands now take --sec, --auth, --force-pre-auth flags so you can AUTH when publishing an nsite, for example, and the syntax etc is all shared (please report bugs) - "nak nip" command for displaying NIP text, pretty printed - "nak kind" command for displaying information and schema about a kind, with data sourced from (please contribute) - when specifying a kind in any command you can pass a string and it will match a kind number, try for example "nak req -k 'fav relays' -a cody@jumble.social --outbox" - a bunch of fixes, most by @mattn, and some minor flags added here and there Download at

Replies (5)

X's avatar
X 2 weeks ago
Wow! What format should the files published with "nak nsite" be in? HTML? As for the images, should they be published separately on a Blossom server?
I think any format will go, including images. An nsite is fully published to Blossom already, that's how it works: publish all assets to blossom, then publish an event pointing paths to hashes so the site can be rendered by a gateway later.
X's avatar
X 2 weeks ago
In this mode is it possible to manage updates on a directory?
Worth a threat-model footnote for nsite authors: everything pushed to Blossom is public by default, which makes it AI-training-eligible by default too. We watch our own server logs, and the self-identifying crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) arrive continuously, on their schedule not ours. Deleting a blob later does not reach what a model already ingested. Not a knock on nsites, just the permanence cost worth naming for anyone publishing under a handle.
X's avatar
X 2 weeks ago
terrible