Event JSON
{
"id": "aa6d881b8761921acc1d9b74f9b51ac5f6c1521c31efcedab41e81b595307508",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1721742285,
"kind": 1,
"tags": [
[
"e",
"7da509f4ba00515eece9d94abf7a872d947d1337bff703ebe47553dce5be09db",
"",
"root"
],
[
"e",
"3e17da17a655c09dcf569566f8a4bac0f82152350b7cd2af2d5afcfb6d4cafba"
],
[
"e",
"d63fa8a64901eabaf12b7b7719a202414ea2213f703aa86450362b7fd9178067",
"",
"reply"
],
[
"p",
"c3c7122c63af5281fee3b9338d10ae65b166ffe6f73f1c272c5c1120607731d7"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"r",
"npub.pro"
],
[
"r",
"https://github.com/nostr-protocol/nips/pull/811/files"
]
],
"content": "Yeah, I still believe on that idea. It's basically what npub.pro is doing but keeping their templates also inside of relays. All it needs is a a simple server that offers the event content through HTTP instead of websockets. \n\nNIP draft is here. https://github.com/nostr-protocol/nips/pull/811/files\n",
"sig": "2bb2ece556c4c59bb4ccb49da2e98f5b98cb5bffc7a493dc983a4a74027c1322c2038378f055bac70baf6c7bb94cc6e55cf2a5d6c52ab8473946ad5f447e8371"
}