Crap. I just checked the Wayback Machine archive I made yesterday before I posted this, and it's scrubbed, too! It shows it has having been archived, but then it gives an error that says "This browser is no longer supported," even when I try three different browsers.
it gives an error that says "This browser is no longer supported," even when I try three different browsers
Interesting...
First up though, it won't matter what browser you use to view or archive from, what happens with sites like Wayback Machine and archive.today is they use a browser (or browser fingerprint) of their own (eg: Google Chrome/Chromium) when they browse to and archive the site in question.
Because of this, archiving sites often have a unique fingerprint which can be rejected by the target site.
So the really interesting part here is that twitter.com is, for some reason, no longer supporting whatever it is that Wayback Machine uses for its archiving.
Ah. Thanks for that explanation. Archiving has been really iffy the past week or so again, I noticed. I guess I'll have to start screencapping everything.
It may be a temporary thing though, due to browser update rollouts.
Example:
Let's say a massive security issue is found with the engine of Browser X. Archiving Site Y also uses the engine for Browser X. Browser X releases a patch for the security issue which was otherwise relayed to 'big websites' and the international IT community, thus twitter.com has been made aware of the vulnerability.
twitter.com may be rejecting the outdated and vulnerable version of engine for Browser X, and Archive Site Y has not yet updated things on their end. Archive Site Y needs to implement the update also, in order to get past the block.
That's all hypothetical of course, and puts a certain amount of faith in twitter.com not blocking Wayback Machine for malicious reasons. It may be worth trying to Wayback a tweet again in a day or 2, to be sure.
view the rest of the comments →
Otto- ago
Aaaand the link is down.
Vindicator ago
Crap. I just checked the Wayback Machine archive I made yesterday before I posted this, and it's scrubbed, too! It shows it has having been archived, but then it gives an error that says "This browser is no longer supported," even when I try three different browsers.
argosciv ago
Interesting...
First up though, it won't matter what browser you use to view or archive from, what happens with sites like Wayback Machine and archive.today is they use a browser (or browser fingerprint) of their own (eg: Google Chrome/Chromium) when they browse to and archive the site in question.
Because of this, archiving sites often have a unique fingerprint which can be rejected by the target site.
So the really interesting part here is that twitter.com is, for some reason, no longer supporting whatever it is that Wayback Machine uses for its archiving.
Vindicator ago
Ah. Thanks for that explanation. Archiving has been really iffy the past week or so again, I noticed. I guess I'll have to start screencapping everything.
argosciv ago
It may be a temporary thing though, due to browser update rollouts.
Example:
Let's say a massive security issue is found with the engine of Browser X. Archiving Site Y also uses the engine for Browser X. Browser X releases a patch for the security issue which was otherwise relayed to 'big websites' and the international IT community, thus twitter.com has been made aware of the vulnerability.
twitter.com may be rejecting the outdated and vulnerable version of engine for Browser X, and Archive Site Y has not yet updated things on their end. Archive Site Y needs to implement the update also, in order to get past the block.
That's all hypothetical of course, and puts a certain amount of faith in twitter.com not blocking Wayback Machine for malicious reasons. It may be worth trying to Wayback a tweet again in a day or 2, to be sure.
MadWorld ago
You smart ass XD