DaGeek247

Brother laser printers last for years without issue. My point was that so long as you put in a little effort to find something that isn’t cheap shit you can actually get a product without any major issues.

Cheap wireless earbuds will fail, and will cause all sorts of frustration. On the other hand, well sourced earbuds will work for years without problems, just like printers.

My wireless g304 has been rock solid for years now. The battery lasts about 48 hours of active use before needing to be recharged. My Logitech ergo lift mouse has been rock solid for the past year as well and it’s still running on it’s very first battery!

I bought both for wrist pain reasons and for the most part they have also been very helpful for that too. Part of the reason I went wireless even for gaming is that the cable always dragged and caused issues with the mouse catching on occassion. It’s very worth whatever “instability” you might see for any product that moves.

My wireless earbuds have been rock solid for several years as well. As far as I’m concerned, wireless has been a solved problem for a little while now, similar to printers. There’s no point in needing a battery for something that doesn’t move, like a keyboard, but damn if it isn’t really nice for something that does.

Network paths in libraries have been fully removed and will no longer work. This functionality has been deprecated for a long time, and most of it was removed in 10.9.0, but this removes the remainder. See PR #12446. Third-party clients relying on this functionality should be able to re-implement it as required.

from the article.

Shame about the network location regression. That’s the only thing that keeps my kodi device from taking 5-15 seconds to load each sub menu.

It didn’t actually. If it had, I wouldn’t have pulled up my podcast app to find and listen to this episode, only to find that it didn’t exist.

Ah. I get it. Pet peeves do be the worst sometimes.

They really aren’t that far off… https://robindev.substack.com/p/cloudflare-took-down-our-website

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.

After minor setup, my experience has been incredibly plug and play.

I’ve been on LMDE for several years now and had no major issues with my 1080. But also I have no idea if I had to do anything to get it started.

I knew the forced dns thing because I have a pihole, and blocking port 53 traffic not heading to my two PIs has not happened yet, despite my best efforts. Shit aint simple for me, much less regular people.

Pihole can be broken with a free vpn, or even just forced DNS on device.

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

Studies that only confirm ‘what we already knew’ are still good to have.

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.