that's literally what entertainers do, so it's not so weird is it...
when i post about this or that project i'm tempted to do, i'm very much counting the likes/shares i get on that, because if nobody else cares, i can't manage to care myself. not unless it's a rage project, that is, where i'm doing it because i've had it with this problem that no one's solving.
this is the bit where nostr-tools crashes because if it receives an event from an unknown subscription ID, it then tries to access the subId key on that object and since it doesn't exist, there's an exception.
yeah, i think there's a connection issue with a lot of the relays where they seem to send rogue events for things the client didn't subscribe to yet and it causes nostr-tools to crash because it tries to insert those events into a subscription key that doesn't exist.
if you look carefully through all the new stuff that's been introduced in JavaScript after ES5, in many respects, it's an entirely new language.
remember that book that was called JavaScript: The Good Parts?
most of the new stuff that's been introduced in the past few years is more good parts, such as a safer comparison operator.
there's this type of function that modern JavaScript supports that i don't see used very often, and it's called an async generator function.
i think you could use it to replace event listeners completely, since the function can just yield whenever there is a new event and the caller can await it, and both run in an infinite loop that ping-pongs back and forth.
semi tempted to take the Relay class i wrote for NostrCrawler and turn that into a Nostr client library. i know that already exists, but it doesn't hurt to have alternatives. and i'm thinking i could try to give mine more of an async/await type API.
this looks like some kind of bug in nostr-tools. it crashes if an event comes from an unknown subscription. 🤔
if you look at the output of Nosy, another tool i make, you can see that certain relays are more common than others. they're usually a bit more reliable as well. relays are run by random volunteers. not all of them are going to work properly all of the time.
it appears that fewer relays are responding to queries for you. i had about 69 unresponsive ones when i tested just now. of those that did respond, 115 had my post and 168 did not. but you don't really *need* to be on that many relays. some relays are far more widespread than others.
NADAR = (na)sal detecting (a)nd (r)anging 😆
NRCheck is now called NADAR:
the old URL redirects to the new one, so hopefully, no one will be confused.
need a better name for NRCheck. it's not very catchy. it also happens to begin with the same letters as the Norwegian state broadcaster NRK, so now my browser wants to complete the URL wrong all the time. 😆
some people are having issues with NRCheck being unable to connect to hundreds of relays. i had such a case a few days back, and it appeared to be because they were using the Brave browser. i'm not sure what could be causing it. on standard Chrome and Safari, it works fine for me, both on WiFi and 4G.
i have added a filter.
updated https://nrcheck.tigerville.no to use a Bootstrap GUI
✅ 
heavy fog outside. +8ºC and 89% rel. humidity. seems to be translating to about 40% rel. humidity indoors where it's 21-22ºC.