Well at least for the near future it would probably work like how people have to find torrents: different sites index meta data in their own data bases. Maybe

Well at least for the near future it would probably work like how people have to find torrents: different sites index meta data in their own data bases. Maybe with something like opentracker there could be an endpoint like /search that translates search phrases into a sparse column vector and looks up cosine similarity against that instances low dimensional space representation of the tf-idf against torrent hashes, those low dimensional space representation files can also be distributed in torrent file and as well as way to constantly update/compute new low dimensional space representation files as hashes are added. For example it would probably look something like what I do in [0] but as a compiled module linked into and accessed from [1] as well constant update/rebuild of ldsr files like [2] linked and kicked off from flags passed in [3] as new hashes come in. [0]: https://github.com/cinquemb/hackedteam-email-index-mining/blob/master/search_emails/search_emails.cpp https://github.com/cinquemb/hackedteam-email-index-mining/bl... [1]: https://erdgeist.org/gitweb/opentracker/tree/ot_http.c https://erdgeist.org/gitweb/opentracker/tree/ot_http.c [2]: https://github.com/cinquemb/hackedteam-email-index-mining/blob/master/mine_emails.cpp https://github.com/cinquemb/hackedteam-email-index-mining/bl... [3]: https://erdgeist.org/gitweb/opentracker/tree/opentracker.c https://erdgeist.org/gitweb/opentracker/tree/opentracker.c