talbot on Nostr: The nostr model in general seems to put a lot of responsibility on the client. Not ...
The nostr model in general seems to put a lot of responsibility on the client. Not necessarily a bad thing, just a lot to think through in implementation. I could imagine in future standing up HTTP frontend services that aggregate, deduplicate data, and serve it up compressed, over multiplexed connections, with certain cacheable endpoints (ie the efficiency benefits of HTTP). Hard to imagine low end phones on low bandwidth networks running such beefy clients - but maybe I’m also thinking about it wrong.
Published at
2022-12-30 08:04:12Event JSON
{
"id": "0ea2d6c95db0833fabf5adb37fdc652b8fef6dbb79061fe71f2d5a947a684786",
"pubkey": "35e2c78fcfc687b77bea5f92117c6197de35ca538ba106d8b162ba6016a7fe55",
"created_at": 1672387452,
"kind": 1,
"tags": [
[
"e",
"5acb02851080c5d68ab63caad6c143cf2a58c6de4f06ec872ef5ae985500563c"
],
[
"e",
"ab0c8d2f15a08b53df6ff03340129b5b8f03b62cb31841f543ea4efa42df939b"
],
[
"p",
"60a3a6b57cf954ae97c1ecd4c48c46e8b9b2476a13274fe2c73eb90f2cfe9879"
],
[
"p",
"00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
],
[
"p",
"eb3a338922741d7014d78ade8c53f138534b6603b032a8289b1cc9b645adfa83"
]
],
"content": "The nostr model in general seems to put a lot of responsibility on the client. Not necessarily a bad thing, just a lot to think through in implementation. I could imagine in future standing up HTTP frontend services that aggregate, deduplicate data, and serve it up compressed, over multiplexed connections, with certain cacheable endpoints (ie the efficiency benefits of HTTP). Hard to imagine low end phones on low bandwidth networks running such beefy clients - but maybe I’m also thinking about it wrong.",
"sig": "ad6897282c6e2d32ed840c9b5b86c0c0fb84f1df84c1d7c352496134e58077a3a3dae69d83967fbbdee32bef27c277a710b24e291245e88f4a0c710c1b0f215f"
}
