laantungir/nak
1
0
Fork 0
mirror of https://github.com/fiatjaf/nak.git synced 2025-12-09 09:08:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

reword some things.

Browse Source
This commit is contained in:
fiatjaf
2025-07-05 11:14:29 -03:00
parent b1114766e5
commit fb377f4775
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -174,20 +174,20 @@ listening at [wss://relay.damus.io wss://nos.lol wss://relay.nsecbunker.com]:
bunker: bunker://f59911b561c37c90b01e9e5c2557307380835c83399756f4d62d8167227e420a?relay=wss%3A%2F%2Frelay.damus.io&relay=wss%3A%2F%2Fnos.lol&relay=wss%3A%2F%2Frelay.nsecbunker.com&secret=XuuiMbcLwuwL
```
You can also display a QR code for the bunker URI by adding the `--qrcode` flag:
you can also display a QR code for the bunker URI by adding the `--qrcode` flag:
```shell
~> nak bunker --qrcode --sec ncryptsec1... relay.damus.io
```
### start a bunker that persists its list of authorized keys to disc
### start a bunker that persists its metadata to disc
```shell
~> nak bunker --persist --sec ncryptsec1... relay.nsec.app nos.lol
```
> [!CAUTION]
> When you start a bunker with `--persist` or `--profile`, it will store `--sec` credentials and authorized keys in
> `~/.config/nak/bunker`. If you don't want your private key to be stored in plain text, you can
> when you start a bunker with `--persist` or `--profile`, it will store `--sec` credentials and authorized keys in
> `~/.config/nak/bunker`. if you don't want your private key to be stored in plain text, you can
> [encrypt it with NIP-49](#encrypt-key-with-nip-49) it beforehand.
```shell
@@ -323,4 +323,4 @@ If you want to run nak inside a container (i.e. to run nak as a server, or to av
```shell
docker build -t nak .
docker run nak event
```
```