hi,
i would like to use ktorrent but without any support for the rss feeds many trackers offer, i am forced to use something else.
are there any plans to add something like that? and if you do, please don't forget to include support for trackers that use cookies

c ya hanta

What exactly are trackers providing in RSS feeds? I've never used that since I couldn't find any usefull RSS. Are the links to torrent files included in feeds?

If you could explain a bit, maybe we can think about adding that feature.

It's probably just an RSS feed with a bunch of torrents included or links to torrents. And I'm thinking it probably works like this :
- User 'subscribes' to an RSS feed
- KT keeps an eye on the RSS feed
- If a new torrent shows up, KT starts downloading it without user intervention

Probably a good way to get all the episodes of a season of a TV show.

After some digging around in KDE's svn repository, I have found an rss library (http://websvn.kde.org/trunk/KDE/kdenetwork/librss/), which should help greatly with any implementation. (if we decide make one, the feature list for 1.2 is getting big)

Ivan wrote:What exactly are trackers providing in RSS feeds? I've never used that since I couldn't find any usefull RSS. Are the links to torrent files included in feeds?

If you could explain a bit, maybe we can think about adding that feature.

what george said, eg a torrentbits tracker would give you something like this

Code: Select all

<item>
<title>some file</title>
<link>http://localhost/download/788/somefile.torrent</link>
</item>

ktorrent would have to check the feeds every few minutes and i could set a few regexps for what i want.
in the end ktorrent would join a swram as soon as the files i am intrested in become availabel and when i come home everythinghas already been downloaded ... like magic

Well why not, I'll add it to the list.

George wrote:Well why not, I'll add it to the list.

This would be a *great* addition to KTorrent. Regular expressions against the title/link could also be usefull. That way you could make a list of stuff you want to automagically download.
E.g if I want to download Lost only, I could tell it to download any file that matches Lost.S02E??.HDTV* (don't know if that is a valid form of regexp, but you get the point) from a specific RSS-feed

By the way. ThePirateBay has a RSS-feed if you want examples:

If implemented, it would be also nice to have to save torrents in different directories per rss feed and given regexps.

Anonymous wrote:If implemented, it would be also nice to have to save torrents in different directories per rss feed and given regexps.

Great idea. To take my previous example with Lost. You might want your Lost-downloads in a Lost-folder, or your Linux-images in a Linux-folder, to take a legal example

Skrot wrote:

Anonymous wrote:If implemented, it would be also nice to have to save torrents in different directories per rss feed and given regexps.

Great idea. To take my previous example with Lost. You might want your Lost-downloads in a Lost-folder, or your Linux-images in a Linux-folder, to take a legal example

We'll see when we implement this.

So, how's the RSS development going? Still only on the todo list? I'd really love to see an RSS function in ktorrent.
Keep up the good work!

mirshafie wrote:So, how's the RSS development going? Still only on the todo list? I'd really love to see an RSS function in ktorrent.
Keep up the good work!

It's not going at the moment, and it certainly will not be in the final 2.0 release. 2.1 at the earliest.

* imported4-Tomasu casts resurect thread.

This would be great, especially with regex matching, so you can make rules for things to look for, and things to weed out, so like a list of rules in a chain. if you need something to look at, the Azureus RSSFeed plugin is pretty good.

Speaking of plugins, this would go great as one

Perhaps this should rather be something combined with aKregator?
Example: I get the Systm torrent feed in aKregator. Every time aKregator gets a .torrent file in that feed, it tells KTorrent to download it. While the file is incomplete, the story is marked as read. When KTorrent completes that file, it signals aKregator, which then marks the article as new.

What aKregator should do is to both get the .torrent file (save it in ~/.kde/share/apps/akregator/torrents) and tell KTorrent where to save the file (given by the user, or in a default place). KTorrent then silently loads the file and starts downloading it (settings can let one choose the priority). Once it's finished, KTorrent deletes the .torrent file from ~/.kde/share/apps/akregator/torrents. The next time aKregator starts (or the next time it scans ~/.kde/share/apps/akregator/torrents), it detects that the torrent is complete and changes the article to unread. aKregator should scan the torrents directory every time it loads new feeds.

Separately, adding this would allow automatic control in KTorrent, which would make it a lot easier for other apps to download torrents, using KTorrent as a backend.