Post B1M62bUog5KVMdl9SS by RedstoneLP2@mastodon.redstonelp2.com
 (DIR) More posts by RedstoneLP2@mastodon.redstonelp2.com
 (DIR) Post #B1M5LoRYfDMD4GpaYC by RedstoneLP2@mastodon.redstonelp2.com
       2025-12-17T22:20:02Z
       
       1 likes, 0 repeats
       
       how do fedi software deal with bogus dates/does activitypub allow bogus dates?
       
 (DIR) Post #B1M5LptxF7fLad7mS0 by arcanicanis@were.social
       2025-12-17T23:48:43.474296Z
       
       0 likes, 0 repeats
       
       I guess by which context (server/client)?At least from what I remember, most things are pretty tolerant. Sometimes shown in the order it was discovered in (at least in a timeline).You can always toy experimentally with this by just static files of the JSON-LD context, as long as the correct media type is served. Mastodon (out of all other implementations) just tends to be the most fickle, expecting WebFinger resolution and a few other prerequisites (in terms of "test labbing" with static JSON files), while most others just simply need a resolvable actor object.
       
 (DIR) Post #B1M5il3JRCU7D9Qooy by sun@shitposter.world
       2025-12-17T23:52:53.705857Z
       
       2 likes, 2 repeats
       
       @arcanicanis @RedstoneLP2 I don't know if it's still true but Pleroma used to just trust the date, years and years ago someone was sending out posts backdated to the 1600s.
       
 (DIR) Post #B1M62bUog5KVMdl9SS by RedstoneLP2@mastodon.redstonelp2.com
       2025-12-17T23:55:40Z
       
       1 likes, 0 repeats
       
       @sun@arcanicanis tbh i was more thinking "57th of march" type of bogus date
       
 (DIR) Post #B1M6PM06SI9ZxzF2yu by sun@shitposter.world
       2025-12-18T00:00:35.259035Z
       
       2 likes, 1 repeats
       
       @RedstoneLP2 @arcanicanis the activities are sent with a standard json-formatted datetime, which allows you to formulate a bogus date, but in mastodon and pleroma's case these are inserted into the database as a timestamp type and if it's a bogus date, there is no way it can even be inserted, it will throw a hard error and fail to insert. I haven't tried it before with mastodon but this is a scenario where 999 times out of 1000, the insert is just going to fail and the data will be dropped. you would have to go out of your way to deliberately retain data with a bad date.
       
 (DIR) Post #B1M9oGyUZvzPTs3uVs by verita84@poster.place
       2025-12-18T00:38:43.313Z
       
       0 likes, 0 repeats
       
       @arcanicanis@were.social @RedstoneLP2@mastodon.redstonelp2.com @sun@shitposter.world pleroma do what masto don’t
       
 (DIR) Post #B1MDbe1Zy6Md1KjvqC by arcanicanis@were.social
       2025-12-18T01:21:14.206510Z
       
       1 likes, 0 repeats
       
       Here's some test fixtures you can play with:https://arcanican.is/fedi/tests/25/timestamp-goodhttps://arcanican.is/fedi/tests/25/timestamp-badTry manually pulling each URL using the 'search' of your instance. First should work, the second is the date you describe. The latter fails on Pleroma apparently, as @sun had mentioned.I also have a query tool at: https://arcanican.is/tools/activitypub.php