4 ms·
Google supports AND, OR, NOT and NEAR. There is an AROUND operator that is similar to NEAR. I think the way DDG can gain more traction is motivating top sites
by wslh 13y ago
Google supports AND, OR, NOT and NEAR. There is an AROUND operator that is similar to NEAR.
I think the way DDG can gain more traction is motivating top sites to enhance their local search pagerank. It's incredible how Google search restricted to Stack Overflow works better than the Stack Overflow local search engine. I wrote a rant about this at Challenging Google’s Search Engine [1].
[1] http://blog.databigbang.com/letters-from-the-future-challenging-googles-search-engine/ http://blog.databigbang.com/letters-from-the-future-challeng...
- lostlogin 13y agoIf double up votes were possible... This isn't uncommon though. Try search "yllow submarine" on Spotify. Is there any other thing this could refer to? Not only do they not have the Beatles, but the search is awful. Nearly as awful as Apple mail. I suspect the real problem isn't that others are bad - Google has spoilt us with how good it is.
- motdiem 13y agoIt's even more the case for local searches. Google routinely finds badly misspelled locations (from I gather interpolating with my location?) - for these kinds of searches, I don't think any of the alternatives comes close.
- dclara 13y agoIt's interesting that you are talking about "two-tiered search would decentralize efforts to improve algorithms". But you mentioned that "this solution does not need to be distributed: sites can share their local indexes and ranking algorithms with the routing search engine." Can you elaborate a little bit about why it's not a distributed solution if sites share their local indexes with the routing search engine?
- wslh 13y agoCan you elaborate a little bit about why it's not a distributed solution if sites share their local indexes with the routing search engine? Yes, sure. I use the concept of distribution in the sense of separating a process within different entities (search router and local searches). In the distributed case the "search router" queries other sites to determine the best results. For example, searching for code samples involved querying Stack Overflow, Code Project, Forums, etc. This approach is clearly expensive: you rely on the other sites speed, web service availability, etc. The non distributed approach is just receiving their algorithms and data and processing everything in the router search engine. Obviously this solution can be implemented in a distributed way inside the search engine but it is not distributed in the sense of distributing the process within different entities. In the two cases you are distributing efforts, one of the key goals of this approach because it is really difficult to compete with Google. Google "knows" how to give good results in diverse areas while in the proposed attack vector you rely on others for part of this optimization. A movie site should know how to give good results about movies while a site related to books knows about books. It's important to note that the vast majority of search results ends in relatively few sites, so if the top visited sites implement this approach Google search market share can be challenged. Obviously we don't really know if this approach will work in practice until we see it.
- dclara 13y agoThank you for your explanation. Now I understand better. But a distributed system is usually defined in the second meaning of what you said inside the search engine, instead of across different websites. I'm very interested in this topic because I've proposed my solution for how to improve search engines, not from algorithm point of view, but from systematic point of view. And making it fully distributed is the key. While you mentioned about the 2-level search and "receiving their algorithms and data ...", I don't think it's very feasible. Do you agree? So vertical distributed architecture across various industries is not a feasible solution. But we can do a horizontal distributed architecture which will collect data from geographic locations. In each location, there will be many different verticals. It's matter of time if Google cannot find a better solution, search engine will be improved in certain way.
- wslh 13y agoWhile you mentioned about the 2-level search and "receiving their algorithms and data ...", I don't think it's very feasible. Do you agree? Why not? I don't get it.
- dclara 13y agoBecause to my understanding, 2-tiered search means that the routing search engine scrapes data from the second level search engines and return it to the users. The second level search engines, e.g., Stack Overflow, are usually running by separate entities from the routing search engine, say DDG. If DDG does not own all the second level search engines, how can they get the local indexes and ranking algorithms from them? And even if DDG does get it, it's no longer decentralized any more. So what's the difference from Google?
- wslh 13y agoThe difference with Google is this: 1) Google quality of indexing doesn't have any competition yet. 2) They can calculate a page rank across different domains 3) No single entity can make the same efforts or is so smart to build a similar thing If you follow the 2-tier route: 1) Each entity takes responsability to optimize the quality of search locally. 2) They know their own domain or they can learn how to optimize their page rank at a local level instead of a global level So, at the end you have distributed the work of local optimization across different intelligent entities. For example, when you look at the Linux kernel or other open source projects you can count million of man hours that are difficult to have if you run a single entity.