oh, good times. I donÂ’t hear people talking about “leveling Fallujah” much anymore….

Prompt the best online shop on sale of Books.

from a personal perspective, i believe we need to implement more security features, for example transport encryption needs stepping up, and perhaps measures such as sharing information with trusted IPs from private trackers to prevent the M/RIAA from undertaking their sneaky shit on the public trackers.

It’s not true that I can stop my computer from uploading? I can’t turn it off? I can’t unplug it? I can’t run my torrent client in, say, a VM and reset the VM? How does cryptography help here? How does it prevent me from installing a client that lies about what it’s ratio is?

I agree there there are some who are more interested in making their content available, but the fact that they’ve put their content on BT shows they *are* interested in reducing bandwith and, so, are concernew with leechers.

The major reason for using BT is to share bandwith with those downloading/seeding.

What’s even more dubious is whether there is something like a perfect ratio and whether it would actually improve anything. If you force people to have a good ratio, even though most have asymmetric bandwidth, they’ll simply move on. There are many people who don’t really care about leeching anyway because they are more interested in making their stuff available than downloading themselves. I mean, just imagine, how would the world-wide web look like if it made use of ratios? “Sorry you can’t browse this website because you don’t have any homepage.”

You take your thumbdrive with it’s cargo of goodies and use a public computer to upload your crap packed in an unlabeled .rar with a few added nonsense files to confuse the hash to a public storage space. Then you go to your Listing space and list the url of your file and the name of your file.

A current incarnation of this is Rapid-Share for storage and Blogger.com for listing and commenting on the files. For security, each member could require an invite or something as we do now…and sense the uploading is done elsewhere, such as a cyber cafe or on public PC’s…

Personally, I’d like to see the cloud be able to act as a sort of informal torrent site. My client can define a local cloud (the definition of local is up for debate) and be able to show me new torrents in my local cloud, allow me to search against a cache of “local” torrents, etc. Because my cloud may not be the same cloud as that of a user three hops from me, with some smart caching, clients could do both “local” and “semi-local” searches or announcements by checking the files available on systems that are outside my cloud, but one “cloud-hop” from me. If connections and a count of available files was also available, the client could make multiple hops to find the clients in linked clouds with the largest caches. Search would be slow, but if you set up “triggers”, you could simply set up a system that identified matches, put them in an unstarted queue, and allowed you to either start them or list them as ignorable.

Comments?

Though that makes me wonder, could you get out of it if you say that your machine was mindlessly routing possibly copyright infringing content, like your isp’s routers do every day…