My neighbor has been pounding on the ceiling with her broomstick because I cannot stop laughing.

poor nostr.watch, no love. Shame too, especially considering this: https://github.com/search?q=api.nostr.watch&type=code

If you use the nostr.watch API in your client or tool, it would be pretty cool if you gave a link-back or credit in some way. There's 90+ tools and clients using the API.

https://github.com/search?q=api.nostr.watch&type=code

ouch

achievement unlocked

group think is the enemy of innovation.

it has shadow masters.

Yes, that's the plan, but there's a lot to do to make that efficient and possible.

According to legacy nostr.watch, `nostr-rs-relay` still dominates.

https://nostr.watch/relays/statistics

But this **only includes `wss` relays, not `ws` or `onion`**. I'm monitoring via NIP-66 for `wss` and `ws` but not `onion` yet, could be calculated pretty easily by anyone...

If they are replacable events, then why would there be an increase in events?

What makes you say that?

also working on a similar tool, but a little different.

standard operating procedure.

Just message me or post an issue on Github.

With NIP-66, yes. These expired certificates can be found in `30066` events right now. And yes, next nostr.watch would convey these details, and any other data present. But then again, any client could convey those conclusions at runtime with NIP-66

looks right to me. Maybe I published twice, as this usually happens when I think I'm signed in, but the alby auth window isn't focused. Will dig into it later today on a burner.

yes.

Here's the replication flow, happened twice today:

1. Be signed out of signer (for example, alby)

2. Write a note and publish

3. Unlock signer

4. Upon signer being "available," Coracle publishes previous note twice.

PineWatch has these features, I have one, but it will take a few ten/hundred thousand hours of work to get where Android/Garmin/Fitbit/Apple are right now in terms of UX , accuracy and integration.

PineWatch has these features.