infrastructure pack rat. relay sniffer. "running branl." I've built other stuff. opensats grants recipient. nostr apologist since 763719. SEC-01 | NIP-66 | NIP-78 | NIP-119
sandwich @sandwich - 8d
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.
sandwich @sandwich - 19d
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
sandwich @sandwich - 1mo
Yes, a long time ago. https://github.com/SamSamskies/nostr-zap
This one is out of date, I will soon update it.
sandwich @sandwich - 2mo
And why?
sandwich @sandwich - 3mo
My mind immediately went to using timers to hotfix race condtions. I should probably go outside.
One step at a time...
Recommend to use relay.nostr.watch or relaypag.es instead or in addition to
NIP-66?
Well, I just figured it out. The changes weren't being deployed :D
Thanks for the help btw, it's difficult to rapidly develop + test every possible case in every possible browser :D
handles serviceWorkers in a secureContext differently*
Should have it this time. I'm assuming you're using Firefox in a private tab. It handles serviceWorkers in a secureContext, and I wasn't accounting for this case. ~10 minutes.
CDN cache has been purged.
It might be a CDN caching issue, with the change that was added, it would be impossible for that error to occur.
hotfix will be deployed in roughly ~10 minutes. It's possible the error caused you to have breaking state. lmk if the error persists.
