Daneal writes "Ars Technica has some interesting analysis of the RIAA's lawsuit against Usenet.com. There's reason to believe that Usenet.com — and most other Usenet providers — could qualify for protection under the DMCA's Safe Harbor provision. 'The DMCA's Safe Harbor provision provides protection for ISPs from copyright infringement lawsuits as long as they take down offending material once they are served with a notice of infringement. "Whether the Safe Harbor applies is the central legal question that is going to be raised," EFF senior staff attorney Fred von Lohmann told Ars. An RIAA spokesperson tells Ars that the group has issued "many" takedown notices to Usenet.com, but von Lohmann says that the volume of takedown notices isn't what counts. "The DMCA's Safe Harbor makes it very clear," von Lohmann said. "The number of notices doesn't matter as long as you take the infringing content down."'"
Arent binaries in most usenet groups removed automatically after a certain number of days whether or not a takedown has been issued? This is usually determined by the volume of messages and storage of the particular provider. So , is there a time limit on how fast you MUST remove stuff once a takedown has been issued? I ask , because the way usenet works , stuff doesnt stay on the server forever.
Stuff doesn't stay online forever, but Usenet.com offers something like 150 days of retention, which is quite a while. Other usenet servers offer even more, e.g., Giganews offers 200 days on binaries and up to 1500 days on text.
The Wired article [wired.com] has a link to the actual lawsuit in PDF format. It actually makes an interesting read.
It's worth noting that Usenet.com does not own/operate usenet, they are just a download service for usenet. They cannot remove things from usenet, they can only prohibit downloads of certain content from their servers, I'd imagine.
"If Usenet.com can show that it complies with the DMCA by removing access to infringing content and by suspending the accounts of repeat offenders, it may be enough to provide it with protection under the hosting and linking provisions of the DMCA."
Hrmm, correct me if I am wrong (usenet servers in aus are a little odd/different than US ones I think) but doesn't the news server only hold the data for like 30 days or so? So they do take the information down, within 30 days of being issued with a take down notice?
That varies widely from provider to provider. A typical ISP, if they bother to offer a Usenet server at all, may retain binary content for just a few days. On the other hand, some of the commercial news servers have much longer retention periods. GigaNews [giganews.com], for instance, now boasts a binary retention period of 200 days.
It's worth noting that Usenet.com does not own/operate usenet, they are just a download service for usenet. They cannot remove things from usenet, they can only prohibit downloads of certain content from their servers, I'd imagine.
As a former INN server admin from 1994 to about 2001, that's bunk I'm sorry to say. I resisted modding you down (even have the points for it!) just to clear the air here. If you stream news to someone else, your removal of an article affects your downstream servers as well. It's quite easy to remove an article - always has been.
That's RIAA FUD. From experience in a webhosting company, RIAA will just send you a notice that there was illegal music found and just give a listing of ALL similar content (like: delete all MP3's although only one is actually infringing) on the site even though it might not be infringing (copyright law DOES have exceptions) or the site might have been hacked before.
They probably refuse to take down content that is legally protected or that is legally not a full work and even if they take it down, within a few minutes another version might be up again so it sounds like the RIAA is going to have to send a lot of notices to take every single Usenet post down.
by Anonymous Coward
on Wednesday October 17 2007, @05:32PM (#21017489)
Some ISPs don't provide newsgroup access anymore, make it a pain to get or have limits on uploading or downloading binaries. RIAA pressure could make this the norm.
Services like Usenet.com and Giganews are quite possibly vulnerable, as we see from this lawsuit. Maybe they'll try to go for customer logs next?
It may not be possible to take down Usenet, but it is quite possible to make it a little more difficult or risky than it is now for the average college student to access binaries.
Although I think the real point of this is to instill paranoia. RIAA lawsuits are a more than anything else a scare tactic and an effective PR campaign designed to instill fear in casual downloaders. That may be why they're going after Usenet.com instead of Giganews or similar sites, to instill some confusion and so that the aforementioned college student thinks he's at risk of a lawsuit himself if he downloads from Usenet (no matter what provider he uses.) My theory at least, take it with a grain of salt.
It's not all that distributed where the binaries are concerned. Unless it's your primary business, you don't carry the binaries groups. I wouldn't be surprised if the majority of USENET piracy could be disrupted by taking down less than a dozen USENET providers. Bummer. But it was bound to happen. The binaries hosts have gotten a bit too blatant with their marketing and have made USENET binary downloads a far easier endeavor than it used to be. The critical mass of users which triggers copyright lawsuit
So, are you saying that NNTP will not allow you to attach a binary file to a post in any other area of usenet but the binaries groups? That sounds wrong to me, but it might be the case. binaries seems to be an arbitrary label on a set of groups. I do not see any reason why other groups/channels could not be created to circumvent this.
That's not what I mean. You can always attach a binary. But... you won't be able to do so in a way that the vast majority of people who want the binary will easily find it.
If the large binary providers go down, it will be back to the days of scattered binaries, ever changing group names, and, any time a group gets too big, your provider will drop it.
It will no longer (or won't become) be a distribution method for the masses.
Who keeps picking out windmills for RIAA to tilt at? Their legal attack strategist needs to put down the crack pipe and step away from his desk. Seriously... --
The RIAA's biggest mistake is picking up the role of angry bull elephant. When an angry bull elephant starts attacking the village with intent to cause as much harm as possible, the villagers are quick to; 1 Run and hide. 2 Put up defenses. 3 Directly attack the threat.
In short.. Number 1 is trade offline with the sneaker net. USB drives, USB music p
Since Usenet just publishes other people's stuff, don't they (at least somewhat) qualify for common carrier classification (similar to phone companies) in that the the content is someone else's?
Along these lines, what about Google/other search engines that show "copyrighted" content - either in the snippet or in their cache?
Since Usenet just publishes other people's stuff, don't they (at least somewhat) qualify for common carrier classification (similar to phone companies) in that the the content is someone else's? Along these lines, what about Google/other search engines that show "copyrighted" content - either in the snippet or in their cache?
The very short answer: No. They're protected by the DMCA safe harbor protections but they are not legally common carriers, which is probably a good thing since it carries a bunch of regu
You're missing the point. (And the Ars Technica article mentions the point and then proceeds to ignore it.)
The issue is that Usenet.com blatantly (from a common-sense point of view, whether it's legally meaningful I have no idea) markets themselves as a way to illegally obtain copyrighted content. As someone put it yesterday, if the phone companies ran commercials advertising "Telephones -- the best way to plan your terrorist activities!" that would cut into their ability to claim common carrier status as a defense. Same thing for Safe Harbor.
Incidentally, didn't we have a story a few months ago complaining that the MPAA and RIAA weren't suing usenet providers, and how that proved some conspiracy theory? If that faction is relieved at this new development, I haven't seen them mention it.
Yes, those ads are part of the problem, because it hurts their Safe Harbor defense (see my post which quotes the section of the DMCA, further down in the thread). But only insofar as they might show that Usenet.com was benefiting directly from illegal content. And I'm not sure they do that, because the ads aren't that blatant. They basically just suggest that they have a rigorous privacy policy, etc. It's not totally damning.
Where I think they get into trouble is that, in order to claim Safe Harbor, they basically need to be able to claim "hey, somebody put that up onto our system, we didn't know it was infringing, we didn't even know it was there!" And it's a bit tough to do that with Usenet, seeing as how it's about 99% binaries and anyone who's ever opened up the alt.binaries.* hierarchy can tell that it's got a lot of bootlegs and warez in it.
It would be a little comical to see a whole bunch of seasoned network engineers and other greybeards try to claim that they had no idea there was copyrighted material on Usenet. ("Warez? On my Usenet?") But that's sort of the position they have to put themselves in, in order to get a successful 512(c) defense.
They also have to show that in the past they've complied with DMCA takedown orders against content that a copyright holder has pointed out as being infringing, which it seems like they weren't doing. That may also be a problem, although maybe they can argue that they didn't have the capability to delete articles (after all, if they took them out of their store, would they just have come in on a feed from another site that they peer with?). It might be difficult to get a judge to swallow that, though.
I think they're in trouble, but I'm not sure exactly how much trouble just yet.
It would be a little comical to see a whole bunch of seasoned network engineers and other greybeards try to claim that they had no idea there was copyrighted material on Usenet. ("Warez? On my Usenet?") But that's sort of the position they have to put themselves in, in order to get a successful 512(c) defense.
Why is that a barrier to a successful 512(c) defense? If the host, Usenet.com in this case, services all take down notices in a reasonable and timely fashion and makes reasonable efforts to accommodate copyright holders (the court decides what is and is not reasonable) then have they not fulfilled their obligation under the law? How would they know if there was a copy of Eric Clapton's greatest hits on their network? Sure they could search for it if they wanted to but are they required to have automated agents searching all of the time for everything that might be copyrighted? Is that reasonable or even feasible? Certainly not, it is the responsibility of the copyright holder to locate infringement and take the legally required step of sending a take down notice. As long as there is a reasonable system in place to service requests from copyright holders, then the content host has fulfilled its obligations and should be able to take refuge in the safe harbor.
If telephone companies advertised themselves as the "best way to plan a terrorist attack" it would be because somebody decided that that was the best marketing strategy. and if so, it would be legal.
When dealing with a massive corporation shoveling buckets of money into the hands of the senators, the "won't somebody think of the children" argument is remarkably hard to hear.
It is a very specific case brought about because fedral funds were used to build the phone network. It is not relevant in any way to Usenet.
The first US telephone exchange opened in 1978. AT&T and the regional Bell companies were privately financed from day one and evolved into regulated public utilities.
The common carrier rule can be traced back to the days when Western Union was in its prime and censoring telegrams it found inconvenient.
With the the exception of civil engineering projects like the Panama Canal, federal spending on infrastructure begins with the New Deal of the 1930s.
To be honest, I don't know how Usenet.com can not qualify for DMCA protection, since it's exactly the type of service that the Safe Harbor exception is supposed to protect. The only thing that seems like it could harm Usenet.com is their advertising, which does veer a little into "wink, wink, nudge, nudge" territory. However, damning a company because it says it respects users' privacy, without actually advocating any type of criminal activity, seems like pretty terrible precedent, and I can only hope (although at this point I have little faith) that a judge will see it similarly.
I think the mention in the Ars article about Safe Harbor being related to "transitory network communications" is irrelevant here. Transitory network communications is covered under 512(a) of the OCILLA (which is part of the DMCA); the portion that I would expect Usenet.com to seek protection under is 512(c), "Information Residing on Systems or Networks at Direction of Users".
You can read the relevant section here [cornell.edu], but the significant portion, IMO, is:
A service provider shall not be liable for monetary relief, or, except as provided in subsection (j), for injunctive or other equitable relief, for infringement of copyright by reason of the storage at the direction of a user of material that resides on a system or network controlled or operated by or for the service provider, if the service provider--
(A)(i) does not have actual knowledge that the material or an activity using the material on the
system or network is infringing;
(ii) in the absence of such actual knowledge, is not aware of facts or circumstances from which infringing activity is apparent; or
(iii) upon obtaining such knowledge or awareness, acts expeditiously to remove, or disable access to, the material;
(B) does not receive a financial benefit directly attributable to the infringing activity, in a case in which the service provider has the right and ability to control such activity; and
(C) upon notification of claimed infringement as described in paragraph (3), responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity.
The major things they're going to have to avoid are that they "had actual knowledge" that the material was infringing (which might be tough -- I mean, anybody who opens up alt.binaries.movies can probably tell pretty quickly that it's full of bootlegs) and that they didn't receive a "financial benefit directly attributable" to the infringing activity. I think that second one is actually a little easier (for Usenet.com) than the former. And, of course, they have to successfully argue/explain that they don't really have the power to remove articles from Usenet, because of the nature of the network -- it would probably help their case if they started at least deleting articles from their spool/store when they receive a complaint.
I suspect that this may lead to a shakedown in the Usenet provider world, if Usenet.com loses. At the very least, the big providers might have to do more in order to maintain a veneer of plausible deniability (deleting some of the more obviously movie and/or warez related groups, perhaps), or move their servers out of the U.S.
There's another section of the DMCA that offers a different "safe harbor":
(a) TRANSITORY DIGITAL NETWORK COMMUNICATIONS- A service provider shall not be liable for monetary relief, or, except as provided in subsection (j), for injunctive or other equitable relief, for infringement of copyright by reason of the provider's transmitting, routing, or providing connections for, material through a system or network controlled or operated by or for the service provider, or by reason of the intermediate and transie
Humm. Yeah, that's a lot more blatant than they were making it out to be in the Ars article. In fact, what the hell, guys? I know it has a copyright date of 2005 on it, but even if that had been written in 1995 it still would have been a little much.
To wit: (in case they take the page down, which I sure would if I were them)
Where Can You Get Free Downloads These Days? Well, we must admit that it is getting harder and harder to find anything free on the Internet these days. File sharing websites are getting shut down, spam is all over the net and free download options are getting thinner by the day. So what is the Internet user who loves to download stuff for free to do in this situation? There is one solution which has existed for a while but not everyone may be informed of just yet. This solution is called Usenet, also known as The Usenet Experience. It is an underground because it is not a website that anyone can randomly access by doing a search in Google, Yahoo, or AltaVista. It is somewhat hidden and restricted because not everyone has access to the free download areas, called newsgroup. So How Do You Get to the Place with Free Downloads? It is easier than you may think. The place which soon may be the only one that offers free downloads is available to everyone through a Usenet service provider company, such as Usenet.com. In order to start downloading all you want, you need to have Internet access (which you probably have already since you're reading this) and a Usenet account. Once you join Usenet.com, you can access the Usenet newsgroups and start downloading all you want without paying an additional cent. Tired of busy file sharing programs such as KaZaa? Then Usenet is the place for you. It's a place that has it all and where you can download it all. Usenet has a much wider selection than any of the other file sharing programs and it is available to you to use 24 x 7, no mater who's online or who isn't. The files are all hosted on the provider company's servers and it is available to all users to view and download. What Exactly Can You Download in Usenet? Anything and everything. Literally. There are movies, mp3s, cartoons, wallpapers, sounds, videos, pictures, warez, games, software and much more. The files (also known as "binaries" in Usenet) are organized by subject in the so called "newsgroups," which makes it really easy for everyone from the inexperienced user to the expert to find what they are looking for.
1) Usenet != usenet.com, which is merely a host. The RIAA is not attacking a protocol. They are suing a company that hosts a lot of NNTP traffic, some of which may be infringing on copyright.
2) It's fscking hilarious that the DCMA may wind up being used against the RIAA. Kudos to Ars for thinking up that one.
3) If the DCMA doesn't help, maybe the supreme court ruling stating that an ISP is not responsible for user generated content will. Details here. [dotcomeon.com] (Note: The article isn't about copyright, i
But they are just a carrier, how are they going to 'take down' a file?
By issuing a cancel message for the Message-IDs composing the "file" (but with a Distribution: local header as that is as far as their responsibility extends).
Of course, that assumes the party issuing the takedown notice knew to cite the offending articles by Message-ID. The canceled messages will not re-propagate to the server. The poster, anywhere else in the world, could still repost under a new Message-ID (automatically generated for every posting). The cancel messages can even contain the takedown notice in each message body, which would be readable in the newsgroup named "control" and/or in "control.cancel" if it is present.
They wouldn't necessarily even have to cryptographically sign the cancels since they are local, though it might be wise to prevent fellow users of the same server wildly canceling other articles.
These organizations could technically send out their own cancel messages with unrestricted distribution, though I'm not familiar with the current state of the art in preventing forged cancels. If spammers have truly lost interest in Usenet, it may have come to the point where cancel messages are generally ignored.
to force ISP's to filter the entire fscking Internet, one service at a time? This is going to be interesting. If Usenet.com goes down, next will be NNTP service filters on every ISP in the US, and then by association, such efforts will be made in the rest of the world. Perhaps it might not work in Russia for fear of being mistaken for a spammer, but in the rest of the world, the US government and the **AA will push to have the entire Internet filtered...
The next step? To filter all your email, IM, and VoIP traffic as well, and in fact any method of sharing data. Sounds like tin foil hat stuff, but that seems to be the writing on the wall. If the **AA has those filters in place, guess who will be using them? Why the NSA of course. Any bets on whether the **AA are digging so deep into their wallets on the legal battles because the NSA is promising to refund some portion of the cost, if they are not already secretly funding them from money that went missing in Iraq?
yeah, sounds a bit crazy, but after the lies that have been discovered lately, it would NOT surprise me.
...someone who put their own stuff on usenet and then someone comes along and falsely claims copyright infringment to the ISP and teh ISP takes it down.
Does the genuine originator ever get notified and given an opportunity to counter?
I see a lot of people saying "They don't host the files!"
This is absolutely wrong. They may not be the initial point that the file enters the network, but they DO host the files on their own servers there -entire- time that it's available to their customers. Every usenet provider does this. It's how the entire system works.
Each provider can choose which groups they will bother to handle (it used to be common for free services not to handle the 'alt.' newsgroups) and they -can- remove anything from that server that they choose. It wouldn't be fun to find exactly what the RIAA has requested a takedown for without specific post IDs, but it can be done.
Places that don't host the files are merely indexing services (like newzbin.com) and truly do not host the files. It's just a list of the post IDs that you need to grab what you are looking for from usenet.
I've never heard of a usenet provider that has removed partial content... Only entire groups, and never (that I've heard of) because someone asked them to.
So while it is theoretically possible for this law to protect them, they've never complied with it and it won't do them a bit of good.
It won't do the RIAA any good, either, though... Hundreds or thousands of servers all over the world mirror the same information from 3 to 200 days... They would have to individually ask for the files to be removed from each of them individually.
(Before anyone objects, I know they aren't stored as 'files', but that's irrelevant to the conversation.)
Despite the fact that this makes some modicum of sense, any sort of legal authority this is brought to isn't going to understand it.
What is, to us, a distributed and self-replicating system of nodes to distribute information (in the form of text "articles") worldwide is, to a judge, a website that sells access to copyrighted materials and refuses to remove them.
It's the same sort of roadblock torrent sites run into: computer illiteracy. Though, to be fair, it's not like judges should be required by l
### What is, to us, a distributed and self-replicating system of nodes to distribute information (in the form of text "articles") worldwide is, In all the decade that I have used the Usenet, I have never encountered a free provide that actually provided the *.binary.* groups, in fact most people considered posting binary to the Usenet a pretty stupid idea and in many Usenet hierarchies its not even allowed in the first place. Usenet.com, Giganews and friends really don't look to me much like a harmless Usene
Personally I rarely use Usenet for binaries - it's just too clunky since my main reader is for just that ("reading", not grabbing binaries), and the binary functions of the program are clunky at best.
That being said, I feel like binaries were a natural evolution of Usenet's purpose of information sharing (copyright issues notwithstanding). And I agree that the expressly binary providers are a lot like warez sites, however a suit against one provider (especially one called "usenet") will be bad PR for Us
What I notice is that while Usenet.com promoted -- stupidly perhaps in today's legal climate -- access to many MP3 files, I didn't see anywhere they they specifically said that these were illegal, copyrighted, RIAA member MP3 files.
The attitude of the RIAA appears to be that any and all MP3 files are by their very nature illegal, and that they deserve huge woges of money for anyone who has ever touched one. This, of course, is not true at all -- except in the mind of the RIAA.
If anyone at all is going to kill the rich culture of this country, it won't be the filesharers. It will be the RIAA, and copyrights extended to infinity -- and beyond!
Maybe i'm missing a point or two here. But it seems to me in order for anyone including the RIAA to define the content of Usenet they would have to decode the binary "and probably have to have a special reader for text" messages. UUencode YENC and MIME seem to be the major encoding types and seeing as the servers store purely code in an unidentifiable format there is no way they could actually SEE what is posted without downloading it and re-encoding it back to a compiled file. Movies/audio etc are all converted TO ascii and then back.
You cannot watch a stream coming into a usenet server and say it's an MP3 or MPEG or AVI If memory serves me. It's possible the subject line would be clear/plain text but more than that is encoding.
Correct me if I am wrong.. I've been using Usenet since 97 but it's been since like 98 since I investigated what made it work.
Seem to remember... (Score:5, Informative)
Re: (Score:2)
"Usenet.com has been refusing the labels requests"
Re:Seem to remember... (Score:5, Informative)
"To date, Usenet.com has refused to remove content or discontinue offering certain newsgroups."
Parent
Re: (Score:2, Interesting)
I ask , because the way usenet works , stuff doesnt stay on the server forever.
Re: (Score:3, Informative)
The Wired article [wired.com] has a link to the actual lawsuit in PDF format. It actually makes an interesting read.
Re:Seem to remember... (Score:5, Informative)
Parent
Re: (Score:3, Informative)
"If Usenet.com can show that it complies with the DMCA by removing access to infringing content and by suspending the accounts of repeat offenders, it may be enough to provide it with protection under the hosting and linking provisions of the DMCA."
Re: (Score:3, Funny)
Binary Retention Periods (Score:2, Informative)
Re: (Score:3, Informative)
It's worth noting that Usenet.com does not own/operate usenet, they are just a download service for usenet. They cannot remove things from usenet, they can only prohibit downloads of certain content from their servers, I'd imagine.
As a former INN server admin from 1994 to about 2001, that's bunk I'm sorry to say. I resisted modding you down (even have the points for it!) just to clear the air here. If you stream news to someone else, your removal of an article affects your downstream servers as well. It's quite easy to remove an article - always has been.
Re:Seem to remember... (Score:5, Interesting)
They probably refuse to take down content that is legally protected or that is legally not a full work and even if they take it down, within a few minutes another version might be up again so it sounds like the RIAA is going to have to send a lot of notices to take every single Usenet post down.
Parent
USENET? (Score:5, Interesting)
They wanna take down USENET?
And they're gonna target a single NNTP provider to do it?
OMFG, USENET was P2P before P2P was invented. It's so distributed, diffuse, and attributionless that it's practically untouchable.
Who keeps picking out windmills for RIAA to tilt at? Their legal attack strategist needs to put down the crack pipe and step away from his desk.
Seriously...
Re: (Score:2, Funny)
Re: (Score:3, Funny)
Re:USENET? (Score:4, Interesting)
Some ISPs don't provide newsgroup access anymore, make it a pain to get or have limits on uploading or downloading binaries. RIAA pressure could make this the norm.
Services like Usenet.com and Giganews are quite possibly vulnerable, as we see from this lawsuit. Maybe they'll try to go for customer logs next?
It may not be possible to take down Usenet, but it is quite possible to make it a little more difficult or risky than it is now for the average college student to access binaries.
Although I think the real point of this is to instill paranoia. RIAA lawsuits are a more than anything else a scare tactic and an effective PR campaign designed to instill fear in casual downloaders. That may be why they're going after Usenet.com instead of Giganews or similar sites, to instill some confusion and so that the aforementioned college student thinks he's at risk of a lawsuit himself if he downloads from Usenet (no matter what provider he uses.) My theory at least, take it with a grain of salt.
Parent
Re: (Score:3, Informative)
Bummer. But it was bound to happen. The binaries hosts have gotten a bit too blatant with their marketing and have made USENET binary downloads a far easier endeavor than it used to be. The critical mass of users which triggers copyright lawsuit
Re: (Score:2, Insightful)
Re: (Score:2)
If the large binary providers go down, it will be back to the days of scattered binaries, ever changing group names, and, any time a group gets too big, your provider will drop it.
It will no longer (or won't become) be a distribution method for the masses.
Re: (Score:2)
I hear they hired a guy named Don Quixote.
-
Re:RIAA's biggest mistake.. (Score:3, Insightful)
Seriously...
--
The RIAA's biggest mistake is picking up the role of angry bull elephant. When an angry bull elephant starts attacking the village with intent to cause as much harm as possible, the villagers are quick to;
1 Run and hide.
2 Put up defenses.
3 Directly attack the threat.
In short.. Number 1 is trade offline with the sneaker net. USB drives, USB music p
Common Carrier Defense ... (Score:4, Interesting)
Along these lines, what about Google/other search engines that show "copyrighted" content - either in the snippet or in their cache?
Re: (Score:2)
Along these lines, what about Google/other search engines that show "copyrighted" content - either in the snippet or in their cache?
The very short answer: No. They're protected by the DMCA safe harbor protections but they are not legally common carriers, which is probably a good thing since it carries a bunch of regu
Re:Common Carrier Defense ... (Score:5, Informative)
The issue is that Usenet.com blatantly (from a common-sense point of view, whether it's legally meaningful I have no idea) markets themselves as a way to illegally obtain copyrighted content. As someone put it yesterday, if the phone companies ran commercials advertising "Telephones -- the best way to plan your terrorist activities!" that would cut into their ability to claim common carrier status as a defense. Same thing for Safe Harbor.
Incidentally, didn't we have a story a few months ago complaining that the MPAA and RIAA weren't suing usenet providers, and how that proved some conspiracy theory? If that faction is relieved at this new development, I haven't seen them mention it.
Parent
Re:Common Carrier Defense ... (Score:5, Insightful)
Where I think they get into trouble is that, in order to claim Safe Harbor, they basically need to be able to claim "hey, somebody put that up onto our system, we didn't know it was infringing, we didn't even know it was there!" And it's a bit tough to do that with Usenet, seeing as how it's about 99% binaries and anyone who's ever opened up the alt.binaries.* hierarchy can tell that it's got a lot of bootlegs and warez in it.
It would be a little comical to see a whole bunch of seasoned network engineers and other greybeards try to claim that they had no idea there was copyrighted material on Usenet. ("Warez? On my Usenet?") But that's sort of the position they have to put themselves in, in order to get a successful 512(c) defense.
They also have to show that in the past they've complied with DMCA takedown orders against content that a copyright holder has pointed out as being infringing, which it seems like they weren't doing. That may also be a problem, although maybe they can argue that they didn't have the capability to delete articles (after all, if they took them out of their store, would they just have come in on a feed from another site that they peer with?). It might be difficult to get a judge to swallow that, though.
I think they're in trouble, but I'm not sure exactly how much trouble just yet.
Parent
Re:Common Carrier Defense ... (Score:5, Insightful)
Why is that a barrier to a successful 512(c) defense? If the host, Usenet.com in this case, services all take down notices in a reasonable and timely fashion and makes reasonable efforts to accommodate copyright holders (the court decides what is and is not reasonable) then have they not fulfilled their obligation under the law? How would they know if there was a copy of Eric Clapton's greatest hits on their network? Sure they could search for it if they wanted to but are they required to have automated agents searching all of the time for everything that might be copyrighted? Is that reasonable or even feasible? Certainly not, it is the responsibility of the copyright holder to locate infringement and take the legally required step of sending a take down notice. As long as there is a reasonable system in place to service requests from copyright holders, then the content host has fulfilled its obligations and should be able to take refuge in the safe harbor.
Parent
Re: (Score:2)
When dealing with a massive corporation shoveling buckets of money into the hands of the senators, the "won't somebody think of the children" argument is remarkably hard to hear.
Federal funds did * not * build the phone network (Score:5, Informative)
The first US telephone exchange opened in 1978. AT&T and the regional Bell companies were privately financed from day one and evolved into regulated public utilities.
The common carrier rule can be traced back to the days when Western Union was in its prime and censoring telegrams it found inconvenient.
With the the exception of civil engineering projects like the Panama Canal, federal spending on infrastructure begins with the New Deal of the 1930s.
Parent
The rub. (Score:5, Informative)
To be honest, I don't know how Usenet.com can not qualify for DMCA protection, since it's exactly the type of service that the Safe Harbor exception is supposed to protect. The only thing that seems like it could harm Usenet.com is their advertising, which does veer a little into "wink, wink, nudge, nudge" territory. However, damning a company because it says it respects users' privacy, without actually advocating any type of criminal activity, seems like pretty terrible precedent, and I can only hope (although at this point I have little faith) that a judge will see it similarly.
I think the mention in the Ars article about Safe Harbor being related to "transitory network communications" is irrelevant here. Transitory network communications is covered under 512(a) of the OCILLA (which is part of the DMCA); the portion that I would expect Usenet.com to seek protection under is 512(c), "Information Residing on Systems or Networks at Direction of Users".
You can read the relevant section here [cornell.edu], but the significant portion, IMO, is:
The major things they're going to have to avoid are that they "had actual knowledge" that the material was infringing (which might be tough -- I mean, anybody who opens up alt.binaries.movies can probably tell pretty quickly that it's full of bootlegs) and that they didn't receive a "financial benefit directly attributable" to the infringing activity. I think that second one is actually a little easier (for Usenet.com) than the former. And, of course, they have to successfully argue/explain that they don't really have the power to remove articles from Usenet, because of the nature of the network -- it would probably help their case if they started at least deleting articles from their spool/store when they receive a complaint.
I suspect that this may lead to a shakedown in the Usenet provider world, if Usenet.com loses. At the very least, the big providers might have to do more in order to maintain a veneer of plausible deniability (deleting some of the more obviously movie and/or warez related groups, perhaps), or move their servers out of the U.S.
Re: (Score:2)
Along with every single high-speed broadband provider on earth.
Re: (Score:2)
Wow. Suicide by advertisement. (Score:5, Informative)
http://www.usenet.com/articles/free_download.htm [usenet.com]
To wit: (in case they take the page down, which I sure would if I were them)The hell with it: They're pretty fucked.
Parent
Re: (Score:2)
Re: (Score:2)
Ok, let's begin with the obvious stuff (Score:2)
1) Usenet != usenet.com, which is merely a host. The RIAA is not attacking a protocol. They are suing a company that hosts a lot of NNTP traffic, some of which may be infringing on copyright.
2) It's fscking hilarious that the DCMA may wind up being used against the RIAA. Kudos to Ars for thinking up that one.
3) If the DCMA doesn't help, maybe the supreme court ruling stating that an ISP is not responsible for user generated content will. Details here. [dotcomeon.com] (Note: The article isn't about copyright, i
Re: (Score:2)
The DMCA specifically says that. this isn't new and it's what protects google et. al.
Take Down Notices? (Score:2)
a host not a carrier (Score:2)
Usenet.com is a host, not a carrier. It advertises easy access to pirated content. It is Usenet.com that may be going down, like Grokster.
Re: (Score:2)
Re:Take Down Notices? (Score:5, Informative)
Of course, that assumes the party issuing the takedown notice knew to cite the offending articles by Message-ID. The canceled messages will not re-propagate to the server. The poster, anywhere else in the world, could still repost under a new Message-ID (automatically generated for every posting). The cancel messages can even contain the takedown notice in each message body, which would be readable in the newsgroup named "control" and/or in "control.cancel" if it is present.
They wouldn't necessarily even have to cryptographically sign the cancels since they are local, though it might be wise to prevent fellow users of the same server wildly canceling other articles.
These organizations could technically send out their own cancel messages with unrestricted distribution, though I'm not familiar with the current state of the art in preventing forged cancels. If spammers have truly lost interest in Usenet, it may have come to the point where cancel messages are generally ignored.
Parent
So the **AA's plan is (Score:3, Interesting)
This is going to be interesting. If Usenet.com goes down, next will be NNTP service filters on every ISP in the US, and then by association, such efforts will be made in the rest of the world. Perhaps it might not work in Russia for fear of being mistaken for a spammer, but in the rest of the world, the US government and the **AA will push to have the entire Internet filtered...
The next step? To filter all your email, IM, and VoIP traffic as well, and in fact any method of sharing data. Sounds like tin foil hat stuff, but that seems to be the writing on the wall. If the **AA has those filters in place, guess who will be using them? Why the NSA of course. Any bets on whether the **AA are digging so deep into their wallets on the legal battles because the NSA is promising to refund some portion of the cost, if they are not already secretly funding them from money that went missing in Iraq?
yeah, sounds a bit crazy, but after the lies that have been discovered lately, it would NOT surprise me.
So how does this work for .... (Score:3, Interesting)
Does the genuine originator ever get notified and given an opportunity to counter?
Re: (Score:2)
"They don't host it!" (Score:3, Interesting)
This is absolutely wrong. They may not be the initial point that the file enters the network, but they DO host the files on their own servers there -entire- time that it's available to their customers. Every usenet provider does this. It's how the entire system works.
Each provider can choose which groups they will bother to handle (it used to be common for free services not to handle the 'alt.' newsgroups) and they -can- remove anything from that server that they choose. It wouldn't be fun to find exactly what the RIAA has requested a takedown for without specific post IDs, but it can be done.
Places that don't host the files are merely indexing services (like newzbin.com) and truly do not host the files. It's just a list of the post IDs that you need to grab what you are looking for from usenet.
I've never heard of a usenet provider that has removed partial content... Only entire groups, and never (that I've heard of) because someone asked them to.
So while it is theoretically possible for this law to protect them, they've never complied with it and it won't do them a bit of good.
It won't do the RIAA any good, either, though... Hundreds or thousands of servers all over the world mirror the same information from 3 to 200 days... They would have to individually ask for the files to be removed from each of them individually.
(Before anyone objects, I know they aren't stored as 'files', but that's irrelevant to the conversation.)
Kinda Sad (Score:2, Insightful)
What is, to us, a distributed and self-replicating system of nodes to distribute information (in the form of text "articles") worldwide is, to a judge, a website that sells access to copyrighted materials and refuses to remove them.
It's the same sort of roadblock torrent sites run into: computer illiteracy. Though, to be fair, it's not like judges should be required by l
Re: (Score:2)
In all the decade that I have used the Usenet, I have never encountered a free provide that actually provided the *.binary.* groups, in fact most people considered posting binary to the Usenet a pretty stupid idea and in many Usenet hierarchies its not even allowed in the first place. Usenet.com, Giganews and friends really don't look to me much like a harmless Usene
Re: (Score:2)
That being said, I feel like binaries were a natural evolution of Usenet's purpose of information sharing (copyright issues notwithstanding). And I agree that the expressly binary providers are a lot like warez sites, however a suit against one provider (especially one called "usenet") will be bad PR for Us
All MP3's Are Infringing (Score:3, Insightful)
The attitude of the RIAA appears to be that any and all MP3 files are by their very nature illegal, and that they deserve huge woges of money for anyone who has ever touched one. This, of course, is not true at all -- except in the mind of the RIAA.
If anyone at all is going to kill the rich culture of this country, it won't be the filesharers. It will be the RIAA, and copyrights extended to infinity -- and beyond!
I thought most if not all of Usenet is encoded. (Score:3, Insightful)
Maybe i'm missing a point or two here. But it seems to me in order for anyone including the RIAA to define the content of Usenet they would have to decode the binary "and probably have to have a special reader for text" messages. UUencode YENC and MIME seem to be the major encoding types and seeing as the servers store purely code in an unidentifiable format there is no way they could actually SEE what is posted without downloading it and re-encoding it back to a compiled file. Movies/audio etc are all converted TO ascii and then back.
You cannot watch a stream coming into a usenet server and say it's an MP3 or MPEG or AVI If memory serves me. It's possible the subject line would be clear/plain text but more than that is encoding.
Correct me if I am wrong.. I've been using Usenet since 97 but it's been since like 98 since I investigated what made it work.
sue the internet (Score:2)
What I want to know is, how long until the RIAA sues Internet.com, because of infringing stuff they found on the internet?
Re: (Score:2)