Is there any other way?

deleted by creator

I did the same thing for my step-kids. firstlast@gmail

And Penistone.

Add to this I read somewhere that she actually purchased more carbon credits than she would need for her tour to cover for unplanned travel - like to football games. Regardless of how some feel about the carbon credits, it’s more than nothing.

You might say it’s an “epic” story!

There’s nothing wrong with the small PC/NAS route. Certainly more powerful and flexible. I’m currently running the *arr stuff in containers on a Synology 1520 (also storing a bunch of other stuff), with Plex running on a Shield Pro. It’s pretty low power draw, and so far does everything I need.

Main thing with running Plex on the NAS is transcoding - audio and/or video. Depending on what your Plex client is, you want to make sure everything you’re streaming can direct play.

FINALLY!

Obvious next question: how’s the privacy policy on 3rd party stereo makers like Pioneer, Kenwood, Alpine, Jensen, etc.?

I have VPN, BitTorrent and prowlarr in one “stack” (a project in Synology Container Manager). Everything else is bundled into a separate project. Not sure how portainer would make this work differently. I don’t have much experience with that.

FWIW, all of my *arr, and VPN containers use the same network bridge. Prowlarr and torrent use the VPN service, though having Prowlarr on there is maybe overkill. They’re all able to access one another using the bridge gateway + port as the host, e.g.: 172.20.0.1:5050

I mostly used this guide, where he suggests:

I have split out Prowlarr as you may want this running on a VPN connection if your ISP blocks certain indexers. If not copy this section into your compose as well. See my Gluetun guides for more information on adding to a VPN.

One thing I had to make sure of was that the ports for Prowlarr were included in the VPN container setup, rather than the Prowlarr section (b/c it’s just connecting to the VPN service):

    ports:
      - 8888:8888/tcp # HTTP proxy
      - 8388:8388/tcp # Shadowsocks
      - 8388:8388/udp # Shadowsocks
      - 8090:8090 # port for qbittorrent
      - 9696:9696 # For Prowlarr

You only ever see those guys lunging forward around the gym. I wanna meet the guy who goes backwards all around!

Or backward.

It’s succinct. I’ll give you that!

I would agree with this. I think the canary in that particular coal mine would be Apple working to kill off Homebrew or Macports. So far, I haven’t seen any indication that this is on the radar.

Fi used to work desktop support, and the “average user” probably has no idea what “root access” even means. I’ve seriously had someone point to my open iTerm window and ask what I was hacking. Always remember what George Carlin said about the average person.

Adding that I’m not saying anyone is a fool for jailbreaking. I think people should have that right. I was saying the fools are the ones who still expected Apple to support the jailbroken OS. To me, if you don’t like Apple’s walled garden on iOS and iPadOS devices, don’t use them.

A laptop is different. People use them from considerably more diverse reasons. Because of that they need to be more flexible.

Also, while all that may seem like BS from a consumer perspective, it’s not as much from a business perspective. If you disagree, take a look at how Apple’s doing these days. Whatever reason you think they’re doing well, they ARE doing quite well.

The argument is that, for most people, letting them do what they want with something they don’t really understand is not a good idea. In this case it also creates a support headache for Apple. At first, they kind of tacitly accepted that jailbreaking was just going to happen and didn’t really actively fight it other than to close exploits used to root devices. As more and more people did it, for the reasons outlined above, more people wound up with bricked, or otherwise malfunctioning iPhones. When they went to Apple to fix it, at first there was an effort to help (you know, to retain customers), but they had voided their warranty. Because of that, Apple wasn’t really interested in spending lots of time troubleshooting something when they didn’t really know the full status of the OS (b/c there were multiple ways to jailbreak, and most of the fools taking their rooted phones to support didn’t understand enough to tell them what all was done beyond, “my kid’s friend said this would be cool”). Eventually Apple washed their hands of the whole thing and started refusing any support for rooted phones. That part, I have no problem with. They also started actively working to stop folks jailbreaking. That part, I thought, was too much. Just tell them they void the warranty by jailbreaking and refuse support. They dug their hole.

FWIW, I use an iPhone for personal use and android (Pixels) for work.