verve

See https://forums.aws.amazon.com/profile.jspa?userID=300396

and

http://stackoverflow.com/users/1205140/verve .

Is anyone who works for Amazon listening?

I'm having immense trouble getting concrete answers to my questions about migrating from AMI 2.x + Hadoop 1.x to AMI 3.1.0 + Hadoop 2.4.0. This is particularly upsetting because:

1) Hadoop debug cycles are already long, and Elastic MapReduce debug cycles are even longer. 2) Amazon Hadoop 1.x seems to interact better with S3 than Amazon Hadoop 2.x; for some reason, small-file issues that did not appear in 1.x do appear in 2.x. This is just a shot in the dark, but I believe it has something to do with the mods hinted at in http://stackoverflow.com/questions/16403576/hadoop-number-of-available-map-slots-based-on-cluster-size . 3) Users are encouraged to used the latest AMI and consequently the Hadoop 2.x line because they are maintained more actively; however, I find most of the Elastic MapReduce documentation is a holdover from Hadoop 1.x. This documentation doesn't just require a light touch-up; much must be rewritten from scratch. 4) Debugging costs users money, so Amazon has an incentive not to help out as actively. Not conspiracy theorizing, here -- just noting the obvious.

After starting a new Twitter account (A) with an alternate email address I had myself emailed from my professional email address, I noticed the following phenomenon on my Who to Follow list:<p>[B: account of user I had emailed with my professional email address but not followed] Followed by [C: the Twitter account associated with my professional email address].<p>Thing is, C is not following B. C never followed B. I had simply permitted Twitter to retrieve my professional email address's contacts -- and now they appear as people C is following under Who to Follow for A? This error occurs for several of my professional email address's contacts.<p>Seems to me it's unwise to give Twitter one's email contacts. Has anyone else noticed this, and does anyone have more intel on it?

I once was able to use my browser's find tool to identify a line from a chat. Then Gmail introduced lazy-loading to chat history, and that became harder; my workaround was to click Print and then use find. But Gmail just recently did away with the print button, and I can't even do that.

Gmail team: the UX is worse; users are loading _text_, and usually not much, so why lazy-load every few lines? I understand I represent an outside use case, but I don't see that the new chat history is more inclusive in the use cases it addresses.