Update of "Application Example: Distributed Search Engine"
Not logged in

Artifact ID: 843ad30c831cae99ff1d45c8d8a21ddb8a284a4e
Page Name:Application Example: Distributed Search Engine
Date: 2020-02-05 03:11:31
Original User: martin_vahi
Parent: bedb2039e6fa5bf2ffda166193e7b70ade1ac3fe (diff)
Next 4cf1857363b1d229053bc5ee881122ce348c7b92

The idea in this chapter has not been tested in practice yet. It's just a thought, a starting point for an experiment.

The Gist of the Idea

A document or part of a document resides at a Silktorrent packet. A search query calculates a rational number, a distance, between the query and the Silktorrent packet. The question to the network of nodes is: "Do You have a Silktorrent packet that has a MAXIMUM distance of L from the point that is determined by a search-engine specific, pre-defined, function with the following input parameters, param_1,...,param_N?" Some of the nodes on the network will lie, but the only possible, specified, answers to that question are:

Each node maintains its own, personal, table of node reputations. The query initiator asks the packet owner directly for the packet and verifies that the promised distance between the query and the packet match. In terms of search hops the nodes closer to the liar get higher penalty points than the nodes further from the liar. The rest is a matter of custom heuristics that can be very creative. The liars might lie only occasionally, at random moments or according to some heuristic or statistical distribution, according to instructions from censors, etc. The search engine might be designed to search for text, but the algorithm works also on other data types, for example, 3D shapes, maps, images, sounds, etc.

Partial list of Sources of Inspiration

Wild Thoughts About Implementation

...reside at a separate wiki page.

Some Related References