The Church is meticulous about good record keeping (which is what makes them so good at genealogy in the first place), and every official member of the LDS church has a unique member identification number, used for things like tracking donations, ordinance records, and, of course, genealogy. Nowadays, the vast majority of these records are digitized and you can access them online through Church-owned-and-operated websites. If you happen not to be in the system yet (maybe you were baptized in the jungles of New Guinea and have only just made it back to civilization), it's pretty simple to meet up with a bishop or clerk who can verify your paper records and tell you what your membership number is, which will let you set up an account on Church websites.
So, to summarize, the Church knows who its members are, and knows how to associate them with online identities. When one of them wants free access to Ancestry.com, it's basically the same process as "Sign in with Google" and such- you tell Ancestry that you're LDS, Ancestry asks the Church's servers if you're telling the truth, and the Church's authentication system teels Ancestry to let you in.
You ask the membership clerk of your ward for your membership number, which you use to upgrade your familysearch.org account to an LDS account. Then ancestry.com uses OAuth to get access to your familysearch account.
Amazon now has Cloud Player Premium, which is very similar to iTunes Match.
"Import your music collection - even music purchased from iTunes or ripped from CDs. All imported songs we match are instantly made available in Cloud Player and upgraded to high-quality 256 Kbps audio."
Are you still limited to method bodies? It seems reasonable that the method signatures and object layouts couldn't be modified because that would invalidate a lot of code already in memory and that may already be optimized.
I have received the following email 6 times, edited to remove referral code and Bitcoin address:
"Dear Sir or Madam,
A few hours ago the Bitcoin trading website Mt Gox has been hacked. Malicious individuals have been able to obtain a database containing usernames, email address and encrypted passwords. This information has been posted publicly on the internet.
As a Bitcoin supporter I'm now sending a message to every email address contained in the hacked database. This is to warn you that your username, email address and password have been leaked. I therefore strongly advice you to change your passwords. If you have used the same password on different websites it's highly recommended to change your password on all of your accounts!
For a more secure alternative to Mt Gox, the community appears to be moving to TradeHill. So this is no reason to lose faith in Bitcoin itself. It must be seen as a warning that not every website can be trusted with your data however! Their link is http://www.tradehill.com/?r=XXXXXXX (Note: You can remove the Referral Code when registering if you want!) This is certainly not the only website where you can exchange Bitcoins, also check out http://www.thebitcoinlist.com/dp_bitcoin/bitcoin-exchange/
A Bitcoin supporter
If the sender is reading this, your script works (too well), and the warning was received 2 1/2 hours after the one from Mt. Gox, so you probably should have saved yourself the trouble.
The From headers shows the email is sent from Bitcoin@unknown.com. However, digging into the headers it is actually coming from gXXXXXXX@bXXXXXXXXXX.gXXXXXXXXXXXXX.com (trying to give the guy some privacy, since he's trying to be helpful, but this way others who get the message can correlate it).