lindvall

It really is a shame they haven't provided any mechanism, even if it were less convenient than the standard API interface.

I've seen a lot of talk from Twitter that "you can trust us", "we still have all of your tweets", but it really doesn't help much if there isn't any way to get at them. Has there been any discussion from Twitter that this is even on their radar as a near-term priority?

I was sort of surprised that the Library of Congress work did not include some sort of web.archive equivalent that allowed anyone access to the entire database — Twitter has shown a willingness to let other people solve hard problems it didn't want to, including when it pointed developers to a 3rd-party firehose for a while.

It's a shame he got himself into this situation.

I think more people need to realize that if you can only win a project by killing yourself, it isn't worth winning. So what if it means someone else gets the gig — it wouldn't have been worth it if that's what it took.

Also, if think copying-and-pasting code and forgoing defining constants are tricks that will save you time, You're Doing It Wrong.

Is there more to this than just a random anecdote? I feel like one of the nobodies that didn't seem to care.

What deficiencies of http://www.reversehttp.net/ is this trying to solve?

I've been happy with the reliability of reversehttp for all the testing I've done with it.

If you're using ruby, hookout does a great job running your rack app as a reversehttp endpoint: http://github.com/paulj/hookout

You may have better luck finding designers by going to where they are.

Start following http://onepagelove.com/ and contact people you like.

Find stuff on http://dribbble.com/ you like and talk to them.

Also, if you can find a designer that has basic proficiency with the technologies you're using, it will save you a world of pain of having to do the integration yourself. With every additional person involved in integrating a design you will lose fidelity.