We all know that connections to #nostr relays are mostly done via websocket.
And then i got an idea: How about i create a way to communicate with Nostr relays via HTTP instead?
You see, We have QUIC already, And we know that most social media apps were using HTTP to communicate. But we are using websocket. So what's wrong with it? As a mobile data user, I am struggling to solve the high bandwidth problem.
So there we go, an prototype nhttp (Nostr over HTTP). It got basic stuff already: REQ, and event publishing
https://github.com/Yonle/nhttp
Yonle
npub1x3…3g4el
2024-01-05 08:09:59
Author Public Key
npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4elPublished at
2024-01-05 08:09:59Event JSON
{
"id": "7aa3880701a7d3279f00bb1f201f962d34d04083d11f9cee610ce7392c109424",
"pubkey": "347a2370900d19b4e4756221594e8bda706ae5c785de09e59e4605f91a03f49c",
"created_at": 1704438599,
"kind": 1,
"tags": [
[
"t",
"nostr"
]
],
"content": "We all know that connections to #nostr relays are mostly done via websocket.\n\nAnd then i got an idea: How about i create a way to communicate with Nostr relays via HTTP instead?\n\nYou see, We have QUIC already, And we know that most social media apps were using HTTP to communicate. But we are using websocket. So what's wrong with it? As a mobile data user, I am struggling to solve the high bandwidth problem.\n\nSo there we go, an prototype nhttp (Nostr over HTTP). It got basic stuff already: REQ, and event publishing\n\nhttps://github.com/Yonle/nhttp",
"sig": "6af375eca3bfc01247dcd1211cbb39f1394681a70dc03f6509a30fe05f04932b41705bbf73ef585decea7a48af017ea1a4009fa6f019f13338f8b6f1367f7fb5"
}