Oddbean

▲ ▼

 this is the way for 1-to-many writes. 

now consider the inverse for reads: connect to 1 relay that fans in many relays. 1 websocket connection to the phone, dedupe happens on the server. I just need nip-42 to prevent crawlers from ddosing my fan in relay nostr:note1hagrnf4jzk37hhdtca5ysz4qjm2qt08tx78ypcx6dc0g3c0tcfas8e08t4

▲ ▼

 Yes, it's called multiplextr: https://github.com/coracle-social/multiplextr

▲ ▼

 nice! I built one too because I am a javascript disrespector 😝

but I need nip-42 auth because I want to whitelist users.

▲ ▼

 Agreed, javascript is bad and AUTH is critical. Let's go!

▲ ▼

 I understand the situation.

1. Realistically it's a good solution.

2. If the problem is bandwidth, ideally, Negentropy or any syncing protocol is a more elegant solution. Weaken the client, the edge, weaken the decentralization.
@@Doug Hoyte

▲ ▼

 I would imagine negentropy on a client would create too much latency for on-demand content. But it's definitely important for powering proxies/dvms

▲ ▼

 I think it depends on perspective/use-case. I love the decentralized network of relays. I just want to connect to it from a single point, in the cloud, on a server I control. this has a few benefits for me:
- not doxing my ip, no vpn
- less bandwidth 
- very fast

▲ ▼

 - better for offline/offgrid clients
- can even be interacted with over an ssh tunnel

▲ ▼

 Good point. I did not consider these use cases.

▲ ▼

 is that relays talking with relays?