Yes. That is exactly the *point* of open source. Don't like it? That's valid! Don't go open source. But to claim that @awscloud and others are somehow doing something underhanded is just flat out incorrect.
As @vmbrasseur points out, using @elastic or Kibana are now actively business risks that your company needs to manage.
And now a livetweet thread of a legal conference in the case of C21-31-BJR, Parler LLC v. @awscloud.
Parler suggests "AWS just has to flip a switch and Parler gets turned back on. Parler has been their customer for 2.5 years."
"They've met and conferred over some user content that violates not only Parler's user requirements, but also Amazon's." Yes, they'll do that, whether you want them to or not.
This one grabbed my attention. I spent two years at @TaosTech. They’re the reason I moved to SF, started my own consulting firm, and met some wonderful people. It’s probably the best job I ever had.
The @TaosTech technical interview is a thing of genius. It's standardized, modeled after SAGE levels, and reshaped how I think about hiring engineers.
At the time my biggest gripe with Taos was that they didn't have a role into which I "fit." With the benefit of hindsight that's not their fault; I don't fit in anywhere, which is why I'm here.
Let me point out some cloud magic tonight / say some nice things.
Normally I dunk on @awscloud in these threads, but today that puts me Nazi-adjacent. Plus AWS marketing's nerves are a little... frayed, so I fear for my safety.
The easy starting point is @awssupport. People are just rude as hell to them and they take it on the chin like the professionals they are. "Amazon is owned by a billionaire!" but he doesn't have to field the support tweets.
They also have to figure out when I'm trolling.
No matter how much you complain, they'll help you out. They're marvels, and good people too.
There's been a lot of noise lately about follower counts, so I'm pleased to leap into that and take a remarkably petty victory lap:
I now have more followers than the hardest working account in cloud, @AWSSupport.
Their milquetoast advice will work, but my terrible advice is way better! @AWSSupport: "Use RDS as your database!"
Me: "Use Route 53 as your database!"
AWS: "Lock down your S3 buckets to avoid data leaks."
Me: "Save money by storing data in other people's insecure S3 buckets."