Thanks Popper that confirms what I thought.

@Popper:

@TerryG:

…
Why is the gaytorrent.ru dashboard suddenly giving me a smaller number for the files I am seeding?
...

I've no explanation for that. Can you look if some of your seeding torrents are queued?

@TerryG:

…
Is my daily seed bonus being calculated on 23 or 37?
...

Neither nor. It is calculated on the fact that you seed at least one torrent. It is a flat 0.5 seed bonus points per hour, not per torrent.

Thank you for these prompt responses. Your answers make perfect sense.

As no one else has reported this issue, it must be my torrent client that is queuing some files rather than seeding all of them.

I performed a “forced check” with the torrent client and the gaytorrent.ru dashboard now shows 35 files are being seeded. :cheers:

All the best,
Terry.

You are currently using µTorrent 3.3.20 which is known to cause some seeding issues. Can you please upgrade to the latest stable built of µTorrent version 3.4.0 and then try again.

As uploader, you can edit the torrent page for 7 days after the upload date / time.

Changeable are:

The title Add or delete pictures The description text

Not changeable are the .torrent file and the torrent's file list and the file names.

–---

How to edit a torrent page:

1/ Go to the torrent page (e.g. from your Profile's Uploaded torrents list))
2/ Locate the "Upped by  (Anonymous)"
3/ Click on the "[Edit this torrent]" there and the torrent page editor opens
4/ Change first pictures, then title and/or description
5/ Click the "Edit it!" button to save changes

Remark: the torrent page editor has as well options to delete the page and torrent. However this should be used only if nobody has yet started downloading or there are serious issues with the torrent's data files. Deleting the torrent will leave the downloading peers with unusable partly downloads counted to their share ratio.

There are two possibilities:

During the time you were seeding there may have been a disconnect between your client and the tracker. Since any disconnect from seeding will reset the sum total displayed, the totals given on your profile are from that disconnect point, and not the entire amount.

Another person with a higher bandwidth has that same completed file, and seeded it to others alongside you, albeit at a faster rate.

I recommend new freelech torrents. Also torrents uploaded in the last 12 hours (the newer the torrent, the better). Then just leave your computer on and seeding. I usually get the majority of my torrents up to a 1.00 ratio within 48 hours (although I do also get about 20% that won't bother going above 0.5 for ratio).

Been doing it like this for the past month and I have really raised my ratio.

In addition, if you have utorrents, you can sort your files by last active and see what torrents were recently accessed/uploaded.

@Redssmoker02:

And for Windows XP?  Yes, some of us out here are still using XP

Same than Vista and 7. Actually it is even simpler, because the it works even without the "run as administrator" (less secure OS).
I've added XP to the list of Windows systems.

Are you using Download Station as the manager/client?
Where are you observing that there are no upload transmission?

Thanks so much 🙂 worked perfectly

If you got an ADSL connection (passing by the telephone copper wires), 98 KBytes/s are an excellent upload rate. If you got a fibre optics connection to your home, it isn't a good rate.

@Popper:

If you shut down your torrent client (or your computer), you'll stop to seed. When you've completed the initial seeding, means distributed a full copy and there are other seeds, that doesn't do a harm to the torrent. It will be kept alive by the others.

If you haven't completed the initial upload and you shut down, the peers will exchange the parts they got, but can't complete the download.

If you know in advance that you can't run the computer long enough without a break (many people don't have their PC running 24/7, so that is normal), place at the bottom of the description an indication of your likely seeding times in UTC. That avoids complains 😉

Thank @Popper! That cleared a lot of things up for me.

You should be able to find it yourself, either by "including dead" (and not only "active") in the Browse or Search or by going to your Profile, scrolling down and expand the uploaded torrents list.

You go to your Profile by clicking on your name in "Welcome back, …" top left below the blue menu band.

Remark: If a torrent has been moved to a category you can't access or see, it won't be visible for you at all. That isn't the case for your upload (unless it is another than the one I see in your Profile and has been deleted)

Restricted access / visibility torrent categories are: Bisexual (Profile setting), Straight older (Profile settings), Straight younger (Profile settings), DVD-R (Power User), non-Porn DVD-R (Power User), 3D (Power User) and for duplicates (Staff Only).

Used wrong password and it said "Login Incorrect"

I am not sure, but in your case my guess is that it is due to the missing special character support of QuickTorrentMaker, unless you've uploaded your other torrents from the same Windows user account and with QTM, too.

Actually I think your Windows user name is not "V.n", but that in the place of the dot "." you've got an accent on the letter. This leads to QTM not being able to use the right file path for your account's application data directory.

It might be better you use the web interface to upload torrents.

That means you haven't indicated a tracker URL while creating the torrent. Any valid URL will do, for example:
http://tracker.gaytorrent.ru:2710/announce

Create a new torrent indicating a tracker at creation.

I downloaded two different torrents but the tracker announce URL is still  http://tracker.gaytorrent.tw:2710 and there is still a scrape error but I can leech and seed. When I went to my profile page and took the passkey from there and then tried to create a new tracker, Transmission automatically changed the announce url from the original url (which contained the passkey) back to http://tracker.gaytorrent.tw:2710 or http://tracker.gaytorrent.ru:2710 .

Thank you so much 🙂 i fixed QTM to make it BitTorrent and then the force re-check works.  :hug:

I've tried to explain already in some other forum replies, that as long as your torrent client can connect to the tracker and get the peer IPs, it is not a technical issue of our tracker. I am sure that any correct torrent client programme can connect to our tracker and get the IPs. I've used myself multiple: µTorrent/BitTorrent, Vuze/Azureus, BitComet, Transmission, qBittorrent, FreeDownloadManager …

That is because the upload/download (aka seeding/leeching) is negotiated directly between the torrent clients. It isn't go over the tracker or is controlled by the tracker.

Looking to your Profile, you seed two torrents right now:
The first got 453 seeds and 70 peers (leecher). Out of the 70, 69 got 98.53%. that means they have chosen not to download the 9 screen captions files, but only the movie. That makes 522 seeds for one real leecher, so it is absolutely "normal" that you won't upload to this single peer, you are in competition with more than 500 others.

The second got right now 53 seeds, no peers (leecher) no upload possible.

So that you don't upload has nothing to do with a technical issue of the tracker, but the dynamics of a torrent and torrent swarm.

If you join in very early, it is likely that you can upload something back. If you join late, many will complete before you and will become seeds before you and few members will join after you and those who do get feed from the many seeds. This leaves only low upload to each of them.

This particular case aside, we currently have a close eye on the "low" number of downloads per torrent, though the total numbers are about 20% higher than 3 months ago.

Please keep in mind that this year has seen two major changes targeting to generate an up-spin dynamic:

Introduction of the Freeleech feature Automatic recycling of old torrents (rewarding those members who kezpt them alive over months)

assorted with once a 24 hours Freeleech Marathon and a few weeks of Freeleech Fest.

@Bonk:

As always, you mods from GTru deny any mistakes. If every user tells you that they only have problems uploading/seeding on your tracker, doesn't that ring a bell?

The questioner is asking for the forum community to provide him with a knowable statement about his problem (i.e., "I know what caused your problem.") It has been said that a well-asked question is already half-answered. The forum's failure to provide this knowable statement is a failure shared with the questioner himself, as key information about the problem was omitted from his query. His problem was thus presented as the following:

@shiftless:

When I'm downloading a file, I'm able to upload at full speed just fine. After the download has completed the upload rate crashes to no activity at all most of the time.

He has presented a scenario whereby uploading rates mysteriously change during the uploading of certain torrents. Missing here are key details about the torrent being uploaded when the occurance was noticed by him.

The age of the torrent at the moment he entered the swarm was a detail not provided. Since any gainful return on seeding depends on bandwidth and torrent age, upload rates tend to be significantly higher when the user arrives early to a torrent, and tend to increase linearly with bandwidth over a given period. What was the duration of this particular event? Was this noticeable drop in upload speed an event with a short duration of time, or was it graduated, occurring over a wider and more cumulative breadth of time?

If these instances of "drop off" were noticed on only a few occasions, should that, in itself, be suspect? People are prone to see patterns where there are none (such as in occurrences of "upload speed drop off") and the mind may attempt to attribute them to some sort of correlation (claiming it's a problem with the client, the tracker, or the ISP) when in fact it may be part and parcel of the normal bandwidth variability inherent in all torrenting.

This "pattern bias" aside, the most important thing to realize about the questioner's issue is that the torrent's age should always factor in any discussion of upload bandwidth (speed). Being able to determine the age of the uploading torrent at the moment the drop off occurred may likely have been the critical component to providing this questioner with the knowable statement he sought. Since we were not provided with it, the only knowable aspect of this questioner's problem is that we will never know what caused it.