I’ve mostly seen posts from five and ten years ago exactly, leading me to think this is may be part of the old “This Day in Blogging History” feature that was discontinued back in 2014. Maybe @jlw or @beschizza can look to see if some automatic part of that feature was re-activated recently.
That was never automatic. @doctorow would do each one manually and personally make the picks.
Huh. Color me even more impressed then.
Another thought. I’ve noticed on Cory’s Tumblr that he still highlights posts from five and ten years ago. Is it possible that when he’s browsing through the old posts that he’s inadvertently tripping the modified date?
I think it might be worth looking into. Not every past post that Cory highlights on his Tumblr gets a repeat thread here on the BBS, but quite a few of them do. And looking at the pattern of events the Tumblr post always comes after the repeat BBS thread which would make sense if Cory is placing these old links in his Tumblr queue to post later.
… Jumping back a few weeks, see if the pattern holds …
July 31 - https://mostlysignssomeportents.tumblr.com/post/148252938740/flowchart-shows-the-complexity-of-the-new
July 30 - Flowchart shows the complexity of the New Zealand’s Internet Disconnection copyright law
If I’m right, by Tuesday we should see Three-hole punch debut, April 1940 and New Zealand wants a Ministry of DRM show up on Cory’s Tumblr.
Edit: So Cory’s going to be at Burning Man until Sept. 5th. and supposedly off the grid. Another test to my hypothesis - do any repeat threads show up on the BBS during Cory’s absence?
Really excellent detective work sir. Let’s see.
This is caused by editing old pre-Discourse era postings in Wordpress, simply because the UI defaults to having “Post to Discourse” checked. As these old posts never had Discourse threads, they are created by the edits.
Oooh, my estimate was way too high. https://mostlysignssomeportents.tumblr.com/post/149564077063/three-hole-punch-debut-april-1940-10yrsago was just posted at 2:41pm EDT on Saturday August 28th and https://mostlysignssomeportents.tumblr.com/post/149558246545/new-zealand-wants-a-ministry-of-drm-10yrsago was posted at 12:06pm EDT.
Now to just keep an eye out for any new WABAC Machine failures here on the BBS.
Interesting. You’re All Just Jealous of My Jetpack: a collection of Tom Gauld’s brilliant cartoons just repeated here on the BBs despite Cory’s presumed unavailability. Now we watch to see if this post gets featured on his Tumblr in a few days time.
@codinghorror or @sam, I’m woefully uninformed as to how you’ve tied Discourse and Wordpress together, but would it be possible to have some kind of “do not post to Discourse if originally posted prior to date” kind of check?
I wonder if that would cause problems with intentionally reposting older material. That has been done before.
Perhaps it could work such that posts prior to the specified date didn’t have “Post to Discourse” checked by default but the box could still be checked if desired.
Not knowing how the 2 are integrated, I have no idea if that’s feasible or if it would disrupt anyone’s workflow.
That was a Mark Frauenfelder post though. Does that affect your theory at all?
Not really. Though most of the posts that Cory features in his flashbacks are his, he does include some from other editors. The California greenhouse gas post that showed up on the BBS on August 22nd was originally by Xeni, for instance.
Here we are again. Cory’s back from Burning Man and new time travel threads are showing up. We went nine days without any repeats, excepting that rogue Frauenfelder post that never showed up on Cory’s tumblr, and now we have Wikipedia’s dumbest arguments posted at 9:15pm EDT on Sept. 6th.
@eviltrout can we prevent very old posts from triggering topic creation? Say anything more than a year old?
I took a quick peek and it doesn’t seem like the
created_at date is being passed over by the wordpress plugin. We do support it optionally via the api.
It looks like it needs to be added to wp-discourse – additionally it occurs to me that we could put the same check on the wordpress side. In other words, don’t send over something whose date is over X.