madmotive

A very long article...

One of the most significant bits for me:

Seedcamp do plan to open source their funding documents.

This underlines to me why it's essential to have technical founders.

You shouldn't expect them to remember what was in the application. If they do remember something it will probably only be one line.

You get an email when you don't get in with a nice couple of lines explaining why.

Our email came in the early hours of the morning. I'd encourage you not to respond to it, at least for a few days. I felt compelled at the time to send a few paragraphs the next morning responding to some of the criticisms. Retrospectively it probably wasn't that all that useful to anyone.

It must be an exhausting 3 days for the YC team. I don't think there are enough hours in the day for them to call all the unsuccessful interviewees. Especially when some of them (like us) will want to take more of their time responding to feedback.

The quantity and quality of the questions and feedback you get in the short 10 minute interview alone is brilliant. Even though we didn't get funded it's had a massive impact on the way I think about things. I'd fly out from the UK to do it again even if there wasn't any chance of funding.

This is exactly how our "interview" went.

Despite being given the same advice by others that had been through the process we still foolishly wasted time preparing a short 1 minute pitch.

We might have had a better result if we'd invested more time in getting the user experience in our demo right and answering the one critical question - "Why would people want this?"

Don't make the same mistake we did. :)

What approaches do other OAuth providers take to this problem? Revoking all OAuth tokens on a password change/reset takes away a good chunk of the value that many people get from using OAuth.