2/
I'm going to post an essay I wrote, it's difficult on Twitler due to the character restrictions. It's about the formation of totalitarianism and group think.
Mass Formation, the Psychology of Crowds, and the Covidian Cult
Army of Shadows - 10 October 2021
1/
2/
3/
4/
1/ Isolation & lack of social bonds
2/ Lack of meaning-making & sense-making
3/ Free-floating anxiety
4/ Consequent free-floating psychological discontent, frustration, & undirected aggression.
5/
6/
7/
8/
Joining the struggle against an enemy, especially an invisible pathogen, provides members of a society in free-fall with a certain mental apparatus.
9/
Western societies have bestowed a kind of freedom without clear guidelines and many people have been cast adrift, searching for leaders and models
10/
11/
Subsequently, in- and out-groups emerge.
12/
13/
14/
15/
16/
17/
18/
19/
20/
3/ Social alignment and control under certain norms and values which constitute a collective consciousness.
The first element is very interesting. A secular religion appears to be emerging
21/
22/
23/
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.