That is one of the main points. Some files are shared by thousands users and can be downloaded in seconds, but others are much harder to find, so that I like to keep the client on to help other people getting it quickly. I usually am annoyed when a file with a single seed reaches like 97% then it dies until the following day because the seeder had to turn off the PC, so I try to avoid this, especially since it costs me nothing as broadband is flat and the client runs on a machine that is always on.
EDIT: closes their browser is a bad way to phrase it. The problem is that the fact that they are seeding would be more in their face instead of hidden away in a notification icon on hover.
I wonder if intellectually "property" groups thought of this playing out.
a person i know (totally not me) only seeds the rarer things. for more popular stuff they only seed for a couple of days.
All things which your home gateway should have in one form, or another, where you designate torrenting a priority which doesn't interfere with the rest of your activities. And adapting dynamically. No need to think about how to slice available bandwith into pieces beforehand.
At the end of the day the bottleneck isn't at the protocol level, but the asymmetry of home cable connections. Torrents are great when you have symmetric fiber, but very few homes do right now.
I haven't visited a torrent site in years.
Not sure if the need to use private trackers can be fixed by the protocol, though. But, maybe adding a bit more of anonymity would be enough? i2p torrents provide that, but sacrifice speed. Clearly it's a spectrum and we need more "points" in the middle of it.
No. He's describing a distributor's options. You are describing a consumer's problem. Specifically pirate comsumers.
He doesn't need to find his own file; he needs to distribute it. Publishing is a separate issue. With napster, you only had one publishing option: napster.com. With torrents, you have many. As he said, "just dump the magnet link somewhere".
> Unfortunately, bad design won.
You're comparing apples and oranges. Napster and bittorent are different tools that solve different problems.
He's describing general issues involved in distributing something.
You're describing specific issues involved in stealing.
Saying "bad design won" is like saying hammers are a bad design compaired to hypodermic needles because you can't use a hammer to inject yourself with heroin.
Torrenting can cause a fragmenting issue, but defragging clears that up. And like anywhere else, random executables sometimes contain malware but there's nothing inherent in torrents that makes that more likely.
Torrents avoid many of those issues; you can see how many seeds a file has (though Kazaa and the like later added that). And you had to have gotten the magnet link from somewhere, which would have its own evaluatable trust. It's the difference between downloading file called "Foo" from random internet user's computer, and going to a website, that you know, and downloading a file called "Foo" that you also know has been downloaded, and retained, by X number of users.
Just as you would download and run an executable from a trusted source, you can download a torrent of an executable (from that trusted source) and run it.
E.g. many Linux distributions offer torrent links next to regular downloads; if you trust that website, you can download either file.
Yes, that's very plausible.
> Have the trust issues improved?
If you're retrieving executable code, the source giving you the magnet link is usually given some implicit trust. A good practice is to distribute a hash or better still a signature of the file(s). Though I would expect BitTorrent is designed to protect the shared contents' extents via hashes too.
If the content is some multimedia, then ideally it could be untrusted. Your favorite OS probably has much more robust libraries handling the multimedia content than it did a decade ago. But ultimately if the content distributed is infringing then it probably comes from a less trustworthy source. In which case you should have a different posture when handling these untrusted files than the generally untrusted interwebs content.
It can, but the clients I use(d) had an option like 'preallocate space', or similar. Then it doesn't, at least not as much.
This seems like one of the biggest problems with more decentralized torrents (i.e. ones not backed by a community / core seeder), but also most a UX issue and seemingly trivially solvable.
Which seems a pretty reasonable question for a user to have, if we're talking about fully decentralized torrents without a tracker.
He's currently creating a cryptocurrency.
* Transfers never starting, or not being able to exceed kbps. * Large amounts of data makes client performance worse. * Adding data to the store doubles the disk space used unless you take extra steps to mitigate that.
Meanwhile, I can point mktorrent at a folder, load it in my clients, and have it saturate my link within seconds/a couple minutes.
I'm keeping a close eye on IPFS and the Dat Project to take over here (and my use of Syncthing), but I'm hoping some refinement can happen first.