I think that's where one of the IPs resolved to, yes.
There was a big post about it on DSLReports.com (Canadian Broadband) back then where people were checking where the 50 IPs resolved to - whether commercial, or private.
In 2011, Voltage asked for IP information from Bell, Cogeco & Videotron, and all 3 ISPs wrote a letter to the court together stating they wouldn't fight it, or even show up to the hearing. http://dwmw.wordpress.com/2013/01/14/voltages-teksavvy-subscriber-shakedown-whats-an-isp-t o-do/#comment-2530
Jean-Francois Mezei (also known as 'JF') is well-known in the Canadian Tech Policy circles, and I can confirm that posting is from him due to a conversation I had with him Sunday night.
They may have fought it in 2004, but they didn't fight the copytroll attempt from Voltage in 2011.
In fact, Bell along with the other ISPs wrote to the Judge specifically stating that they wouldn't be fighting the court order, or even appearing for any court hearings.
The letter was mistakenly in the public file when someone viewed the file in the Montreal courts. When the person who saw it and requested a photocopy of the page, staff realized their error, and removed it from the file, refusing to allow it to be copied.
Nowhere in the privacy policy does it say they have to fight a potential court order on behalf of their customers. Privacy policy does essentially say that if there is a court order, they have to follow it.
I don't get why people seem to think Teksavvy should they pick up the bill to defend their customers from the suit?
Meanwhile, just last month Distributel & 3web (2 other major indie ISPs here in Canada) didn't do what Teksavvy has done (ie fought to push back the order so that they could inform affected customers, and advise them to get legal counsel), and just rolled over and handed over the subscriber info.
They did NOT fight the order in any manner whatsoever, and will now be seeing settlement letters in their near future.
What neither of these 2 stories said, was that its a small test of 157 children in the US, ages 6-17, who are already opioid-tolerant, and are experiencing extreme pain from cancer, post-operative pain, and severe burns.
If your child had severe burns, and you had the choice of giving them Oxycontin to remove the pain entirely, or giving them lesser pain meds and them still being in pain, what would you choose?
Now, I'm not saying Purdue is doing this out of the goodness of their hearts (more like to increase their wallets), but its not a bad thing that they're doing this testing.
Re: Re: Re: Re: Re: Re:
I think that's where one of the IPs resolved to, yes.
There was a big post about it on DSLReports.com (Canadian Broadband) back then where people were checking where the 50 IPs resolved to - whether commercial, or private.
Re: Re: Re: Re:
In 2011, Voltage asked for IP information from Bell, Cogeco & Videotron, and all 3 ISPs wrote a letter to the court together stating they wouldn't fight it, or even show up to the hearing.
http://dwmw.wordpress.com/2013/01/14/voltages-teksavvy-subscriber-shakedown-whats-an-isp-t o-do/#comment-2530
Jean-Francois Mezei (also known as 'JF') is well-known in the Canadian Tech Policy circles, and I can confirm that posting is from him due to a conversation I had with him Sunday night.
In 2012, NGN asked for & got IP information from 4 ISPs; Access, Distributel, 3web & ACN Inc.
http://copyrightenforcement.ca/wp-content/uploads/2012/11/NGN-Order-Montreal.pdf
Re: Re:
They may have fought it in 2004, but they didn't fight the copytroll attempt from Voltage in 2011.
In fact, Bell along with the other ISPs wrote to the Judge specifically stating that they wouldn't be fighting the court order, or even appearing for any court hearings.
The letter was mistakenly in the public file when someone viewed the file in the Montreal courts. When the person who saw it and requested a photocopy of the page, staff realized their error, and removed it from the file, refusing to allow it to be copied.
Re: Re: Re: Re: Re: Re: Re: Why is it up to teksavvy to protect us?
Some US judges have ordered that, due to the company suing being a foreign company...
Re: Re: Re: Re: Why is it up to teksavvy to protect us?
Marc's been responding this morning regarding reasoning.
http://www.dslreports.com/forum/r27824891-Why-we-are-not-opposing-motion-on-Monday.~st art=440
Re: Re: Why is it up to teksavvy to protect us? (as Teresa)
Nowhere in the privacy policy does it say they have to fight a potential court order on behalf of their customers. Privacy policy does essentially say that if there is a court order, they have to follow it.
I don't get why people seem to think Teksavvy should they pick up the bill to defend their customers from the suit?
(untitled comment) (as Teresa)
Meanwhile, just last month Distributel & 3web (2 other major indie ISPs here in Canada) didn't do what Teksavvy has done (ie fought to push back the order so that they could inform affected customers, and advise them to get legal counsel), and just rolled over and handed over the subscriber info.
They did NOT fight the order in any manner whatsoever, and will now be seeing settlement letters in their near future.
http://copyrightenforcement.ca/wp-content/uploads/2012/11/NGN-Order-Montreal.pdf
I think its good on Teksavvy that they gave customers time to get their own lawyers anonymously so as to dispute being named in one of these suits.
Re: Re: (as Teresa)
What neither of these 2 stories said, was that its a small test of 157 children in the US, ages 6-17, who are already opioid-tolerant, and are experiencing extreme pain from cancer, post-operative pain, and severe burns.
http://thechart.blogs.cnn.com/2012/07/03/pharma-company-studying-oxycontins-effect-in-chil dren/
If your child had severe burns, and you had the choice of giving them Oxycontin to remove the pain entirely, or giving them lesser pain meds and them still being in pain, what would you choose?
Now, I'm not saying Purdue is doing this out of the goodness of their hearts (more like to increase their wallets), but its not a bad thing that they're doing this testing.