If you download some old massively-seeded-and-few-downloaders file, it becomes almost impossible to meet private tracker upload ratios. You could seed for a month and end up with a 0.1 upload ratio.
I've been there. My first experience with BT was someone invited me to a private tracker to get something that was not exactly breaking news. 600mb later and I went into seeding and was horrified to see my fat upload pipe barely cracking 2k/sec. I left it seed, a week later I get a ratio warning. A week after that I get my login banned. I could still continue to seed though so I prayed it would eventually crawl above acceptable.
And then we had a blackout that beat my UPS. game over man game over.
So what should I do when my torrents are being pruned but are still at 0.2 or something?
That can happen if you happen to join a swarm that's near the end of its life. If it's been going for 4 months and has already been snatched 500 times, and there's currently five seeds and no leeches, it's a prime candidate for pruning.
There are lots of things you can do to help your ratio. Most good sites have a lounge area with pages with specific suggestions for how to do this given their site's rules and SOP. If not:
1) run a seed box. Use another computer to do your torrenting, and when something finishes, let it ride until it gets deleted. Set the computer to auto start after power fail etc.
2) don't cap your upstream. or if you need to, be sure to uncap it when you don't need it anymore.
3) upload your own torrents. 100% of your traffic on an upload is upload ratio. Just be sure you mind the site's rules. Read them, create the torrent, and before you upload it, read them again and make sure you are following the rules.
4) get on torrents early. Keep an eye on the front page, and download things you want the day they are uploaded. Your seeding will go much better in the first two weeks of the torrent than if you join a swarm that's two months old. Avoid trawling old torrents for something you want or might want. Have some patience and see if someone else will upload a newer/better version that you can hop right on while it's new instead.
5) advanced technique for power-ratio'ing: if you spot something just uploaded that you know is going to be popular, and you have a good upstream, download it. I don't care if you don't want it, download it anyway. Put your seed box to work. That 500mb ISO you download can quickly turn into 5-10gb of upload over the next two weeks. The faster you can get it downloaded, the faster you can seed it, so don't use your downstream for other things while downloading it, so you get it seeding as quickly as possible.
6) all the usual BT stuff... make sure your ports are mapped, connectable, clever, whatever you want to call it. Make sure your port isn't being throttled by your ISP. Try different BT clients that may perform better. Check those advanced options. Check your seed box every few days in case it needs your attention.
7) another advanced power-ratio'ing technique: if you spot a swarm that's still in midlife (or better, new!) and you already have that, download the torrent. Start it and stop it immediately. Drag in a copy of it from your files. Tell your client to recheck it. It should recheck at near 100%. You'll be seeding it within minutes. It's as good as an upload.
Software update will have a new update for iTunes every 4-6 days, with an ever more entertaining list of "bugfixes and improvements", none of which will mention anything about palm.
I remember them doing this awhile back for a plugin for itunes that would add a second ipod to your list on the left, that you could drag and drop FROM. That spawned three iTunes updates in two weeks. People that diff'd the updates found basically all they were doing was adjusting their plugin acceptance code. Finally on the third update, they gave up on trying to filter it by behavior, and just plain banned the name of the plugin. It was at this point the author basically said ok I'm done, they're targeting me personally and that's not a war I'm going to win.
We checked our corporate charter and it said we were supposed to do whatever a copyright owner tells us to do, but there was nothing in it about being creative. If we just do whatever they tell us to, we can claim them as an excuse. It's when we get creative and try to be a suck-up that we can get into trouble, so we're going to ratchet back to simply being a yes-man instead of a foot kisser.
I tried to have that discussion with several people in the past and was unsuccessful at penetrating their skulls with the concept.
For any one user that has a ratio of 2.0, there must be two users with a ratio of 0.5, etc. (in other words, the sum average ratio must be exactly 1.000) But there are other factors at work. deadbeats with low ratios (0.1) get banned. FreeLeech events. Both of these raise the average ratio above 1.0 . I think keeping the average ratio above 1.0 is the main reason we see freeleech events on all private trackers. Other private trackers make similar events such as "2-for-1 upload week", "freeleech torrents" or something like that.
But I'm one of those that skews the curves. I have a seedbox and generally don't stop a torrent until the tracker removes it. I see people stop in and snatch something I'm the only one seeding a month after everyone else has left the swarm. That keeps my ratio well-fed and allows me to hop in and grab a gig or three when I want to without having to worry about my ratio. It also keeps content availability/selection high, it's nice to go to a tracker and immediately find what you're looking for even if it's not all that popular or common. People like me are what make that happen.
Unfortunately there are enough people doing this that it puts a lot of announce load on the trackers. I've seen private trackers actually request that users don't seed beyond a certain time past the "no leeches" point, or to cap the total number of torrents they are seeding. Most trackers just run scripts that automatically delete torrents after they have gone a certain time without any leeches. I suspect a few of them dynamically adjust the prune point based on the number of announces their tracker is receiving, to keep traffic at a level their tracker can manage.
Poison-resilient networks based on the BitTorrent protocol are not affected.
So, the most effective method of P2P is the one that's immune. Really, Edonkey? who uses that? Find yourself a good private BT tracker and be done with it. There are many to choose from. Not only are they immune to content filtering, but due to ratio requirements and the possibility of getting banned if you misidentify content you upload, they're immune to content poisoning as well as data poisoning and have pretty much guaranteed high speed across the board.
Keeping in mind that Apple doesn't make the batteries, they have to have some degree of trust in their suppliers. I doubt anyone can picture Apple stupid enough to bait PR nightmares and lawsuits when their image is very important to their business model. Apple's typical reaction is the industry best-case product-problem-coverup-job - do everything reasonable to stick a lollypop in the mouth of anyone that screams, and quietly correct the problem so it doesn't happen again. They're unlikely to admit fault, that would just fan the flames. (pun?)
Batteries lately though do seem to be a serious problem all around for everyone. DSLAM phone boxesblowingup down the street, laptops and ipodscatchingfire, liio batteries puffing up like balloons. Inadequate testing if you ask me. New technology trying to get rushed into a highly competitive new market, skip the tests it's good enough, just ship it. Then stuff blows up catches fire, or generally misbehaves. But right now rechargeable batteries are making a shambles out of Moore's Law.
This isn't really news any more than the 5 o-clock rush hour. Blame Apple, blame Sony, whatever, it's going to happen. It's not anywhere outside the bell curve yet.
I was thinking about this and the only way they could engineer it to work even remotely like they advertise is if someone wanting to read the material forwarded it along with their 1/2 of the key to the 3rd party. The 3rd party then combines their 1/2 of the key with the provided, decrypts the data, and sends it back to the requestor. As long as the requestor does not maintain a copy of the cleartext, (as several have quipped with "screenshots?") then this would work. Once the 3rd party no longer has their 1/2 of the key, the data is irrecoverable. This however requires that only the 3rd party have a copy of their 1/2 of the key. Otherwise someone could cache a copy of the keys and as long as they have the keys and can hook up with a requestor, the data continues to be recoverable.
It's broken worse if the requestor requests the key from the 3rd party and gets it, because they themselves could cache a copy of the key just the same. But that's not fairing any better against the "screencapture" argument.
This isn't going to work. Another approach is to keep the 1/2 of the key in the cloud, but after a preset time, to flood the cloud keystore with plausible keys, too many to practically sort through to figure out which was the correct key. This only partly unbreaks the problem though.
The only example of anything even remotely similar having a "future-breaking" effect is in verifying identity. Create a key for say, year 2099. Make a key for 2098 and use 2099's key to sign it. Repeat the process down to current. Release all public keys for 2009-2099 to the public domain. Sign a document with key from 2009. You can be verified as the signer of the document. But on jan 2010, release the private key for 2009 into public domain and start using the key for 2010 to sign. Anything signed in 2009 can't be verified to be you anymore because the private key for 2009 is in public domain and records plausibly could have been altered. You can repeat this process until you reach the end of your chain of keys. There's no reason to expire keys on a certain date either, you could roll up 10,000 of them in this manner and expire them anytime you wanted or needed to, and as long as the entire set of keys remains available, anyone can verify your identity as long as it's signed with a key that has not yet been released. Done properly, the entire keyset could be in one document/package, as a giant chain of trust. Technically the only key they need to have that matters is your "root" 2099 public key because it can be used to verify the authenticity of any of your other public keys.
Though that breaks the past. You can't break the future
Am I the only one that didn't find that earthquake video very impressive? I would hope any building would survive that. Looks like a very tame earthquake.
Also it was really light... no siding, no SHINGLES, no furniture, probably no plumbing. NOT impressed.
Or maybe they really think they can buy the government (lobbying the legislative branch and suing through the judicial) to keep their current business model going even though it doesn't make sense anymore. From what we've seen so far, it appears that they'd be right.
you can just plug in an external HD and click the time machine button and forget about it.
For things important enough to be offsite you can just save them on your MobileMe drive and let apple mirror it for you.
Irony here is I am one but do neither. I use rsync all over the place here and don't presently have an offsite. I just got done downloading and building Rsync 3.06 and need to figure out how to build it for a different architecture, as I only have dev tools on my intel and I need to get rsync updated on the ppc's. (I know only just enough to be dangerous with fink/dev tools/etc and follow instructions for downloading and compiling builds)
It kind of sounds like he was trying to hold a rigged election early to save his seat in power by making it look to the people like he was more popular than he was, and that he just didn't pull it off in time. Possibly also that by holding it 'out of season' would make it easier to rig because those that might be in a position to monitor it wouldn't be prepared?
The NYTimes has a related story about how the music industry is trying to convert casual pirates by offering more convenient new services.
orly? Millions of people find our existing service so detestable that they turn to an illegal service to get what they want. Maybe, just maybe, there's a market for what they're looking for? Maybe we can make more money by selling them what they want instead of suing them?
That was sort of my point. "Thanks for saving me from dying from radiation poisoning. Can you do anything about the 25 year battle with cancer that's about to start?"
Sort of like the use of the iron lung for the polio victims. Thanks for saving my life. what's left of it anyway. You sure there's not a more comprehensive solution?
Of course, the police deserve criticism for applying the law in a case that was clearly not in its original spirit, but let's not remember the law they used to do it is broad and draconian.
Any law so loosely defined that it requires "interpretation" of the law to see if it falls under the "spirit of the law" is a bad law If you're willing to accept that the police are capable of properly interpreting overly broad/vague laws then you can just pass "breathing when inappropriate" as illegal, get rid of the rest of the laws, and call it a day as the police just interpret everything for you.
Police enforce the law. Judges educate the jury on interpretation of laws. Juries interpret laws. The job of the police does not, and should not, include interpretation of law. The correct way to deal with overly broad or vague laws is not to adjust their interpretation, it's to change or repeal them.
I wonder if this could be used to help cancer patients who are undergoing radiation treatment.
Radiation is a good way to cause cancer. Radiation does damage not only to cell structures, but also does irreversible damage to DNA, which can cause cancer. People being treated for severe radiation poisoning may survive only to find they are plagued by repeated development of cancerous tumors all over their body.
Alive still, but not nearly the rosegarden of living that the casual headline reader would envision.
I was just looking at this comment, 'the Court does not comprehend how disclosure would impair the Plaintiffs' competitive business prospects when three of the four biggest record labels in the world â" Warner Bros. Records, Sony BMG Music Entertainment, and UMG Recording, Inc. â" are participating jointly in this lawsuit and, presumably, would have joint access to this information.'" and wondering if that may mean that they only are required to release this information to that group.
What I'm wondering at this point is do they have to release this information publicly, or only to those participating in the case, or ? Betting next thing we see is for them to try to limit as much as possible who has access to this evidence.
One minute ads per half hour doesn't sound so bad to me either.
Heck, that's a lot better than I get over the air here! I would PAY (a small amount...) for a service like that.
As it is, I can't get radio reception at work due to the building, and I have to listen to my favorite station's stream at a pathetic bitrate (24!) AND put up with about 8 minutes of ads per hour.
Rogers, meanwhile, compared 'person-to-person file-sharing to a car that parks in one lane of a busy highway at all times of the day or night, clogging the roadways for everyone unless someone takes action.'
Close but no banana. There's one severe disparity in that analogy. They're not parked cars. This example makes it look like the resource is being wasted, unused, and entirely withheld from others that need it. I'd go for that comparison if it were a car that was driving on that highway. I might have to concede that they have a rather large gas tank and have been driving in circles around the bypass ring all day long, consuming resources continuously that others need only a small portion of, but the used analogy here is just fraud.
This is just getting back to the people getting kicked out of the all-you-can-eat-buffet for eating too much. Now there's an accurate analogy.
Slashdot Mirror
but Mac has no real "economy" option.
You sure about that?
federal agencies would be able to use cookies as long as their use is lawful,
The feds promising to only do lawful things? What a novel concept! I wonder how they will adapt?
If you download some old massively-seeded-and-few-downloaders file, it becomes almost impossible to meet private tracker upload ratios. You could seed for a month and end up with a 0.1 upload ratio.
I've been there. My first experience with BT was someone invited me to a private tracker to get something that was not exactly breaking news. 600mb later and I went into seeding and was horrified to see my fat upload pipe barely cracking 2k/sec. I left it seed, a week later I get a ratio warning. A week after that I get my login banned. I could still continue to seed though so I prayed it would eventually crawl above acceptable.
And then we had a blackout that beat my UPS. game over man game over.
So what should I do when my torrents are being pruned but are still at 0.2 or something?
That can happen if you happen to join a swarm that's near the end of its life. If it's been going for 4 months and has already been snatched 500 times, and there's currently five seeds and no leeches, it's a prime candidate for pruning.
There are lots of things you can do to help your ratio. Most good sites have a lounge area with pages with specific suggestions for how to do this given their site's rules and SOP. If not:
1) run a seed box. Use another computer to do your torrenting, and when something finishes, let it ride until it gets deleted. Set the computer to auto start after power fail etc.
2) don't cap your upstream. or if you need to, be sure to uncap it when you don't need it anymore.
3) upload your own torrents. 100% of your traffic on an upload is upload ratio. Just be sure you mind the site's rules. Read them, create the torrent, and before you upload it, read them again and make sure you are following the rules.
4) get on torrents early. Keep an eye on the front page, and download things you want the day they are uploaded. Your seeding will go much better in the first two weeks of the torrent than if you join a swarm that's two months old. Avoid trawling old torrents for something you want or might want. Have some patience and see if someone else will upload a newer/better version that you can hop right on while it's new instead.
5) advanced technique for power-ratio'ing: if you spot something just uploaded that you know is going to be popular, and you have a good upstream, download it. I don't care if you don't want it, download it anyway. Put your seed box to work. That 500mb ISO you download can quickly turn into 5-10gb of upload over the next two weeks. The faster you can get it downloaded, the faster you can seed it, so don't use your downstream for other things while downloading it, so you get it seeding as quickly as possible.
6) all the usual BT stuff... make sure your ports are mapped, connectable, clever, whatever you want to call it. Make sure your port isn't being throttled by your ISP. Try different BT clients that may perform better. Check those advanced options. Check your seed box every few days in case it needs your attention.
7) another advanced power-ratio'ing technique: if you spot a swarm that's still in midlife (or better, new!) and you already have that, download the torrent. Start it and stop it immediately. Drag in a copy of it from your files. Tell your client to recheck it. It should recheck at near 100%. You'll be seeding it within minutes. It's as good as an upload.
Now announcing iTunes Update Month!
Software update will have a new update for iTunes every 4-6 days, with an ever more entertaining list of "bugfixes and improvements", none of which will mention anything about palm.
I remember them doing this awhile back for a plugin for itunes that would add a second ipod to your list on the left, that you could drag and drop FROM. That spawned three iTunes updates in two weeks. People that diff'd the updates found basically all they were doing was adjusting their plugin acceptance code. Finally on the third update, they gave up on trying to filter it by behavior, and just plain banned the name of the plugin. It was at this point the author basically said ok I'm done, they're targeting me personally and that's not a war I'm going to win.
They used to make people sign confessions to witchcraft, too.
and they received lesser sentences too.
We checked our corporate charter and it said we were supposed to do whatever a copyright owner tells us to do, but there was nothing in it about being creative. If we just do whatever they tell us to, we can claim them as an excuse. It's when we get creative and try to be a suck-up that we can get into trouble, so we're going to ratchet back to simply being a yes-man instead of a foot kisser.
But the sum of share ratios can never exceed 100%
I tried to have that discussion with several people in the past and was unsuccessful at penetrating their skulls with the concept.
For any one user that has a ratio of 2.0, there must be two users with a ratio of 0.5, etc. (in other words, the sum average ratio must be exactly 1.000) But there are other factors at work. deadbeats with low ratios (0.1) get banned. FreeLeech events. Both of these raise the average ratio above 1.0 . I think keeping the average ratio above 1.0 is the main reason we see freeleech events on all private trackers. Other private trackers make similar events such as "2-for-1 upload week", "freeleech torrents" or something like that.
But I'm one of those that skews the curves. I have a seedbox and generally don't stop a torrent until the tracker removes it. I see people stop in and snatch something I'm the only one seeding a month after everyone else has left the swarm. That keeps my ratio well-fed and allows me to hop in and grab a gig or three when I want to without having to worry about my ratio. It also keeps content availability/selection high, it's nice to go to a tracker and immediately find what you're looking for even if it's not all that popular or common. People like me are what make that happen.
Unfortunately there are enough people doing this that it puts a lot of announce load on the trackers. I've seen private trackers actually request that users don't seed beyond a certain time past the "no leeches" point, or to cap the total number of torrents they are seeding. Most trackers just run scripts that automatically delete torrents after they have gone a certain time without any leeches. I suspect a few of them dynamically adjust the prune point based on the number of announces their tracker is receiving, to keep traffic at a level their tracker can manage.
Poison-resilient networks based on the BitTorrent protocol are not affected.
So, the most effective method of P2P is the one that's immune. Really, Edonkey? who uses that? Find yourself a good private BT tracker and be done with it. There are many to choose from. Not only are they immune to content filtering, but due to ratio requirements and the possibility of getting banned if you misidentify content you upload, they're immune to content poisoning as well as data poisoning and have pretty much guaranteed high speed across the board.
Keeping in mind that Apple doesn't make the batteries, they have to have some degree of trust in their suppliers. I doubt anyone can picture Apple stupid enough to bait PR nightmares and lawsuits when their image is very important to their business model. Apple's typical reaction is the industry best-case product-problem-coverup-job - do everything reasonable to stick a lollypop in the mouth of anyone that screams, and quietly correct the problem so it doesn't happen again. They're unlikely to admit fault, that would just fan the flames. (pun?)
Batteries lately though do seem to be a serious problem all around for everyone. DSLAM phone boxes blowing up down the street, laptops and ipods catching fire, liio batteries puffing up like balloons. Inadequate testing if you ask me. New technology trying to get rushed into a highly competitive new market, skip the tests it's good enough, just ship it. Then stuff blows up catches fire, or generally misbehaves. But right now rechargeable batteries are making a shambles out of Moore's Law.
This isn't really news any more than the 5 o-clock rush hour. Blame Apple, blame Sony, whatever, it's going to happen. It's not anywhere outside the bell curve yet.
I was thinking about this and the only way they could engineer it to work even remotely like they advertise is if someone wanting to read the material forwarded it along with their 1/2 of the key to the 3rd party. The 3rd party then combines their 1/2 of the key with the provided, decrypts the data, and sends it back to the requestor. As long as the requestor does not maintain a copy of the cleartext, (as several have quipped with
"screenshots?") then this would work. Once the 3rd party no longer has their 1/2 of the key, the data is irrecoverable. This however requires that only the 3rd party have a copy of their 1/2 of the key. Otherwise someone could cache a copy of the keys and as long as they have the keys and can hook up with a requestor, the data continues to be recoverable.
It's broken worse if the requestor requests the key from the 3rd party and gets it, because they themselves could cache a copy of the key just the same. But that's not fairing any better against the "screencapture" argument.
This isn't going to work. Another approach is to keep the 1/2 of the key in the cloud, but after a preset time, to flood the cloud keystore with plausible keys, too many to practically sort through to figure out which was the correct key. This only partly unbreaks the problem though.
The only example of anything even remotely similar having a "future-breaking" effect is in verifying identity. Create a key for say, year 2099. Make a key for 2098 and use 2099's key to sign it. Repeat the process down to current. Release all public keys for 2009-2099 to the public domain. Sign a document with key from 2009. You can be verified as the signer of the document. But on jan 2010, release the private key for 2009 into public domain and start using the key for 2010 to sign. Anything signed in 2009 can't be verified to be you anymore because the private key for 2009 is in public domain and records plausibly could have been altered. You can repeat this process until you reach the end of your chain of keys. There's no reason to expire keys on a certain date either, you could roll up 10,000 of them in this manner and expire them anytime you wanted or needed to, and as long as the entire set of keys remains available, anyone can verify your identity as long as it's signed with a key that has not yet been released. Done properly, the entire keyset could be in one document/package, as a giant chain of trust. Technically the only key they need to have that matters is your "root" 2099 public key because it can be used to verify the authenticity of any of your other public keys.
Though that breaks the past. You can't break the future
Am I the only one that didn't find that earthquake video very impressive? I would hope any building would survive that. Looks like a very tame earthquake.
Also it was really light... no siding, no SHINGLES, no furniture, probably no plumbing. NOT impressed.
Or maybe they really think they can buy the government (lobbying the legislative branch and suing through the judicial) to keep their current business model going even though it doesn't make sense anymore. From what we've seen so far, it appears that they'd be right.
There, fixed that for ya.
you can just plug in an external HD and click the time machine button and forget about it.
For things important enough to be offsite you can just save them on your MobileMe drive and let apple mirror it for you.
Irony here is I am one but do neither. I use rsync all over the place here and don't presently have an offsite.
I just got done downloading and building Rsync 3.06 and need to figure out how to build it for a different architecture, as I only have dev tools on my intel and I need to get rsync updated on the ppc's. (I know only just enough to be dangerous with fink/dev tools/etc and follow instructions for downloading and compiling builds)
It kind of sounds like he was trying to hold a rigged election early to save his seat in power by making it look to the people like he was more popular than he was, and that he just didn't pull it off in time. Possibly also that by holding it 'out of season' would make it easier to rig because those that might be in a position to monitor it wouldn't be prepared?
The NYTimes has a related story about how the music industry is trying to convert casual pirates by offering more convenient new services.
orly? Millions of people find our existing service so detestable that they turn to an illegal service to get what they want. Maybe, just maybe, there's a market for what they're looking for? Maybe we can make more money by selling them what they want instead of suing them?
That was sort of my point. "Thanks for saving me from dying from radiation poisoning. Can you do anything about the 25 year battle with cancer that's about to start?"
Sort of like the use of the iron lung for the polio victims. Thanks for saving my life. what's left of it anyway. You sure there's not a more comprehensive solution?
Of course, the police deserve criticism for applying the law in a case that was clearly not in its original spirit, but let's not remember the law they used to do it is broad and draconian.
Any law so loosely defined that it requires "interpretation" of the law to see if it falls under the "spirit of the law" is a bad law If you're willing to accept that the police are capable of properly interpreting overly broad/vague laws then you can just pass "breathing when inappropriate" as illegal, get rid of the rest of the laws, and call it a day as the police just interpret everything for you.
Police enforce the law. Judges educate the jury on interpretation of laws. Juries interpret laws. The job of the police does not, and should not, include interpretation of law. The correct way to deal with overly broad or vague laws is not to adjust their interpretation, it's to change or repeal them.
and then there's also the DNA getting chopped up and shuffled around
I wonder if this could be used to help cancer patients who are undergoing radiation treatment.
Radiation is a good way to cause cancer. Radiation does damage not only to cell structures, but also does irreversible damage to DNA, which can cause cancer. People being treated for severe radiation poisoning may survive only to find they are plagued by repeated development of cancerous tumors all over their body.
Alive still, but not nearly the rosegarden of living that the casual headline reader would envision.
What will the department do during a power failure?
absolutely nothing
Did you think these were manual typewriters? No, they're electric typewriters of course.
I don't think you can buy a new manual typewriter anymore, nobody makes them?
I was just looking at this comment, 'the Court does not comprehend how disclosure would impair the Plaintiffs' competitive business prospects when three of the four biggest record labels in the world â" Warner Bros. Records, Sony BMG Music Entertainment, and UMG Recording, Inc. â" are participating jointly in this lawsuit and, presumably, would have joint access to this information.'" and wondering if that may mean that they only are required to release this information to that group.
What I'm wondering at this point is do they have to release this information publicly, or only to those participating in the case, or ? Betting next thing we see is for them to try to limit as much as possible who has access to this evidence.
One minute ads per half hour doesn't sound so bad to me either.
Heck, that's a lot better than I get over the air here! I would PAY (a small amount...) for a service like that.
As it is, I can't get radio reception at work due to the building, and I have to listen to my favorite station's stream at a pathetic bitrate (24!) AND put up with about 8 minutes of ads per hour.
Rogers, meanwhile, compared 'person-to-person file-sharing to a car that parks in one lane of a busy highway at all times of the day or night, clogging the roadways for everyone unless someone takes action.'
Close but no banana. There's one severe disparity in that analogy. They're not parked cars. This example makes it look like the resource is being wasted, unused, and entirely withheld from others that need it. I'd go for that comparison if it were a car that was driving on that highway. I might have to concede that they have a rather large gas tank and have been driving in circles around the bypass ring all day long, consuming resources continuously that others need only a small portion of, but the used analogy here is just fraud.
This is just getting back to the people getting kicked out of the all-you-can-eat-buffet for eating too much. Now there's an accurate analogy.