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?
cloud fodder
npub10n…ztl5h
2024-10-19 15:02:54
in reply to nevent1q…4j0l
Author Public Key
npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5hPublished at
2024-10-19 15:02:54Event JSON
{
"id": "168dda09252dec41d83c6e57a1b2eef3bcf73ee09365adf6b2506bb1121ae781",
"pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"created_at": 1729350174,
"kind": 1,
"tags": [
[
"e",
"00000109bb6d0d0262452ae57799bd7fd55d88af7e5aae71d33f82cacb64502c",
"",
"root"
],
[
"e",
"7cd22c3264f0d750e7f041043bb1e7ff63825bf9cae0fb972657f4daa136fe06",
"",
"reply"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"p",
"7fa56f5d6962ab1e3cd424e758c3002b8665f7b0d8dcee9fe9e288d7751ac194"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd",
"",
"mention"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"",
"mention"
]
],
"content": "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.\n\nnip98, 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.\n\nThe flow could be something like:\n\n98auth - POST /api/relays {name, desc ... duration of service}\nreturns: bolt invoice, id\n\nGET un-auth - /api/invoices/id\nreturns paid/unpaid\n\nand some further crud stuff like GET all, delete etc..\n\ncc nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsxct838 nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq35amnwvaz7tmjv4kxz7fwwajhxar9wfhxyarr9e3k7mgprdmhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8x6lmt90, any thoughts on nip98?\n\n",
"sig": "360f912c1cad129fa1ab5b46365a93a055fb23a65f1778d4696dedc8a6bcd7cbb9283308dbf0a05d093e4408d340d1f48c51e42eb7fa71965a039520b3b6c8ce"
}