Bittorrent updating nodes
There needs to be a BEP for a way to host, serve and search metadata about torrents, not just their info-hashes. Fortunately, there is at least some related thinking in this direction: I don't think that it really goes far enough, as there is no standardization around how the data for searching will be structured, etc.Tribler is a research project of Delft University of Technology.I don't see how IPFS is significantly different in this regard. If we're trying to design new systems, we shouldn't design them with the exact same problems.What's the point of "decentralizing" if it just means another Google? Donating resources to a "traditional" scanning search engine is also probably doable.I was experimenting with p2p some years ago, and I considered extending the protocol, but I figured it would be more practical to work out-of-band, rather than relying on widespread implementation of an extension (which didn't seem that likely to me at the time).Well, to be fair, neither does HTTP, short of either name-services (DNS), or crawling-and-indexing.(...) Tribler is the first client which continuously improves upon the aging Bit Torrent protocol from 2001 and addresses its flaws.
To date, I'm unaware of an IFPS crawler-and-indexer search engine. https://github.com/ipfs/faq/issues/16Why is that fair? IPFS falls far short of being useful in a transformative way because it lacks this important feature.
But unlike Web, IPFS lacks intense linking and thus "citation ranking" (Page Rank-like). I don't disagree that having content discovery would be nice, but IFPS makes a pretty good case  about what it brings to the table over HTTP.
My point was that HTTP also has "zero out-of-the-box support" for content discovery, yet once search engines came out, we were fine. https://ipfs.io/#why I don't really believe the same network can carry its metadata.
This implementation relies on BEP 44 (Storing arbitrary data in the DHT) , which, together with the design of the DHT, does have some security implications . https://ipfs.io/ https://gist.github.com/substack/eadd13302d785dc13aac#file-r...
Seems to fit the same usecase as Freenet USK keys: https://wiki.freenetproject.org/Updateable_Subspace_Key They allow the holder of the private key to add new data and clients who know the public USK can get notified of updates.