I just read a somewhat clueless post from one of those "moderate" Right Wing Instagram handles. You know, the sort that has a Sanskrit word in the name and is run by middle-class techie. After a significant amount of groaning, I decided to write this response about their...
More from Culture
.@bellingcat's attempt in their new book, published by
@BloomsburyBooks, to coverup the @OPCW #Douma controversy, promote US and UK gov. war narratives, and whitewash fraudulent conduct within the OPCW, is an exercise in deception through omission @marydejevsky @freddiesayers
1) 2000 words are devoted to the OPCW controversy regarding the alleged chemical weapon attack in #Douma, Syria in 2018 but critical material is omitted from the book. Reading it, one would never know the following:
2) That the controversy started when the original interim report, drafted and agreed by Douma inspection team members, was secretly modified by an unknown OPCW person who had manipulated the findings to suggest an attack had occurred. https://t.co/QtAAyH9WyX… @RobertF40396660
3) This act of attempted deception was only derailed because an inspector discovered the secret changes. The manipulations were reported by @ClarkeMicah
and can be readily observed in documents now available https://t.co/2BUNlD8ZUv….
4) .@bellingcat's book also makes no mention of the @couragefoundation panel, attended by the @opcw's first Director General, Jose Bustani, at which an OPCW official detailed key procedural irregularities and scientific flaws with the Final Douma Report:
@BloomsburyBooks, to coverup the @OPCW #Douma controversy, promote US and UK gov. war narratives, and whitewash fraudulent conduct within the OPCW, is an exercise in deception through omission @marydejevsky @freddiesayers
In response to @marydejevsky seemingly bad faith questions about Bellingcat on @unherd I've written a response providing details of where Bellingcat came from, and why it is like it is https://t.co/5rCsSwpcAm
— Eliot Higgins (@EliotHiggins) February 15, 2021
1) 2000 words are devoted to the OPCW controversy regarding the alleged chemical weapon attack in #Douma, Syria in 2018 but critical material is omitted from the book. Reading it, one would never know the following:
2) That the controversy started when the original interim report, drafted and agreed by Douma inspection team members, was secretly modified by an unknown OPCW person who had manipulated the findings to suggest an attack had occurred. https://t.co/QtAAyH9WyX… @RobertF40396660

3) This act of attempted deception was only derailed because an inspector discovered the secret changes. The manipulations were reported by @ClarkeMicah
and can be readily observed in documents now available https://t.co/2BUNlD8ZUv….
4) .@bellingcat's book also makes no mention of the @couragefoundation panel, attended by the @opcw's first Director General, Jose Bustani, at which an OPCW official detailed key procedural irregularities and scientific flaws with the Final Douma Report:
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.