hhmx.de

Chee Aun πŸ€”

Föderation EN Fr 28.02.2025 03:19:30

Took me a while to debug this on Phanpy's Catch-up, date range is wrong, the squares are all group into a single tall bar πŸ˜‚

Turns out one of the posts is… ✨in the future✨ (2026). This: community.nodebb.org/topic/186 (Mastodon: mastodon.social/@julian@commun)

Anyone knows why/how this happens? πŸ˜†

Phanpy's catch-up UI showing posts from February 28, 2025, 1:54 AM to February 28, 2026, 1:00 AM.

The posts visualization shows on very tall bar of squares.

Code snippet from browser's devtools console, displaying date and time information with properties like `minDate`, `maxDate`, and `range`, in the context of Singapore Standard Time.

minDate shows Feb 28 2025, maxDate shows Feb 28 2026.

A post featuring a surprised-looking cat, with text mentioning "NodeBB Community" and hashtags "#nodebb" and "#release."

The post is posted on Feb 28 2026.

(Medien: 3)

fashionable cyber witch project vyr

Föderation EN Fr 28.02.2025 03:24:17

@cheeaun sometimes people do it just for goofs. i thought Mastodon clamped remote post dates to within a few minutes of current time, but maybe that's only when building timelines

Chee Aun πŸ€”

Föderation EN Fr 28.02.2025 03:31:35

@vyr Catch-up fetches the same "home" timeline API. I thought it's probably boosted by someone I follow, but I actually follow @julian so it appears on the timeline as-is.

Chee Aun πŸ€”

Föderation EN Fr 28.02.2025 04:28:58

Shoving it to the last bin for now.

A graph displaying timeline posts data from Feb 28, 2025, to Feb 28, 2026, with options for "All," "Original," "Replies," "Boosts," and "Filtered" interactions.

The future post is at the last bin.

(Medien: 1)