Disqus - Latest Comments for davehauenstein

Re: Ajax Search for your Tumblr

davehauenstein — Fri, 13 Mar 2009 16:23:48 -0000

I dont even have an ajax based search on my tumblr. I'm just confused as
to what i have to do with this...

Re: Ajax Search for your Tumblr

davehauenstein — Fri, 13 Mar 2009 16:10:25 -0000

Hey. I'm not really sure what' you're talking about, at all. Can you
clarify?

-Dave

Re: MIAMI90210 - Dave checking the mix during drum sessions Posted...

davehauenstein — Fri, 13 Mar 2009 00:24:47 -0000

As if i actually had any idea of what the hell i was looking at... Ahem!! I mean... yea, everything looked awesome.

Re: MIAMI90210 - This weekend at THE FORT studios in Brooklyn,...

davehauenstein — Wed, 11 Mar 2009 21:14:25 -0000

Killer! Steve McQueen would be happy such excellence was named after him. Rock that shit fer sure. Miami90210 will destroy all animals and fish that get in it's way.

Re: Hello! I'm Dave.

davehauenstein — Wed, 24 Sep 2008 22:08:42 -0000

I hope it's stuck in your head so you play it at work all day. I can't stop watching it. I've watched it about 25 times today. At least, with no exaggeration.

Re: Peter W Knox .com

davehauenstein — Wed, 13 Aug 2008 23:20:47 -0000

i agree with him. thank you liam.

Re: foo9 URL Shortener - Click On Tyler Blog

davehauenstein — Mon, 14 Jul 2008 13:22:58 -0000

right... so say you generate the word 'ass' based on an autoincrement ID, you checked it against a black list and your program throws a red flag, which means "generage a new hashed id!", since your algorithm is based off of an auto increment id, you cant just change the number because it could've been a past, or future, ID, right? So how would you handle it? I'm trying to tackle this right now...

Re: foo9 URL Shortener - Click On Tyler Blog

davehauenstein — Mon, 14 Jul 2008 13:04:43 -0000

shit was a bad example because you removed the 'i', so what about 'ass'... you get the idea...

Re: foo9 URL Shortener - Click On Tyler Blog

davehauenstein — Mon, 14 Jul 2008 13:03:45 -0000

what happens when this algorithm generates a word that shouldn't be in a url, like 'shit', etc... you dont want your service to generate foo9.net/shit, or anything of the like... what does your algorithm resort to in that case?