Perhaps just uninstalling Nouveau and falling back to the Intel driver, if it’s already installed, is sufficient? Or if that doesn’t work, worst case OP could blacklist Nouveau and and update initramfs? I’m just guessing as long as the Nvidia driver is never actually active perhaps that’s enough to avoid excess power consumption.

OTOH there isn’t much harm in OP keeping Nouveau enabled and seeing how things go though I’m in agreement with you, on an older laptop there’s not much advantage to be gained with the older Nvidia hardware.

All the loaded torrents in a torrent client already get stored somewhere in the torrent client’s own settings folders. e.g. if you look in qBittorrent’s settings folders you’ll find a folder full of .torrent files representing every single torrent currently in the torrent client.

So if it’s a torrent I’m going to leave loaded in the torrent client then no, there’s no reason to save a second copy of the .torrent file. But I guess if it’s a torrent I’m not going to load in the torrent client, or will remove it from there, then maybe it’s worth saving depending how you do things.

I’m undecided. I figure if I save them and back them up to an offline/offsite device, then I can (mostly/hopefully) recover from hardware failure by simply re-adding all the torrent files to my favorite client.

It would be better just to back up your entire torrent client settings folders, you’ll save all the .torrent files along with the save folders and other information you have in the torrent client.

Remmina and Xrdp are probably the better RDP clients at the moment. I’ve had no problems using either to connect to Windows 10 desktops but have not tested Windows 11.

FreeRDP is used by most (all?) Linux RDP clients, it does have its own active development.

