DaGeek247

Yup. If the sd card doesnt have enough space for everything, you could attach an m.2 hat to it as well. https://www.raspberrypi.com/news/using-m-2-hat-with-raspberry-pi-5/

Basically, jellyfin on the pi, with the wifi setup as an access point, and whatever amount of storage you need. The pi requires 5v/5a, so you’ll probably run into issues running off the car usb power, but a cheap 30amp hour battery should run it for 6-10 hours if my napkin math is right.

Or just use a password manager like keepass where the problem of storing passwords has been solved already…

They exist, but they’re not nearly as fleshed out as the bitcoin vanity generators are. https://github.com/danielewood/vanityssh-go

That’s not how hard drives work, and doesn’t take into account that OP might want to download more than one thing at a time.

Hard drives are fastest when they are moving large single files. SSDs are way better than hard drives at lots of small random reads/writes.Setting qbittorrent up so that all the random writes inherent to downloading a torrent go to a small ssd, and then moving that file over to the big hard drive with a single long writer operation is how you make both devices perform to their best.

qbittorrent moves the completed files to the assigned literally as soon as it is done.

Yeah, I use the incomplete folder location as a cache drive for my downloads as well. works quite nicely. It also keeps the incomplete ISOs out of jellyfin until they’re actually ready to watch, so, bonus.

If it’s not going faster for you there’s probably something else that’s broke.

Not access, knowledge. Giving a specifically unique device identifier every time you visit a page is different from the website guessing if you visited recently based on your screen size and cookies.

You have to set up ipv6 to change regularly to avoid that.

You have to take extra steps to ensure that the benefits of NAT aren’t lost when you switch to ipv6. Everyone knowing exactly which device you’re using because a single ipv6 IP per-device is the default.

Ipv6 is nice, but also you need to know what you’re doing to get all the benefits without any of the downsides.

I have the att bgw-320 as well. Very excited for when the hardware for the bypass comes around.

I tried using the IP passthrough setup on it, but it ended up causing all sorts of slowdowns that I had troubles diagnosing. I was using the nanopi r4s with a WiFi AP when I had this issue. Make sure to look into compatibility with ATTs IP passthrough is not total passthrough so you might have to dig into the details to make sure it all works together.

Is this a bug, or is it actually just limited to the transcode speed? I would love to read the incident/bug report about this.

I run Debian with zfs. Really simple to set up and has been rock solid for it too. As far as I can tell all the issues I’ve had have been my fault.

ZFS looks like it uses a lot of RAM, but you can get away without it if you need too. It’s basically extra caching. I was thrilled to use it as an excuse to upgrade my ram instead.

Mdadm has a little more setup then zfs, as far as I’m concerned. You need to set your own scrubbing up whereas zfs schedules it’s own for you. You need to add monitoring stuff for both though.

I’ve considered looking into the various operating systems designsd for this, but they just don’t seem to be worth the effort of switching to me.