sandwich on Nostr: I've spent today refactoring `nostrwatch-js` and combing the logs on the daemons. 1. ...

I've spent today refactoring `nostrwatch-js` and combing the logs on the daemons.

1. I found an bug in `nostrwatch-js` that caused problems for slow relays which would result in a latencies not being calculated correctly. This is an edge case, but I found 6 relays affected by this in production.
2. I found a bug in `nostrwatch-js` that caused write checks to fail for slow relays. (this is **not** related to paid relay write checks, those should fail)
3. I found a pretty big issue in the daemons, where the jobs overlapped after ~7 days of running. I haven't been able to identify if this caused any issues with data yet, but it definitely caused the daemons the crash periodically.
4. It is possible the improvements to `nostrwatch-js` mentioned above will resolve issues that some relay operators have reported related to Uptime, but cannot confirm with certainty at this moment in time.

I have long wanted to refactor `nostrwatch-js` (formerly `nostr-relay-inspector`, and have spent part of yesterday and today doing so. I also added features that are in line with the goals of `nostr.watch@0.3`. `0.3` provides more data to operators and completely refactors the relay detail page.

The improvements to `nostrwatch-js` will be rolled out to the daemons tomorrow and will be rolled out to nostr.watch with the `0.3` release or possibly as a patch to `0.2` if `0.3` takes longer than anticipated.