Slashdot Mirror
Popular Torrent Site ExtraTorrent Permanently Shuts Down (torrentfreak.com)
ExtraTorrent, the world's second largest torrent index, on Wednesday said it is permanently shutting its doors. The site, which launched in 2006, had steadily climbed the ranks in the piracy world to become the second most popular torrent site, observing millions of daily views. TorrentFreak adds: "ExtraTorrent with all mirrors goes offline.. We permanently erase all data. Stay away from fake ExtraTorrent websites and clones. Thx to all ET supporters and torrent community. ET was a place to beâ¦." TorrentFreak reached out to ExtraTorrent operator SaM who confirmed that this is indeed the end of the road for the site. "It's time we say goodbye," he said, without providing more details. [...] ExtraTorrent is the latest in a series of BitTorrent giants to fall in recent months. Previously, sites including KickassTorrents, Torrentz.eu, TorrentHound and What.cd went offline.
Nyaa.se was shut down voluntarily as well at the beginning of the month, but a group from the fandom and people close to the old site started a replacement that will eventually be just like the old site for all intents and purposes.
There have been multiple volunteer shutdowns in recent weeks, whether it's release groups like JYK or torrent sites like Nyaa. No information is ever revealed as to why they decided to shut down, just that it was voluntary. I assume somebody is putting a lot of pressure on these people and they're doing it to avoid criminal charges.
This is clearly a far better approach to stopping piracy than suing a few downloaders, but I'm not sure they can win this game of whack-a-mole. Nyaa was almost immediately replaced by nyaa.pantsu.cat, while the Pirate Bay is still running as an alternative to ExtraTorrent. It'll be interesting to see what happens if they sustain this attack.
https://sourceforge.net/projec...
Is there a reason one would use a site like extratorrent rather than piratebay? They all just list torrents, right? I recognize I'm terribly uninformed when it comes to piracy, just wondering if I'm missing something.
If you put the word 'illegally' then yeah, i think most would say no. The problem is, i don't think it is EVER a crime to share ANY information. The only crime one can do with information is to bypass someones firewalls and security measures to gain access to information stored on a hard drive that does not belong to you. That to me is 'digital trespassing' but i don't think sharing information over the internet should ever be a crime, in any form whatsoever
Why aren't there any distributed indexes? Seems silly to have an entire distributed distribution system without a matching index.
Torrents were made so that you could put a 10kb torrent file instead of a 700 MB Linux ISO on your website, it was a way for a master source to "crowdfund" hosting. It didn't try to be a P2P solution like Napster or Kazaa. That's also why they never got sued, nothing about the tool itself made it dubious in the the eyes of the law. The biggest problem with an index is spam and DDoS. For it to work well I think you'd have to do something more like RSS with digital signatures and PGP's web of trust. Like say if you find a torrent made by a release group, you can subscribe to their "channel" where only they can post new torrents + info about other "channels" they trust/no longer trust.
Even then there's issues of propagation and when a client should start/stop searching for new posts. Then again magnet links are pretty small, might just say that every update is a full replacement with a timestamp and max limit like 1000 torrents * 20 (SHA-1) = ~20kb. So distributed host checks signature and timestamp, if newer replace RSS "feed". Client asks by signature hash and gets the latest version, can verify signature and start downloading the magnet links for more info on each entry. Web of trust can be done similarly, hash of trusted signature + trust value. It all sounds pretty doable...
Live today, because you never know what tomorrow brings
Technically speaking, It's not impossible; The problem is that it's spammable/DoSable and will need an authority to either allow/deny nodes from inserting to index or someone like our good old friend 'hosts guy' to maintain a list of known good source nodes that people can download and only share the indexes from those.
No authority is needed, because there isn't one already. In the centralized index situation, no human validates torrents uploaded to the centralized indices. Instead, the users do. If you go search for any blockbuster movie you care to name on Pirate Bay, you'll get 50 pages worth of hits. The first 10 to 15 hits might be useful, with various bitrate encodings and various subtitles and audio tracks in them, and then it very very quickly tails off into utter trash. It doesn't seem to hurt Pirate Bay. Nobody ever selects the torrents with zero seeds unless they're looking for something so niche that there's no other option, and no one seeds bogus torrents. Even their pathetic originators give up extremely quickly.
And/Or other simple restrictions like limiting the number of torrents any node can add to the index.
In a decentralized index, that limit is only in the local node, where it is easily removed. Not worth bothering to write the code in the first place.
And/Or a voting system that allows all nodes to vote on others to help the client applications with prioritizing/filtering the index.
The seed count effectively serves as a voting system today. It's by far the most useful metric. About the only other useful metric is a user-defined list of strings. Quality video encodings tend to have some release group tag in the torrent name. Easy enough to push priority up a bit if the user's preferred string is present.
What's missing is implementing support for search within Mainline DHT. Kademlia DHT on which it is based has a scheme already designed:
Filename searches are implemented using keywords. The filename is divided into its constituent words. Each of these keywords is hashed and stored in the network, together with the corresponding filename and file hash. A search involves choosing one of the keywords, contacting the node with an ID closest to that keyword hash, and retrieving the list of filenames that contain the keyword. Since every filename in the list has its hash attached, the chosen file can then be obtained in the normal way.
Mainline DHT has omitted that functionality. If it were implemented, index sites would no longer be required.
Obviously Mainline DHT traffic would increase substantially, but it would still be quite small compared to torrent traffic. Also, if it were implemented exactly as described, clients would be responsible for filtering results coming in from the DHT. Most users want the logical AND of their search terms, but Kademlia specifies a logical OR. Performing that processing is simple enough though, and of course the client could present results much like web search engines do, with results that contain as many of the keywords as possible presented first, followed by results with fewer and fewer matches. You don't get the fuzzy matching most of the web search engines employ doing that, but as it happens, you also don't get fuzzy matching from Pirate Bay search anymore, so that's no loss. Client authors then have the option of preemptively fetching .torrent files in order to get tracker lists to be able to rank the results by how active they are, or of waiting to let users do some manual culling first. That whole process is substantially slower than a centralized index site. Mainline DHT is anything but fast, most of the time. It is, however, bulletproof. As long as the DHT exists, files could be found.
BEP 0005 specifies KRPC methods of ping, find_node, get_peers, and announce_peer. What's needed is a new BEP to extend the protocol, adding search_peers.