Page 1 of 1

Imageshack uses Transmission?

Posted: Fri May 30, 2008 1:50 am
by amc1

amc1 the Azureus dev is here again. *waves*

Just thought you might like to know that I had a look at Imageshack's torrent service, tested with an example torrent (because I wanted to get the peer identification sorted), and the peer seems to be identifying itself as Transmission 1.10.

Don't know if you were aware of it (didn't see other posts in the forum mentioning it) - just wanted to say... well done. :)


Posted: Fri May 30, 2008 5:06 am
by Jordan
Personally, I think that's a hoot. If one of the imageshack devs reads this, feel free to post here or PM me. I'd love to hear the story behind that.

On the other hand, is it true that Imageshack's beta stops seeding once a torrent's completed? That's not good. :(

Thanks for the heads-up, amc1...

Posted: Fri May 30, 2008 7:02 am
by Waldorf
Thats cool! Thanks amc1 for the post, and the heads-up!

Posted: Fri May 30, 2008 11:52 am
by amc1
Jordan wrote:On the other hand, is it true that Imageshack's beta stops seeding once a torrent's completed? That's not good. :(
It does appear to be, unfortunately. This post seems to agree with me - mind you, that comment was made about a month and a half ago, I could've just read that rather than testing with it in the first place... :)

Imageshack uses Transmission

Posted: Tue Jun 17, 2008 5:31 am
by janderso
Hi guys, and Waldorf, thanks for the email and invitation to post. I have been working on the torrent stuff at imageshack.

We have been using Transmission 1.10 CLI via the torrentflux-b4rt package and Python + BitTornado for selective downloading. At the time we were unable to use transmissioncli exclusively as transmissioncli did not seem to have an option to support selective downloading, and the daemonized version just wasn't working for us / refused to move data for some reason (this was a few months ago now though, have not tested lately).

The Python + BitTornado combination requires amounts of memory several times greater then transmissioncli, so we use this client during selective downloads only.

Benefiting from transmissioncli's small memory footprint, using both clients made it possible to handle significantly more simultaneous downloads while keeping selective functionality when needed.

As for the seeding, we are currently seeding at a fixed rate during the download, and stop the process once it finishes. This translates into the logic of "the less healthy a torrent is, the more it gets seeded". Though not realized by many (and I have seen lots of passionate emails come through on this subject), the unhealthy torrents actually reap the most benefit from this. We see very large contribution ratios to (900%+ sometimes) to the sickly torrents over long spans of time.

We also have a special account setup where we permanently seed some linux and freebsd torrents.

The service is still in beta though and things are still being tweaked. I was given the OK to seed to 100% or even 150% which should be implemented before the end of this week.

Also, looking at the recent happenings of transmission's development, the daemonzed beta version is looking absolutely amazing!


Posted: Tue Jun 17, 2008 8:04 am
by Jethryn Freyman
Awesome :)

Posted: Tue Jun 17, 2008 9:11 am
by Waldorf
Awesome indeed.

For more in depth discussions or request, feel free to jump into our [url=irc://]IRC channel[/url].

Posted: Thu Jun 19, 2008 2:24 am
by Jordan
Hi Josh, thanks for posting!

If you have any suggestions or feature requests for the Daemon/RPC rewrite, feel free to ask. I'm currently trying to finalize the spec for 1.30. :)

Re: Imageshack uses Transmission?

Posted: Mon Aug 11, 2008 12:59 am
by Jordan
Josh, as of 1.30 you can do specific file selection in the daemon, so maybe you don't need BitTornado anymore. :)