Dutch Usenet Provider Ordered To Remove Infringing Content
dutchwhizzman writes "Amsterdam-based Usenet wholesale provider News Service Europe has been mandated by a court to remove all copyright-infringing content on their servers, or face severe financial penalties. Dutch copyright organization BREIN has won a court case making the Usenet provider responsible for the content posted on platforms other than their own. Could this be the end of Usenet as we know it, or will an appeal be won by NSE? Why didn't the judge make the provider that allowed the posts responsible? Why didn't the judge honor the 'cancel message' procedure that technically exists in the NNTP protocol?"
News-Service.com sold their services to the likes of Binverse and Usenext, so it's not really surprising. While it takes away sad piece of history, the leeches and warez destroyed it. While some people still use it for talking, for the common people and most of the world it's just like BitTorrent. Not like I agree with the situation, but if something that is a major problem needs to be shut down and for the few using it for legal purposes need to move to something else, well, it's not surprise move.
While still being somewhat similar to ISP's and contraty to popular belief here on Slashdot, it's the intent that counts. That's why ThePirateBay was also found quilty in court.
Such a shame. Usenet was a tiny little holdout of what the internet used to be. Crazy, lawless, illegal, sometimes informative, and full of porn and spam.
I dont know what you're talking about... but I agree :P
Duh, Judges judge law, they don't know technical protocols and unless outlined and understood properly they are poorly equiped to issue judgements based on the information they receive by prosecutors and defense attorneys... imho :-)
You aren't fooling anyone AC.
We all know that the REAL way you got good at using regular expressions was by bulk downloading alt.sex.binaries, then using ls, grep, and rm to automatically remove all the kiddie porn before the fbi became the porn police.
You only refuse to talk about it now out of fear of goons knocking in the door. ;)
Could this be the end of Usenet as we know it
Usenet as I knew it was a bulletin board system for worldwide discussion of all kinds of subjects under the sun, from politics to auto mechanics to cigars to, of course, Star Trek - For me it was never a place to download gigabytes of binaries of Fringe episodes. To me, SPAM killed usenet, not a binaries ban.
before the mouth breathers and their lawyers understood how to use the internet and we could enjoy it with impunity,
The link provided returns: You have asked Firefox to connect securely to torrentfreak.com, but we can't confirm that your connection is secure. The certificate is not trusted because the issuer certificate is unknown.
Fifty years of Yippie! 1968-2018
Once again they point fingers at the hammer, while the thief gets away...
Burn the land and boil the sea........
Dear government. You provide the streets, therefore you are responsible for all crimes taking place on said streets. If you cannot stop all crimes on the streets you will face severe penalties.
Therefore, I conclude that this is fucking stupid.
Ok, fess up you guys. Who told the government about USENET?
There was a time when patches were distributed via usenet. I haven't touched it since technology shifted to web interfaces, subversion clients, etc.
But as far as I can recall, it was always rife with spam, offtopic posts, script kiddies, porn, and illegal binaries.
I won't mourn usenet any more than I mourn the kermit protocols.
Sad that another company's business is going the way of the dodo, but that's life.
I do not fail; I succeed at finding out what does not work.
Is it me or is https://torrentfreak.com/major-usenet-provider-ordered-to-remove-all-infringing-content-110929/ untrusted? My Mozilla's SeaMonkey v2.0.14 web browser says:
"torrentfreak.com uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
The certificate is not valid for any server names.
The certificate expired on 2/9/2011 6:43 AM.
(Error code: sec_error_expired_issuer_certificate)"
ELinks v0.12pre5 says "SSL Error".
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
They waited till Friday to announce this. Bad news is best broken on Fridays.
"A 'person' is smart. 'People' are dumb, panicky animals and you know that."
The answer to why server admins don't honor cancel control messages is simple: they are routinely and regularly abused and honoring them would make USENET unusable.
This decision will be the death knell for USENET. Making server admins responsible for monitoring content will get them to turn it off.
How do they know what content is copyright infringing?
Snuff the binaries groups and improve Usenet. It will still be spammy though.
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
Why didn't the judge honor the 'cancel message' procedure that technically exists in the NNTP protocol?"
Because that's implementation details that the judge doesn't and shouldn't care about. If they want to remove the content that way, he'll decide whether or not that's good enough to count as compliance. But the job of the judge is to decide what should be done, not how.
Assorted stuff I do sometimes: Lemuria.org
database sites that generate NZB files. Makes it easier for the technologically illiterate to use it, therefore brings it onto the radar...
Because News Service Europe stores the infringing posts and makes them available. The judge has to honor the law and the company has to follow it not some self appointed RFC "cancel" procedure that may or may not work. Why is it that whenever a downloader gets cought people say: go for the hosters, when a hoster gets cought go for the provider when a provider ....
An enormous FAQ on RFC cancel, cancel bots, forged cancels, cancel wars, etc. can be found here:
http://wiki.killfile.org/projects/usenet/faqs/cancel/
Unfortunately, the ability to cancel someone else's post is just too much power, so that privilege is not freely given out. Chances are, this hoster has probably turned it off. Maybe just turning it back on would be considered "following the judges orders", but it would open a lot of new problems.
A better way to fight this is using Mere Conduit, which is similar to the Safe Harbor provisions we have in the DMCA.
Free unix account: freeshell.org
Not in the USA: we have the DMCA "safe harbor" provisions.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
The Dutch were notorious for abusing Usenet binaries. They would post floods (ignoring upload limits in group rules, such as uploading whole TV seasons all at once), post off-topic binaries (such as US cartoons in anime groups), post passworded archive binaries, and worst of all, they had warez-exchange programs using Usenet as a file transfer protocol that meant they didn't have to care, much less know, what Usenet was. Basically, they used alt.binaries.* as their own personal file dump. And their news admins didn't care.
I'm not surprised that Rule #1 and Rule #2 were broken over there. Nor am I sympathetic about this situation.
And cancel messages? Gimme a break. Once the net.kooks learned that they could forge cancels to wipe anything they didn't agree with, larger NSPs simply ignored cancels wholesale. That was in the mid '90s or so.
#naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
How does this spell the end of usenet? There are way more providers than this one.
Could this be the end of Usenet as we know it?
For those of us that were around before Usenet existed, and watched it overtake local dial-up BBSs i can assure you that Usenet effectively died a long time ago. The Usenet of today is just a obscure shadow of what it was at its height.
---- Booth was a patriot ----
... the provider did offer a YouTube-type "if you tell us we'll remove it" deal but BREIN didn't want that. BREIN ultimately wanted to create a precedent where the owner of a service is solely responsible for finding out which content infringes on random copyright, remove it from their servers and from everybody else who downloaded it.
Custom electronics and digital signage for your business: www.evcircuits.com
alt.nuke.the.usa
While searching for some foreign music, I ran into a 'catchall' on Google...
They'd gotten a take-down notice for including search results about licensed anime, on blog and database sites -- that included no downloads or links to downloads...
Now we are talking not just going after linkers, but linkers to people who even talk about the content.
The takedown notice to google (to block search results -- freedom of speech),
shows the list of sites I first ran into...then I ran into a real hilarious one --
one against TWITTER -- and multiple 'twitters' that were deemed
infringing content!! Like I be they were distributing movies 140 bytes
at a time!
Yeah...must be some serious 'intent' going on here...
Oh yeah...lest I forget...the takedowns against Music Blogs almost 12,000/month -- musta been writing about the lyrics...
Yeah, right...
For every 'pirate' out there, there, there are 10-100 corporate pirates stealing the rights of the rest of us...
Yeah, tell that to my ISP that decided to get rid of it just because they don't want to risk taking a risk with a risk of risking risk with risk.. yadda yadda...
My provider's name is Time Warner.
phpBB (and other messageboards, like vBulletin) killed usenet.
that the only remaining purpose of USENET is accessing binaries of pirate material, than it's day has long past. The only requirement to apply this decision is to remove the binaries newsgroups. and maybe some post filtering as well. That will cut down 90+ percent of the data traffic.