Cool, thanks!
1. Yes some providers don't accept "@" or misinterpret it, some require it, not sure how to make it right yet.
2. It's DNS caching issue, it got stuck checking your updated DNS settings, will look into it.
brugeman
npub1xd…mntxy
2024-09-19 13:16:08
in reply to nevent1q…ed3x
Author Public Key
npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxyPublished at
2024-09-19 13:16:08Event JSON
{
"id": "05c2b9a28b01d76638bbd42f239ba3382d8fabc021aec8d9fd69be8dd95613f5",
"pubkey": "3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd",
"created_at": 1726751768,
"kind": 1,
"tags": [
[
"e",
"0e990261cba88ab73e159bb16fc676b35bbde6d4f6db6032754560d8ec826312",
"",
"root"
],
[
"e",
"d1745c4e63338a2e80334ebc2e52e64c40e5eb73bea5de134444bd660e785e88",
"wss://nos.lol/",
"reply",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "Cool, thanks! \n\n1. Yes some providers don't accept \"@\" or misinterpret it, some require it, not sure how to make it right yet.\n2. It's DNS caching issue, it got stuck checking your updated DNS settings, will look into it.\n\n",
"sig": "5a77f9e1a45654c227ffa407286805ddc04209ea428103229e3217243475c46bca194670c2ae391a7b93dcd007f6465bb0691d1c178cd564736c6c82c3c69063"
}