cloud fodder on Nostr: I've always assumed this would be a good feature, and RT is in a good position ...
I've always assumed this would be a good feature, and RT is in a good position code-wise to build it. Since its been mentioned a bit lately, I will put some priority on it in the various roadmap planning Im doing.
nip98, has anyone actually used it? It's a standard but I am curious if users will be wanting to sign for every api req, or instead with extra effort, get a jwt token to perform further calls (currently i use jwt, but it seems like people 'say' they prefer 98.. :) I agree, that it's probably easier to implement.
The flow could be something like:
98auth - POST /api/relays {name, desc ... duration of service}
returns: bolt invoice, id
GET un-auth - /api/invoices/id
returns paid/unpaid
and some further crud stuff like GET all, delete etc..
cc brugeman (nprofile…t838) hodlbod (nprofile…mt90), any thoughts on nip98?
nip98, has anyone actually used it? It's a standard but I am curious if users will be wanting to sign for every api req, or instead with extra effort, get a jwt token to perform further calls (currently i use jwt, but it seems like people 'say' they prefer 98.. :) I agree, that it's probably easier to implement.
The flow could be something like:
98auth - POST /api/relays {name, desc ... duration of service}
returns: bolt invoice, id
GET un-auth - /api/invoices/id
returns paid/unpaid
and some further crud stuff like GET all, delete etc..
cc brugeman (nprofile…t838) hodlbod (nprofile…mt90), any thoughts on nip98?