#Thread: Though it's important to shed light on the ongoing humanitarian crisis in #Yemen, you could read this entire @reuters article (and most articles written about Yemen) and not know why this boy is starving or who is responsible for these conditions:

The boy travelled from Al-Jawf to Sana'a because al-Jawf is among "high intensity battlefronts" & is the target of repeated civilian airstrikes. https://t.co/1KlIN5ixTf

Also, roads are "damaged" because they're frequently bombed by US/Saudi airstrikes: https://t.co/0a8XFCQEsH
Shockingly, he's one of the lucky ones who managed to make it to a hospital.

Only 51% of health facilities are (barely) functioning: https://t.co/GBgKXM562t

And hospitals have been frequently targeted by airstrikes: For example: https://t.co/3Uto5dCKYE
International aid & donations are necessary for Faid & millions to survive because of the Saudi/US/UAE blockade that prevents Yemenis from trade and makes them reliant on aid instead. Before the war, Yemen imported 90% of its food; now, 80% rely on aid. https://t.co/iVF4fYAfAW
Famine hasn't been declared because the UN faces immense pressure from its top donors, the US & Saudi, who are also causing the famine in Yemen.

The US went as far as pressuring the UN to restrict aid to Northern Yemen, where 70% of Yemenis live: https://t.co/6Fk95cUkB9
Speaking of donors, "significant underfunding of the 2020 aid response" is due to Saudi & UAE not fulfilling their pledges.

"Those who. made the largest pledges...have so far paid only a modest proportion of what they promised." - @UNReliefChief

https://t.co/KNgQCoOO8G
Now, the Trump administration may designate the Houthis as a foreign terrorist organization, which would result in mass deaths: https://t.co/crLXjskWPp
I've said this for years, but in the case of Yemen, there's significant underreporting & misreporting. Read almost any article about #Yemen and you'll be confused about the agents & the causes.

@AkbarSAhmed's recent article is an exception. Please read it https://t.co/jIqso2dT4B
6 years into the US/Saudi war, most US-Americans still don't know that our government (under Obama & Trump) provides the weapons Saudi & UAE use, helps impose the blockade that's starving Yemenis, trains Saudi & UAE forces, & so much more.

This must stop https://t.co/v4LTwcIqaf
Here's what folks could do to help:
1. Write to your paper to help people understand US complicity
2. Organize with @Jehan_Hakim, @masspeaceaction & others: https://t.co/Lh73ngOJLt
3. Donate: https://t.co/uPutGXfPnt
4. Follow @HassanElTayyab & @ErikSperling for political actions

More from Society

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.