11–20 of 89 posts
So if you only want to download some of them, you first have to wait for the magnet to download the torrent, then go back to it and pick the files you want.
A magnet link also makes it hard to check if the link you are looking at is a duplicate of what you have already.
With a torrent you can check the file size and compare to others.
I've been using mostly magnet links for the past year and haven't experienced any issues. If people understand that they work just like a normal link/torrent file, this won't make the process any more complicated. Hopefully this is another win in the long run, as links are harder to stop than files.
Only slightly as I understand it, since from a legal perspective the intent of someone providing providing links instead of files doesn't change, and that's what counts. From a technical perspective, and as someone who doesn't understand how magnet works under the hood, I'm slightly concerned that DHTs might be easier to attack in an underhanded manner than an HTTP server would have been.
Indeed, but a link can be posted anywhere a user can post text. Here, have Pioneer One:
magnet:?xt=urn:btih:3a4be1d48c31dfa62bf52958f3fdca3d5ce91cf1&dn=Pioneer%20One%20SEASON1.720p%20x264-VODO
I can see this leading to a block on many sites on all links starting with the "magnet"-protocol, if it's not in place already. It also highlights the issue with SOPA further. Had that series not been allowed to be shared, Hacker News would be in big trouble for hosting the link.
So, what if you don't run the client on the same machine you're browsing TPB with, like people who have torrent enabled routers or VPS/seedboxes? I suppose you can copy-paste the link to your client, but clients which had automatic pick-up of .torrent files (like rtorrent) were nice because you could just drop them on a remote directory and have them be downloaded. I wonder if I could write a small application just t…
I tested it, and it works as advertised.
For firefox integration, in about:config create a new boolean as:
network.protocol-handler.expose.magnet := false
So, what if you don't run the client on the same machine you're browsing TPB with, like people who have torrent enabled routers or VPS/seedboxes? I suppose you can copy-paste the link to your client, but clients which had automatic pick-up of .torrent files (like rtorrent) were nice because you could just drop them on a remote directory and have them be downloaded. I wonder if I could write a small application just t…
One drawback to magnet links is that you can not in advance see what files are there. So if you only want to download some of them, you first have to wait for the magnet to download the torrent, then go back to it and pick the files you want. A magnet link also makes it hard to check if the link you are looking at is a duplicate of what you have already. With a torrent you can check the file size and compare to other…
I've been using mostly magnet links for the past year and haven't experienced any issues. If people understand that they work just like a normal link/torrent file, this won't make the process any more complicated. Hopefully this is another win in the long run, as links are harder to stop than files.
Only slightly as I understand it, since from a legal perspective the intent of someone providing providing links instead of files doesn't change, and that's what counts. From a technical perspective, and as someone who doesn't understand how magnet works under the hood, I'm slightly concerned that DHTs might be easier to attack in an underhanded manner than an HTTP server would have been.
The key is in the D. Since it is distributed, there's not a single server that can be attacked.
Earlier quoted context omitted.
Only slightly as I understand it, since from a legal perspective the intent of someone providing providing links instead of files doesn't change, and that's what counts. From a technical perspective, and as someone who doesn't understand how magnet works under the hood, I'm slightly concerned that DHTs might be easier to attack in an underhanded manner than an HTTP server would have been.
"Only slightly as I understand it, since from a legal perspective the intent of someone providing providing links instead of files doesn't change, and that's what counts." Indeed, but a link can be posted anywhere a user can post text. Here, have Pioneer One: magnet:?xt=urn:btih:3a4be1d48c31dfa62bf52958f3fdca3d5ce91cf1&dn=Pioneer%20One%20SEASON1.720p%20x264-VODO I can see this leading to a block on many sites on all…
Linux Distro excuse comes to mind.
A cynical person might say that the intent would also further kill free content creators, restricting the supply of content; consumers then see only paid content.
Earlier quoted context omitted.
"Only slightly as I understand it, since from a legal perspective the intent of someone providing providing links instead of files doesn't change, and that's what counts." Indeed, but a link can be posted anywhere a user can post text. Here, have Pioneer One: magnet:?xt=urn:btih:3a4be1d48c31dfa62bf52958f3fdca3d5ce91cf1&dn=Pioneer%20One%20SEASON1.720p%20x264-VODO I can see this leading to a block on many sites on all…
That would be a restriction of freedom of speech and Internet Freedom for blacklisting magnet urls. Linux Distro excuse comes to mind. A cynical person might say that the intent would also further kill free content creators, restricting the supply of content; consumers then see only paid content.
Earlier quoted context omitted.
That would be a restriction of freedom of speech and Internet Freedom for blacklisting magnet urls. Linux Distro excuse comes to mind. A cynical person might say that the intent would also further kill free content creators, restricting the supply of content; consumers then see only paid content.
Sadly, that hasn't prevented censorship of "neutral" keywords before. See: https://torrentfreak.com/googles-anti-piracy-filter-110712