The proper procedure would be to propose it to the spec and allow the community to debate such an addition.
this simulation is so rampant with bugs
Go 3.11 will be the best because we'll finally get support for Workgroups
one time he said america needs to evaluate its defensive posture in the metaverse, as if it had oil in it or something.
nah i'm good
"After visiting an Orb, a biometric verification device, you will receive a World ID. This lets you prove you are a real and unique person online while remaining completely private. As the global distribution of Orbs is ramping up, you can find the closest one and book time to be verified with World App and at worldcoin.org."
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424
building
nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a we need George Gammon on #Nostr!
Thank you for your time. I get the same result. However, is it expected to get new events over the socket as they happen and have them print to the screen? Or is that behavior relay-specific?
(don't think my original reply went through, reposting).
My theory is that the code I shared (https://satellite.earth/thread/note183zt68szqs35204wskmwn6jyeqp24kgkk7k8vzy0r2hqc8lymc2qhj0aqn) should live update with each TextNote from that npub. Perhaps it's relay-specific?
@fiatjaf
I'm having trouble getting new events from wss. I'm trying to write a client in Go using https://github.com/nbd-wtf/go-nostr/blob/master/example/example.go but I am not receiving events as they occur. Know anyone who could assist?
Looking for some help from Go developers on some #Nostr client-side code problem I'm having, please reach out if able.
#dev #devs #developers #golang #go
nostr:nprofile1qqst4z7jg8d2rm3ypt69g4n3phdfv09qfeyp866pu50ltgm4m072g2shj0tft hi there. wondering if you can help me with something frustrating i'm seeing with nostr code. i'm trying to catch new Events as they come in. so i'll run it and post something, but don't see that event until i re-run the code. have you ever seen this behavior?
Hi nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft wondering if you may be able to help me here.
I'm using the code here (https://github.com/nbd-wtf/go-nostr#subscribing-to-a-single-relay). When I run that code and subscribe to a relay, I can see my own events. But if I create a new event, I have to re-run that code to see it...I would expect the websocket to deliver that. Is that relay-specific do you think?
nostr:npub12gu8c6uee3p243gez6cgk76362admlqe72aq3kp2fppjsjwmm7eqj9fle6
Hi, I'm hoping you can help or know of someone who can. I'm developing a Nostr client. When I subscribe to a relay's websocket and create a new event, that new event doesn't come through on the websocket. If I kill the program and reconnect, I see it. Is that behavior relay-specific do you think?
playing with the idea of a nostr tui client.
thinking about a cool nostr client idea




