The End: NZBMatrix closes
nzbmatrix.com
nzbmatrix.com
Extremely common DMCA misconception: it's not enough to be "takedown compliant". That's not how the law works. You also can't ever operate with specific knowledge of infringing content; you are, in effect, required to "take down" any pirated content you find.
My technical understanding of this could be incorrect, but it seems to me that there is a meaningful difference between a BitTorrent tracker actively coordinating copyright infringing downloads vs. a website like NZBMatrix hosting nothing but static links to another location on the Internet.
At any rate, services like these rely on the DMCA Safe Harbor provision. Regardless of whether the potential liability is civil or criminal, you can't have actual knowledge of infringing activity on your site and the ability to remove that activity from your site and claim safe harbor.
It seems to me that the only difference between Google and NZBMatrix et al is that the media companies like one more than the other.
Sure, if you only watch high quality stuff like Skyfall and listen to Lady Gaga, a site like nzbmatrix is probably useless to you. But for those who appreciate things that aren't that easy to come by, it is essential to have some sort of an index to even HEAR about them. My estimate is that at least half of the movies and games I got through nzbmatrix, I had not heard about anywhere else. And as every usenet user knows, it's basically just not possible to "browse" the usenet itself.
Then there are software releases where 95% are fake or bug-ridden. Where it saves a LOT of trial & error if people help each other out by posting only those that are for real.
And I found no other nzb site as useful when it comes to finding all new releases. And I have looked at them all because I did not appreciate nzbmatrix's own censorship.
Here lies the real problem
I suspect I probably got burnt trying bitcoin, but I would still warn anyone against using Blockchain for anything more than a toy.
The alternative is to run your own client, and download close to 3GB of data at a snails pace. Neither are at all attractive at the moment.
Banks are massive and have pretty much everything insured. If they mess up, it's on them. Not so much with bitcoin, if they mess up their users lose out.
Additionally demonstrated by Mt. Gox, most bitcoin services are run by complete novices. Basic SQL injection on a website dealing with currency is unforgivable.
They're right that many providers are getting hit with notices, which causes them to remove a few chunks of each rar from their server making it impossible to complete the download and too pervasive for repair by typically-sized parity file, but this can be circumvented by using a lesser-known news server as a backup; you still use Astraweb or Giganews for 99% of the transfer, but your fallback picks up the pieces that have been DMCA'd out of AW/GN/another major carrier.
I would be happy to see a more intelligent splitting system than rars, as one missing block in a couple of rars will often make it really difficult to extract the content you DO have and use a more robust delivery system, like a torrent, to download the blocks you're missing. This is going to become increasingly important.
News servers are interesting because they really are a non-optimal method for this kind of transfer that has incidentally become a hot bed for filesharers, probably just because of the plausible deniability ("yes officer, of course we only intend our server to be used by those discussing photography..."). I too wonder if it's not time for a new protocol, something more direct than torrents (webseeds kinda works here, but not quite what I'm looking for) but less hacked-up than NZBs and ASCII-encoded binaries in split files.
It's time to stop skirting around the issue and try to put together a serious underground analog to direct-downloaded binaries, something hearty and immune, or as immune as possible, to interference and foul play like this.
When I was 18, I ran a competitive (on the Freenix leaderboard) full-feed Usenet server for the ISP I worked at. Every ISP in the world could have provided full-feed Usenet access, but for the assholes who loaded the system down with ASCII-encoded binaries. Even while it was possible for an independent provider to offer Usenet to customers, it was still a total nightmare because of the ludicrous storage requirements for binaries, which ensured that only an ever-dwindling number of providers would take the time to offer it at all.
It's startling to me that there's a Usenet at all anymore, since it's essentially been reduced to a collaborative system for sharing pirated binaries.
So I am chuckling at the idea that some young guns who want to be "free" to do what ever they want in their network of computers to come up with a scheme where they are will use telephones to call up one computer to the next, and addressing will be free form a series of "hops" where you tell the computer what sequence of machines will have to be called in order to get your message from you to your destination. You could use a character like ! to separate the hops making an address 'bobs-machine!piratebay!alices-machine!alice' delivering through three hops to Alice.
I wasn't still around, but I expect the second wave of automated binary posting/retrieval tools in the late 90's probably created the surge that changed Usenet access into a separate paid service, no longer something that came with an ISP account like email.
However, it wasn't just warez and porn that killed Usenet. Spam took off there before email, and it wasn't until email spam became untenable that modern automated filtering tools were created.
Furthermore I don’t think it’s true that the Usenet is dead. There are still some active groups that rely on it. It’s just that there’s so much more these days. There are several social services competing with each other, there are a lot of web sites that let you discuss about things and are targeting specific niches.
Usenet wasn’t killed, it’s natural progress.
NZBMatrix was just one of dozens of indexing sites.
Apparently their last payment gateway wouldn't deal with them any more.
*Thought it was part of the DMCA
They have allegedly shut the site down because they lack the resources to handle the growing tide of takedown requests.
In other words, though you don't have an active duty to police your site, if you do become aware, and don't take action, you're not protected. Similarly, if you set up something with the sole purpose of distributing copyrighted material, and try to hide behind a "gosh, we never knew that kind of thing was going on until you told us", you're probably not going to get a court to believe you.
>Once this notice is completed we are left with an impossible task of policing our indexing bots. Even then it won't stop there, there will be follow-up notices etc.
This seems to me like they're being told to actively police automatically-indexed content after this notice is processed?
I'm not sure how provable that 'knowledge of infringement' clause is.
In any case, with more and more takedown requests being directed at usenet providers, I think usenet's days as a safe haven for piracy are numbered.
Generally speaking it's very easy to find material just using binsearch. If you want a 1080p copy of a particular film, just search for the film name along with '1080p' and you're almost guaranteed to get relevant results on the first try.
Almost all the automation tools spoke newzbin and nzbmatrix.
Back to torrents / DC++
It helps if people put big pars out.
Indices come and go... Much of the Usenet crowd know how to set up an indexer if need be. Perhaps a hidden service is warranted?
[1]: Basically, you connect to a central server (that anyone can run), and you can share files with other connected to the server, chat with them (a single central chat room), private message connected users, and search files shared by connected users. Note: that some of this may be out of date as I'm mostly referring to the initial implementation.
Wow, a blast from the past - AND a comment asking what it is.
Is it weird to feel old at 29?
"2TU4K75C6Z" (45 rars, 9 pars)
And here's one from a.b.multimedia...
"DTTBiAp23.101.by.NYCrules" (14 rars, 11 pars)
no .nfo included and no way to know what's inside. Does anybody know how people are decoding these titles into meaningful information?
"291112_08_29" (60 rars)
There are lots of these and they are interesting because the first part suggests a date, 29/11/12, and the second part suggests a sequential number. The size is almost 6 gig.
The first one is passworded, presumably detected by looking at the RAR header.
I can't find the second.
All in all, nzbs are a much more pleasant experience if you can afford the account (and pretty much any employed person can) and have a good indexing site (harder to come by, and now I don't have one either :( ).
Just a heads up for whoever wants to do the same: the process that it goes through to create the releases is that it downloads all of the binaries and parts and then runs that through a few regular expressions to determine what goes with what and how it should be categorized and displayed. The free community edition only ships with two regular expressions and it wasnt creating releases for me. I donated to the project and got a lot of regexes plus some other stuff and now it works as expected.
I'll be building a box to handle this in my home.
http://usenetreviewz.com/dutch-usenet-providers-banned-by-pa...
http://falkvinge.net/2012/11/20/europarliament-scolds-visa-m...
Here's a breakdown of one NZB, for a single 3.88GB file.
Inside are 74 RAR files, and 15 additional PAR files containing parity for recovering corrupted data.
Each of these 89 files is split into 37 parts of 1.4MB for ~3200 pieces total.
These pieces are then encoded with yENC (similar to base64) and then uploaded to the newsgroup.
Every single one of these yENC pieces is referenced in the NZB file, making for a total of 400KB. Just because of this, the NZB indexs are enormous; hundreds of gigabytes, probably terabytes in some cases.
> downloading billions of headers to try and find a
> particular NZB is a mammoth task
This is true. Even a ~10 of years ago, downloading just the headers on some of the newsgroups shot my cache directory into the gigabytes (for a single newsgroup).http://en.wikipedia.org/wiki/Spotnet
The searchable information (and comments and such) is distributed through Usenet itself.
In my short few weeks of using it, the API seems better than nzbmatrix, but the community / comments on files is near nonexistent. If you're only looking for something to hook up to sickbeard / couchpotato though, it should do the job just fine.
I don't care who you are, if you see an agent, you do what the rest of us do. You run. You run your ass off.