I've just installed bigly bt, and I have three questions: 1) is it possible to set the seeding ratio 2) do we really need to confirm the deletion of every torrent via the pop up? (I have RSI, and the less popups or clicking the better) and 3) why does searching for a torrent via the internal search engine result in a captula.?

load more comments (3 replies)

[–] princessnorah@lemmy.blahaj.zone 4 points 2 years ago (6 children)

Is there a docker container for BiglyBT that handles java and has a webUI, similar to qBittorrent? And can it integrate with the *arrs in the same way?

load more comments (6 replies)

[–] ryannathans@aussie.zone 3 points 2 years ago

Finally real content

[–] Jourei@lemm.ee 3 points 2 years ago

Oh, so I wasn't going crazy after all, when my antivirus started getting hostile at uTorrent.

[–] Templa@beehaw.org 3 points 2 years ago

Does anyone have recommendations on configuration for qbit? I'm a casual user and I have been using out of the box for years now, but I've been wondering how it could be improved.

[–] bear_with_a_hammer@lemm.ee 3 points 2 years ago

People tend to forget about BitComet, due to its past fails with tracker exchange and padding files.

It still improves, and if you say, that the reputation is lost, then that's good, don't use uTorrent in this case.

[–] jmp242@sopuli.xyz 2 points 2 years ago

I am interested in some of the features of BiglyBT, but don't love the .sh installer for Linux - they should have rpms and debs IMO. I'm a little concerned they don't end up in EPEL or whatever like qbittorrent is.

[–] Grey@lemmy.dbzer0.com 2 points 2 years ago (1 children)

Flud gang

load more comments (1 replies)

[–] thelastknowngod@lemm.ee 2 points 2 years ago

It's completely overkill for pretty much everyone but I have been thinking about building a kubernetes native client for months now.

Like the torrent should be treated as a normal resource with a Torrent CRD. It should be scheduled onto whichever node has available capacity and rescheduled onto a different node if it goes down. If allowed by the tracker, multiple instances could be run. You could set resource limits programmatically, easily configure block storage, build dashboards, export logs/metrics.. It would be open ended enough that you could have interfaces built as browser extensions, web ui, mobile app, tui, cli and be unopinionated so much that the method for torrent ingestions could be left up to the used. HTTP request, watch directory, rss client, download manager.. You could even do stuff like throw magnet links into a queue.. etc, etc..

I keep thinking it would be a great project but I just do not have the spare time to dedicate to it.. I imagine it could be used for large scale deployments for something like the Internet archive or whatever.

[–] gunpachi@lemmings.world 2 points 2 years ago

On android I'm currently using Libretorrent, how does biglybt's android app compare to it ?

load more comments