The Jab - Chapter 9

There is one inescapable, and ugly, truth: in order to fight an army, one has to have an army. But, how does one build an army when no one is allowed to gather together? How does one have a voice, when all dissenting voices are silenced on any mass communication system?

Well, what if we didn't need mass communication after all? What if we could find a way to massively coordinate one-on-one communication? This poses a technical challenge, but anyone who has used the internet for their entire lives knows that this is not impossible.

Systems get hacked. We know that. What some people don't realize is that the reason for the hack is simply to harvest personal information -- name, address, phone number, and email address. 

Emails have their set issues when you're trying to reach people. Obviously, there are lots of people who use a separate email address for sign in capabilities as they do from their day-to-day email. For some people the day-to-day email is their work email. Neither emailing an unattended email address or work email would be ideal. The unattended address would never be checked, and, in all likelihood, the work establishments filter out, or perhaps even read, emails prior. So what about phones numbers?

Phone numbers are hit and miss. The reason is because of the sheer inundation that many people have experienced from robocallers. Technically, my plan would fall into that, so it's fair to say that their instinctual ignoring of the call would be justified. Well, gosh darn it, that doesn't sound like a viable option straight out of the gate. Where does that leave us? Their address.

Addresses are an interesting case. Email addresses are purely digital; phones are have a physical presence (typically on the person or at a location where the person spends significant time), but there is a physical distance between those on either end; but addresses are only physical, which options up multiple options. The first option is the less intrusive approach: simply putting something into the mail. The other, which is massively intrusive, is to simply knock on the door. Both have their positive and negative attributes, but neither option needs to be written off completely.

I had my plan, and it was going to be in phases.
Phase 1: Acquire names and addresses of the people who are going to be "vaccinated."
Phase 2: Send mail.
Phase 3: Knock on doors.
Phase 4: Organize.
Phase 5: Strategize.
Phase 6: Confront.
Phase 7: Spread the word.

***

Phase one involved a high level of personal risk, but what choice did I have?

Conveniently, some set of hackers had actually infiltrated the vaccination database. The price was within my allowance, but how could I be sure that this was not a honeypot?

One of the contacts that I had gained throughout the use of the DWAs was a DevOps expert. He was an expert of spinning up and maintaining clouds of containers. This gave us access to "fake computers," as a non-technical person as myself would say, that could appear and disappear on a whim. He and I decided that this would be best. We set up a series of containers that would be able to talk to one another, and thus play a game of hot-potato with the information until we can extract it all into a safer document. As each container did it's own task of extraction, a new container would be spun up, the hand-over would occur, then the previous container would be spun down. It was our hope that this would obfuscate our operations just enough to not get caught prior to the vaccination event.

DeepStatePepe, the DevOps contact whose real name I did not know, was quicker than I had expected in setting up the environment. It went off without a hitch. The one additional risk, of which I am now unsure of why we took it, was to upload compiled list to the DWA repository. No one, and I repeat, no one was to download this list onto their personal computer. We just could not risk exposing any trackability to ourselves, even with the cyber security protocols that we had already established for ourselves.

Despite not being able to download the file itself, I simply took screenshots while the database was open. This gave me what I needed. And now would come the legwork.

----------------------------------------------------------------------
Index