I’ve kept a raspberry pi 4b that’s given a mild OC to 1900Mhz in my boiler cupboard for a year and all its needed to keep it below 50 is:

1. a tiny metal heatsink
2. a 5w usb fan blowing already-warm air sorta towards it

I’m quite new to docker for NAS stuff - how many pulls would the average person do? like, i don’t think i even have 10 containers 🤨

gotcha!

I don’t have much issue with email as a technology. It does what it needs to do, and does it well. The client side software is what hasn’t budged in years - Search barely works, files and attachments are cumbersome, and spam is still rampant.

It would be much cheaper and easier if users weren’t centralised under a few big providers that prefer to bar any and all access to said users if you’re self hosting, making it almost mandatory to use a private service.

EMA-AI-L protocol that turns your prompt into AI slop during transit, but contains a header with the original prompt so the recipient gets your actual message without bullshit attached.

Does this use Btfs’ RAID5? If so you might want to avoid since RAID5/6 arent production ready for Btrfs and contain known bugs that can lead to parity loss.

private trackers are the way. DigitalCore is one Im signed up for and it helps a bit with fleshing out my library.

thats like the only thing that would’ve made this better bro

Yeah it’s pretty much seamless. You just spin them up bare metal or docker (both are fine honestly) and follow any old tutorial for setup.

If using docker, ensure you mount the qbittorrent’s download folder to /config/Downloads with a capital D or you’ll get a warning about paths being set up wrong.

Also, I assume this isn’t really an issue for you unless you mess with the downloads after the fact, but *arrs expect the torrented media inside a folder with the title of the media on it. It picks through torrent naming conventions fine, but when I migrated some movies yesterday I noticed it wouldnt pick up any video files that weren’t inside a directory.

Small note, the *arr stack (at least when running in docker) will prefer you mount qbittorrent’s download folder to /config/Downloads (case sensitive). otherwise it whines about paths in the health menu

Our government is so goofy. These massive overreaches into privacy and fair use all while having zero resources to actually enforce anything.

Remember the ““porn ban””? Beyond ISPs changing some filtering settings I don’t think anything actually changed for 99% of internet users.

Hell, our copyright laws might be based on the DMCA (The EU copyright directives and DMCA are ratifications of the same treaties) but I have never received a single Copyright letter in my life, even whilst running a seedbox for the last 2 years from my boiler cupboard!

I still don’t understand why Fedora feels it is superior at packaging a flatpak over the people who actively develop and distribute their own flatpak.

Sure, the bugs might be fixed now, but Fedora still prefers its own flatpak repo over flathub for little benefit, duplicating the effort of dozens of developers for a worse downstream experience.

If you distribute your app via Flatpak, what benefit is there over “disk space” (irrelevant for all but embedded devices) or the vague superiority complex of distro maintainers to manage your dependencies for you.

Even if downstream fixes a bug or two, those should be merged upstream. Imagine if Fedora staunchly refused to upstream fixes to bugs in the kernel?

Greg is a great level head in the kernel regarding rust, at least among the senior maintainers. I hope he can convince some of the more hostile maintainers to accept the new status quo that includes Rust in the Kernel at all levels.

You could get special NES items in the game for completing certain tasks. They designed the emulator to work with arbitrary ROMs so they could add ROMs later as part of nintendo promotions and events using the eReader Cards.

These custom items are encoded in a standard format in a user’s save file, so you can still visit people’s towns and transfer these items around.

No issues at all! Obviously speed caps will be useful since eventually you’ll have enough torrents that even gigabit will be saturated, but even a low speed can mean a lot over a long time.

I use qbittorrent so maybe this is why, but when my downloads finish theyre moved to my movies/tv folder but since qbittorrent handles that, it keeps seeding the files afterwards.

KDE and I keep it mostly stock. I usually get a compact desktop pager widget and add a kwin plugin to dynamically add/remove virtual desktops.

i have a raspberry pi 4 and it’s completely fine running 24/7 with torrents. Granted, with 3MB/s upload it’s currently hitting one core at 60% but I use Dietpi which has a nice utility to reduce the CPU priority on qbittorrent if another service needs it.

Plus, you could set up a samba share, store your torrents on the shared drive, and copy them to your Main PC when you need em. Doesnt need to be sophisticated.

My current plan once new migration is completed:

Primary pool - 1x ZFS (couldn’t afford redundancy but no different to my RPI server). My goal is to get a few more drives and set up a RAIDZ1/2.

Weekly backup of critical data (eg. nextcloud) from primary pool to a secondary pool. Goal here is to get a mirror but will only be one drive for now.

Weekly upload of secondary pool to hetzner storage box via rsync.

Current server

1x backup to secondary drive (rpi) 1x backup to hetzner storage box via rsync

That’s a damn shame, I’m sorry! I hope you got to back up a few of your personal things, and if you didn’t at least you have a bunch of knowledge to take onto your next project