BIG NEWS: COUNTERFEIT FULTON COUNTY GEORGIA BALLOTS. On a tip, our operative entered the Fulton County (Atlanta) Warehouse and took this series of photos: THESE ARE FAKE BALLOTS (note the quantity):

https://t.co/toCAMeoDpD
https://t.co/YdI5ZMCl2O
https://t.co/ngsBGorsAA
https://t.co/VCcL66t14d
https://t.co/3O9pAwJzYK
https://t.co/GuwdbpseYC
https://t.co/pHp4yYoPFV
https://t.co/55NHU05Pbt
https://t.co/mG2TN3GlLE
On Wednesday afternoon in the Georgia Senate Judiciary voted to have these ballots inspected. What happened next?
Rented Enterprise moving vans pulled up to the warehouse and began loading up. I will post that video promptly.
And then, a shredding company was engaged. They shredded everything. Not just a normal shredding either. They did not shred into long strips, or even tiny confetti: they did military-grade shredding down to tiny spitballs.😂🤣😂🤣🤣😂🤣😂🤣😂🤣😂
The video of the enterprise van is too big for me to upload right here. But trust me, there is a video of enterprise moving vans pulling up at 10 o’clock at night, after the Senate subcommittee voted to investigate the stuff, and they got loaded up.
Oh, I guess I should mention: we grabbed samples of the fake ones.😂🤣😂🤣😂🤣🤣

More from Politics

1/ Imagine that as soon as the referendum result the EU announced that it was looking forward to the end of free movement of UK citizens in the EU


2/ Imagine if the EU said finally all those retired Brits in the EU27 could go home

3/ Imagine if the EU said finally all those Brits in the EU could stop driving down wages, taking jobs and stop sending benefits back to the UK

4/ Imagine if the EU said it was looking to use UK citizens as “bargaining chips” to get a better trade deal

5/ Imagine if the EU told UK citizens in the EU27 that they could no longer rely on established legal rights and they would have to apply for a new status which they have to pay for for less rights

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.