Event JSON
{
"id": "766237d7809b5e421e92fcf2498a1bb868d3bf86105d679b467b4296cf953a47",
"pubkey": "91be5c15af34e54c65b1489763bacda05c31b1b5046e0c077cb3ae148d211d85",
"created_at": 1695742982,
"kind": 1,
"tags": [
[
"p",
"93a8f0c358cdd2fd3c8be6b1e4578d1dfba43dea40ddddac4c4dec735a879e6c",
"wss://relay.mostr.pub"
],
[
"p",
"81e31d02b3d0b97ae960104572e2d79bf26e647a4d82afef56ce2395055364ff",
"wss://relay.mostr.pub"
],
[
"e",
"bd3e4688bf1927e11d3e3ccb051de3e68eb616e86d420c917a238237727227e3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://framapiaf.org/users/pmevzek/statuses/111132212107283721",
"activitypub"
]
],
"content": "nostr:npub1jw50ps6cehf060ytu6c7g4udrha6g002grwamtzvfhk8xk58nekq4k9fry Seems to be a very specific edge case, both at deployment and implementation: 1) \"Conditional DNS Resolver\" aka both recursive and forward (I never thought this is a good idea, even if used a lot to \"speed up\" some internal requests on a closed network and 2) \"they share the same global DNS cache\" (the recursive part and the forward part). So I am not convinced. Even if it seems all nameservers strains were updated because of those bugreports.",
"sig": "c5b44f7eaec359973b8b9e7d0ec2ef08829d37cc509dc5a4e5dcdee64f892ed37e7df0ad8489f827d0b3d9087097794d262ec570dcc493aadb3215f868918e89"
}
