Earlier quoted context omitted.
IANAL and I'm not saying I disagree with your conclusion, but I do think the case is more interesting than just AWS booting a malicious customer (with regards to their TOS). > there's the fact that AWS doesn't host Twitter's feed This is funny (as in, LOL funny) to point out because it makes parler seem completely inept, but it's only technically correct. They just negotiated a fat contract to host twitter, and that'…
> parler can make an interesting case about AWS picking a winner and damaging a loser Parler made this specific allegation under the Sherman Act. It was rejected because "Parler...proffered only faint and factually inaccurate speculation in support of a Sherman Act violation. AWS, in contrast...submitted sworn testimony disputing Parler’s allegations." That said, Parler "has not yet had an opportunity to conduct disc…
Well, tried to. They didn't do a good job of it at all. What they actually alleged (relevant towards this theory) was:
* There was set to a mass exodus of Twitter users to Parler
* AWS also hosts Twitter
... They didn't even allege that AWS conspire with Twitter. Sure, they don't have any evidence of that conspiracy without discovery, but they didn't even allege a fact that could be proven with discovery.
These two facts are supposed to sustain the theory that AWS had no other reason to kick off Parler other than a conspiracy to keep Twitter the dominant platform. Despite the complaint itself opening up by alleging that AWS kicked off Parler because Parler espouses conservative views and later conceding that Parler knew that its content violated AWS's terms, albeit Parler was attempting to rectify it.
There's another issue with Parler's claims that I haven't seen anyone else bring up: if Parler was expecting the influx of Twitter users as a result of Twitter banning Trump, how would kicking off Parler keep these users on Twitter or otherwise buttress Twitter's dominance?