Live data from Hacker News

Show HN: Didyougogo – An Altavista slayer

didyougogo.com

31–40 of 131 posts

Re: Show HN: Didyougogo – An Altavista slayer

#33
Interesting idea. Isn't it a little late to slay Alta Vista though? :)

I searched for apple. Top result was the archive.org macos that showed up here on HN recently, 2nd and 3rd were apple.com indexed 10s apart.

Then some odd results - though they do include the word apple on page just once. The imdb page for 12 Monkeys appears 3 times.

I guess you're not trimming duplicates? Seems like you need some way to weight rankings too.

I wish you every success - search definitely needs some competition.

Re: Show HN: Didyougogo – An Altavista slayer

#34

Interesting idea. Isn't it a little late to slay Alta Vista though? :) I searched for apple. Top result was the archive.org macos that showed up here on HN recently, 2nd and 3rd were apple.com indexed 10s apart. Then some odd results - though they do include the word apple on page just once. The imdb page for 12 Monkeys appears 3 times. I guess you're not trimming duplicates? Seems like you need some way to weight ra…

I "googled" Google using Did yougogo, and Google.com didn't appear once on the first page. Funny.

Re: Show HN: Didyougogo – An Altavista slayer

#37
Definitely some ambitious goals. There's nothing bad about that, but this has an awfully long way to go - e.g. searching for "hacker news" works fine, searching for almost anything else didn't find anything relevant. So while it's nice to say it can run in 1CPU / 1GB, I'm not sure it's very useful at that size (but I don't know how big it'd have to get to "break even" there).

Anyway, noted that it's a very early version, so good luck with it!

Re: Show HN: Didyougogo – An Altavista slayer

#40

I searched for "Cnn" and got 0 results. I searched for "Amazon" and got a five random results, including the IMDB page for "Rambo, Part 2." If this were really like AltaVista, I'd get 3 trillion results and have to use advanced Boolean logic to cut that down to the most useful 7,000 - so I guess having no results is sort of easier...

My boolean logic is here: [1] I'm sure it has flaws. Since the index had only five or six entries a couple of hours ago I set the matching to be wide instead of narrow. I'm also experimenting with loading the model with phrases, phrases and words or words only. I might have f-ed up the query parsing because of that. Remember, this is 0.1, fresh out of the press. Searching the tree is here: [2] Tokenization is here: […

[deleted]
Post reply on HN