manime on Nostr: I am dumb client dev. I just want clients to suffer less from data consumption and IP ...
I am dumb client dev.
I just want clients to suffer less from data consumption and IP exposure AS WELL AS indie relay operators to suffer less from being underutilized.
Semi… I know your plan is excellent, as a single relay architecture. However, IF there is a NIP for “relay pools” (which … why not?) I see that this would be BETTER if it allowed for the same client benefits.
If a “relay pool” NIP were to suggest that clients COULD connect only to the relay pool address, and that relays in a pool SHOULD transfer data between each other, then BOTH solutions (Semi’s single relay architecture and Cameri’s relay pool architecture) would provide a consistent benefit for clients and relay operators. The only difference then would be how the infra is hosted…
Am I just wrong here?
I just want clients to suffer less from data consumption and IP exposure AS WELL AS indie relay operators to suffer less from being underutilized.
Semi… I know your plan is excellent, as a single relay architecture. However, IF there is a NIP for “relay pools” (which … why not?) I see that this would be BETTER if it allowed for the same client benefits.
If a “relay pool” NIP were to suggest that clients COULD connect only to the relay pool address, and that relays in a pool SHOULD transfer data between each other, then BOTH solutions (Semi’s single relay architecture and Cameri’s relay pool architecture) would provide a consistent benefit for clients and relay operators. The only difference then would be how the infra is hosted…
Am I just wrong here?