What do y'all think? WebTransport?

nostr:nevent1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqheasfuakefvmatunl7le7nqmsesr52xcc0aw0tc7neqj23e0v4q6jl3h6

Reply to this note

Please Login to reply.

Discussion

protobuf and gRPC

most widely supported binary encoder and RPC library after JSONRPC2 which BITCOIN uses but nostr invents its funny Envelopes instead

filters need better documentation

someone has made a client that sends bech32 encoded entities in place of IDs right now

whoever you are

shame, shame shame.

lmao

Instead of event IDs?

Is that why my downloaded events have some with things in the wrong fields? It's confusing data.

no, just a different encoding, it's supposed to be a hash

Oh, right, sorry, instead of the hex.

yeah, it was "nevent" which is that plus can have also relay URLs

The key point here is using oblivious http (OHTTP) relays. WebTransport would be simpler and more efficient but not a requirement to make that work, I think.

It is a requirement since WebSocket is not really HTTP, but a hack that breaks out of HTTP to keep a TCP socket open. WebTransport lets you do the same kind of streaming split into genuine HTTP packets.

Thanks, that saves me a lot of time.