Yeah, I think its a browser thing. https://stackoverflow.com/questions/70503250/how-to-stop-chrome-from-upgrading-websockets-from-ws-to-wss-when-the-websocket-o
The TLS mafia requires everything to be TLS
i am debugging why clients are not connecting to my relay, and comparing nostrudel production vs next version:
if i'm not mistaken, it looks like next version (and this is probably the same with primal and coracle, which also don't talk to my relay anymore) is messing up the TLS/SSL and asking for a secure connection even though the URL protocol i see in the source code says `ws://` for the local relay
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr any idea what is going on here? it looks like this is actually kinda wrong that it's trying to connect using SSL when the protocol is not SSL nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and whoever else works on NDK, dis you guys?
Discussion
ok so next gets this, but production gets this
ok but why does production version of nostrudel do it fine, in every respect, and not next version, there is a break somewhere along the line
i really don't think this is a break in my code but in the client libraries, not even the runtime itself because how else was it still working? and further, brave wasn't able to do the thing at all, but firefox is, even without changing that about:config setting, in fact i've started using it because i can do this, but now i'm thinking, the easiest solution to this all nonsense is that the local relay is going to be modified in my version to point to my relay's reverse proxied https address and see if that changes things