just a sandwich.
sandwich @sandwich - 2mo
No, clients in general. The user would either paste the code or be provided a link
Gateways are only a stepping stone for nsites, the end goal is native resolution. Try https://nsyte.run, with the command nsyte run
nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl There was a line break between bitcoin and the link.
why?
sandwich @sandwich - 3mo
What methods are they using?
Lexical ambiguity.
nsyte v0.11.0 release: https://github.com/sandwichfarm/nsyte/releases/tag/v0.11.0 new site: https://nsyte.run jsr: https://jsr.io/@nsyte/[email protected]
sandwich @sandwich - 4mo
Lost my follow list again.
sandwich @sandwich - 5mo
oh yeah, one of the nostr.watch agents has been monitoring tor relays for the last week. Checks tor relays every 24 hours and publishes as: `9e81fadfe8c07351d806b47bc6c0d0dfb189343656e400e207a2be9b37411e79` Right now it is reporting that around 255 relays are accessible over toor.
Is this still using NIP-66?
Added fan for this voltage regulator, adds some noise, but more stable.
... And an 8cm radiator.
8cm raditator
After tuning and rise in ambient temperature (took the photo in the morning), hash-rate is ~2TH/s @ 63C, still no radiator fans. https://image.nostr.build/f7615d732c4ad651c34657acd315793359eaa1998833082a21fb93dea0e4e42a.png
Probably. Someone should PR NIP-11, would propagate changes faster than a note
sandwich @sandwich - 6mo
Yes, a long time ago. https://github.com/SamSamskies/nostr-zap
This one is out of date, I will soon update it.
And why?
sandwich @sandwich - 7mo
My mind immediately went to using timers to hotfix race condtions. I should probably go outside.
One step at a time...
