#Alert: US Chargé d'Affaires Atul Keshap is under personal/professional attack after doing what diplomats from Germany, Australia, UK, Singapore & dozens of EU countries did before--visiting RSS headquarters as part of routine diplomatic outreach in India.

#Hindphobia? 1/

Amb. Keshap made no endorsement & met several other civil society leaders during his honorable service & tenure. But @johnsifton @hrw @MalikMujahid & Pieter Friedrich, an operative funded by an @IAMCouncil founder, are brutally singling out Keshap as no other diplomat before. 2/
This pattern of attacking #HinduAmericans public servants--appointed or elected--to deny them positions or have them fired/censured for being "too close" to the Indian govt. is a standard too frequently & exclusively applied to Indian/Hindu Americans in public service.
Many of the same actors targeting Amb. Keshap also maligned several Hindu candidates in 2020, elected reps & even staffers in the Biden campaign. Only Hindu Americans are targeted, alleging dual loyalty or "Hindutva" sympathies. Wrote about this here:
https://t.co/ypG86r0KwU
We stand with accomplished, committed public servants like @USAmbKeshap and condemn these ugly attacks and harassment. We stand with Amb. Keshap for carrying out his duties in exemplary fashion and doing what senior diplomats do every day.

Stop the bigotry. End #Hinduphobia.

More from All

You May Also Like

The YouTube algorithm that I helped build in 2011 still recommends the flat earth theory by the *hundreds of millions*. This investigation by @RawStory shows some of the real-life consequences of this badly designed AI.


This spring at SxSW, @SusanWojcicki promised "Wikipedia snippets" on debated videos. But they didn't put them on flat earth videos, and instead @YouTube is promoting merchandising such as "NASA lies - Never Trust a Snake". 2/


A few example of flat earth videos that were promoted by YouTube #today:
https://t.co/TumQiX2tlj 3/

https://t.co/uAORIJ5BYX 4/

https://t.co/yOGZ0pLfHG 5/
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.