Content
@
0 reply
20 recasts
20 reactions
ʞɔɐſ
@farcasterjack.eth
Back day, WordPress let you pick any date and time for a post in the classic editor’s “Publish” box. If you punched in something wild—say, January 1, 2075—and hit Schedule, WordPress dutifully stored that future timestamp in the database. A quick flip from “Scheduled” to “Published” (either through a dashboard “Quick Edit” or a direct SQL nudge) made the post go live immediately while still wearing its far-future date. Because themes, RSS feeds, and comment sort order trusted the stored timestamp, everything—from your homepage chronology to external aggregators—made it look like you’d just blogged from half a century ahead. Modern versions tighten that loophole, validating dates and locking down status changes, but the old trick was a fun bit of temporal mischief. maybe this is some strange Farcaster verion of that Wordress exploit. i thought it might be related to the client they used to send it but it lists the client as ....the name on the account? im even more confused than b4 tbh
1 reply
1 recast
11 reactions
Josephine Oriaku®
@josephineoriaku
How did you find out this truth?
0 reply
0 recast
0 reaction
