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
很早之前就看到有对 Nostr 通讯使用协议的争论. 虽然 nips 中的设计默认都是 WebSocket, 但是看起来实践后也有很多人想在某些使用场景下使用 HTTP.
nostr:nevent1qqs84gugquq605e8nuqtk8eqr7tz6dxsgzpaz8uuaesseeee9sgfgfqpz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzqdr6ydcfqrgeknj82c3pt98ghknsdtju0pw7p8jeu3s9lydq8ayuqvzqqqqqqyqcge5u
Please Login to reply.
我开始这样做有重要的原因。最值得注意的一个主要是移动数据用户。
能理解, 社区很多次提议使用 HTTP 与中继通讯都是有原因. 我支持你的想法.