Some new #nak features since the last time I mentioned new f...

3bf0c63fcb934634...

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

hex

c8524387d6076edd7238a7b910f153c4383f95828d67e9ec39fcea06b26bbef7

nevent

nevent1qqsvs5jrsltqwmkawgu20wgs79fugwpljkpg6elfasule6sxkf4maacprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gvam94n

Kind-1 (TextNote)

2026-08-18T00:15:17Z

Some new #nak features since the last time I mentioned new features:

  • nak git ls [subdir]: lists files in remote repositories (without cloning).
  • nak git cat : prints a file content (idem).
  • nak git history: lists commits for a remote repository (idem).
  • nak git pr: opens new NIP-34 pull requests or browses open pull requests.
  • nak serve: supports --auth flag for requiring a useless AUTH from everybody (any pubkey will be accepted, it's just for testing stuff) .
  • nak req/fetch/event commands support a --jq flag that can be used for very crazy oneliners in computers that don't have jq installed (scripts run inside --jq can access a bunch of special helper functions for reading tags, parsing dates etc).
  • nak admin: supports NIP-43 roles.
  • nak publish: works better, can read from stdin, supports kind:1111 comments.
  • nak group: support NIP-29 subgroups.
  • nak group chat: streams chat with parsed nostr:... entities turned into usernames, other links and hashtags colored differently.
  • nak bunker: always display bunker information at the bottom, courtesy of nostr:npub1u035wtfjf9h79r94srwljmekwrczhyq9a2760a23dpeh2ulgh09s08njfd.
  • nak fetch and nak group: support NIP-AD web addresses (NIP-05 of things).
  • dozens of fixes from nostr:npub1937vv2nf06360qn9y8el6d8sevnndy7tuh5nzre4gj05xc32tnwqauhaj6.
  • no more hardcoded key "01" for everybody, now each computer gets a supposedly unique key based on some CPU number (do not use this as your real key, it's only for testing)(it can be bypassed with the $NOSTR_SECRET_KEY environment variable, as always).
  • same for the default bunker client key (for when you pass a bunker URI to --sec in any command).

原始 JSON

{
  "kind": 1,
  "id": "c8524387d6076edd7238a7b910f153c4383f95828d67e9ec39fcea06b26bbef7",
  "pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
  "created_at": 1787012117,
  "tags": [
    [
      "t",
      "nak"
    ],
    [
      "p",
      "e3e3472d32496fe28cb580ddf96f3670f02b9005eabda7f55168737573e8bbcb"
    ],
    [
      "p",
      "2c7cc62a697ea3a7826521f3fd34f0cb273693cbe5e9310f35449f43622a5cdc"
    ]
  ],
  "content": "Some new #nak features since the last time I mentioned new features:\n\n- nak git ls [subdir]: lists files in remote repositories (without cloning).\n- nak git cat \u003cpath\u003e: prints a file content (idem).\n- nak git history: lists commits for a remote repository (idem).\n- nak git pr: opens new NIP-34 pull requests or browses open pull requests.\n- nak serve: supports --auth flag for requiring a useless AUTH from everybody (any pubkey will be accepted, it's just for testing stuff) .\n- nak req/fetch/event commands support a --jq flag that can be used for very crazy oneliners in computers that don't have jq installed (scripts run inside --jq can access a bunch of special helper functions for reading tags, parsing dates etc).\n- nak admin: supports NIP-43 roles.\n- nak publish: works better, can read from stdin, supports kind:1111 comments.\n- nak group: support NIP-29 subgroups.\n- nak group chat: streams chat with parsed nostr:... entities turned into usernames, other links and hashtags colored differently.\n- nak bunker: always display bunker information at the bottom, courtesy of nostr:npub1u035wtfjf9h79r94srwljmekwrczhyq9a2760a23dpeh2ulgh09s08njfd.\n- nak fetch and nak group: support NIP-AD web addresses (NIP-05 of things).\n- dozens of fixes from nostr:npub1937vv2nf06360qn9y8el6d8sevnndy7tuh5nzre4gj05xc32tnwqauhaj6.\n- no more hardcoded key \"01\" for everybody, now each computer gets a supposedly unique key based on some CPU number (do not use this as your real key, it's only for testing)(it can be bypassed with the $NOSTR_SECRET_KEY environment variable, as always).\n- same for the default bunker client key (for when you pass a bunker URI to --sec in any command).",
  "sig": "853e0ec94b692e421fc44c73932c180df97e45dd671fd9289c8ec622308a2872276b1932a087f52eadc826b45a3548288789658337674450a2fd02d28bb1f37e"
}