THREAD: tomorrow, Jan 25 is the global day of action for Yemen. Here’s a list of everything you can do to support it 🇾🇪👇🏼👇🏼

Show up in person if you can! there are protests happening all over the world. You can look at the action map here and RSVP to one! https://t.co/5jbHhdFY12
Register for the online rally happening tomorrow featuring @mrdannyglover, @jeremycorbyn, @CornelWest , @shireen818 and more! We will be highlighting the importance of ending US/UK/Canadian etc support for the war and the weight of the crisis! https://t.co/TYqcLX3zMJ
if you can’t get out to a protest, no worries, social media action is super important too! Use these super easy toolkits to take action online.
Here’s one the entire world can use! https://t.co/vAXlZDvKL9
Here’s one for the UK! thank you @STWuk ❤️ https://t.co/p6VoJZNqVG
do you know @blackrock finances the weapons companies that make the war in yemen possible? @nancymancias put this social media toolkit together to call blackrock out! send some tweets here: https://t.co/6r5yEV36sb
Join me in donating $10 (or more, or less, whatever you can do) to @yemenrrf. Yemen Relief is a Yemeni run and led group that gets aid to the most hard to reach places in yemen. They are the MOST trusted aid group in yemen. https://t.co/TQL1PeVLTM
if you are in the US, you should know that we are one of the biggest allies to saudi arabia in this war. You should call 1-833-STOPWAR to be connected to your congresspeople. say you don’t want the US to support or sell weapons to saudi arabia anymore.
follow these people/orgs who do great work on yemen and can keep you up to date on actions etc #worldsaysno #yemencantwait
@shireen818 @AishaJumaan @Jehan_Hakim @HassanElTayyab @YemenSource @yemenrrf @FCNL @STWuk @codepink @Students4Yemen @theactioncorps

More from World

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.
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.