Farcaster Devs

just realized that some messages seem to be timestamped before their parent cast (eg https://warpcast.com/degentipbot/0x32c0d96fe987f958adf372a4ec1a08189a1f58ea)

is this known? (screenshot below from warpcast showing this)

fiids.xyz | deescuss.com | bondes.xyz | feedbac.xyz

You can set the cast timestamp in the past. My guess is the tip bot has the wrong timezone.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

i thought there was a threshold on how much in the past the timestamp could be from one of @v's discussions but i'm likely wrong. thanks @vrypan.eth

"Must be a valid Farcaster epoch timestamp not more than 600 seconds ahead of the current time" (the limit is in the future, not past). Epoch starts Jan 1, 2021 00:00:00 UTC, so it can't be before that.

got it, thanks. so timestamps are not reliable to order casts or validate accuracy since these can technically be forged.