🧵 ⚡️ #Navalny, in handcuffs, expects his second verdict in one day NOW, about to be ready any minute now. He’s joking about cucumbers he pickles in his cell. I will translate his SECOND last address in one day but here is the previous trial coverage
#Navalny is facing TWO court hearings today; one is happening now. I'm listening to his speech. He's trying to explain: he was not hiding from the court; he was in a coma. The whole thing is so absurd that it is impossible to comment. In a nutshell: they just want him locked up. pic.twitter.com/LXEdJX7rIm
— Zarina Zabrisky (@ZarinaZabrisky) February 20, 2021
The expert explained that the negative assessment applies to all persons depicted in the video, and the commentary contains a statement, the judge said.
More from World
@Ayjchan @K_G_Andersen @stgoldst @RozSofia @Ayjchan @K_G_Andersen please note that there were 11 infections in the Beijing 2004 leaks, not 8.
The 8 you are mentioning are for the main chain of infection with 3 levels from one primary case in April.
But there were 3 more primary cases for a total of 11 cases.
@K_G_Andersen @stgoldst @RozSofia All were linked to the heavily contaminated CDC P3 lab (the top P3 in China at the time).
The cases are typically separated between:
- The February ones (Cui and Ren) which seem to have been covered up by the CDC Institute of Virology. Also we only have pseudonyms for these 2.
@K_G_Andersen @stgoldst @RozSofia - The April ones-9 infections (1+8, officially the 'Beijing-Anhui Apr-2004 breakout'.
The official Chinese report only focussed on the April infections - keeping very quiet about the February ones. Here is the main April chain of infection.
Here is are the 9 from Apr 2004:
@K_G_Andersen @stgoldst @RozSofia And here are the 9 people infected in Apr 2004:
(4-22 in the title -> April chain with alarm raised on the 22nd):
@K_G_Andersen @stgoldst @RozSofia The WHO eventually correctly mentioned 11 cases:
https://t.co/a1HvuT0C8z
The 8 you are mentioning are for the main chain of infection with 3 levels from one primary case in April.
But there were 3 more primary cases for a total of 11 cases.
@K_G_Andersen @stgoldst @RozSofia All were linked to the heavily contaminated CDC P3 lab (the top P3 in China at the time).
The cases are typically separated between:
- The February ones (Cui and Ren) which seem to have been covered up by the CDC Institute of Virology. Also we only have pseudonyms for these 2.
@K_G_Andersen @stgoldst @RozSofia - The April ones-9 infections (1+8, officially the 'Beijing-Anhui Apr-2004 breakout'.
The official Chinese report only focussed on the April infections - keeping very quiet about the February ones. Here is the main April chain of infection.
Here is are the 9 from Apr 2004:
@K_G_Andersen @stgoldst @RozSofia And here are the 9 people infected in Apr 2004:
(4-22 in the title -> April chain with alarm raised on the 22nd):
@K_G_Andersen @stgoldst @RozSofia The WHO eventually correctly mentioned 11 cases:
https://t.co/a1HvuT0C8z
You May Also Like
First update to https://t.co/lDdqjtKTZL since the challenge ended – Medium links!! Go add your Medium profile now 👀📝 (thanks @diannamallen for the suggestion 😁)
Just added Telegram links to https://t.co/lDdqjtKTZL too! Now you can provide a nice easy way for people to message you :)
Less than 1 hour since I started adding stuff to https://t.co/lDdqjtKTZL again, and profile pages are now responsive!!! 🥳 Check it out -> https://t.co/fVkEL4fu0L
Accounts page is now also responsive!! 📱✨
💪 I managed to make the whole site responsive in about an hour. On my roadmap I had it down as 4-5 hours!!! 🤘🤠🤘
Just added Telegram links to https://t.co/lDdqjtKTZL too! Now you can provide a nice easy way for people to message you :)
Less than 1 hour since I started adding stuff to https://t.co/lDdqjtKTZL again, and profile pages are now responsive!!! 🥳 Check it out -> https://t.co/fVkEL4fu0L
Accounts page is now also responsive!! 📱✨
💪 I managed to make the whole site responsive in about an hour. On my roadmap I had it down as 4-5 hours!!! 🤘🤠🤘
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.