#RepublicWontCompromise
bcz from day one @republic z with us
#RepublicWontCompromise
bcz @republic alwyz support ssr the truth
#RepublicWontCompromise
bcz @republic alwyz bcm the voice of truth
#RepublicWontCompromise bcz @republic iz that channel who only fights for ssr the truth
#RepublicWontCompromise
bcz there were many difficulties in the way of truth bt they r stick in their word
#RepublicWontCompromise
bcz they alwyz show their humanity in all matters
#RepublicWontCompromise
bcz they don't tolerate any dramma
#RepublicWontCompromise
bcz they alwyz stand for common ppl
we common ppl love @republic bcz #RepublicWontCompromise

More from India

A lot has happened in the last week re: the IT Rules, 2021! It may feel chilling, but mass awareness is the first step. This is an official thread of our resources on the Rules. Send it to anyone who wants to learn about them. This thread will evolve with updates over time.
1/n

On Feb 25, 2021 we published an analysis of the draft IT Rules, 2021. Alongside the analysis is a rundown of the contentious history of the Rules and the need for starting afresh on this vital conversation about platform accountability. Thread


On Feb 25, 2021, the IT Rules, 2021 came into force. On Feb 27, 2021, we shared with you our comprehensive deep-dive into the Rules - an overview of its contents, the “safeguards” it seeks to establish, and how they affect your fundamental rights.


We're also talking directly to young people and making sure that they are empowered with knowledge about their digital rights w.r.t. the IT Rules, 2021. Watch our video explaining the background of the Rules and the crux of the matter in 5

Currently, public analysis including our own provides a broad overview of concerns. Since new IT Rules are here to stay, we're also providing you with segmented explainers. Our simple video on how the new Rules will affect digital news

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.