zlacker

>>cebert+(OP)
Host an event you where you're hoping to co-opt third party developers into using and evangelizing your platform. Provide a lousy interface to navigate the event. Send cease and desist notices to those same developers when they try to improve it. Hmm.

>>tyingq+B1
Well, for one reason, having third-party apps for an AWS event that might confuse users about how official/genuine what they're saying is... could be a big security problem.

(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.

>>neilv+U2
> might confuse users

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.

>>london+Yj
That would be nice. But how would they check that the trackers comply?

Taking down has the advantage of being easy to enforce.

>>nine_k+qx
I think the enforceability of these things is roughly equivalent.