yup, that's why it will have a new event structure, one that i have been designing, that specifies application and mimetype, the same way as defined in HTTP headers, and it will use HTTP as the main transport and leverage what it can do as well
http doesn't need sockets, it has SSE for subscriptions and the rest is standard request/response pattern
other than that, there is just the matter of *where* you store the data and the idea is to generalise this service in a nostr-like protocol, which lets you have data storage and relaying combined into one server, so it can act as a proxy, let you subscribe to data updates, and store and retrieve data in one server, and this can then be generalised so deploying the data storage/relay/proxy back ends is a generic, simple service that will achive Amazon style efficiencies of scale (so probably there will be a small few like we have with "cloud" services, amazon, microsoft, google, but because it's a general purpose it will be easy for businesses to deploy their own infrastructure as well as pay outside providers, providing maximum flexibility.
mleku
npub1fj…mleku
2025-06-04 12:12:33
in reply to nevent1q…nj2l
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-06-04 12:12:33Event JSON
{
"id": "00d005100cae585d57ccdcb6fea2e03a29b8668d72adc0342c6d5fc0b00baff5",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1749039153,
"kind": 1,
"tags": [
[
"e",
"80593c6f7a8201c81a42884299502838123b857173d92a75a8e759b4f2e6e834",
"",
"root",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
],
[
"e",
"776d0fb49f2670c73e124e8423cca10457800f9de15bb4f187ba75a1830eaf84",
"wss://theforest.nostr1.com/",
"reply",
"75656740209960c74fe373e6943f8a21ab896889d8691276a60f86aadbc8f92a"
],
[
"p",
"75656740209960c74fe373e6943f8a21ab896889d8691276a60f86aadbc8f92a"
]
],
"content": "yup, that's why it will have a new event structure, one that i have been designing, that specifies application and mimetype, the same way as defined in HTTP headers, and it will use HTTP as the main transport and leverage what it can do as well\n\nhttp doesn't need sockets, it has SSE for subscriptions and the rest is standard request/response pattern\n\nother than that, there is just the matter of *where* you store the data and the idea is to generalise this service in a nostr-like protocol, which lets you have data storage and relaying combined into one server, so it can act as a proxy, let you subscribe to data updates, and store and retrieve data in one server, and this can then be generalised so deploying the data storage/relay/proxy back ends is a generic, simple service that will achive Amazon style efficiencies of scale (so probably there will be a small few like we have with \"cloud\" services, amazon, microsoft, google, but because it's a general purpose it will be easy for businesses to deploy their own infrastructure as well as pay outside providers, providing maximum flexibility.",
"sig": "89fa43730d3e7dbd445fe4fa775c2edfd4b76c951b16ddfb8ed1fd72a09f930405e7b665b7289a669055efe7f98ef121b0073d74b399da29801db2f6fb1c15de"
}