A fucking 8th grader can write a program to tally votes. It's like Computer Science 101. So this was definitely on purpose.

My personal theory is that Jack Dorsey and the other tech giants decided they could steal a country, and that's exactly what they planned to do.

Think about all the oddly concerted efforts to constrain trump's message.

Now then, imagine how complicated it would be to rig an election across multiple states on the fly, and make it seem on the surface as a plausible win. Then to cover their tracks.

However, they truly underestimated how much trump was going to win by, and the bullet was already screaming down the barrel. The battle ground states weren't, they were complete trump land slides.

Oh but trump was way down in the polls, the fact he lost by a percent is way over performance! Gah guys, see democracy works. Accept it and move on.

Except we didn't. We haven't, and every bit of their media gas lighting has gone for naught.

May have been that late night internet update they talked about.

Their human error was not anticipating the Red Tsunami.

Can you imagine any amateur coder using a floating point decimal to store vote tallies? That shit is the biggest red flag off the bat.

Thank you. Computers only do what they are told.

Actually, that's not a rule in software engineering, that's Mother Nature's rule. How many Liberals does it take to defeat Mother Nature. None have lived to tell...

We used to say "garbage in, garbage out" back in the day.

You sound like those Nazis in Requirements.

It's the same in manufacturing. I've tried explaining this to the production side but even some maintenance guys SWEAR there are magical fairies in the logic that make things happen.

I've spent hours investigating how some magical incident happens and it turns out, it's either someone overlooked needing an interlock for a rarely occurring situation or an individual flagged a sensor confusing the system.

Unless its skynet than the glitch is feature on the new patch

I write programs that tally numbers and then have a "bug" that distributes the counts logarithmically. That happens ALL the time.

Hahahahahahahaah

I am glad someone else brought this up.

Suppose we live in a universe where a vote counting machine is running software that, throughout the country, accidentally through some flaw in the code keeps initially giving Donald J. Trump some thousands of the votes (odd also that it is in these weird, non-specific packets of votes instead of individually) that Joe R. Biden earned only to inexplicably hours later switch those votes back for some reason to their proper place.

Even if, to the eventual tally, these numbers are correct (which is of course fucking ridiculous) why would ANYONE EVER USE THAT SYSTEM EVER AGAIN, LET ALONE SPREAD IT TO ALMOST EVERY COUNTY IN 60-75% OF THE STATES IN THE COUNTRY?

The only answer is that the eventual tally is not the correct tally, and the system was designed to slowly, and perhaps randomly, shift some of Trump's votes over to Biden in a subtle way in order to close a gap that is small enough not to be detected.

The real gold in this conclusion is that, for the most part, that means if the system relies on scanning paper ballots, then the original ballots should contain the original configuration of the votes. It makes sense to do this in places where you know the margin will be big enough that recounts, audits, or recanvasses wont be needed like VA, RI, NY, or IL because those aren't considered swing states.

Even so, the anecdotal evidence this time seems to indicate that the strategy was modified at some later point when someone realized that the vast majority of Trump voters were going to vote on election day, bringing about uncertainty in the numbers. They likely adjusted as best as they could, positioning themselves with outside contractors and supplemental, cruder methodologies to fix the final vote tallies depending on the state.

The election day numbers were larger than anything that they expected, so much so that most of those back-up methods were automatically activated such as the sharpie-gate tactic or the poll watcher intimidation and ballot harvesting. The plan was modified to have a triggerpoint, and that was the Fox News premature call for AZ which broke the red wave of momentum that was clear everywhere before that.

The haphazard call to stop was clumsy, as apparent by the ridiculous excuses by the respective state officials in WI and GA like 'we are tired' or 'there is a broken water pipe down the street'. They needed the time necessary to be free of watchful eyes to make the 4 AM drops, and they also needed to manufacture the difference associated with the replacement ballots that match the results in the subsequent 'glitches' which took each state over the top; after all, their crimes needed a false paper trail and they knew that most of the swing states were going to be close because they didn't want to plum too deep into the well of the 100s of thousands of dead and inactive voters that they needed. This explains the insane turnout numbers everywhere.

In MI, GA, NC, AK, and AZ they also wanted to get the totals up enough to flip the Senate with one or more of these races, as such the slow counting method allowed for fine tuning without the 'glitches', which is crucial because by then they probably noticed that the rest of the world has started seeing these software bugs as something more.

They are failing so misurably now because they have been caught somewhere, though I don't know where. They know that their shallow confederation of conspirators is fractured figuratively and geographically. A couple of captured members in custody, right now are probably being faced with the prisoner's dilemma of who will turn on the other first (which can work even if you only have one captive, if you convince them that you are holding one of their associates which could even be an asset.) The question is who has captured this person or these persons, and whose side are they on.

A confederation that survives on covert activity cannot rely on conventional forms of communication in order to conduct business, which means that with unconventional forms you sacrifice convenience. Inconvenient forms of communication aren't easy to rely on so the reasons surrounding suspected captive members will be hard to come by, and thus they might assume that it is a proper authority that captured that individual.

With this assumption in mind, why do I personally think they are failing: The answer is simple, Biden's AZ and GA leads are shrinking and NC has been called for Trump. These aren't coordinated moves, these are independent vectors moving on their own pretending like they were doing the job that they were originally tasked with as election officials. They are assuming the worst in their minds and at least some don't feel that the cause is worth it anymore.

MI, WI, AZ, NV, PA, GA, NC, VA, IL, and RI will all likely have some sort of external auditing process before the various Secretaries of State submit their final certifications, and for most of these states auditing was never well prepared for by the confederates because turnout was never supposed to be this high for Trump, whereas a low Trump turnout Biden landslide wouldn't be challenged and a modest Trump turnout modest Biden victory would have been relatively undetectable in the swing states.

Their sloppiness in MI, WI, PA, GA, NV, and AZ has raised enough red flags that the Supreme Court is going to have to intervene at some point beyond Justice Alito's order to segregate the ballots in PA that arrived after election day. These states have Democrat operated cities that are still refusing meaningful access to their facilities because these places are crime scenes and they haven't finished the crime or cleaned up the evidence. Partisan access gives reliable witnesses to either or both.

You don't need a genius to look at a map and uncover which areas are seeing the anomalous numbers.

Hmmm. I wonder if the name program comes from the act of what creates them? Programming? Or perhaps it originates from who does the work? Programmers?

Either way, yeah, programs are programmed by programmers to do their program by following the code written.

This is what I've been telling all my friends. If you don't know how to write code, apparently you don't know that a "glitch" isn't just that the computer spazzes and does whatever TF it wants for a blip, then goes back to normal.

Tell me about it. I was an aeronautical engineering student and had to pound programs in FORTRAN on mainframes. OMFG, the long nights.

I always tell my computing students: "You tell the computer what to do, not vice-versa."

Glitch is the term from computer games.

NPC and monsters in games have programmed behaviour. Glitch is whe they do not adhere , do something strange --> like they walk through the wall because there is bug somwhere in the assesmet "Is it wall here? Can I go?"

This does not happen in any COUNTING software. Because no couting alghorithms have BEHAVIOUR.

They just "I see mark here, I add number there". That is it.

As a programmer, I find it so frustrating when I make a minor typo in the code for my Mario game and it suddenly fabricates millions of fraudulent votes in favour of Joe Biden.

You'd think in critical vote counting software, the COUNTING part would kind of work???

Write code to redistribute the votes and the code will do that.

They were caught because of fraudulent ballots.

Confirmed.