mirror of
https://github.com/vishalxl/nostr_console.git
synced 2025-03-27 10:11:49 +01:00
Updated Nostr Console Best Practices (markdown)
parent
98b95d8904
commit
1bde124ab4
@ -1,7 +1,15 @@
|
||||
|
||||
# Introduction to Basic Nostr Console
|
||||
# Introduction to Nostr Console
|
||||
|
||||
The basic flow of the Nostr Console application is the following: You can invoke the application with a --prikey option, giving it your private key. This allows you to use this app as a Nostr client, where you can send events, as well as read them. Relays are hard-coded into the app right now, and multiple relays are used.
|
||||
The simplest way to start nostr console is
|
||||
|
||||
```
|
||||
./nostr_console_exe -k <private key in hex>
|
||||
or
|
||||
./nostr_console_exe --prikey=<private key in hex>
|
||||
```
|
||||
|
||||
Once it starts, the basic flow of the Nostr Console application is the following: Once you invoke the application with a --prikey option, it allows you to use this app as a Nostr client, where you can send events, message etc, as well as read them.
|
||||
|
||||
After you exit the app for the first time ( at end of its first invocation) the app will store all the events it has received in a file in pwd which by default is named "all_nostr_events.txt". The name does not imply that it has ALL nostr events, but only it has all the events that have been received by this client till now.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user