pull down to refresh
22 sats \ 3 replies \ @TonyGiorgio 24 Feb 2023 \ parent \ on: GH/http-nostr-publisher: Cloudflare worker to publish Nostr events through HTTP nostr
Not only that but it's compatible with nostr clients, has a POST endpoint, batches events to be more efficient with sockets, only uses relays that are actually online at the time, and is available to use for free by the public.
Not sure why they didn't just use blastr (since its actually MIT) but hey to each their own I guess. Maybe they weren't aware.
I didn't really know about blastr. thanks for sharing it.
Is it correct that blastr sends to as much as relays out there? here the client defines the relays that an event should be sent to. It is also NOT intended to be used in a Nostr client but simply tries to be a tiny, stupid HTTP function that takes an event and an array of relays and publishes to those. So the goal is a bit different.
reply
Yeah all those things are correct, I can see why it's a bit different. Though can easily add the array of relays to the POST endpoint if needed.
reply
that's great to hear. would for sure love to support it.
Rust is just not my main language and it was easy to write those lines of JS.
Can the relay be disabled? because I assume if it gets used as a relay it needs much more resources and has more traffic.
My use-case is mainly that existing apps can publish events to Nostr without the requirement to add the websockets handling.
Potentially also loading specific notes through a HTTP get.
reply