wdym
these are browser APIs
Discussion
spec is very simple
disable buffering on your proxy
Content-Type: text/event-stream
each line has a prefix + data (followed by a newline), like so:
prefix: data 1
prefix2: data 2
two newlines = end of message
types:
- event: once per message, defines event type
- id: event ID to be given to consumer
- data: data for event, multiple data lines can exist (they are joined by newline)
- retry: send by itself with nothing else, number in milliseconds to try to reconnect after connection loss
also, have subscription (new events) separate from request (stored events)
what protocol is this and where is the #golang implementation?
i'm in the process of building something like this damn you
oh, reading closer, yeah, nah, your idea is more complicated, pass
it is not really complicated
this is for realy protocol btw not nostr clients
with `application/nostr+json` it requires a JSON body and POST method
what you are talking about is something separate for a different `Accept` value
i'm trying to diverge as little as possible from existing code to make adding this simple
problem is browser won't render them... maybe it would with some CSS juju?
anyway i don't want to be anchored to fucknig shithole browser bullshit
what browser, am i reading my feed as raw json with all the ugly escapes and no linebreaks?
what is a "browser api" exactly?
i don't want to mess with making shitty parameters with ?key=value&... i thought about taht, and i decided no, just simple, post json, return json, that's what `application/nostr+json` means, really, except they didn't delineate between websockets and http request/response