still, that leaves traces on relays hinting about what you're doing...
Problem with that is that either you click ok on the chrome extension all the time, or you just trust blindly what the site will post…
To me, the whole point of the extension is to control what’s happening with my keys… so I probably won’t set it to auto-sign, and I guess I’m not the only one.
Why is Coracle trying to sign so many events just for seemingly readonly usage?
running a lightning routing node is hard these days…
gm builders
can't wait to plug this in #nostr 
Nix fixes this
Looking for the best in depth iptables documentation available... thanks for any tips!
This is the way
Yeah, it's VERY important to self custody all your shitcoins by downloading all those blockchains.
you guys know of a simple way to validate a nostr event as a JSON string straight in the CLI?
Nobody giving af about Bittrex going belly up on nostr is priceless
I just roasted Bank of Canada in their survey about CBDCs...
sending a message from iris
guys, I need a nice list of what nostr is currently used for, aside from microblogging… could be alpha form, doesn’t matter, as long as it is currently working.
Nevermind, I changed the relay and it’s working fine now.
gm builders
working on a very low level nostr presentation for tomorrow… having fun connecting to a random relay with netsocat in the command line and sending some raw REQ…
it works very well and that’s a testament to the ease of dev and the permissionless properties of nostr…
I am wondering, though… if I REQ two notes, as such
["REQ","1",{"kinds":[1],"limit":2}]
I get them, but then there’s no realtime feed following… I was expecting to have an incessant flow of global stuff.