In Passwords: Adam Dempsey voted up an answer.

An IRC user named AzureDiamond was famously tricked [1] into revealing their password, hunter2, in this exchange immortalized on Bash.org:

<Cthon98> hey, if you type in your pw, it will show as stars
<Cthon98> ********* see!
<AzureDiamond> hunter2
<AzureDiamond> doesnt look like stars to me
<Cthon98> <AzureDiamond> *******
<Cthon98> thats what I see
<AzureDiamond> oh, really?
<Cthon98> Absolutely
<AzureDiamond> you can go hunter2 my hunter2-ing hunter2
<AzureDiamond> haha, does that look funny to you?
<Cthon98> lol, yes. See, when YOU type hunter2, it shows to us as *******
<AzureDiamond> thats neat, I didnt know IRC did that
<Cthon98> yep, no matter how many times you type hunter2, it will show to us as *******
<AzureDiamond> awesome!
<AzureDiamond> wait, how do you know my pw?
<Cthon98> er, I just copy pasted YOUR ******'s and it appears to YOU as hunter2 cause its your pw
<AzureDiamond> oh, ok.

It's now commonly used as an example password or an inside joke in tech circles. I liked it so much I even used it here on Quora.

----
[1] The story may or may not be genuine, but it's genuinely famous.

See question on Quora

In Google Reader Shut Down (March 2013): Adam Dempsey voted up an answer.

Let's be clear that this has nothing to do with revenue vs operating costs. Reader never made money directly (though you could maybe attribute some of Feedburner and AdSense for Feeds usage to it), and it wasn't the goal of the product.

Reader has been fighting for approval/survival at Google since long before I was a PM for the product. I'm pretty sure Reader was threatened with de-staffing at least three times before it actually happened. It was often for some reason related to social:

• 2008 - let's pull the team off to build OpenSocial
• 2009 - let's pull the team off to build Buzz
• 2010 - let's pull the team off to build Google+

It turns out they decided to kill it anyway in 2010, even though most of the engineers opted against joining G+. Ironically, I think the reason Google always wanted to pull the Reader team off to build these other social products was that the Reader team actually understood social (and tried a lot of experiments over the years that informed the larger social features at the company)[1]. Reader's social features also evolved very organically in response to users, instead of being designed top-down like some of Google's other efforts[2].

I suspect that it survived for some time after being put into maintenance because they believed it could still be a useful source of content into G+. Reader users were always voracious consumers of content, and many of them filtered and shared a great deal of it.

But after switching the sharing features over to G+ (the so called "share-pocalypse") along with the redesigned UI, my guess is that usage just started to fall - particularly around sharing. I know that my sharing basically stopped completely once the redesign happened [3]. Though Google did ultimately fix a lot of the UI issues, the sharing (and therefore content going into G+) would never recover.

So with dwindling usefulness to G+, (likely) dwindling or flattening usage due to being in maintenance, and Google's big drive to focus in the last couple of years, what choice was there but to kill the product?

Personally, I think that there is still a lot of value a service like Reader could provide -- particularly in a world with increasing information overload coming at us from many different sources. But Reader at Google was pigeonholed as an RSS-reader explicitly, and didn't have a chance to grow beyond that to explore that space. But that's neither here nor there.

[1] See Reader's friends implementations v1, v2, and v3, comments, privacy controls, and sharing features. Actually wait, you can't see those anymore, since they were all ripped out.

[2] Rob Fishman's Buzzfeed article has good coverage of this: Google's Lost Social Network

[3] Reader redesign: Terrible decision, or worst decision? I was a lot angrier then than I am now -- now I'm just sad.

Edit: I left Google in 2011 so this is all my own speculation. I have no idea if this is the real reason or not, and there certainly could be more to the story. Don't take my word as gospel -- I'm looking at you, TNW (Former Google Reader product manager confirms our suspicions: Its demise is all about Google+).

See question on Quora

In Filemaker Pro: Adam Dempsey added an answer.

Depending on which version of FileMaker you are using, the OnLayoutExit trigger was added in FileMaker 11.

See question on Quora

In iOS 6: Adam Dempsey voted up an answer.

In no particular order:

