Holy $&#%! **Khaled Saffuri** is the source for these Jamal Khashoggi stories? Khaled Saffuri, longtime aide to US al-Qaeda fundraiser Abdurahman Alamoudi (currently in federal prison) and friend of convicted/deported Palestinian Islamic Jihad leader Sami al-Arian?? 😳😳😳

Just a reminder that Khaled Saffuri’s former boss, Alamoudi, was convicted for being the bagman in an al-Qaeda/Libyan plot to assassinate the Saudi Crown Prince. Yeah, totally unbiased observer! https://t.co/NEQH6aR85C
As @paulsperry_ discovered, Khaled Saffuri was the registered lobbyist for Alamoudi’s American Muslim Council front https://t.co/poLkDe5TwH
And as Franklin Foer at the New Republic revealed, when Khaled Saffuri opened up shop as the Islamic Free Market Institute, his first event was funded by Qatar’s Ministry of Foreign Affairs https://t.co/0v3LlAC92B
And as I reported back in 2016, one of the prime promoters of Alamoudi and Khaled Saffuri, his deputy at the time, was none other than then-First Lady Hillary Clinton. Alamoudi and Saffuri arranged the first White House Iftar for the Clintons. https://t.co/yL7cU4FmUK
Who brought his former boss, al-Qaeda fundraiser Abdurahman Alamoudi, to meet with then GOP presidential candidate George W. Bush and Karl Rove in 2000? That's right, Khaled Saffuri, the source of the media's recent Jamal Khashoggi scoops. Here they both are with Bush ⬇️
After Khaled Saffuri's former boss, al-Qaeda fundraiser Abdurahman Alamoudi, was convicted for playing bagman in the Libyan intel plot to assassinate the Saudi Crown Prince, Ken Timmerman wrote about Saffuri's extensive terror ties. N.B. for when you see media citing Saffuri.
Here's the WAPO reporting from when Khaled Saffuri's mentor and former boss, al-Qaeda fundraiser Abdurahman Almoudi, was arrested and later plead guilty as the bagman in the Libyan intel/Al-Qaeda plot to assassinate the Saudi Crown Prince.
Another @paulsperry_ discovery was that al-Qaeda fundraiser Alamoudi provided the start-up funds for Khaled Saffuri's Islamic Free Market Institute

More from All

Master Thread of all my threads!

Hello!! 👋

• I have curated some of the best tweets from the best traders we know of.

• Making one master thread and will keep posting all my threads under this.

• Go through this for super learning/value totally free of cost! 😃

1. 7 FREE OPTION TRADING COURSES FOR


2. THE ABSOLUTE BEST 15 SCANNERS EXPERTS ARE USING

Got these scanners from the following accounts:

1. @Pathik_Trader
2. @sanjufunda
3. @sanstocktrader
4. @SouravSenguptaI
5. @Rishikesh_ADX


3. 12 TRADING SETUPS which experts are using.

These setups I found from the following 4 accounts:

1. @Pathik_Trader
2. @sourabhsiso19
3. @ITRADE191
4.


4. Curated tweets on HOW TO SELL STRADDLES.

Everything covered in this thread.
1. Management
2. How to initiate
3. When to exit straddles
4. Examples
5. Videos on

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.