Certain torrent app using Transmission code again? Or not?

[ThreeDee912]

I've read about the whole issue about a certain torrent client using Transmission's code a while ago.

A certain developer of this torrent app just introduced "New! Version 2.0 with Xcore engine"...

Anybody know what's up with this?

EDIT: I've noticed you censored some things, so I've edited my post.

[Jordan]

I don't have any firsthand knowledge one way or the other. Guessing from secondhand talk, such as this twitter, my guess is that "Xcore" is new as advertised. It's an odd choice though. If I needed a closed-source-friendly, embed-me-in-your-commercial-product torrent engine I would use Arvid's libtorrent, which is one of the best BitTorrent engines in existence...

[livings124]

And, to stroke our egos a bit more, our engine has a lot more features than his (DHT and tracker customization come to mind). Not to mention the Mac version has groups, autogrouping, speed limit customizations, and more. Plus we have a full web interface.

[Rolcol]

If libtransmission were to be licensed under LGPL, would that allow them to use it as long as they only link to the library without modifications?

[Jordan]

If libtransmission were to be licensed under LGPL, would that allow them to use it as long as they only link to the library without modifications?

Yes, I think so. But if David's put in the hard work of writing a new torrent engine -- which is quite time-consuming to get all the little details tweaked and running smoothly -- I can't imagine why he'd want to walk away from that. Second, I wouldn't be surprised if he feels once bitten from our previous license change. Thirdly, I've currently got no plans to make libtransmission LGPL.