God Bless you, Dan. I could kiss you right now -THREAD-

1.31.21 60 Minutes on CBS (shredding China, https://t.co/GO0A4skh92, 23&Me, Gov. Inslee (WA) and more - Watch it.. Not the FULL truth but enough to tell some people "Told ya."

Then Dan posts this vid👇

51 seconds long.
Depending on which numbers you go by...
Or MIL⌚️

🤔Graham is no longer head J Committee. Grassley is.
Did this make sense BEFORE?
Does it NOW?
On the East Coast.. It was already FREEDOM DAY when Dan posted.
Then we got this little dandy.
https://t.co/1taP5mek1I
Now, we've seen this one before.. but something was bugging me, so I pulled up the original and focused on the change.
https://t.co/1taP5mek1I
3 seconds were shaved off.
An interesting 3 seconds, since S3v3nt33n said they wouldn't use THIS phrase until after arrests.
That also puts extra emphasis on the "36."
Additional points brought up by anons..

-Silver

-Directive 51

- 👇
https://t.co/oftwWYuhzP
https://t.co/EU7FkzMFDC

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.