• Do Not Disturb: Allow text messages from people on the Favorites list to bypass DnD in the same way as phone calls.
  
  
• Apple ID: Integrate the "Apple ID" as a system-level account in a manner similar to the existing Twitter and Facebook integration. Every app that needs access to your Apple ID currently requires the user to login separately. If a password changes this means re-entering it at least half a dozen times on every iOS device.
  
  
• Notification Center: Allow enabling/disabling Do Not Disturb, Airplane Mode, WiFi, LTE, and Bluetooth from the Notification Center instead of digging into the Settings app every time.
  
  
• Bluetooth Audio: Finally change the top bar icon for bluetooth headphones/audio devices from one that looks like the now-discontinued Apple Bluetooth headset to something more generic.
  
  
• Safari: Allow a user to toggle incognito mode on/off from within the app. Allow users to set up alternate "read later" services to work instead of the native "Reading List" integration
  
  
• App Store: Allow apps to auto-update in the background when on WiFi. Allow apps to include a demo video in their store listing.
  
  
• Newsstand: Allow users to remove/disable Newsstand or put it in a folder. Allow other apps the ability to update content in the background even if they aren't a part of Newstand.
  
  
• Apps: Allow apps on the same device to swap data and register handlers for particular types of data that other apps could then use as a conduit.
  
  
• iCloud: Allow apps to access documents created by other apps. For example, allow a third-party text editor to read/write documents saved into iCloud by TextEdit and vice versa.
  
  
• iCloud Storage: Give every customer an extra 5GB of iCloud storage for each iOS device activated on their iCloud account. This allows for every device to be safely backed up without running into data storage limits or requiring people to pay $20/yr for an additional 10GB of cloud storage.
  
  
• iTunes in the Cloud: Improve the reliability of iTunes Match/iTunes in the Cloud. It got a lot better on iOS 6 and with the iPhone 5, but playback can still be erratic at times.
  
  
• Lock Screen: Allow notifications to be cleared from the lock screen individually without unlocking the device.
  
  
• Calendar: Abandon the "faux paper calendar" look on the iPad and re-skin the app similar to the efficient look on the iPhone.
  
  
• Siri: Allow third-party developers to write apps that interact with Siri.
  
  
• Game Center: Allow users to find their friends using Facebook/Twitter, instead of using email addresses for everything. Nobody uses email to talk to their friends.
  
  
• Phone: Allow Skype and other approved VoIP providers to become the "default" phone application on an iPhone/iPod Touch and use all the features that comes with that access. Allow users to opt-out of voice service on their iPhones and solely use Skype. Allow making phone calls over any WiFi network.
  
  
• Messages: Integrate Facebook Messages directly into the Messages app. Sort out the issues where messages may go to the wrong device. Put the persistent history of every conversation over Messages on every device attached to the service (like Facebook Messages already does).
  
  
• iPhoto in the Cloud: Not specifically related to iOS, but Apple needs to launch a service that stores all of the photos in a user's iPhoto/Aperture library in iCloud for a yearly fee. All photos AND videos shot on iOS devices would automatically be added to this cloud archive.
  
  
• Misc: Integrate Dropbox as a system-level service alongside Facebook and Twitter. Allow apps to natively read/write from Dropbox.
  
  
• Misc: Find a better way to secure Apple IDs that isn't a password easy enough to type quickly on a small keyboard. Apple IDs control vast access to extremely personal data and the ability to purchase things via the iTunes Store/App Store/Apple Store (via EasyPay).
  
  
• iPod Touch: Again, not strictly related to iOS. Ship an iPod Touch with a cellular modem and data-only access to the Internet under an iPad-like integrated billing system. Allow the option to pay for data service via an Apple ID, instead of typing a credit card directly into the device.

See question on Quora

Adam Dempsey voted up an answer.

None. The questions have to be in the right order, so that they match the video slides back-projected onto the triptych of screens behind us. So I have a pile of cards with the questions and supplementary facts on them. During the afternoon I will have tried to familiarise myself as much as possible with the details of each question and answer so that I’m not too dependent on the cards (bad TV if my face is lowered all the time!). But the others playing the game have no script and no advance sight of the questions. But note Kristian Carter's reply below…

See question on Quora

In Facebook Friends: Adam Dempsey voted up an answer.

Yes.



Simply go to your activity log, and select "Friends" from the dropdown of what activity types to show. (At the time of this writing, you can go there directly by navigating to https://www.facebook.com/ [your_username]/allactivi ty?log_filter=cluster_8)

Then, scroll all the way down (you can use the timeline on the right to quickly click to the beginning).

Note that this also gives you a chronological ordering of all your friends, as requested in the question details.

See question on Quora

In Innovation: Adam Dempsey followed a question.

In iPhone Applications: Adam Dempsey followed a question.