OK, let's start talking about the House's 80 page brief on impeachment. It really is an incredibly well-done piece of work. There are some things I'd do differently and some pieces I didn't love, but overall, it's very very good.
1) Why, on their own merits, Trump's conduct requires conviction
2) Why Trump's defenses don't fly
3) The Senate can convict Trump even though he's out of office
And 27 pages - again, a whole brief by itself - on "ex-President"
They're pretty confident that they can get whatever R-votes are gettable on the basics; after all, those Senators lived through the Capitol assault, they know what's what. But ...
More from Akiva Cohen
Looks like we need to spend some time talking about the Parler lolsuit against Amazon and why it's deader than a Mitch McConnell comedy special. They've brought three claims - antitrust, breach of contract, and tortious interference. None will survive. Here's why
Here's the meat of their intro: Amazon isn't being fair to us. They're holding us to a higher standard than Twitter - they say we allow violent content, but look what Twitter does!
There are a few problems with this approach. First, there's a factual problem: Twitter and Parler take very different approaches to moderation. Hell, *that's Parler's entire pitch.* So "we're the same as Twitter, why are you treating us different" isn't going to fly
ALSO, the hashtag was mostly people saying "these folks are calling to hang Mike
And ALSO also, did anyone notice any prominent right wingers complaining about losing tens of thousands of followers yesterday? You know why they did? Because Twitter has been active in deleting accounts that violate its TOS
Here's the meat of their intro: Amazon isn't being fair to us. They're holding us to a higher standard than Twitter - they say we allow violent content, but look what Twitter does!
There are a few problems with this approach. First, there's a factual problem: Twitter and Parler take very different approaches to moderation. Hell, *that's Parler's entire pitch.* So "we're the same as Twitter, why are you treating us different" isn't going to fly
ALSO, the hashtag was mostly people saying "these folks are calling to hang Mike
Five minutes of scrolling a search for #hangmikepence, a gallery: pic.twitter.com/40hsyJNK50
— Jawafawa (@jawafawa) January 11, 2021
And ALSO also, did anyone notice any prominent right wingers complaining about losing tens of thousands of followers yesterday? You know why they did? Because Twitter has been active in deleting accounts that violate its TOS
More from Culture
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.
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.