Just a test...
Dynamic screen and string formatting based on screen resolution finished 😁 A day of testing tomorrow on both devices and then I have another PR waiting for nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt 🤣 #nostr #nsd nostr:note1xn08udt49a2689r4xp9hn4g7ce6lkq5nh2cfg6aah0wtmf6lnc5q5u6yzz
Ok… I did it… 🙄 No fires so far… 🤣 nostr:note1u5t75awjhrhxfsv3um4qdvuhru7rlstmlt83th4rxdm4e99ltugsujlzmk
Sounds like a scientific decision I could get on board with 😁
Would like to us my daily driver, but always worried that someone I start using may mess it up one day. 🤣
Anyone using 0xChat? 🤔 Are you using the daily npub or do you have a separate one for chat? #asknostr #0xchat
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr added a new commit to my PR this morning with a few bits for you 😁
Support for the LilyGo T-Display-S3 coming soon too. Just need to sort dynamic calculation of menu items and max string length. 😁👍 
Made a few changes based on user feedback. Including only using hex on commands not bech32, supporting key switching via serial, key naming and a few updates to the config tool.
Also fixed a bug around not returning to the logo screen correctly when the device goes idle. 👍
Interesting sky 🤔 
There’s a cult on Nostr that only zaps nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m and a few other high-profile people. You’d never see them zapping 3k sats to a regular pleb regardless of the quality of their posts. I call them the “ass-licking zappers”.
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m once zapped me 1337 sats
All internal on the device just works with hex, ui uses a format function to present in bech32 on the screen. I’ll amend the commands to use hex only.
nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt do you want me to wait until the existing PR is reviewed or raise a commit on the current to tweak this?
Amended the code to only use hex on commands (list key, encrypt, decrypt etc), also updated the config tool to include all new commands and parameters.
Will commit once nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt lets me know how I should manage it with the existing PR 👍
Thanks for the feedback, appreciated.
also another idea I just had, would be really cool for users to be able to set a name on the account
Yeah I did consider this, will add a /set-name command to change the name of a key index in the next release. 👍
All internal on the device just works with hex, ui uses a format function to present in bech32 on the screen. I’ll amend the commands to use hex only.
nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt do you want me to wait until the existing PR is reviewed or raise a commit on the current to tweak this?
Seeing lots of zap pings in #damus but only a couple on #albyhub … very odd 🤔
I was thinking mainly from a user experience point of view as most clients use npub etc, knowing which key is which hex could become a bit of a faff so switching keys in the format they’re used to would make sense. Easy tweak though 👍
Send it the pubkey of the 3rd party you want to send to and the message you want to send and it’ll encrypt on device. Same for the reverse with decrypt. So yeah, on device NIP-04.