Activist best practice: auto-archiving web pages

Today its not uncommon to find a growing number of media outlets censoring stories about vaccine injuries.

 

Online activists preserve and share important information that powerful interests want to keep hidden from the public. To the uninitiated, this sounds like – at best – an exaggeration. (I used to think that, too.) But if you’ve spent a few years as an activist, you’ve probably seen this for yourself too many times.

Even trusted hospitals with great brands such as St Jude’s have been caught watering down vaccine risk information that they have publicly posted online for many years.

 

Ooops!  Did you notice that?

St. Jude was able to hide all their pages archived in the Way Back Machine! Most people who use the Way Back Machine for archiving don’t realize how quickly what they think is permanent can disappear.  St Jude disappeared all their archives simply by editing their robots.txt file.

Here at VaxCalc Labs, Archive.is is our preferred archiving tool because it provides single-page archiving capability that isn’t impacted by robots.txt. Even better: you can make a local copy of any archive and store it in your Dropbox.

What we are doing now is building an auto-archive feature deep into Autovist so that activists don’t have to worry about taking the time to archive web pages and documents – it just happens.  Auto-archive is rapidly becoming an absolutely critical feature to have in your activist toolbox.

Fortunately, we captured what St. Jude, for many years, used to tell their patients and their families about the risks of live virus vaccines.  And because we captured it on archive.is, we are able to create a powerful message about the risks of live virus vaccines:

 

However, there are some problems with archive.is during the past few days.  While I can invoke it via Autovist running on my local machine, and via curl on my local machine – archive.is responds with an error when run from Heroku:

The response comes so quickly that I suspect the request isn’t even reaching archive.is — instead, it’s probably from Cloudfare, who may have blocked an IP address range and responds with a fake error message.

Whatever the root cause, it is looking like we cannot rely on archive.is. Moreover, every I try to create a local copy of an archive, the process times out:

Yikes!  I have serious second thoughts about relying on archive.is, which is a shame because it is normally such a wonderful tool.  When manually archiving, it remains a superb choice; but as an automated background service for Autovist, no.

Currently, I’m uncertain about how we will implement auto-archiving. Here are a few notes that could shape the design:

guid = SecureRandom.random_number(10_000_000_000).to_s(36).upcase
# 1D1ZK04
wget -nH -P "#{guid}" -p -k https://autovist.com

The above pseudo code will create a globally unique directory that stores all files needed to show the Autovist home page.  An associated database table will track: URL, domain, path, home directory (guid).

The server will be created on AWS, communicating with Autovist via webhooks.

More to come…

Chris Downey

Founder, VaxCalc Labs and creator of Autovist and the Vaccine Ingredients Calculator.

Author: Chris Downey

Founder, VaxCalc Labs and creator of Autovist and the Vaccine Ingredients Calculator.

Leave a Reply