First, it asserts that AWS took Parler down to... benefit Twitter since AWS had just signed a deal with them.
I'm sorry, the idea of AWS actively helping a customer compete against another is laughable. They don't extend that courtesy to their own service teams!
I'll also point out that had Parler been a Grown Up Company and gotten a $0 Enterprise Agreement in place like responsible orgs do, this entire section would have been extended out massively:
I'd accept their framing of "they saw Twitter growing too fast and wanted to kill Parler in anti-competitive ways" if it weren't for, y'know. @SnowflakeDB kicking the crap out of Amazon RedShift but still getting MASSIVE assistance from @awscloud to improve further.
I'm also giggling at the fact that despite $300K a month in spend, Parler apparently didn't have a contract for committed spend in return for an across-the-board discount from @awscloud.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So there's a lot of confusion about what Parler being kicked off of Amazon Web Services (@awscloud) means. Let me do a quick thread to explain it to folks who aren't deep in the technical weeds...
You use an app (in this case, Parler). There's a web site you can use, and apps you can download onto your phone via Apple and Google. Those three versions of the app all talk to servers (big computers) behind the scenes.
In the Olden Days, getting those servers took months. Then you had to sign deals with companies to host those servers--they take massive amounts of power, they run hot so air conditioning is a big deal, and they need a *lot* of bandwidth.
I don't know that I can do @iancoldwater's response justice, but I'm going to assume that @peterskillman's question was sincere and answer it in good faith in this thread. What would I change about @awscloud's UX design?
A "v2" series of APIs for everything that is standardized between services. v1 will work forever (I know, you never turn off anything) but v2 will remove huge customer friction.
Hurl money at @iann0036 to implement Console Recorder as a first party service. The fact that someone else had to do this and got it done in a month or two of their own spare time? Bad look.
So! New Relic sponsors my stuff. (Thanks! You help keep the Duckbill Group's Spite Budget topped up, and that's profoundly appreciated.)
"You say mean things about New Relic but take their money, isn't that disingenuous?"
It would be if I wasn't exceedingly clear about this up front with all of my sponsors. Specifically "if I only say nice things about you because you pay me, nobody will listen to me."
"X" is a cool letter. Be sure that all of your EC2 instances start with it. #techtipsforParler
S3 buckets are finite resources, so be sure to use one bucket for your Lambda jobs. Make sure that the source and destination are in the same place, and automatically triggered. #techtipsforParler
What does it mean to work at IBM? A bunch of things that absolutely don't apply to a corporate comms role. Get any thoughts of being valued right the hell out of your non-coding head immediately.