Re: nhttp - Nostr over HTTP communication

Interesting! Thanks for sending.

I am a bit curious about the motivation though: "struggling to solve the
high bandwidth problem." My understanding is that neither websockets nor
Nostr's protocol itself are particularly wasteful in terms of overhead. So
all else equal, assuming the same Nostr client and relay(s) and operations,
would HTTP really save that much bandwidth, if any?

On Thu, Jan 11, 2024 at 10:32 PM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

> May be of interest to some here, though of course wss is indeed an http
> upgrade protocol, quote from Yonle:
>
> "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://nostr.at/npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4el
>


-- 
https://snarfed.org/