Thoughts on URI
First we need a URI spec for Nostr, maybe a simple NIP like BIP 21 identifying a few Nostr schemas. IIRC they don’t need to be final.
Then;
Anyone with the patience of an elephant and experience with browser’s politics willing to file tickets on Chromium, Mozilla, and Webkit/Apple's repos for “nostr:” URI? This will require a lot of wiki style politiquing. Literally hell. So a white knight is required.
If you work at any of these entities, I’d love to enlist you. ;)
NVK
npub1az…am8y8
2023-04-09 13:07:03
Author Public Key
npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8Published at
2023-04-09 13:07:03Event JSON
{
"id": "40a1dab64ba7fc78036d2178e83aa81d0af412b0ca132a2426b0584a61b862de",
"pubkey": "e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411",
"created_at": 1681045623,
"kind": 1,
"tags": [],
"content": "Thoughts on URI \n\nFirst we need a URI spec for Nostr, maybe a simple NIP like BIP 21 identifying a few Nostr schemas. IIRC they don’t need to be final.\n\nThen;\n\nAnyone with the patience of an elephant and experience with browser’s politics willing to file tickets on Chromium, Mozilla, and Webkit/Apple's repos for “nostr:” URI? This will require a lot of wiki style politiquing. Literally hell. So a white knight is required.\n\nIf you work at any of these entities, I’d love to enlist you. ;)",
"sig": "332ef4f72d391cf1f427cd469c07af0638b7cca13164a014f7235379307450f6f7dea9131814655aaf27c684163e9a13088b06343df555e33b1a67f02244d21e"
}