made a labeller for backdated posts
@backdate.mozzius.dev
helps spot posts that show up on the firehose at a different time than when they claim to be created. sometimes it's archival posts, or sometimes it's someone trying to be sneaky. this labeller helps spot them!
Samuel
@samuel.fm
lemme know if it's working correctly - there's a good chance I've messed up timezones or something like that 😅
5 1 32ObXKCD xkcd.com/2867/ (I wanted to embed this in my latest declaration against the terrible social media bills sweeping the country because the latest law includes a "parents must be able to specify lockout times for their kids' accounts" clause, but alas judges have no sense of humor)
DateTime
xkcd.com
need to check in few days if @lucid-twitter.bsky.social's posts have gotten labeled. :D
1 4it's won't backfill, since it can only tell if a post has been backdated by comparing the time it appears on the firehose to the claimed time. nothing I can do about already created posts
2 14ah, okay, but like @monicarose.ca said, still a good time to add this labeler as people start porting old tweets on to bsky.
1 3yeah any future archives showing up will get tagged :)
2 7can you add an opt - in label that can tag the account as tweet archive - which we can get by liking a post or something?
1 2I'll consider it, this is really more intended as a moderation tool to catch people being sneaky with post dates rather than a vanity label
1 6yeah, i figured -- and my idea wasn't as much vanity label in this case, as much as just a way for people to clearly see it.
but i guess in my case I put the account name in a way it shouldn't matter at all.
1 2Yay ok so mine will :)
1Any chance it could be an official label that's automatically on anything with a date older than when Bluesky was created?
I can imagine a universe a few years from now where people dig up 'old' posts without even realising that Bluesky isn't nearly that old. Would be a small client addition
1 5hmm, wouldn't be unreasonable to backfill the labeller in theory but scraping the whole network is a big job beyond the scope of the labeller
I'd rather avoid client-added labels, but that might be easier
1 6You could spot check the oldest timestamps on repos, skip those whose oldest timestamp is not backdated and then traverse those where it is
This is why backend timestamps should be timezone agnostic and just carry a timezone flag on top