hello everybody.

can anybody share with me a tutorial to create my own #torrent (even better if it's via #qbittorrent ) I think I've gotten the gist but everything I seem to find on the net is pretty old, like 2019 most-recent-old...

I know there are alternatives but I think sharing what I want with a select few people over bittorrent is the best for me (and yes I understand I have to be seeding so anybody else can download)

#Linux Weekly Roundup for May 4th, 2025: #Firefox 138, #qBittorrent 5.1, Trinity Desktop Environment R14.1.4, #LibreOffice 25.2.3, #Thunderbird 138, openSUSE Leap 16 beta, and more https://9to5linux.com/9to5linux-weekly-roundup-may-4th-2025

#qBittorrent 5.1.0 has been released (#BitTorrent / #Torrent / #Qt / #libtorrent) https://qbittorrent.org/

I like #snaps they work, and they get out of the way. #Flatpaks are fine as well, I install them if that is an option over an #apt install. But, #Flatpak does have its annoyances like when I open #Calibre, and it tells me there is an update but nothing in #Discover. Or, when there is a flat in Discover, but it does not update. Also, #Qbittorrent stopped launching, so switched that to snap. Just my experiences and preferences. #YouDoYou
#Kubuntu #Ubuntu

#qBittorrent 5.1 Open-Source #BitTorrent Client Is Out Now as a Major Update, Here's What's New https://9to5linux.com/qbittorrent-5-1-open-source-bittorrent-client-released-as-a-major-update

#qBittorrent 5.0.5 has been released (#BitTorrent / #Torrent / #Qt / #libtorrent) https://qbittorrent.org/

#Linux Weekly Roundup for April 20th, 2025: #Fedora Linux 42, #Ubuntu 25.04, #LXQt 2.2, #KDE Gear 25.04, #NVIDIA 575 beta, #Manjaro 25.0, #GNOME 48.1, #VirtualBox 7.1.8, Linux 6.13 EOL, #PipeWire 1.4.2, MX Linux 23.6, #PeaZip 10.4, #qBittorrent 5.0.5, and much more https://9to5linux.com/9to5linux-weekly-roundup-april-20th-2025

#qBittorrent 5.0.5 Open-Source BitTorrent Client Is Out Now with Various Improvements https://9to5linux.com/qbittorrent-5-0-5-open-source-bittorrent-client-brings-various-improvements

When is #I2P support coming to #qBitTorrent's flatpak?

I wanna seed those GNU/Linux distros privately.

My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0

Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.

Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.

I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.

https://github.com/irfanhakim-as/charts/pull/136

What are your #openmediavault and #docker resources for installing #arrs and #qbittorrent?

The new #Gnome background apps feature is nice, except that I still can't turn off the AppIndicator extension, because if I do #qBittorrent suddenly has some sort of non-existent window that shows up in Activities and the window switcher, so the feature is actually totally useless for me…? Is this a bug just with qBt or is the feature just not finished yet…?

When I need docs I do

`man command'

When I pressed F1 in a gui program it did the following

* Request a helper running in my DE to parse a html page
* Ask the helper to open my default html parser
* __Without asking me__ the helper opened a __massive browser__ ravaging ram just to show me what I could find with
`man command`
* I wonder why instead the Ui program did not do the following

* request a helper open a (ba)sh
* parse >man command to the helper
* have the helper display the manpage in the sh

The results would be
* Much less resources used
* No assumption on my current internet connection would be made
* That method has worked for 60 years

<IRC>
/m shakes head and looks at the massive browser showing the equivalence of a manpage
</IRC>

@altbot

#bash #sh #zsh #ksh #csh #qBittorrent #torrent #manpage #man1 #F1 #F1Help #WomenWhoCode #640daysofcode #301daysofcode #730daysofcode #100DaysOfCode #1000DaysOfCode #Linux #POSIX #Programming #DEVCommunity

https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions

Why does #qbittorrent for Windows open a http link in the browser after you click "yes" when it notifies you of an update? Why doesn't it just open a magnet link, downloading the update as a torrent from within qbittorrent? That would be much more convenient IMHO. When there is a #Filezilla for Windows update and you click "yes", it just opens an FTP link within the running Filezilla instance, then closes Filezilla and runs the installer, qbittorrent should do it like that, only with a magnet link to a torrent, of course.

#qBittorrent: Ignore all SSL errors.

Was soll schon schiefgehen?

CVE-2024-51774 hat die Antwort.
Mittlerweile gibt es auch einen Fix: https://github.com/qbittorrent/qBittorrent/commit/69812173690eb11a747b06f8b5b9d4e5230fbd89
"Don't ignore SSL errors".

Never again miss a #qBittorrent docker release: Follow me and hit the notify button on my profile page to get a notification when a new qBittorrent docker release has been published!