Show HN: Hacker News Instant (3 hour project)
hninstant.com
hninstant.com
[Edit] Scratch that. Typing anything followed by a space character tends to make things crash. Why would this happen? I find this bug interesting. Let me know what the problem was when you fix it.
[Edit2] Okay looks like the problem may be with anything that needs to be url encoded.
[Edit3] I think the problem comes down to your call to encodeURIComponent in your search function and the behavior when the hash changes. Basically, we enter the search function when the hash changes. But then you call encodeURIComponent and assign the result to the hash. If the query contains characters that need to be escaped then the new value is different (meaning the hash changes), which means that your search function is going to get called ad infinitum.
In order to fix this I think you need to do two things. 1) Keep track of the in flight request unencoded and 2) if your search function is triggered by a hash change decode the query and compare it to your in flight request. If they are the same then you can bail out of the search function early. Otherwise you should cancel the in flight request and launch a new one.
It's not enabled by default because it's not as useful without autocomplete.
Oh well, this is better than what I would have had anyway.
Every single letter typed creates a new history item. It got to the point where so many history items were added that HN was pushed out of my history: I couldn't use "back" to get back to HN. I had to type in the URL to get to HN, then I had to find the comments page to get back here again to see the discussion.
I continued on looking at other HN stories. Once, I went back too far and landed on the HNI page again. I typed "L" as one does in Vimperator and Pentadactyl to go forward and get back to HN. The only problem was the text box stole my input, this resulted in a new query and a new history item, erasing, once again, HN's history item. I had to (again) type the URL to get here!
Will wait for MVP2.0
It's a warning. They aren't looking for startup advice, they just want to show a (hopefully) helpful project that may have a few bugs.
drop > dropb > dropbo > dropbox
Seems like ThriftDB is still in a pretty early stage of development so I doubt that they support this. But autocomplete is a solved problem so I'd be surprised if it doesn't make it in at some point.
You guys can probably do a pretty effective version right now but I imagine data about what people are searching for allows you to create a better autocomplete feature. And that data only comes with time.