Event JSON
{
"id": "df3eb4830377579bf28a8d1a8e352c627605f1f9ecb801d5b6307d094969d5a5",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1707764552,
"kind": 1,
"tags": [
[
"e",
"859463c2cbd191a54cac358f7af82b39921de7712bb8b91101e4dbde26df62e6",
"",
"root"
],
[
"e",
"299dba71c3ce10d3f8d8eab8c213955db002d490da7c13e125cf54098f24f584",
"",
"reply"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
],
[
"p",
"7bdef7bdebb8721f77927d0e77c66059360fa62371fdf15f3add93923a613229"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"p",
"00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "I am dumb client dev. \n\nI just want clients to suffer less from data consumption and IP exposure AS WELL AS indie relay operators to suffer less from being underutilized. \n\nSemi… 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.\n\nIf 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…\n\nAm I just wrong here?",
"sig": "516596befbb03722e53af7a6f6155e03705591acc54016107cc6a2f96655deed1f4ba78299362a944859d52ca388a7d33d0ca229a9457810aa655c94edb7b558"
}