4 ms·
hey thanks for the recognition, people. :) finally, all my problems are solved. this comment is here for hacker news karma points.
by gbmatt 5y ago
hey thanks for the recognition, people. :) finally, all my problems are solved. this comment is here for hacker news karma points.
- kingcharles 5y ago*throws karma at the screen*
- ivanche 5y agoHey Matt, would you consider making a search box (input with id="q") a bit wider? I can type only around 15 characters before the beginning of search query becomes "cut off".
- InfiniteRand 5y agoThe too small text box is also a pain when deleting the query in order to type a new one on mobile. A clear button would mitigate some of this pain although making the field larger would probably be sufficient
- dzdt 5y agoSeconded. I went to check out a few example searches and the too-narrow search bar is the first annoyance I found. The next annoyance was that the crawled index seems much smaller than google's or bing's. I looked for things I know exist on twitter, on an old wordpress blog, on obscure websites I frequent: forcing terms to not be skipped using + I could see that none of my test cases were in the index.
- benwills 5y agoI noticed there were IPs in the source code that seemed to reference yours, and mabye others', home IP addresses. I'm curious if you run any parts of either the crawling, indexing, or searching from home networks? I'm asking since I'm working on similar/different crawling problems that would make some stuff easier to just handle from the hardware I have at home, and have always assumed the provider would shut it down. Have you had any issues with that?