(2/43)
John Sullivan / “#ActivistJohn” / "#JaydenX" Update
Our first thread about John was intended to help protect leftist protest communities from his harmful behavior. Since John’s little stunt at the Capitol during the DC #Insurrection, we have more to talk about.
(1/43)

(2/43)
(3/43)
1. General updates (since our 11/26 thread)
2. John’s harmful tactics/behaviors
3. What happened last week (DC, 1/6)
4. Next steps
If you haven’t read our 11/26 thread about John, we recommend doing so for full context.
https://t.co/eIyK0tr1oW
(4/43)
\U0001f6a8#SeattleProtests Community Alert:
— Rebellion Baby (@RebellionBaby) November 26, 2020
We have reason to believe that a likely infiltrator/agent provocateur by the name of John Sullivan, or \u201cActivist John,\u201d is attempting to insert himself in the Seattle protest community.
(sorry babe, long thread)
(1/23) #seattleprotestcomms pic.twitter.com/MuxQ74XCJo
Shortly after our 11/26 thread, Seattle protesters made it clear that John is not welcome at our actions or in our online spaces. He later changed his main account names from “Activist X” and “Activist John” to “Activist Jayden” and “Jayden X.”
(5/43)
(6/43)

(7/43)

(8/43)
1. Building mutuals as a form of credibility
2. Reckless group chats with poor opsec/infosec
3. Fixation on "spicy" actions, trauma porn
4. Grifting, mishandling of protester info
(9/43)
John is continuing to burn through new accounts, shed and develop aliases, and is still recklessly putting leftist protesters at risk. (When we say “John” is doing this, we’re more than confident that a small team is helping him.)
(10/43)
(11/43)

(12/43)
John has added people to signal/telegram chats — sometimes containing hundreds of people — with no vetting processes. Any serious protester will tell you that this behavior is suspicious and dangerous. Poor vetting allows fash, LE, and even …
(13/43)
(14/43)

(15/43)

This one’s tricky. For transparency, the Rebellion Baby team supports a broad diversity of protest tactics, including the smashy and spicy kind. We don’t peace-police, and we believe in people over property.
(16/43)
(17/43)
(18/43)
(19/43)

(20/43)
John’s “Insurgence USA" site is still thought to primarily be another desperate attempt for monetary gain and credibility. Most of his site content is ripped off from other online resources without credit attribution.
(21/43)

(22/43)

(23/43)

(24/43)
(25/43)
(26/43)
CW: gun violence
On 1/6, John was present and enthusiastically participating in the DC Insurrection. He streamed himself breaking into the Capitol with Trump supporters, as well as the shooting of Ashli Babbitt.
https://t.co/1F6b7l5GuF
(27/43)
Activist John storming the Capital maskless and standing over a woman and recording her bleed to death is weirdly unsurprising. pic.twitter.com/aAN5zzdANh
— Dublin (@DublinPDX) January 7, 2021
https://t.co/GKtlldazV0
(28/43)
Fucking shocked to see none other than grifter and opp John Sullivan AKA Activist John go on CNN and describe the death of the woman who was shot in the capitol. pic.twitter.com/rvJ04josEH
— max curtis (@MaxGeopolitics) January 7, 2021
More from Politics
You May Also Like
There are many strategies in market 📉and it's possible to get monthly 4% return consistently if you master 💪in one strategy .
One of those strategies which I like is Iron Fly✈️
Few important points on Iron fly stategy
This is fixed loss🔴 defined stategy ,so you are aware of your losses . You know your risk ⚠️and breakeven points to exit the positions.
Risk is defined , so at psychological🧠 level you are at peace🙋♀️
How to implement
1. Should be done on Tuesday or Wednesday for next week expiry after 1-2 pm
2. Take view of the market ,looking at daily chart
3. Then do weekly iron fly.
4. No need to hold this till expiry day .
5.Exit it one day before expiry or when you see more than 2% within the week.
5. High vix is preferred for iron fly
6. Can be executed with less capital of 3-5 lakhs .
https://t.co/MYDgWkjYo8 have R:2R so over all it should be good.
8. If you are able to get 6% return monthly ,it means close to 100% return on your capital per annum.
One of those strategies which I like is Iron Fly✈️
Few important points on Iron fly stategy
This is fixed loss🔴 defined stategy ,so you are aware of your losses . You know your risk ⚠️and breakeven points to exit the positions.
Risk is defined , so at psychological🧠 level you are at peace🙋♀️
How to implement
1. Should be done on Tuesday or Wednesday for next week expiry after 1-2 pm
2. Take view of the market ,looking at daily chart
3. Then do weekly iron fly.
4. No need to hold this till expiry day .
5.Exit it one day before expiry or when you see more than 2% within the week.
5. High vix is preferred for iron fly
6. Can be executed with less capital of 3-5 lakhs .
https://t.co/MYDgWkjYo8 have R:2R so over all it should be good.
8. If you are able to get 6% return monthly ,it means close to 100% return on your capital per annum.
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.
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.