Could also try the Linux RDP client that Thincast has, still uses FreeRDP in the backend like the others but it does seem work well at least with Windows 10 (https://thincast.com/en/products/client).

Also for what it’s worth I’ve seen mention of a FreeRDP bug when the client fails to connect to Windows 11 with multi monitor enabled (since most Linux RDP clients use FreeRDP the bug affects them all too). Think the workaround for now is to disable multi-monitor in the RDP client settings before attempting to connect. Think it is getting fixed in the next FreeRDP release. No idea if that’s your issue but worth a look (e.g. https://gitlab.com/Remmina/Remmina/-/issues/3403)

Still learning this myself but I’ve found that Xrdp is Wayland compatible so there’s that if you want to remote using RDP protocol.

Gnome has its own version called Gnome Remote Desktop that is also Wayland compatible.

And for KDE its own KRdp is another RDP protocol remote server that is Wayland compatible (https://github.com/KDE/krdp). I haven’t tested the KDE version yet but I’d guess it works similarly to Gnome Remote Desktop and Xrdp, AFAIK they all use FreeRDP in the backend.

All the Linux RDP servers seem to have their own quirks but seem okay for personal day-to-day use least.

Beyond RDP solutions you could also check out stuff like RustDesk and NoMachine, they seem to be Wayland compatible as well. Though I am curious what else people use.

PS - Gave up looking for a Wayland compatible VNC, not sure if VNC will sort of die out as more and more Linux distros switch over to Wayland.

Kind of seems like an ad, every link to their site has a referral in it ( /?ref=news.itsfoss.com ), guessing itsfoss gets paid for those clicks.

Nope, I prefer being able to run my own network router, open/close my own ports, block ads on the network, hopefully get as much bandwidth as I can, etc. so it’s usually better for me to subscribe to my own internet.

… But since you bring it up, coincidentally I currently live on a street with shops/restaurants on the main floor under me. And all their wifi networks are visible from my apartment… so technically yeah, if I go through the trouble of collecting all their wifi passwords I could just hang out on their networks for free internet. Internet probably wouldn’t be great and not very private without a VPN but for free web browsing it should work.

combine announce URLs into one torrent file

No.

or create a separate torrent file for each tracker?

Yes.

You can also check in the rules/FAQ of each private tracker but it’s universal that all private trackers require their torrents to exist and announce/share peers separately. That doesn’t mean the data has to be separate e.g. if it’s the same torrent data you can point multiple torrents to the same data.

You forgot to mention their Tor link, seems to be working fine http://l337xdarkkaqfwzntnfk5bmoaroivtl6xsbatabvlb52umg6v3ch44yd.onion/

(also linked in https://1337x-status.org/ )

Eh, sure OP could do that. Does seem a bit over the top for OP to pursue the most complicated backup solution possible :D Maybe as a strange experiment to see how it goes, not as a trusted backup solution. (like you said not for critical data)

IPFS would also require more bandwidth vs just about any other solution since it has to constantly talk to other IPFS nodes. And more finicky, last I used IPFS the client would run into memory leaks and other weirdness requiring restarts every now and then (hopefully it’s more stable for long-term runs nowadays).

Similar but no, Syncthing does not use bittorrent or the bittorrent protocol.

Though if you’re curious Resilo Sync (formerly Bittorrent Sync) is similar to Syncthing and does use bittorrent.

Wouldn’t be a good solution, you’re hoping that other users are going to volunteer to pin (aka store and seed) your personal backup data for you.

Using IPFS for personal backups is exactly the same as creating a torrent with your backup data - With both it would be unlikely that your personal backup data will actually exist anywhere beyond your own data storage, no one’s going to freely volunteer to store your backups for you.

Not overly active but there are a few communities you could join if you like

!OpenSignups@lemmy.dbzer0.com

!Opensignups@lemmy.ml

!Opensignups@noworriesto.day

https://opentrackers.org/ is also a good site to keep an eye on (though it seems to be less active at the moment).

Not sure which country you’re in but in the U.S. I haven’t seen many gift cards that are contactless tap-to-pay so you would want to double-check. Without tap-to-pay those type of cards would need to be added into a phone app (Google Wallet / Apple Pay) to be able to tap-to-pay using it.

It’s possible outside the U.S. it’s more common for gift cards to be able to tap-to-pay.

Or if you’re talking about store gift cards then the same applies, most of those aren’t tap-to-pay either so you’d want to double-check.

Prime95 and Memtest86+ both run under Linux so no issues there.

You could also run those sort of apps off a Linux boot USB, or one of the Linux based diagnostic boot USB projects. I like SystemRescue (https://www.system-rescue.org/System-tools) but there are plenty of others you can check out - SystemRescue includes memtest86+ / stress / stress-ng / stressapptest for system stress testing so that could be something to try.

Yup like others said the lack of a CPU cooler is definitely the problem here. CPUs heat up quickly and once they hit their thermal limit the system will shut down to try to avoid hardware failure. Hopefully the CPU wasn’t damaged from repeatedly overheating while you were testing without cooling… it might be okay, only way to know for sure is to properly install a cooler and then test.

Once you’ve got it going I’d suggest doing a burn-in test just to be sure the CPU will last. Been a bit since I’ve done a build but usually I’d run something like Prime95 to be sure the CPU and cooling is stable.

Ah yeah I saw that one but I don’t think it does quite what OP wants. Seems more like it is designed to monitor a running qBittorrent client and then copy the .torrent file(s) to Transmission, with all torrent data in the same data folder. Might not help much for OP with all the different data folders they have in their current setup.

My concept is as such: have a shared folder where everything is moved after download. I call this /mnt/torrents.

The script provided that makes all of this happen is a python script. It queries the qBittorrent client for uploading or completed downloads, checks to see if they are private or public torrents, then copies the .torrent files to the respective “watched” directory of the public or private (transmission) client. It just copies the .torrent files to directories, so it should be usable with other torrent clients that have “watched” directories.

But either way nice effort! I’m kind of surprised at the lack of scripts to import torrents into Transmission. The only related script I could find is to do Transmission --> qBittorrent but it doesn’t seem to do the reverse https://github.com/Mythologyli/transmission-to-qbittorrent

and even then, I tried one and for some reason it wouldn’t verify my downloaded files and insisted on redownloading the torrent from scratch. Even though I had made sure I was pointing to the correct directory. This may be because I’ve renamed files in the past

That should work fine… I suspect that failed maybe because you renamed like you said. Make sure Transmission is adding torrents in paused mode, then do another test with a torrent you definitely didn’t rename. Maybe just do a test download in qBittorrent and then attempt to add it into Transmission e.g. a Linux Mint torrent or similar is usually a safe test https://www.linuxmint.com/edition.php?id=319

Because of how you have your torrents organized it does sound like you’ll need to tough it out and add each torrent and configure it manually.

It would be easier if you had all the torrent data saved in the same folder(s), in which case just configure Transmission to add torrents in pause mode, configure a watch folder, copy your qBittorrent’s .torrent files into that watch folder, and finally do a re-check in Transmission and start all the torrents. Then just hardlink the torrent data out into your own nested folders how you want them set up, that way the same data exists and is linked in two places (torrent data folder and your own folders). Maybe it’s something to consider for your future configuration but it’s not going to help you much right now.

For now yeah, the best you could do is set Transmission to add torrents in paused mode, configure a watch folder, copy paste your current qBittorrent .torrent files, then afterwards in Transmission change each torrent’s data location and re-check one-by-one. Not sure if it’s any faster than just adding the torrents manually one-by-one :/

You should be able to find the current .torrent files wherever MacOS saves your qBittorrent files, look for a folder that looks like qBittorrent / BT_backup, all the .torrent files in BT_backup are your loaded torrents inside qBittorrent.

With some luck maybe you can find a tool that does qBittorrent --> Transmission migrations? I wasn’t sure if any exist, all I can find are tools to do Transmission --> qBittorrent e.g. https://github.com/undertheironbridge/transmission2qbt

(note I’m not on MacOS so maybe someone else has more direct advice to offer)

and then aggressively super-seed that content back out.

What exactly do you mean by super-seed? In torrent clients there is indeed something called super-seeding aka initial seeding but that does quite the opposite of “aggressively” seed anything. The whole point of super-seeding is to encourage other peers/leeches to share data amongst themselves and hopefully become seeds themselves. This results in your own torrent client avoiding uploading torrent data to the swarm more than necessary, it’s the opposite of building ratio if you’re minimizing uploading data.

https://en.wikipedia.org/wiki/Super-seeding

https://www.bittorrent.org/beps/bep_0016.html

It might be you meant to aggressively seed on an internet pipe with high upload bandwidth e.g. one of those 20 Gbps seedboxes or similar, that would make sense.

The vast majority of private trackers do not have a “hard” ratio economy like you describe. Most private trackers are flexible to give users ways to increase their own upload ratio without requiring that ratio to be “paid” by another user doing the downloading. e.g. when torrents are freeleech the users get to download for free but can still upload to improve their own ratio. And when there’s bonus systems in place those bonus points can be used to add to the user’s own uploaded data count. And sometimes private trackers have events where they make the entire tracker, or entire categories of torrents, freeleech so a whole ton of users get to download for free and will still be able to seed those same torrents afterwards.

does that mean that there are some users who will forever be below 1, and thus end up getting kicked out, thus resulting in the private tracker just… shrinking over time?

Sure, that could happen too. Private trackers will always get some users that just aren’t going to cut it and eventually lose access to the tracker. In most cases the tracker will just end up adding new users and maintain the total user count. Each tracker is going to be different in how they approach this… I think over time the user churn doesn’t happen as much, at some point there’s enough users on the tracker that are doing fine with ratio and whatnot while the tracker hits its own maximum user count so actually needing to replace users with new signups becomes less of a priority.

Agree with you, SO is great for finding info. There are solutions on there for niche problems that I haven’t been able to find elsewhere, the type of thing where someone actually took the time to type out a step-by-step answer and it’s now there and searchable on SO. It’s a bummer that so many people seem to hate on the site nowadays.

And lets not forget the whole reason SO came out in the first place, back then web results were littered with question/answer links to sites like Experts-Exchange. I hated trying to figure out if an answer was on there, most of the time you ended up with a link to a question that you think has an answer but oh no you need to subscribe to view an answer that may or may not exist.