Anonymous ID: 995b46 Nov. 27, 2020, 12:31 p.m. No.11809834   🗄️.is 🔗kun

Tl;dr, 1) keep working to convince people of election fraud with the evidence you've got, not with the evidence you're anticipating, 2) I've scraped more than 500 MB of archived NY Times election night/week data, worth checking out if you're a data type, 3) cross correlating vote counting irregularities in the NYT data with archived MSM election night broadcasts turns up great material for convincing normies of electronic voting fraud. (Could I get graphixanons to make this memeable/shareable for the masses?)

 

1) I've been lurking since back when Q first started posting on halfchan, but haven't posted till now. I prefer optimism have we counted how many times Q says "nothing can stop what is coming" but not at the expense of pragmatism. Evidence of voter fraud (all kinds) keeps growing like a tsunami, but sometimes tsunamis hit unpopulated areas and no one sees them. I like to believe that part of "The Plan" Q always tells us to trust includes exposing the tsunami of election fraud evidence/proof to the masses, but the only way I see that happening at the moment is through us anons and our information warfare. Trust me, I want as badly as the next fellow to wake up tomorrow and see the MSM gushing about Trump's incredible election fraud sting op and how he saved our nation. Whether or not you believe this will actually happen is irrelevant though… It hasn't happened yet and until/if it does we need to keep working to convince people that the election was stolen, using whatever facts/evidence they will take seriously.

 

2) I have some experience working with data (making probabilistic models for my PhD research) and I'm trying to get into data science for a career, so when I found out that the NY Times exposes their election results data, I thought it would be a good project to pull as much data as possible. Others have beat me to it with some of the data (e.g., all 50 states timeseries, or precinct timeseries for Philly), but I think I have compiled a lot of data that hasn't been passed around yet (i.e., precinct level timeseries for GA, FL, MI, NC, and PA, county level timeseries for the whole country, congressional, senatorial, and presidential timeseries for all 50 states). Since the NYT terms of service prohibit scraping their website, and I'm not a legalanon, I thought it would be wiser (albeit slower) to grab everything from the Internet Archive instead (actually, some data I couldn't have found without using the Archive, so that worked out better anyway). Anyway, web scraping is new to me, so the effort took longer than I would have wanted, but I guess better late than never, right? If you're interested, I've put everything on GitHub at https://github.com/d0ntw84f8/election2020-timeseries-data, which includes the data, some explanation of dataset fields, scripts used to extract the data, and a few simple analysis examples (in Python) to get you started.

 

3) In the process of looking through the states timeseries data (this particular data has been around for a while now), I discovered several instances where Biden and/or Trump's vote counts dip down instead of up on some of the state totals. Others have looked at this in more depth, including the anon who estimated the number of votes stolen from Trump (perhaps someone can reply with a link…I can't remember where I saw that interesting analysis). This is really crazy to me as a numbers person, but your average normie needs something a bit more tangible. For most, it's all just too "wacky" and completely out of touch with their experience. How do we convince people our numbers-based conclusions are real or make sense? One answer: show them something familiar, video/still captures of glitches in the MSM election night broadcasts!

 

1/3 continued…

Anonymous ID: 995b46 Nov. 27, 2020, 12:33 p.m. No.11809846   🗄️.is 🔗kun   >>0019 >>0093

…continued

 

I was inspired by the powerful live broadcast video clip from this excellent presentation on electronic vote counting vulnerabilities and proof of their exploitation: https://youtu.be/ficae6x1Q5A?t=1994. The video clip shows an example of vote-switching where ~600 votes are taken from the 2019 KY republican gubernatorial candidate and switched live on cable television to the democrat candidate (but you couldn't see it unless you were really fast!). It turns out that a couple similar examples have been discovered the 2020 presidential election (I think the Gateway Pundit published these examples), but if you look at the NYT data, there should be many more. So, I went hunting for video evidence of the glitches that I found in the NYT data and I rediscovered every glitch in the MSM broadcasts (at least, every glitch where the vote counts showed up on the broadcast chyron for the right state at the right time). Below, I'm listing the examples that I found. This is just the low hanging fruit, however…I'm sure there are numerous glitches I missed. I'm not good at taking video clips or screen captures to make gifs and memes out of this material, so I'm appealing to you anons to help simplify the graphical presentation. I think this sort of thing could be very useful for redpilling folks as Sidney Powell's lawsuit(s?) heats up.

 

Okay, so here are the archived CBS and CNN broadcasts that I dug through:

CNN: https://archive.org/details/CNNW_20201104_000000_Election_Night_in_America

CBS1: https://archive.org/details/KPIX_20201104_000000_CBS_News_2020_Election_Night_–_America_Decides

CBS2: https://archive.org/details/KPIX_20201104_073500_CBS_News_2020_Election_Night_–_America_Decides

 

And here is what I found. Notice that the glitches occur in both battleground and non-battleground states, plus some glitches are actually in Trump's favor. Also, some of this stuff may be caused by human intervention/mistakes rather than an algorithm, but the really fast glitches are hard to explain as human manipulation.

 

Pennsylvania:

CNN: 6:10pm, 6:25pm PST

CNN: 8:08pm, 8:09pm PST

 

Virginia: (check out further analysis at https://github.com/d0ntw84f8/election2020-timeseries-data/county-level-president)

CBS1: 8:51pm, 9:17pm, 9:23pm, 9:39pm PST & CBS2: 11:41pm PST

 

Georgia:

CNN: 6:50pm, 6:54pm, 7:01pm, 7:42pm PST

CBS1: 9:16pm PST & CBS2: 9:20pm PST

CNN: 10:08pm, 10:15pm PST

 

Florida:

CNN: 4:57pm PST (this is a small one, that appears as a questionable dip in the imprecise (due to rounding error) NYT data)

CNN: 6:40pm, 6:41pm PST (this glitch actually favors Trump…useful for redpilling dems?)

 

New Jersey:

CBS1: 7:21, 7:32pm PST

 

Here are a couple states where I only found one video snapshot and need a second one to verify the NYT glitch…

 

Minnesota:

CBS1: 8:42pm PST is the peak in vote counts, but then I need to find video of an expected drop in votes over the next ~15 minutes

 

New York:

CBS1: 8:??:-8:31pm PST (I just need to find a clip to check between 8:23pm and 8:29pm)

 

2/3 continued…

Anonymous ID: 995b46 Nov. 27, 2020, 12:34 p.m. No.11809852   🗄️.is 🔗kun   >>9929

…continued

 

Based on the NYT data, there should also be smaller vote dips (i.e., the number of votes for a candidate, usually Trump go down after an update) in the following states (but I haven't hunted for video of these yet):

 

Massachusetts:

has a small Trump dip, approx. -1300 votes @ 6:28pm PST (hard to find because the drop is so short-lived)

South Dakota:

has a small Trump dip, approx. -800 votes btwn 8:38pm and 8:40pm PST

South Carolina:

has a small Trump dip, approx. -1000 votes btwn 5:47pm and 5:52pm PST

Montana:

has a small Trump dip, approx. -2300 votes btwn 3:53am and 7:08am PST (11/04)

Kentucky:

has a small Biden dip, approx. -1800 votes btwn 5:52pm and 5:55pm PST

Kansas:

after 5:50pm before 6:05pm PST (Biden dip)

after 6:31pm before 6:50pm PST (Biden dip)

after 7:06pm before 7:08pm PST (Trump dip)

after 7:56pm before 8:00pm PST (Biden dip)

 

That's all I've got for now, hopefully someone here can pick up where I left off while we wait for Q to save the world!

 

3/3 End.