Ratio Faker 0.9.10

[anon]

SB-Innovation Presents

>>>>>> Ratio Faker 0.9.10 <<<<<<



╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> Matías <<<<<<

╔═══════════════════════════╗
Supplier:
╚═══════════════════════════╝

>>>>>> anon <<<<<<

╔═══════════════════════════╗
Changelog / Features:
╚═══════════════════════════╝

0.9.10:
* FIX: RF is now a single instance app, you can't launch more than one instance. This should lower the number of people asking for the error "socket in use" :)
* FIX: auto checking for updates might display the new version message even if there's none.
* CHANGE: Some language updates.
* CHANGE: your real upload will be appended when you use "report my upload as x.x times my download". The final result then will be downloaded x multiplier + uploaded. That way, even if your download has been completed, you can continue seeding.

0.9.8:
* FIX: RSS not working in uTorrent when Ratio Faker is enabled
* FIX: write permission error for debug.log (in Windows Vista/7)

0.9.7:
* FIX: tracker offline message on 0.9.6
* FIX: after closing Ratio Faker there's still a running thread of it
* ADD: option to not generate error.log (not recommended!)
* CHANGE: some multi-threading improvements

Remember!: Before changing from one mode to another, changing the modifier or ratios, ALWAYS stop (not pause!) all your torrents.

What is this?:

If you know what GreedyTorrent is, then the answer is really simple: it's a clon.
But wait, it's not based on GT ... this is a written-from-scratch software, I don't even know GT author.

I've started this project because I think that there's one important missing feature in GT, and that's the ability to pick up a random modification ratio. That's the biggest problem of GT, and because of that it's relative easy to detect when someone is using it (for tracker admins).

Ratio Faker offers the possibility to generate a random value in every announce, like in a real bittorrent transfer scenario. Obviously, you must select the extreme values moderately.

Please, report any bug or problem that you find by posting a comment here.

Should work with any client that support http proxy, but I've only tested with µTorrent 1.8.x.

How to use?

- Open Ratio Faker and check in what port is listening

- Open µTorrent or your favourite bittorrent client and set the proxy with the following data:

Host: 127.0.0.1
Port: 8282 (you should put here the listening port of step 1)
Proxy Type: http

For example, in µTorrent you have to go to Option, Preferences. Go to Connection, under Proxy Server section enter the above data and then click OK to save.

That's all!

╔═══════════════════════════╗
Tutorial by SealLion
╚═══════════════════════════╝

Using Ratio Faker Strategically

Note: we have permission from the coder to distribute this tool.
It's not related to the tool RatioFaker 0.65b!

[vDD+wR]

I guess it should, since it's stated in the first post, that RatioFakers functionality was tested on µTorrent 1.8.x.

Should work with any client that support http proxy, but I've only tested with µTorrent 1.8.x.

[dbj]

which should go without bann

[anon]

which should go without bann

What do you mean?

You won't be banned with the right settings, that's for sure.

[deepforce]

just btw.

it unfortunately crashes with Mac OS and XP in Parallels

[deepforce]

Does anyone know if I can have Ratio Faker or any other Proxy Ratio Tool as a proxy in a network and route my mac torrent client to the win xp machine with ratio faker running?

[anon]

I think that should work if RF can take non-loopback connections. The only way to know this is trying it.

[deepforce]

For me it didn't work but I am not sure if my router/firewall setup is right to be able to.

Can anyone confirm this?

[alpacino]

I have a question: If you are using a given upload multiplier on a given session, would it be bad if you lower this multiplier? I mean, it's ok if you increase it, as RF alters the &uploaded string right? So the tracker could detect you with a script that detects a lowered total uploaded amount in one session. Unless I'm missing something here .

[anon]

That should be no problem - the tracker will see that you "uploaded" less than the last time, which by itself is nothing suspicious.

So the tracker could detect you with a script that detects a lowered total uploaded amount in one session.

The upload you've already reported is stored server-side and can't be decreased, not even by sending negative values.

[alpacino]

That should be no problem - the tracker will see that you "uploaded" less than the last time, which by itself is nothing suspicious.

I'm still confused, doesn't RF report a multiplied uT uploaded (total) column?

The upload you've already reported is stored server-side and can't be decreased, not even by sending negative values.

Let me try to explain what my doubt is, suppose I use a high multiplier, then next I use a lower multiplier. This will make the total uploaded amount report, a decreased one. In this case, how then can it differentiate?

[anon]

I saw you were going to reply, so I stayed up a few more minutes.

I'm still confused, doesn't RF report a multiplied uT uploaded (total) column?

As far as I know, uTorrent only reports what it has uploaded since the last announce, so that's the only thing RF can cheat on. If RF took your whole uploaded amount, faked it, and reported it, you'd be faking on every announce.

Now anon ->

[alpacino]

I saw you were going to reply, so I stayed up a few more minutes.

I thought so, thanks. Now I'll leave yet another reply.

As far as I know, uTorrent only reports what it has uploaded since the last announce, so that's the only thing RF can cheat on. If RF took your whole uploaded amount, faked it, and reported it, you'd be faking on every announce.

That's pretty strange, from what I've been looking here on RF log and from packet sniffing, it is reporting the multiplied grand total on each announce. So my statement is still plausible I guess.
Example on RF log:

05:19:17  Download: *.**, Upload: xy.zw MB, Upload (modified): abc.de MB, Ratio: f,gh 
05:19:17  Reported to tracker.*********.net on port 80.

In this case I can assure you RF is reporting "xy.zw" as the total uploaded amount as seen on uT uploaded column, even after having started RF way after the uT session started.

Now anon ->

Now alpacino -> same, night watch is over

[anon]

That's pretty strange, from what I've been looking here on RF log and from packet sniffing, it is reporting the multiplied grand total on each announce. ... even after having started RF way after the uT session started.

Interesting... and now I remember, Mihai mentioned this RF property several times.

What I don't really know is, even if the log entry showing the total upload is just for looks, and only the uploaded amount since the last announce is being reported (as I think it should), how is it getting that data? Can you check with another client?

[cheatos]

@ Alpacino it happened to me too,
to make RF announce correctly(report the needed uT session) , you need to shutdown uTorrent & RF too as mentioned in Mihai's thread about the waffles method using RF.

[alpacino]

Thanks both of you for your inputs. After a while, uT queued the torrent I was monitoring, so on the logs it sent the event stopped. After sometime I did a force start, and it seems everything is working as it should, as you said anon, i.e., RF sends a new announce with uploaded=0, and after the first announce everything seems to be going sharply, with correct uploaded amount reported. I guess I became a little paranoid here. .