A story ...
In 1994, I was teaching U.S. history and American government at Oak Ridge HS in El Dorado Hills, California.
I had three bright students who were my TAs. The 20th anniversary of Richard Nixon's resignation was a few months away. I decided to have ... 1/
Before long, responses started to show up in my mailbox at school. 3/
"That a mountain can be made of a mole hill if one listens to media with a political agenda." 23/
Because as we've seen these last four years, the wrong person in the presidency can be catastrophic.
I hope we learn the lesson this time.
25/end
More from Government
'Peaceful transition to Military Power....'
Cannon
44
....heard around the world
NG - High Alert https://t.co/lfeSiUCCRB
We Will Never Forget
44
Stage is set
https://t.co/h6G3LCevII
Following the 44 trail of breadrumbs
https://t.co/PcX0uKUEUW
Cannon
44
....heard around the world
NG - High Alert https://t.co/lfeSiUCCRB
\U0001f4a5 BOOM \U0001f4a5
— R\u0113d.P\u012bll.Ph\u0101rm\u0101c\u012bst (@Red_Pill_Pharma) January 18, 2021
30 secs in - what do I hear?
\u2018Peaceful transition to military power\u2019
\U0001f1fa\U0001f1f8 MILITARY IS THE ONLY WAY \U0001f1fa\U0001f1f8 pic.twitter.com/9NPMT7N7Qy
We Will Never Forget
44
Stage is set
https://t.co/h6G3LCevII
The stage is set. Staged.
— JeLove (@LovesTheLight) November 7, 2020
Where? (the) Delaware.
10:44
Purple
First graphic in 98https://t.co/PKHlxp0rzS pic.twitter.com/XCx6pVQTHx
Following the 44 trail of breadrumbs
https://t.co/PcX0uKUEUW
Boom, Boom, Boom pic.twitter.com/ZcZXAgL0Qf
— JeLove (@LovesTheLight) August 13, 2020
About 3 weeks ago I contacted some folks in our government and wrote up a 33 pg rough draft outlining what I believed was taking place based on Data driving the narrative. For those that aren't sure how data science works, one takes raw data and attempts to find useful actionable
If I had a vision that outlined how a foreign actor killed over 50 percent of the young men in this Nation and the young girls were sold into slavery and there was only a 1 in 1000 chance I was correct, would it be worth sharing? Even if it meant no one would ever read my tweets
— BobbyPiton (@BobbyPiton3) January 1, 2021
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.
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.