Do you know why notes often only get transmitted to 1 relay? Seems like you reach only a fraction of the people on Nostr whenever you post something.
somewhat tempted to set up a tracker on tigerville.no to store the metadata i need for https://nrcheck.tigerville.no, https://nosy.tigerville.no and other tools. i'm not finding the relays very reliable or consistent. you'll search them for the exact same thing and they respond with a slightly different list of results each time.
Discussion
are you sure they're only being transmitted to one relay?
This is a typical response I get searching for notes.
that's a rare sight for me. can you send some notes that i can search?
your "didn't connect at all" number is VERY high though. that means your computer can't reach those relays.
on my end, i'm only getting 2 relays that didn't connect at all and 67 that took so long to respond that the tool gave up.
I'm using Iris webclient, android, Brave browser(shields off)
Had always been under the impression I had low visibility. Not sure how Nostr works so wouldn't be able to figure that out myself.
could you right click the page, click Inspect, select the Console tab, run a search and show me the errors you're getting there?
(using NRCheck i mean)
mostly: Can't connect to wss://nostr.jatm.link (caught exception)
a good bunch of : Info fetch timeout for wss://www.weixin.com
about 15 like : Access to fetch at 'https://nostr.easify.de/' from origin 'https://nrcheck.tigerville.no' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
and a handfull of: Failed to load resource: net::ERR_FAILED
Do I tried the client on windows aswell, and both on mobile network and wifi. I get different results when I'm not using Brave btw
this is somewhat more typical using Impervious browser
if you're getting 300 "didn't connect at all" you should also be getting 300 WebSocket errors in the console. it should be the most common error message. if your browser isn't letting you talk to remote WebSocket servers, you're going to have low visibility.
#[2]
try blastr ! one write relay - rest all READ - this is where i am posting it now
i use nostr.mutinywallet.com that does the same thing. i could always add blastr to the arsenal too 😅
aha, so this appears to be for Cloudflare. something you set up on your own. maybe that's what they're running on that relay.
user can install or use hosted one - 2 ways
can u tell if it use a "huge DB" ? like a normal relay
at this point hosting a relay biggest load in on DB grow - rest r manageable
100%