Nostr Console v0.3.3-beta: With linux arm64 release, docker images pushed to ghcr.io

0.3.3-beta

• Linux arm64 build added; docker images pushed to github ghcr.io; and improving of build process by @AaronDewes
• added display_name and website field support for reading and updating kind 0 , or profile; now damus profiles won't get messed up if they're edited from Nostr Console.
• color fix - where likes to right of a notification-like were shown in white rather than as colored text

after tag with suffix a

• fix issue so now dm sent to user are saved ( this avoid unnecessary notification of dm sent to user on program startup)

0.3.2-beta

• fixed or improved mention expansion
• displayed global feed. which has all latest in last 2 hours
• in incoming notifications, only showed notifications for follows.
• In writing events, only writing follow's events. and the ones they interact with.
• now friends have a tick; no tick for defaults
• fixed colors issue for notification likes that were shifted to left since last 2 releases
• added build arm 64 for all three desktop platforms Not working right now. Removed attachments. Use this guide to build for arm64.

0.3.1-beta

• added nostr.ch as another default relay to sync with anigma
• printed only 20 maximum events in a thread to reduce screen spam from long threads. Only in search results are all threads printed; and a thread or event can be searched by 6 digit id-prefix of the event thats mentioned.
• improved user notifications , menu 2 -> 3, now likes are shown as notifications
• improved 2 -> 5. better printing. and fixed the issue where later reactions were being printed in white after highlighted reaction
• improved 2 -> 6 too, now follows posts get highlighted, and so do their reactions.
• p tag mentions of user get highlighted in above menus
• if too many wrong menu inputs are given ( >40) then program exits without saving any new events. for issue #49
• showed lud06 and lud16, if any, in profile as qr code

after tagging version 0.3.1-betaa

• improved notification count and display with recent clipped-thread change
• fixed issue where had to go to main menu from SN menu to get notifications ; related: also got notifications in other menus so now on following someone, that event is processed in this menu itself
• added lightning prefix in profile

help and reference

• link to nostr console wiki
• link to discussions

Binaries

All binaries built using Github workflow automatically

• nostr_console_windows_amd64.zip this has a win64 executable file with extension .exe.
• nostr_console_linux_amd64.zip this has a elf file, dynamically linked, built using 'dart compile' on a Ubuntu-latest 64 bit amd64
• • nostr_console_linux_arm64.zip this has a elf file, dynamically linked, built using 'dart compile' on a Ubuntu-latest 64 bit rm64
• nostr_console_macos_amd64.zip has an executable .app file. Needs to be unzipped. Built similarly on macOS

Usage

usage: nostr_console [OPTIONS] 

  OPTIONS

      -p, --pubkey  <public key>    The hex public key of user whose events and feed are shown. Default is a hard-coded
                                    public key derived from a well known private key. When given, posts/replies can't be sent. 
      -k, --prikey  <private key>   The hex private key of user whose events and feed are shown. Also used to sign events 
                                    sent. Default is same-as-above hard-coded well known private key. 
      -r, --relay   <relay wss url> The relay url that is used as main relay. Default is wss://nostr-relay.untethr.me.
      -d, --days    <N as num>      The latest number of days for which events are shown. Default is 1.
      -q, --request <REQ string>    This request is sent verbatim to the default relay. It can be used to recieve all events
                                    from a relay. If not provided, then events for default or given user are shown.
      -f, --file    <filename>      Read from given file, if it is present, and at the end of the program execution, write
                                    to it all the events (including the ones read, and any new received).
      -s, --disable-file            When turned on, even the default file is not read from.
      -t, --translate               Translate some of the recent posts using Google translate site ( and not api). Google 
                                    is accessed for any translation request only if this flag is present, and not otherwise.
      -l, --lnqr                    If set any LN invoices starting with LNBC will be printed as a QR code. Will set 
                                    width to 140, which can be reset if needed with the --width argument. Wider space is 
                                    needed for some qr codes.
      -g, --location               The given value is added as a 'location' tag with every kind 1 post made. Shortcut g for
                                    geographic location.
      -h, --help                    Print this usage message and exit.
      -v, --version                 Print version and exit.

      
  UI Options                                
      -a, --align  <left>           When "left" is given as option to this argument, then the text is aligned to left. By default
                                    the posts or text is aligned to the center of the terminal. 
      -w, --width  <width as num>   This specifies how wide you want the text to be, in number of columns. Default is 100. 
                                    Cant be less than 60.
      -m, --maxdepth <depth as num> The maximum depth to which the threads can be displayed. Minimum is 2 and
                                    maximum allowed is 12. 
      -c, --color  <color>          Color option can be green, cyan, white, black, red and blue.

  Advanced
      -y, --difficulty <number>     The difficulty number in bits, only for kind 1 messages. Tne next larger number divisible by 4 is 
                                    taken as difficulty. Can't be more than 24 bits, because otherwise it typically takes too much 
                                    time. Minimum and default is 0, which means no difficulty.
      -e, --overwrite               Will over write the file with all the events that were read from file, and all newly received. Is
                                    useful when the file has to be cleared of old unused events. A backup should be made just in case
                                    of original file before invoking.