bombthrower on Nostr: So then the well known URI faces the exact same risk since that's under a domain name ...
So then the well known URI faces the exact same risk since that's under a domain name anyway.
I'm just saying to signal the hexkey via DNS TXT, not via a flat file confined to the domain component of a NIP-05.
You don't gain any advantages to doing it via well-known URI in censorship terms and you lose flexibility and usability in terms of deployment.
Published at
2023-07-12 16:55:47Event JSON
{
"id": "05d126eaa6c0dbad9b5bfb4da70b4d3e8cef99a03251ceaa421c6fd51de0d0c1",
"pubkey": "cfdc11439f3b4b6aad060365c1182f774b524075170a6cf1a3c1b2abc61d102c",
"created_at": 1689180947,
"kind": 1,
"tags": [
[
"e",
"8980106c69c2f97e3dae0b5e5dda7c8aa650577570d733f62618c38cf819e17a",
"",
"root"
],
[
"e",
"778231fffa6ebf98a206e875c2fc35b9fbebcafc62d05167a45f8b381a53501c",
"wss://nostr.bitcoiner.social/",
"reply"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"6a02b7d5d5c1ceec3d0ad28dd71c4cfeebb6397b95fef5cd5032c9223a13d02a"
],
[
"p",
"2f02d76f09666ae076e65beb60ff195eb7f44b51c73147a6a37748bfabd60a7c"
]
],
"content": "So then the well known URI faces the exact same risk since that's under a domain name anyway.\n\nI'm just saying to signal the hexkey via DNS TXT, not via a flat file confined to the domain component of a NIP-05.\n\nYou don't gain any advantages to doing it via well-known URI in censorship terms and you lose flexibility and usability in terms of deployment.",
"sig": "bb8dc297ab7515ab952c82b9ddbc8e67c2565a38c41f137641ba4f77ba57a01b8fc305fbcb7b8b5295fe103dd241fef78fdf88f3835e137f067ecbfd66017d8b"
}
