More Technical Notes
Why don't you use a public tracker?
The way I’ve gone with this so far is letting Azureus serve as its own tracker
on one of my PCs. Some of the guides I read either glossed over this, didn’t
mention it at all, or otherwise suggested that using a public tracker was the
way to go.
At this stage I don’t know enough about it to understand the pros and cons.
The machine I’m hosting the files on is the oldest and slowest of my PCs – I
don’t know how this will affect your download. I may look further into this in
In any case, please be aware that these are my initial attempts at sharing files
and, as such, you will be helping me test things out as one of the first
downloaders. Feedback is welcomed, particularly on how long download actually
takes, or how long it looks like it’s going to take.
And apologies in advance if what I’ve done doesn’t work first time. For
example, if it turns out that my nominated PC can’t handle the load, or it looks
like it's going to take unreasonably long download times.
Once I’m happy that downloads are looking good, I’ll submit the torrent
information onto search sites such as TorrentSpy to get more people involved.
Such ‘publicising’ is not the same thing as using a public tracker I know, and I
will further investigate using a public tracker as an alternative if Azureus
tracker on my machine is not working well enough and/or I feel it could improve
Results from test Sacred_Weeds_e2_Salvia_divinorum_pt1_v0.1.torrent:
The test torrent was submitted to TorrentSpy and this soon resulted in a
spike of activity. Connection by multiple peers was followed by a good
number of seeds, and what looked like good download speeds.
However, an issue I had is that while this was happening, TorrentSpy’s
‘health’ statistics remained unchanged. They did not update to indicate that
I was happily up and running. I checked this as long ago as 12 hours after
submission, when I had 15 or so seeds,
and 22 hours after submission, when I had 8 seeds. I’m sure the unavailability of
good statistics would put some potential downloaders off. It would be much more
encouraging to see healthy stats.
This struck me as something of a catch 22 situation. With healthy stats
encouraging more downloads, and more downloads in turn encouraging healthy
stats, it seems like a good idea have a number of seeds and/or downloads
going before submitting to TorrentSpy.
If you look at TorrentSpy’s latest releases page you’ll see that most newly
submitted torrents have no statistics available. However, a few of them do
have stats. I can only assume that ‘latest releases’ with healthy stats must
have been publicised elsewhere first, for example, on other torrent search
sites, before being submitted to TorrentSpy.
Bearing this in mind, I thought I would have a go at submitting information
to Pirate Bay, thinking maybe the best way to go when I come to do
full release would be to get something started elsewhere before TorrentSpy.
I tried, but Pirate Bay will not let me upload
Sacred_Weeds_e2_Salvia_divinorum_pt1_v0.1.torrent. It complains ‘Invalid
If you’re with my story so far you’ll have read how I used Azureus’s own
tracker function (URL:sallyscot01.dyndns.org:49162).
As yet, I don’t yet know what the most common standard is for submitting to
other torrent search sites. Will they mostly insist on their own trackers?
I do know that Azureus offers the option of ‘multiple’ URLs when creating
What I want to do next is investigate this further.
I appreciate that I could simply create another torrent for Pirate Bay (and
others) but I don’t want to have separate torrents unless I have to. I think
that separate torrents would create separate ‘swarms’ – each of which would
not perform as well as a single larger one.
For this reason I’m going to postpone my main release of the full download,
– pending results from a second test torrent SW_e2_Sd_pt2. This second test
torrent will be created primarily for release on Pirate Bay and possibly
some other search sites, after which I will announce it to TorrentSpy and
see if can get it to start there with healthy stats.
Any feedback and advice is welcomed.
Thank you for your patience.
Even More Technical Notes:
Azureus ‘sharing’ versus ‘seeding’
Results from test Sacred_Weeds_e2_Salvia_divinorum_pt2_v0.2.torrent:
To arrive at what I reckoned would be the best way of making my files
available took (/is taking) some guesswork, trial and error.
There’s a confusion, maybe particular to ‘Azureus’, in the idea of ‘sharing’
Many of the ‘how to’ guides out there, quite reasonably, talk about what to
do if you want to share files using BitTorrent. Even guides that
specifically mention Azureus don’t especially suggest a difference between
the idea of ‘sharing’ and the idea of ‘seeding’.
Intuitively, whatever BitTorrent client software you use, if you create a
torrent, publicise it (i.e. tell the world about it) and open the torrent,
then, because you’ve got the files already, you are, by definition,
‘seeding’. And, as far as most people would be concerned, that’s you
sharing the files – ‘seeding’ just being a technical term for sharing.
However, Azureus has a ‘share’ menu option distinct from its ‘create/open
torrent’ options. Azureus also supports its own tracker functionality (as
Now, from what I can make out, it looks to me as if the ‘share’ option may
be appropriate if you are using Azureus as the tracker for your torrent, but
not if you are using a public tracker.
In fact, Azureus’s ‘share’ option effectively scuppers your ability to open
any torrent referring to the same source files. It simply won’t let you, -
meaning that you can’t then ‘seed’ the torrent.
With Azureus acting as the tracker this doesn’t matter, you don’t need open
your own torrent, - other people will be able to connect via the ‘share’
But if the torrent was created with reference to a public tracker, then
‘sharing’ doesn’t seem to work. – At least, that’s what I found with my
public tracker test SW_e2_Sd_pt2 torrent released to Pirate Bay.