I think this is debatable, and we won't know the answer for a while. There are two possible trajectories here. 1/x

Trajectory 1: The attack becomes a signal event like Ruby Ridge or Waco, and extremists use it as a rallying point going forward. They will certainly try to do this, but there are some key differences.
Primarily, the tepid federal response (which is bad on most levels) doesn't compare to those events, where LE screwed up and people died as an unambiguous result of questionable or straight bad LE action rather than the melee situation here.
Also those cases were the result of proactive federal enforcement, as opposed to a clearly defense posture here.
Trajectory 2 is backlash. There's some growing evidence for that in the snap polls from the last couple days. See:

https://t.co/lOi6DCZ9CK

https://t.co/lOi6DCZ9CK

This won't affect the diehards, but it might suggest the event won't bring a lot new blood into the movement.
I suspect the backlash will grow if, as seems likely, more violence and/or intimidation occurs on Jan. 17 and Jan. 20.
It is possible, of course, that the trajectory will thread the needle between these poles, as the Unite the Right rally did. It didn't touch off a new golden age of extremism, but the pot has been simmering since then, with a longer-term effect.
And one point of value in these events, especially as the online crackdown grows, is that people meet and make connections IRL, some of which will be enduring connections.
On the other hand, a few people (and hopefully a lot by the end) are getting introduced to the idea of consequences for their actions, which may have a chilling effect.
Ultimately, none of this is likely to be clear until the Trump presidency is over, and maybe not then. But we've never had an extremist leader who was President (or ex-President) of the United States. And much will ride on what he does.
Ultimately, all bets are off until after the inauguration
Or more accurately, we can't assess the impact of this event until it's over, and it's not over yet.
Muting this thread because y'all can't stop feeding the trolls

More from Politics

Trump is gonna let the Mueller investigation end all on it's own. It's obvious. All the hysteria of the past 2 weeks about his supposed impending firing of Mueller was a distraction. He was never going to fire Mueller and he's not going to


Mueller's officially end his investigation all on his own and he's gonna say he found no evidence of Trump campaign/Russian collusion during the 2016 election.

Democrats & DNC Media are going to LITERALLY have nothing coherent to say in response to that.

Mueller's team was 100% partisan.

That's why it's brilliant. NOBODY will be able to claim this team of partisan Democrats didn't go the EXTRA 20 MILES looking for ANY evidence they could find of Trump campaign/Russian collusion during the 2016 election

They looked high.

They looked low.

They looked underneath every rock, behind every tree, into every bush.

And they found...NOTHING.

Those saying Mueller will file obstruction charges against Trump: laughable.

What documents did Trump tell the Mueller team it couldn't have? What witnesses were withheld and never interviewed?

THERE WEREN'T ANY.

Mueller got full 100% cooperation as the record will show.

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.