Fascinating, we (Tiny Review) are finding out about this through Google Alerts, haven't received a letter yet.

Interesting existential question. Just so all of you know, we're just having a bit of fun and not selling anything to anyone.

This was a 3-day hack to test a mobile version of our iPhone app (Tiny Review). It worked out pretty well; next week we'll convert our existing site tinyreviewapp.com into the same hmtl5 mobile format.

We tried this and found the response to it very minimal. It's probably better than nothing but I wouldn't expect it to do wonders.

FYI, here is another perspective on FB Connect signup: http://damurillo.tumblr.com/post/9214057988/disappointment-w...

You're right, although I expected a much lower drop-off. We'll post follow-on data soon(ish).

Yes, asking for FB permissions twice was tripping over our users however. What seems to work right now: login with Twitter or username/password, and add FB auth later when a user wants to share. This apparently doesn't feel the same as allowing FB on signup. Makes sense?

Initially we had a 2-step process: ask for email permissions only during signup, and for post permissions later when you actually wanted to share something. Unfortunately this confused our users even more - they didn't understand why they had to FB-auth twice. I guess that many don't actually read the list of permissions (although a short list is better than a long list).

Agreed, the headline comes from a real email from one of our users. It's just one of many pretty direct responses to (only) fb auth (I'm the author)