save travel.
work can always wait 😉
someone wrote a nice article how you can verify if you can write to a #nostr relay with https://websocketking.com
but I can’t find it anymore 😢
was it #[1] ?
this looks interesting!
i have to check if #[5] is supporting this 🤔
go to a box training you will perhaps change your mind 😉
if you do not have a free mind there, you will feel it 😉
but for sure running is also great.
i’m now a fast zapper in #snort thanks to nwc.
btw great work nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 !
sounds very interesting! I have no business and i‘m also not a heavy user of lightning payments… but if you need some one to test it, i can do it if you like.
GM 🥱
#sunday #zoo
if you use #[2], you can long press on the ⚡️ icon then comes a quick selector up.
oh i forgot to mention something. there is also a copy&paste typo in the example docker-compose.yml file 😉
yes there is a message with published to the 2 relays in my config.
I was just wondering why i see errors there.
you can very easily do this with Atlas Notes right now
and even with drag and drop support from one list of pubkeys you want to focus on into the list you want 😉
(ignore the debug data, this is my local version I was working on today 😂)
just made this video 👇
https://nostr.build/p/nb7478.mov
(these are obviously ALL nostr events, including the nesting of lists!)
it looks on 🔥
is altas notes already public available? or just on localhost 😉
but according the message nostdress was not able to ping one of them 🤔
#[0] i have just a small question, i have only set 2 relays in my env file. but nostdress connect/ping to a few more… is this because I have set get_nostr_profile to true?
