3 ms·
I always had this idea of a distributed search engine that uses free CPU time and bandwidth on client machines for crawling and indexing. The code could either
by BjoernKW 11y ago
I always had this idea of a distributed search engine that uses free CPU time and bandwidth on client machines for crawling and indexing. The code could either be distributed by <script> tags or as browser plugins
The problem is however not so much if it's technically feasible but why users should contribute their CPU time and bandwidth in the first place (particularly on mobile where both are scarce).
I suppose enterprise environments might be more amenable to such a system than consumer applications, particularly because most office PCs don't use most of their CPU time anyway. The question is what exactly to do with distributed computing capabilities in such environments.
- koesterd 11y agoI think YaCy[1] is similar to what you describe. [1] http://yacy.net/en/index.html http://yacy.net/en/index.html
- BjoernKW 11y agoYes, pretty much. This never took off though, to a large part because the UX sucked and the search results used to be terrible. It's a classic chicken-and-egg problem: The search results get better with more users but you can only hope to acquire users if the results are any good right off the bat.