Unpopular Opinion:
I still believe that a request/response model for relays/servers are benefitial for nostr. It can drastically simplify many aspects of client development. Not all data are streams. Therefore, I am implement a request/response nostr event server in Rust. The current network solution is just HTTP GET/POST of events.
I hope at least blowater can use it earlier next year so that many aspects of this client can be simplied.
Waterdan /
npub1dw…6pdnf
2023-12-21 20:23:00
Author Public Key
npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnfPublished at
2023-12-21 20:23:00Event JSON
{
"id": "2bb56fe3a90b0a1fb47b06ccb621aab9f4856574f71f7ffc2afd439711f8bb58",
"pubkey": "6b9da920c4b6ecbf2c12018a7a2d143b4dfdf9878c3beac69e39bb597841cc6e",
"created_at": 1703186580,
"kind": 1,
"tags": [],
"content": "Unpopular Opinion:\nI still believe that a request/response model for relays/servers are benefitial for nostr. It can drastically simplify many aspects of client development. Not all data are streams. Therefore, I am implement a request/response nostr event server in Rust. The current network solution is just HTTP GET/POST of events.\n\nI hope at least blowater can use it earlier next year so that many aspects of this client can be simplied.",
"sig": "d4a0bcfa571c1f329fe7d7642cce946814718576c11a3a7427d926ffd0e0de019d6bf1b26fdf9d6d2ae2a021d8ffdaa5d02b301b0711c0d1094c94ecaa42bc86"
}