-A relay might not record the time it received an event
-A relay might record the time it received an event but this information isn't exposed to clients
-A relay might record the time it received an event and this information is exposed to a given client but that client might not care to compare timestamps
-A relay might record the time it received an event and this information is exposed to a given client and that client might care to compare timestamps but from a discrepancy is unable to determine whether something suspicious is going on (are the event date and receipt date out of sync for THAT relay only, perhaps because the event was rebroadcast, and then which other relays to cross-reference before feeling confident enough to make a determination...)
And then someone indexes every known relay in the Nostr universe and offers an API for this specific purpose and that solves the problem :)
JoeRuelle / Joe Ruelle
npub1hy…wtqnx
2025-03-24 11:39:28
in reply to nevent1q…7jmn
Author Public Key
npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnxPublished at
2025-03-24 11:39:28Event JSON
{
"id": "e74406358b60af144ec0bdc32d5a6085b3a5f1aed013dc36593f634c5448d5e2",
"pubkey": "b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823",
"created_at": 1742816368,
"kind": 1,
"tags": [
[
"e",
"d615e3c6467c22878bab8a2a72c6013b19504489d2c8011b6fc8dbbcd78acd53",
"wss://a.nos.lol",
"root",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"e",
"8c465570568e400ee1b92e8d0d4bbb1be02dfc3385ee636e1da3f1033bc99c06",
"wss://nos.lol/",
"reply",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"p",
"11b9a89404dbf3034e7e1886ba9dc4c6d376f239a118271bd2ec567a889850ce"
],
[
"p",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
]
],
"content": "-A relay might not record the time it received an event\n-A relay might record the time it received an event but this information isn't exposed to clients\n-A relay might record the time it received an event and this information is exposed to a given client but that client might not care to compare timestamps\n-A relay might record the time it received an event and this information is exposed to a given client and that client might care to compare timestamps but from a discrepancy is unable to determine whether something suspicious is going on (are the event date and receipt date out of sync for THAT relay only, perhaps because the event was rebroadcast, and then which other relays to cross-reference before feeling confident enough to make a determination...)\n\nAnd then someone indexes every known relay in the Nostr universe and offers an API for this specific purpose and that solves the problem :)",
"sig": "75c4da8206dd425ad00eec9a6b1138b12f476c1924724d2825f79ce053c64dee125b486868aade80a54a189b4aff468bea980b584bc8dd4e9ff163491dbe5a3a"
}