+1 to using the "Waffles" method on Waffles.
+1 to using the "Waffles" method on Waffles.
"I just remembered something that happened a long time ago."
For me the safest way is to download the torrent, real seed, stop the torrent, use W-M with speed a little higher than my real one, then keep real seeding for a while.
Quick question regarding this method. Is it best to stop before the update in RM or just let it go for a bit and stop after a few hours? Also, is it okay to be seeding other torrents (for real on What) at the same time?
Letting it run for a while and update is fine, as long as the torrent has activity.
Seeding for real on other torrents at the same tracker is also ok, though it is advisable that you don't use tcp on RM.
Edit: Now I have a question :S
How do scripts that detect seeding when no one is leeching work?
I was wondering what would happen when:
No leechers
You are cheating at low speed
One leecher joins for a very short time
He becomes a seeder
No more leechers
You keep seeding
Send announce
As far as I know, the tracker only gets the average speed, in this case the low speed. Would it be able to determine whether you seeding constantly at that speed, or had a burst seeding period to the leecher?
Last edited by GotIt; 12.03.10 at 12:29.
Well on trackers that have small swarms it wouldn't be hard to determine that if in 2 hours you claim to have uploaded 1GB and nobody claims to have downloaded anything somebody lies.
Personally, I let it run the whole day until I either have to go or have faked a maximum of three times the torrent's size.
Sure, if you've used the memory reader.Also, is it okay to be seeding other torrents (for real on What) at the same time?
No, it wouldn't, since as you said it only sees the average speed since the last announce.
"I just remembered something that happened a long time ago."
In my opinion it is silly to burst... If all that matters is the average speed you're faking, why bother?
But anyway... this strategy is totally separate from the bursting one. I've had success with it ON THIS TRACKER. You should not try to combine strategies because you might mess something up, or overlook it, and then you will get banned.
Last question: the scraper info isn't showing in RM. It was earlier, but I wonder if this is related to the ongoing issues that what is having with timed out connections and what not.
I do have RM checked to get the scraper info, but it's not showing up. Should I be concerned? I'm watching the torrent on the site and I'm in no danger as far as the swarm is concerned, but just wanted to make sure that RM wasn't having a malfunction that could get me busted.
You should show us the log so that we can know if it's a timeout or simply the known "failed to decode tracker response". Don't worry, none of those can get you banned.
"I just remembered something that happened a long time ago."
Error : Tracker Response is empty
The tracker isn't replying with anything other than the HTTP headers, happens sometimes... just keep the RM running or do a manual update if you're worried - but if a single one doesn't do the trick, keep your hands off the "Manual Update" button
"I just remembered something that happened a long time ago."
Yes- legit clients typically don't spam update requests, so that's a sure way to get banned
I may suggest posting issues about RM in a separate threat though, to get maximum feedback/help (Plus, it's easier for people who have the same problem to find it later:])
Bookmarks