pippellia on Nostr: nostr event created_at field is a Unix timestamp. A timestamp of 0 is I think Jan ...
nostr event created_at field is a Unix timestamp. A timestamp of 0 is I think Jan 1970, and negative before that.
Most likely the client is not parsing as an integer but unsigned integer, so a negative timestamp is treated as a very high timestamp (a lot in the future), which is always the newest event. Or some silly thing like that
Published at
2025-06-06 20:51:12Event JSON
{
"id": "2f7cfe2673829241e928c3f3f70b4259fa4285c261c0ed36a65f6a8c54442ba1",
"pubkey": "f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2",
"created_at": 1749243072,
"kind": 1,
"tags": [
[
"e",
"7729cbb7b59879c5bfffb4aefd410a2d4b085e20a95abaac30a22237e9a71124",
"",
"root"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"c7eda660a6bc8270530e82b4a7712acdea2e31dc0a56f8dc955ac009efd97c86"
]
],
"content": "nostr event created_at field is a Unix timestamp. A timestamp of 0 is I think Jan 1970, and negative before that.\n\nMost likely the client is not parsing as an integer but unsigned integer, so a negative timestamp is treated as a very high timestamp (a lot in the future), which is always the newest event. Or some silly thing like that",
"sig": "9982819ae74be4dce3733d70e6beea91991e4959dd2db6ce73149ea55a39f7d9bbe6072819eb3f554a0bd45ea0cf12f0294c2a674cdab985fb80792e4dd75e29"
}
