i've just been made aware that Brave might cause reachability issues in Nostr in web clients. maybe it's blocking WebSocket connections to non-origin domains as an anti-tracking measure. i don't use Brave so i can't check personally.
Discussion
firefox has CORS add-on
yeah, the thing is that a properly configured relay sends proper CORS headers. i don't care if a relay is badly configured and lacks this, but i had someone just now who said that *most* relays failed to connect when he used Brave. i'm *assuming* it's a CORS issue, but it might also be a resource limit. i know Firefox maxes out at 200 connections per tab and Chrome at 255 but i don't know about Brave. Safari seems to handle at least 200 just fine. my tools open a lot of connections simultaneously.
(another reason for setting up a little daemon on tigerville.no that tracks the metadata i need for these queries instead of having them run on the clients, i suppose. one could make a separate web tool just for debugging connection issues that connects directly to relays.)
u can change based how powerful ur PC is RAM is or ordinary user leave as is - network / RAM will be killed - disk/cpu not much impact
there isn't much a web app can know about the power of the client or the network. not without running some kind of benchmark first. but i don't find that these queries overwhelm either. it's rather a case of how browsers put artificial resource caps on web apps to contain them a little.