And will that stand up?
(For example, you just know that some users would be willing to enter their IAM credentials when prompted at some point.)
There's also all the marketing data leakage, and access to the users to promote other companies' products, or maybe even get an affiliate/intermediate cut for AWS sales that were already AWS's leads to begin with.
Or at least always be prepared to get the rug pulled. I also have a hard time to understand why anyone would use their free time and energy to help a billion dollar company to get richer for no reward.
Then, on the day of the event, I drove 5 hours to the conference hall, but when I arrive there, none of the staff know anything about an AWS event! there is some other event happening for high school teachers, and that's it. I double and triple check the AwS event website. It's still up, and still has the same location and date. I call our rep, who reaches out to some other people and eventually gets back to me and tells me the event was cancelled!
Why did nobody reached out to let me know, and why didn't they even take the website down! it was bizarre. I really had thought I was going insane.
I had brunch, and then drove back another 5 hours. At least I got reimbursed for the mileage!
I don't see how this tracks when it's scheduling for an AWS run conference. The source of data for the event schedule is AWS.
> no reward.
The reward for some is just having a better UX for planning their attendance.
The email from AWS could easily have said:
We request you put a notice on every page saying "This is a copy of data from <Official Site>. Please check there to verify correctness". If you don't want to add such a notice, then we respectfully request you take this data down, since it is against our terms to host the data in this fashion.
But glad to see they took care of these terrible grifters! How dare they make the exprerience for our guests/user better! /s
tbf, they've invested a lot in messing up the UX the last 6 years, so maybe this is part of that effort..
Loved aws from the start and still use the platform but frankly it’s expensive, feels very hard to get help from and when there’s alternatives it’s hard to want to continue to reward their mediocre customer experience.
It’s about time to take some of the learnings and prepare to slowly move away from them again.
I will add that, if it is on company time, I may use it as a networking opportunity.
Taking down has the advantage of being easy to enforce.
The C&Ds on Twitter offer no rationale for the takedown request (i.e. DMCA claims or whatever). It looks like they're just "asking nicely" at this point.
I'm still waiting for someone to send a take-down notice to ToS's on major platforms. That'll be entertaining.
is that not how we all make presentations?
That's precisely what a cease and desist is: asking nicely, possibly with legal merit, possibly not.
Average tenure at amazon for corporate employees is less than a year.
- remember that Tuesday last October, when I spent 10 hours driving to ... AWS ... or
- remember that Tuesday last October, when I debugged my Flexbox CSS?
Again, it isn't "providing unpaid labor to AWS". It's "problem solving and exhibiting talents to others that are in your field". It's showing you have the skill to throw such a thing together quickly. It's a resume builder. And most importantly, what you seem to be missing, it's a fun challenge to some people.
If I stretched your analogy a bit, I would say it's like seeing a body shop do a shitty job on a car, and then buying $30 worth of tools and doing a better job in an hour than they did, then posting the video to Youtube to show all your fellow car enthusiasts.
There is no incentive to do so, on the contrary, the metrics for the SA are quantitative and focused on scale, not one-on-one interactions.
Of course, if you are a large customer, have interesting projects that can be used to improve one's promodoc, the SA has a good manager etc., it's another story.
I suppose at the end of the day, everyone receiving nastygrams could have a contract with AWS that prohibits disclosing the names of talks at their conference. That is a shitty condition to attach to a cloud service and should not be legal, but it probably is. (I wonder what speech conditions I agree to for receiving electricity at my house. I've never checked.)