mleku on Nostr: one of the nice things about using http/websockets is we have many options i already ...
one of the nice things about using http/websockets is we have many options
i already have simple web services that you can dump or pull events en masse or filtered by pubkey, currently fixing it at the moment to play nice with the pubkey indexes
it is trivial to add a path-defined HTTP endpoint to POST stuff to and you don't even need special tools to do it, but also, there is very many functions in all the programming languages libraries to push and pull data via post, get, and put (and whatever else) over http, you can even have more fun things by turning paths into parameters for these things as well as using json or whatever format, or HTTP headers to specify parameters
ultimately blossom is actually just a http server with a specific HTTP API based on paths, i believe, or maybe it uses ?parameters=thing as well or can do
if you want to drop giant loads into your relay rather than mess around with interactive sockets if your task is singular, in, or out, it's dead easy to do it with http, you can control access with http-basic or - i haven't got this done yet, that nip-98 stuff, that uses auth events in their place
after having built a http import/export and your specific task requires sometimes bulky up or downloads i think this is what you should do, it's really simple, i wish i could convey to you how joyously simple it is to write web services with Go, but probably it's similarly simple with php
and not only that, as is done with strfry, you can even have http endpoints invoke other programs and pipe them data directly, like a series of tubes (and so on)
so, really, i think what you need is to learn how to write simple TTY savvy things that can read stdin and spit stuff to stdout and yell at you over stderr, and i think chiptuner will also concur with me about this, though i don't know how fun http or socket programming is in C but it's sure as hell fun with go
i already have simple web services that you can dump or pull events en masse or filtered by pubkey, currently fixing it at the moment to play nice with the pubkey indexes
it is trivial to add a path-defined HTTP endpoint to POST stuff to and you don't even need special tools to do it, but also, there is very many functions in all the programming languages libraries to push and pull data via post, get, and put (and whatever else) over http, you can even have more fun things by turning paths into parameters for these things as well as using json or whatever format, or HTTP headers to specify parameters
ultimately blossom is actually just a http server with a specific HTTP API based on paths, i believe, or maybe it uses ?parameters=thing as well or can do
if you want to drop giant loads into your relay rather than mess around with interactive sockets if your task is singular, in, or out, it's dead easy to do it with http, you can control access with http-basic or - i haven't got this done yet, that nip-98 stuff, that uses auth events in their place
after having built a http import/export and your specific task requires sometimes bulky up or downloads i think this is what you should do, it's really simple, i wish i could convey to you how joyously simple it is to write web services with Go, but probably it's similarly simple with php
and not only that, as is done with strfry, you can even have http endpoints invoke other programs and pipe them data directly, like a series of tubes (and so on)
so, really, i think what you need is to learn how to write simple TTY savvy things that can read stdin and spit stuff to stdout and yell at you over stderr, and i think chiptuner will also concur with me about this, though i don't know how fun http or socket programming is in C but it's sure as hell fun with go