I hand-rolled a simple API that only reads from a website, so that you can download the e-books we're printing as epubs and mobi/AZW3. Had to strip the whole site down. No Javascript, websockets, nothing. Just HTML and HTTP.
There's no standard. @mleku and I have done some fiddling with Rest, for a while, is all. We are trying to get Nostr onto more different types of machines and deal with the sort of slow Internet that I regularly have to deal with, in my region. Websockets sometimes result in my seeing a blank page because they time-out over and over.
Login to reply
Replies (1)
There are lots of OtherStuff use cases where speed is less important than persistence and reliability of the connection. Websockets are an artifact of starting off with Twitter clones. We've already spread out from there.
Since there are Nostr clients and relays using the other protocols, they already count as part of the Nostr protocol. As per the Nostr rules.