this post was submitted on 09 Aug 2026
152 points (98.1% liked)

Linux

18666 readers
175 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] comrademiao@piefed.social 6 points 4 days ago (4 children)

Why does anyone use this over qbit?

[–] amorpheus@lemmy.world 6 points 3 days ago

Tried both, qBittorrent is much heavier on the CPU just sitting there idling. I do have a large amount of torrents, maybe over 200, and I didn't expect to notice such a difference.

[–] Vegan_Joe@anarchist.nexus 21 points 4 days ago (3 children)

It's lightweight, open source, and does exactly what it's supposed to.

I kind of legacyed my way into it. It was the first thing I grabbed after uTorrent went to hell decades ago.

What is the advantage of qbit over it?

[–] muusemuuse@sh.itjust.works 5 points 3 days ago

I2p torrenting is supported by QBitTorrent not transmission. Transmission is simple, clean, lightweight and does the thing. QB is a million knobs dials and levers and comparatively heavier though not offensively so.

[–] PabloSexcrowbar@piefed.social 9 points 4 days ago

Qbittorrent feels a lot closer to what uTorrent used to be, while Transmission has more of a Mac-style simplicity to it.

[–] comrademiao@piefed.social 2 points 4 days ago

My main point of concern is most of my indexes often ban versions of transmission but I never see that for qbit.

[–] schnurrito@discuss.tchncs.de 8 points 4 days ago (1 children)

I don't often use BitTorrent at all, but Transmission is certainly the first client that comes to my mind, probably mainly because it came preinstalled with the distros I used when I was new to Linux (Debian and Ubuntu in the late 2000s). Not sure what advantages there are either way.

[–] comrademiao@piefed.social 3 points 4 days ago

That makes sense, qbit was the first recommended to me too.

[–] whaleross@lemmy.world 3 points 4 days ago (1 children)

It works great headless on my server. It does what it is supposed to do without any bloat that I would not use anyway.

[–] Squizzy@lemmy.world 1 points 3 days ago (2 children)

Headless means no GUI is it? How do you go aout getting used to these programs

[–] muusemuuse@sh.itjust.works 3 points 3 days ago

For things like this, the system you leave running the client all the time isn’t always the system you actually sit down and use. So it’s common for there to be a webUI, waypiping the GUI, or good old fashioned CLI

[–] whaleross@lemmy.world 1 points 3 days ago

Do your mean how I use it? With a remote client and other services use the RPC API. How to get used to it? Being a lifelong nerd?