AWS motion opposing Parler’s temporary restraining order motion lists a bunch of examples of direct threats they’ve been flagging and asking Parler to deal with since November. ht beta.documentcloud.org/documents/2044
Conversation
I suspect the seemingly coordinated action last week was the result of options set up since November by all who acted. Normally I assume businesses are pretty knee-jerk, but in this case risk managers would have started thinking exposure insurance in November at least.
2
1
13
I’d like to have been a fly in the wall at those meetings. What prompted them? The election itself? What led to saying, “hey the election result challenges could end badly, let’s start keeping an eye on Parler”
I’d like to know how those dots were connected.
2
1
6
Obviously outfits as big as AWS won’t have the bandwidth to monitor everything hosted on their servers for TOS compliance, so I guess there’s some process that puts sites that create exposure risk on a watchlist.
1
2
Replying to
at their scale, they don't bother making friends with edgelords of the community. They just move right to Willy Wonka suddenly quoting the contract they signed when caught stealing fizzy, lifting drink.
1
Replying to
They clearly did more. Look at the motion. They’ve sent over a 100 examples in show-cause type notices to Parler since November.
Replying to
True, it would be high viability. but after 15 years of hosting sites one expects the collection process is automated and the paralegal team has technical expertise to quickly collate the supporting documents with clients who might explore legal retaliation.
1
Replying to
It’s not collection. It’s *action* since November. They’ve been sending notices since November with specific examples of violations called out.
1
Show replies

