Dimi
· 1w
Ya, shimming is necessary at this stage, but I don’t see that as a downside. As of the last Sov Eng demos nostr:npub1ffhcyatymrryprsqcfty4hpqghknyc6s6n7fe279z0e9sf95lkasuws272 put it in Opnsense, no...
oh yeah, proxying it via a standard websocket is a possibility too.
i've also thought about the thing of boot strapping a user onto the network via specialised introducer points that distribute relay addresses. then you can bootstrap a user into that, their client then has a full list of a large number of relays they can access, and don't have to use the introducer again, instead they can access the relays direct. have the relays supporting a message encryption layer that bypasses TLS and uses noise protocol handshakes as plaintext http/ws messages, and another innovation i've been working on - a proxy extension for nostr relays, that fans out the actual requests to relays that sends the requests, caches the data, and sends back the deduplicated responses back to the user. this is best for the mobile user too because instead of 5-10 different relays being queried it's just one and one set of results come back, no 5 different relays sending back 5 copies of everything.