mleku on Nostr: sorry to disrupt the joy there i just did literally implement a nip05 feature in my ...
sorry to disrupt the joy there i just did literally implement a nip05 feature in my fork of leproxy (which automates getting certs, i recently added the ability to add your own paid certs) and i understood how it worked at the abstract level for the domain, and how all of those name@ parts refer to a different user but they don't refer to a different name or address so the web server would need some other scheme to specify
perhaps it can be simply done with an automatic http-basic path resolution rather than a subpath as i am suggesting, maybe this is just "implementation details" but i think it's important to establish a standard practise
Published at
2024-12-20 19:51:28Event JSON
{
"id": "bc3e8a2a6ab3e4613a4851f3df46dd9308084d7f47716fde39fc6db7c6a1af00",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1734724288,
"kind": 1,
"tags": [
[
"e",
"9f37906b07aa219762513385e723003043eb52c16ddc611822d1441ec3210533",
"",
"root"
],
[
"e",
"0245d3780d9f8d0906a03ca1be01f6ab14dfad7d0f84c3fa203dc99869e3e659",
"wss://nostr.wine/",
"reply",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
],
[
"p",
"cfd7df62799a22e384a4ab5da8c4026c875b119d0f47c2716b20cdac9cc1f1a6"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"wss://nostr.wine/"
],
[
"p",
"a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "sorry to disrupt the joy there i just did literally implement a nip05 feature in my fork of leproxy (which automates getting certs, i recently added the ability to add your own paid certs) and i understood how it worked at the abstract level for the domain, and how all of those name@ parts refer to a different user but they don't refer to a different name or address so the web server would need some other scheme to specify\n\nperhaps it can be simply done with an automatic http-basic path resolution rather than a subpath as i am suggesting, maybe this is just \"implementation details\" but i think it's important to establish a standard practise",
"sig": "3c0f2f33525b7f61ea353778f6c9633678a3fca47381930c9f7016c088eaa8d8d9707ac79a9256d4e0191f42fbb9afcb139195ed8e308237a518de533545356d"
}