I have merkle roots
But that doesn't help you
I thought we were agreed tentacle roots is where it’s at?
does anyone know how to actually add a http source to a torrent file?
so apparently there are two competing unapproved BEPs on that https://wiki.theory.org/index.php/BitTorrentSpecification#WebSeeding
one of which requires dynamicity on the webfront
I have the links for field 7 ready
and damn, getright is still around
i wonder what blizzard does in its updaters
or microsoft these days for that matter too
seems simple enough, just add a list http://bittorrent.org/beps/bep_0019.html
that should be encodable as a magnet uri as well
url-list
(anyone can already use the above links)
@mjay so i guess just grab the current torrent, edit and try
@Rotonen how to edit? Looks like binary
last i looked they were plaintext, compression?
but it has been over 10 years
I have the raw files on the servers - I need to change url-list instead I guess
or just make a magnet uri of it and add ws= parametres to the query string
and add the tracker as a tr=
and urlencode
http://torrent2magnet.com/ Torrent to Magnet online converter
magnet uris are IMO neater to deal with than .torrent files
the info hash for field 7 is 9760e073e3cf6dbe6f2525040f1550b8d3a73eb6
so that as btih, tr pointing to the tracker of @Fireduck and multiple ws parametres pointing to the servers should do the trick
some assembly required, cannot conveniently enough pull that off on a mobile
I'll probably setup a tracker as well
DHT should cover most users
or just using open trackers
unless you explicitly want to monitor the swarm easier
can someone set this up? torrents are nothing I'm experienced with
My part is setting up the mirrors
at a terminal now, will try
field 8 and 9 are also ready, same ip's
so, starting point, here is a valid magnet uri for the field 7 torrent `magnet:?xt=urn:btih:9760e073e3cf6dbe6f2525040f1550b8d3a73eb6`, next step is to add the tracker to that
working magnet uri with the tracker in there `magnet:?xt=urn:btih:9760e073e3cf6dbe6f2525040f1550b8d3a73eb6&tr=http%3A%2F%2Ftracker.1209k.com%2Fannounce`
goes to setup a tracker
@Rotonen you suggest any trackers?
no, i roll with DHT
i do not see the point of trackers
@mjay not a 100% on how that works for directories and not single file torrents - can you symlink or move the one on 136.243.82.213 to match the directory structure from the torrent? it could be fine you just offer one of the files (as in the large one), but i suppose it needs to match the file list by path
at least pointing the webseed parametre at the file or the root of the server does nothing for me
heh, getright documented it well enough http://getright.com/seedtorrent.html Award-winning GetRight download manager software for Windows. For faster download speeds, automated downloads, and more, download GetRight today!
`For Multi-File torrents, this gets a bit more interesting. Normally, BitTorrent clients use the "name" from the .torrent info section to make a folder, then use the "path/file" items from the info section within that folder. For the case of Multi-File torrents, the 'url-list' should be a root folder where a client could add the same "name" and "path/file" to create the URL for the request. ` so yeah, as suspected, you need to have the subdirectory structure as it is in the .torrent
and it will get the file list / other metadata from the peers once it finds any off the dht or off the tracker
so i guess that's fine so long as there are > 0 peers
but dunno if i can actually encode that into the magnet uri itself, but figuring that out should come later
so preliminary full answer `magnet:?xt=urn:btih:9760e073e3cf6dbe6f2525040f1550b8d3a73eb6&dn=snowblossom.7&tr=http%3A%2F%2Ftracker.1209k.com%2Fannounce&ws=http%3A%2F%2F136.243.82.213%2F`
and the tracker may be omitted by anyone whom dislikes trackers
I moved it over to this directory
anything in your access log?
213.55.165.17 - - [06/Dec/2018:00:33:31 +0100] "-" 408 0 "-" "-"
thats probably not you
that is me, but via a browser
but where i'm testing from is ``` 144.76.2.138/27 144.76.46.6/29 144.76.2.153/27 2a01:4f8:190:7289::4/64 2a01:4f8:190:7289::3/64 2a01:4f8:190:7289::2/64 ```
not in the logs
``` 15:27:28 torrents.public Torrent a3647e5b5ac9685eb40f738f858e3e976f734ed1 - snowblossom.9 - <2 Available Seeders 10m 42s No 2 actions 15:27:28 torrents.public Torrent 7f66b2966d92d368ace6160a94cd0304f4766831 - snowblossom.11 - <2 Available Seeders 10m 42s No 2 actions ```
no 144.76.x.x at all
7 is very busy so i get full 1gbit saturation on the downlink from the swarm, put the 8 up that way as well
could be it just prefers low latency, i'm assuming you're on a different continent
try pinging it
should be quite fast
fair enough, seems you're just a few racks over in falkenstein actually :stuck_out_tongue:
:wink:
heh, 200 microsecond pings, their network is pretty good
move snowblossom.8 also over to a directory?
yes
once I've finished downloading those fields, they'll be up to the 2 or so.
@Rotonen do magnet links work without a tracker?
seems i forgot the trailing slash in the 7 uri actually
@Clueless all torrents work without a tracker, it's not a metadata dependent feature
neat, so they can work dht without tracker, nice
the only thing you actually need is the content hash, then it discovers peers until it finds one whom can give the full set of metadata for that
never looked into DHT tables before
but of course if you have a http accessible tracker, that helps people in networks with certain restrictions
and the other way around, dht helps people in other situations
i just like the elegance of `magnet:?xt=urn:btih:9760e073e3cf6dbe6f2525040f1550b8d3a73eb6` being a 100% valid way to grab field 7
@mjay anything in the logs?
148.251.122.19 - - [06/Dec/2018:00:09:39 +0100] "GET /snowblossom.8.snow HTTP/1.1" 200 154559569232 "-" "Wget/1.18 (linux-gnu)"
oh well thats me :wink:
no nothing
also getting link saturation on field 8
but `magnet:?xt=urn:btih:a83c3c8e5a8f68ffb1004dd0e62d380b6fa46805&dn=snowblossom.8&tr=http%3A%2F%2Ftracker.1209k.com%2Fannounce&ws=http%3A%2F%2F136.243.82.213%2Fsnowblossom.8%2F`
moved all files in directories, on all servers
37.201.195.53 - - [06/Dec/2018:00:50:45 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.b HTTP/1.1" 404 487 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:45 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.a HTTP/1.1" 404 487 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:45 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.a HTTP/1.1" 404 487 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:45 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.snow HTTP/1.1" 404 485 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:47 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.b HTTP/1.1" 404 487 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:47 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.a HTTP/1.1" 404 487 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:47 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.snow HTTP/1.1" 404 485 "-" "Transmission/2.92" 37.201.195.53 - - [06/Dec/2018:00:50:47 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8.deck.a HTTP/1.1" 404 487 "-" "Transmission/2.92"
thats me using the magnet link above
well, i could add another directory ...
yeah, it's a bit dumb as it seems to add the display name to it
but that's sorta in the spec, maybe
add another dir?
so field 8 deeper url `magnet:?xt=urn:btih:a83c3c8e5a8f68ffb1004dd0e62d380b6fa46805&dn=snowblossom.8&tr=http%3A%2F%2Ftracker.1209k.com%2Fannounce&ws=http%3A%2F%2F136.243.82.213%2Fsnowblossom.8%2Fsnowblossom.8%2F`
does that nesting also happen for you if you strip the `dn=` parametre out of the query string?
37.201.195.53 - - [06/Dec/2018:00:55:33 +0100] "GET /snowblossom.8/snowblossom.8/snowblossom.8/snowblossom.8.deck.a HTTP/1.1" 404 501 "-" "Transmission/2.92"
with the link above
oh
so one less
neat
`magnet:?xt=urn:btih:a83c3c8e5a8f68ffb1004dd0e62d380b6fa46805&dn=snowblossom.8&tr=http%3A%2F%2Ftracker.1209k.com%2Fannounce&ws=http%3A%2F%2F136.243.82.213%2F` ?
that's neat
so you just point the webseed at the root of your webserver
https://www.urlencoder.org/ Decode from or Encode to URL encoded (also known as Percent-encoded) format - Here, with our simple online tool.
just urlencode and add more `&ws=` things into the query string
and use any torrent inspector to grab the hash from the .torrent files
and remember to amend the `dn=` to match the field name
@Fireduck would you mind switching your .torrent files to magnet uris on the site? makes it easier to point to http(s) seed sources