I must be the only human being that doesn't use tags, sorting by announce URL is enough for me. But filtering torrents by regular expressions is a really good feature uTorrent doesn't have :smilie4:
Printable View
I must be the only human being that doesn't use tags, sorting by announce URL is enough for me. But filtering torrents by regular expressions is a really good feature uTorrent doesn't have :smilie4:
I automate a few things based on tags; They're really useful. For Instance putting things into a subcategory folder. Or Speed Scheduler. Few more things available. I don't use them to actually find a torrent in my list though. Does anyone have that many open that finding something becomes hard?
Removed by request
Strange, I've encountered torrent that won't finish. It just stops at certain %. I only managed download the torrent with other client. qBittorrent did the job.
Yes, tried spoofing with that client, and saw older versions in the peers. So any ideas why it stalled or something...?
Never had this happen to me. The advice here may help?
deleted due to security
If you are flooding a cloudflare protected server with rss requests every 2 minutes, issues like that are no wonder. I would recommend to increase the time between rss requests or better, use another (better for this situation) mechanism.
Querying RSS feeds faster than every 15 minutes is generally frowned upon and a lot of services don't even allow that often. Is it really that time critical to get the torrents?
deleted due to security
@anon:
please can you delete my post 48
I hired the author you sent me to him for report it
he is working on it to solve this known problem for me
Please delete the whole post #48
Rebound and Sazzy are correct; RSS is not meant as a solution for time-critical scenarios, nor is it efficient to attempt to use it as such. You should be running an IRC autodownloader instead.
Anyway, as far as I can grasp here, the problem is that the mod resorts to the default 1800-second announce interval when it receives a Cloudflare error instead of a tracker response, and that's too long for your particular needs. If you can make a patch that recognizes these errors and uses a much shorter interval, that should solve it (it wouldn't even need to have configurable settings).
I once wrote a script that emulates Cloudflare errors, among many other possible responses, on a "fake" local tracker. You may find it useful, so here it is.
BiglyBT Extreme Mod 2.0.0.0 was missed out
is there going to be a BiglyBT Extreme Mod 2.1.0.0
as the new version 2.1.0.1 is out now
Maybe BiglyBT did a major refeactoring and the sweet days of copy-pasting code and release notes are over? :-oQuote:
Originally Posted by lil-fella
There is a refactoring of the configuration views. I do not have time to fix it.
Well, stating the obvious, it would be nice if you'd continue the project sooner or later and keep the community updated.Quote:
Originally Posted by DigitalDJ
BiglyBT 1.9 ist stable and mature, the torrent protocol isn't changing, so unless unforseen compatibility issues appear I guess it's fine as it is. Thanks for all your work!
So I'm using BiglyBT 1.9 Extreme Mod to ghost leech.
On large swarms it is snatching great however I wish to snatch a few low seeded torrents (specifically one seeder) and I am seemingly unable to connect to the seeder.
If I snatch legitimately (ie not ghost leeching) using a different client I can download with no issues.
I have the particular seeder's IP and port number, is there a way to manually add a seeder to a torrent on BiglyBT so I can ghost leech it?
I know you can do this with Transmission but I can't find any way of doing this with BiglyBT.
Any suggestions?
Thanks again for BiglyBt Exreme Mod btw. I think the problem is with this seeder vs the client itself.