/c/titlegore

You would need to set up routes on these other devices to tell them that VPN devices can be reached through the Pi. It’s possible, but I’ve never done it myself, so I don’t have any useful pointers.

Use opusenc directly. It preserves covers and the CLI is literally opusenc --bitrate B INPUT OUTPUT.

Not surprising. The quality of their articles is usually mediocre at best. I occasionally look at their RSS feed and most of what I see is “How do I achieve <trivial task>”–style posts.

Yes. All devices connected to the VPN will have a private IP inside the virtual network. You can use these to communicate as though they were public IPs, except that they can’t be used from outside the VPN.

Yes, you can connect the device behind CGNAT to your existing VPN as a client. Then, from inside the VPN, you would use the its virtual address to connect to it. You can use a systemd service or similar to have the VPN connect at boot.

There is also an other approach: encode your media a priori into a format that you can play direct, and then you don’t have to worry about transcoding performance. The advantage of this is that you can likely get better quality encodes.

deleted by creator

I can recommend Navidrome as a server. I’ve had great experience with it.

Tailscale and Netmaker use wireguard under the hood, so as long as you manage to establish the connections, they should be just as fast! If you need to use relaying, however, that will introduce additional overhead.

Omnivore look excellent! Thanks for the suggestion!

I do this, too. I haven’t tried Tailscale, but Netmaker wasn’t able to deal with my CGNAT without a relay node, and I found that to be hit-and-miss.

Shell tools, mostly. For example: ripgrep, nnn, or newer versions or vim or tmux.

Does pkgsrc need RHEL 7? If so, I wouldn’t be able to use it.