I suggest we’ll call it NIP-80 after the default http port.
Imagine future browsers ( #browstr ) allowing you to enter http://<some-nprofile>.nostr/… and it would simply send the http request and receive the response via nostr events! Just like .onion sites but without the slowness of TOR.
It can also be useful for #iot devices that can serve a simple configuration-website and allow “browsing” them from anywhere in the world. I think TOR is too complicated to run on such devices.
{
"id":"da9a8c1364c84206249d5342224f0184b92dccbd1e01c1591143c02c4d44ea81",
"pubkey":"3316e2d88ff91e1089c75feedcd8baa2258b45455a3b156af617d7ec79b45fe5",
"created_at":1720565162,
"kind":1,
"tags": [
[
"imeta",
"url https://v.nostr.build/VAREX7f6XB8sTPQr.mp4",
"blurhash e00J8VfQM{ayxufQfQfQfQfQM{fQxuj[M{ayfQj[fQayxufQM{ayxu",
"dim 1920x1080"
],
[
"r",
"https://github.com/nostr-protocol/nips/pull/1276"
],
[
"t",
"browstr"
],
[
"t",
"iot"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"r",
"https://v.nostr.build/VAREX7f6XB8sTPQr.mp4"
]
],
"content":"Here is another demo of my NIP implementation.\nNow using ephemeral events, NIP-44 encryption and NIP-59 gift wraps:\nhttps://github.com/nostr-protocol/nips/pull/1276\n\nI suggest we’ll call it NIP-80 after the default http port.\n\nImagine future browsers ( #browstr ) allowing you to enter http://\u003csome-nprofile\u003e.nostr/… and it would simply send the http request and receive the response via nostr events! Just like .onion sites but without the slowness of TOR.\n\nIt can also be useful for #iot devices that can serve a simple configuration-website and allow “browsing” them from anywhere in the world. I think TOR is too complicated to run on such devices.\n\nnostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z WDYT? https://v.nostr.build/VAREX7f6XB8sTPQr.mp4 ",
"sig":"b0236683bb861d70cde2ffc940c9986e38e41e6da392e9aebd067039cbd939264c6f5a6a0dfaef409eb53b845c90b2e1a1ef0812963ae5e4e00487f787f38adf"
}