1/ Hey guys, remember that time Steve Bannon ran an army of game virtual currency miners in Asia, for sale to westerners at discount prices, arbitraging attention for profit?

That was

2/ “The company was founded by former child star Brock Pierce, and Bannon was an investor. Bannon managed to convince Goldman Sachs to plow $60 million into a company that sold imaginary goods in an imaginary world.”

In 2020, Brock Pierce ran for President. Guess who...
3/ was Pierce’s campaign manager?

Brittany Kaiser, the fake whistleblower who left Cambridge Analytica in late March 2018 — right *after* it blew up.

https://t.co/KIPotgw3M9
4/ Guess who was all excited about today’s $GME activity? Steve Bannon and Russia shill, Jack Posobiec. They called it a “populist uprising against Wall Street.” That’s cool... just leftists, Steve Bannon, and Russia shills cheerleading for the same stuff. It happens...

More from Dave Troy

More from Finance

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.