Hacker News Reader

Comment by jashkenas | Hacker News Reader

Twitter thread about the mislabeling/misattribution/removal, for context: https://twitter.com/maxwelltani/status/1214957104206876672

Mashable story tracking the takedown and statements by Teen Vogue: https://mashable.com/article/facebook-teen-vogue-sponsored-c...

Update: Sadly, it looks like the Internet Archive copy has now turned into a 404. Mods should probably replace this link with the Mashable writeup above instead.

View on HN

https://archive.is/8J1qB

Since Internet Archive chucked it in memory hole.

The Internet Archive is working for me:

https://web.archive.org/web/20200108170304/https://www.teenv...

Please see my post in the other thread about how TFA images fared on the Internet Archiv.

https://news.ycombinator.com/item?id=21998463

Archive.is blocks cloudflare dns from resolving it's site. I'd recommend finding something else.

Yes, for a while. But I wonder how that happened.

Assuming that the timestamps in the archive.org timeline are UTC:

   2020-01-08 17:03:04 UTC   capture with content
   2020-01-08 18:02:12 UTC   capture with "Uh-Oh ..."
   2020-01-08 18:10:22 UTC   capture with "Uh-Oh ..."
   2020-01-08 18:10:25 UTC   capture with "Uh-Oh ..."
   2020-01-08 18:11:28 UTC   capture with "Uh-Oh ..."
   2020-01-08 ~22:40 UTC     17:03:04 capture present
   2020-01-08 ~23:40 UTC     17:03:04 capture missing
   2020-01-09 ~02:40 UTC     17:03:04 capture present

As I understand it, archive.org will take down captures if robots.txt is changed to exclude them. But that can't be the explanation here, because that robots.txt edit would necessarily have occurred after ~22:40 UTC. And that would arguably have taken down all of the earlier captures.

So arguably this must have been a manual intervention.

And again, no blame. It's just metadata.

(This comment was posted to https://news.ycombinator.com/item?id=21996263 and merged hither along with the rest of that thread.)

Reply on news.ycombinator.com