so i finally figured out the problem with my curl-replacement that uses #nostr nip-98 auth (it's what the relay now uses for its admin port)
yeah... ContentLength
http doesn't do streamy stuff... you must be thinking of websockets
anyway, just to tie up a few bows and realy v1.8 is about to be a thing, with extra`curdl` for your jsonl import and export pleasure
it's toasted!
Have you tried "nak curl"? It just calls curl underneath, but adds the NIP-98 header.
i just wrote it without looking at your code anyhow
the thing that stucked me was the need for the contentlength field, i didn't see that, idk even how i figured it out but there it is...
i will look at your code now to see what you did but #realy v1.8.1 is now live and does all the admin http port stuff with nip-98
Yes
Yes it can
but you must use chunked encoding or http2
yeah, that multipart form jazz, that's not what `curl -X POST -T filename
i poked through the go stdlib http library comments and apparently there was some kind of bunfight around this shit that led to some certain things
keep in mind that this is the golang web server receiving it, so whatever retardations it has baked in i have to deal with
i don't really mind, piping from the stdin wasn't actually important at all, as soon as i saw it works when you read from a file just needed to tell it the file size, done, finished, i removed the pipe option because it doesn't come with a size information
it does, however, enable the use of a `$(sha256sum filename) in place of just the filename and it will conform to the nip-98 thing of giving the file hash as well, not that i'm enforcing it but it gives it
