If you can get signed messages following the JSON format described in NIP-01 and verify them... it's nostr
It doesn't matter if a websocket or a pigeon delivered it ona piece of paper
If you can get signed messages following the JSON format described in NIP-01 and verify them... it's nostr
It doesn't matter if a websocket or a pigeon delivered it ona piece of paper
This is true. Also valid if you can compose a json doc from disparate pieces and verify. Thats how Corny Chat has been handling server and client side verification for nostr users.
Interesting
That's actually pretty inspiring to me. There's a platform I wanted to build a Nostr relay on but it doesn't support websockets yet.
I didn't realize it's feasible to build a relay that doesn't use websockets. Got an example?
I implemented it on mine: https://github.com/zapstore/ftsrelay , should be pretty simple to do it on other relays
Oh what I meant is that the language / programming environment where I want to build a relay doesn't support websockets at all. Basic HTTP only.
I was intrigued to see you say that ws wasn't a relay requirement, as I always saw that it is.
Isn't websockets and HTTP the very minimum needed to get stuff from relays?
I suppose it's just a client minimum.
If you had a relay that accepted requests from carrier pigeons and responded appropriately, then your client would just need to know how to talk to the carrier pigeons.
All of our clients assume websockets (and HTTP) right now.
Train them so nostr peep be like.
"Send a crow"
-Game of thrones"
Wen pigeon relay? 😂