[Linux] Transmission 2.83 (14283) + No Report Leecher

SB-Innovation Presents

>>>>>> [Linux] Transmission 2.84 (14307) + No Report Leecher <<<<<<


http://www.sb-innovation.de/attachme...chmentid=14861

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

>>>>>> Transmission <<<<<<

╔═══════════════════════════╗
Modded by:
╚═══════════════════════════╝

>>>>>> deysmacro <<<<<<

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

Mod features: No Report Leecher

• No Upload
• No Download
• No Complete
• Always shown as Leecher @ 0%
• Stopped flag send to tracker when done leeching
• Based on Transmission 2.84 (14307)
• Native Linux mods

How to Compile: https://help.ubuntu.com/community/CompilingTransmission.

What-To-Do: Just straight away compile the attached file.

Word-Of-Advise: The mods are powerful.
Therefore, don't leech multiple files from the same tracker.
Have some constrains and you're gonna be fine.

Tested platform: Ubuntu 14.04 @ 32bit architecture
Compatible platform: Any 32bit Linux (should be)

Quote:

---

I am no Linux Experts but I did try. :cool:

---

Quote:

---

I am no Linux Experts but I did try. :cool:

---

I don't think it is a good idea to report to the tracker req->leftUntilComplete
with a "No Report Leecher" mod. leftUntilComplete decreases as the download proceeds.
What you'll need to do is always report the total size, otherwise it can be sure sign of cheating :00000020: when using "No Report Leecher"

I don't particularly care for the transmission 2.8x branch quark and threading model changes
so that is why I mod a port of transmission's 2.77 core. Below is what I use for always leacher
in my mod and something like this will work fine for the 2.8x core.

Code:

---

....
    else if(cheatMode == TR_CHEAT_ALWLEECH) // always leecher
    {
        *up      = 0;
        *down    = 0;
        *corrupt  = 0;
        *left    = tr_torrentInfo( tier->tor )->totalSize;
        if( *event == TR_ANNOUNCE_EVENT_COMPLETED )
        {
            *event = TR_ANNOUNCE_EVENT_NONE;
        }
    }
....

static tr_announce_request *
announce_request_new( const tr_announcer  * announcer,
                      const tr_torrent    * tor,
                      const tr_tier      * tier,
                      tr_announce_event    event )

....

    letsCheat( tier, &req->up, &req->down, &req->corrupt, &req->left, &event );

....

---

I see in your mod that it is hard-coded to always announce the mod values. It's not hard to allow for other options so that's what my mod does.

Well, I did try to use your Linux mods first before I did this mod. For some reasons, I never get lucky. I then gave up and decided to make this mods and then I use my mods on vps. Therefore, people don't notice what happens because the data transferring is real fast. It is more to occasional leeching, not hard core one.

I can do like uTorrent 3.x mods where No-Report-Leecher always shows 98%. Should I do it?

Quote:

---

Originally Posted by deysmacro

I can do like uTorrent 3.x mods where No-Report-Leecher always shows 98%. Should I do it?

---

That's because what you can do with hardcoded uTorrent mods is liited. The best option for a NoReport-Leecher is to send "left" as the full size of the torrent, with zero traffic in either direction and never reporting the "completed" event.

Quote:

---

Originally Posted by anon

The best option for a NoReport-Leecher is to send "left" as the full size of the torrent, with zero traffic in either direction and never reporting the "completed" event.

---

Well, that is what the mods are all about, in this case.

Updated to Transmission 2.84 (14307).

Rest assured it is working properly this time. A true leeching mods. :klatsch_3:

One click hoster aren't allowed. I uploaded the new mod to our attachment system.

Thanks. Actually I did try to attach using the system but I don't have the permission to use it.

Quote:

---

Originally Posted by deysmacro

Updated to Transmission 2.84 (14307).

Rest assured it is working properly this time. A true leeching mods. :klatsch_3:

---

There's a bug in the official 2.84 that can send duplicate
"stopped" events. I don't see that this is fixed in the mod
so you might want to be careful with this.
https://trac.transmissionbt.com/ticket/5092#comment:6
see comment 6

And actually stopping the torrent manually and with the mod's changes will again send "stopped" events making it that a tracker will receive multiple "stopped" events without any corresponding start event. Might look a little suspicious. With the mod it would be best to send just a single "stopped" event no matter what unless there's a matching start.

Actually I only change the completed flag to stopped flag. Nothing more.

EDIT: Well, I patched it regardless.

Thanks for the quick update. I replaced the attachment in the first post.