That would make it impossible to copy the magnet link from the search results page, which I believe is a really nice usability perk. For users that are less technically inclined, clickable links could be crucial (even if it gives you the theoretical possibility to track the click).
I guess it depends on if you are prepared to be a search engine only for the 1337 crowd, or if you want casual users to have access to a decent search engine too. The Hacker News crowd could still just right click and copy the magnet link, so essentially you're just removing features for those who don't understand how technology works but are still dependant on it.
Perhaps the best idea would be to keep the link and have a text area for selecting and copying like requested above.
Consider this.
I don't get this. It's a magnet link with magnet protocol. It will be handled by your torrent client, no additional request to the server whatsoever if you click on them. It's the same as plain text copying, but more convenient.
I don't think that one is.
If in doubt: If it happens over or in a browser window, it is probably trackable from JavaScript.
See: https://developer.mozilla.org/en-US/docs/Web/Events/copy
Same origin policy doesn't do anything to stop you from being tracked, though.
Or if you just block scripts.
1. The search engine adds itself to the tracker list in the magnet URI (&tr= query parameters), but with a unique subdomain and using HTTP (i.e. it adds http://asdfkja.skytorrent.in/announce to the tracker list)
2. The client announces itself to the tracker, sending the unique "Host" in the GET request (asdfkja.skytorrent.in in the example).
Email addresses can be used for tracking by having each request for an address (e.g. each GET of a "contact us" page) return a different email address (e.g. contact43327@example.org). Checking which address gets used allows the GET request (and all associated information) to be associated with the email message (and all associated information).
Likewise, magnet links can be tracked by looking for torrent clients trying to access them. A sibling has pointed out that unique tracker URLs can be used for this. Another way would be to make up a unique content hash for each request, then lurk on the DHT looking for queries for those hashes.
If the operator has no qualms with transferring data (e.g. being directly exposed to copyright infringement) they could even service such requests, with the user being unaware of the fact they're being tracked: the operator alters the hash by making some innocuous "watermark" change to the content, e.g. altering a filename inside an archive; each time a chunk is requested, the operator fetches it from the "original" and passes it on.
To keep the technical details short: the events are logged with JS and sent over either ajax or a websocket in the background as you navigate the site.
http://www.bittorrent.org/beps/bep_0009.html#magnet-uri-form...
That being said DHT and PEX (BEP 5 and BEP 11) is good enough that you don't need them.
For example, to get information about torrents that are on life support (e.g. have a couple seeds that show up for a few minutes a day), having the torrent file downloadable is invaluable, as it includes info like the size and the file names, etc. In many cases it's even possible to bring a torrent /back to life/ if you have the torrent file and got the content that was in it out of band.
If you just have the magnet link you cannot do any of this.
I use this all the time for downloading very long tail content, and the move to have indexing sites be magnet-only is very frustrating.
I prefer using torrent files, because I can just wget/curl them down into a directory being watched by my server which downloads torrents.
Is the current world we live in.
A magnet as a link would be more useful. I'm sure the people worried about letting others know what they download can copy the link without clicking anyway.
Selecting the text will trigger no such request, the developer will still know who opened the site and searched for what, but he cannot know the exact torrent that was copied.
http://dcarlbom.com/google-tag-manager/event-tracking-gtm-wh...