sorry for barging in but can't this be avoided by either strict naming conventions (i.e. the name.year.quality-team used by torrents, but really enforcing it this time) and/or tags, and allowing multiple hashes to point to the same files?
or "tag" hashes to point to the real hashes of the wanted file (thus avoiding giving a single file multiple "valid" different hashes) that way a name or a tag search could result in a list of (real names, hashes) pairs and allow the search engine to be distributed as well. I'm unaware of anything that is currently doing this, but i guess it must be already used by few of the big DHTs. my two Agorot, - nir On Mon, Jul 16, 2012 at 12:36 PM, James A. Donald <[email protected]>wrote: > On 2012-07-16 10:10 AM, Tony Arcieri wrote: > >> I'm hacking on this regularly enough I'd like to officially announce it >> here: >> >> https://github.com/tarcieri/**cryptosphere<https://github.com/tarcieri/cryptosphere> >> > > > As I understand the design, immutable data is identified by two non human > readable keys, one of which is more secret than the other. > > Ignoring the issue of secrecy for the moment, this is roughtly equivalent > to bittorrent magnet link. > > But for bittorrent magnet links to be useful, and for immutable data to be > useful, we need mutable widely available directories, such as pirate bay, > directories that can be efficiently searched using human readable terms - > directories that must be protected against spam, while allowing lots of > people to add to them. > > ______________________________**_________________ > p2p-hackers mailing list > [email protected] > http://lists.zooko.com/**mailman/listinfo/p2p-hackers<http://lists.zooko.com/mailman/listinfo/p2p-hackers> >
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
