Interviews do typically count, it just has to be citable. Videos are sufficient in that regard as well, not just articles or books. It would be different if Torvalds had edited his own wikipedia page, but an editor who updates the page and cites this video would not be in the wrong.

I mean, I feel like he outright confirms it in the video. It’s his distro of choice since it allows him to easily use his own compiled kernels in testing. Anything else is an inconvenience to his work.

How’s the overall health of the drives? You might want to get a quick SMART report.

Otherwise, this sounds like pretty normal drive activity. It could be the result of anything from indexing tools to casual background processes doing a read.

If it’s periodic in a way that’s consistent, then it’s almost definitely something in software. What docker services are you running? Do you have any auditing tools or security processes that might be actively logging activity?

It’s pretty unlikely you’ve contracted malware unless you’ve gone out of your way to expose the server to outside sources, so I think you can alay those concerns.

Something KDE has done seems to have resolved the issues I used to have with DPI related scaling problems in Wayland. Once Plasma 6 hit, it’s been nothing but rapid improvements with Wayland as a focus and man does it feel nice.

That said, there’s virtually no downside to still using X unless you have explicit display features you need from Wayland like HDR or the per-display scaling. Xfce is stupid lightweight and still my default for anything where battery life is a benefit.

In my experience, they come in waves. They come either as data centres seek to replace or renew existing drives, but as a result, there aren’t as many lower capacity drives available. Lately, I’ve only seen 10+TB drives under a recertified banner, though you can find lower capacity drives that are “refurbished” instead. They will have the power-on hours to match though, as these are the refuse from those sorts of drive replacements.

You may find better luck with local used marketplaces if you only need cheap storage. Otherwise, they do seem less common if you don’t need large capacity drives.

Echoing the sentiment of the other commenter. A link would be great!

“Community Add-ons” leads me to think this is probably Kodi. You can generally do IPTV streaming through it, or torrent streaming even.

I don’t feel like this is a terribly recent attitude. It’s definitely one I’ve encountered repeatedly over a decade or more of dipping my toes in the pool. It’s not incorrect in a lot of circumstances, but it’s very difficult to find support when no one wants to help you improve. There’s always been a significant degree of ego in Linux user communities.

Flatpaks are basically containers, allowing applications to maintain their own dependencies separate from your system. It’s similar to a Windows program shipping with its own precompiled DLLs, helping prevent dependenct conflicts when you go to update something you installed with pacman or yay.

Arc support was added after release to Linux Kernel 6.2 and it’s steadily improved since. Older Linux distros, or “LTS” oriented distros that favour stability may still not have support for them. I know Unraid was very slow to pick up on it and I had to settle for passing the pcie device through to a VM to get it working. Intel is keen to made these viable though, and I love having the AV1 encoder from my A380.

That one sounds squarely on Nvidia. Any driver that uses undocumented workarounds to gain kernel level access or utilizes an access loophool for system hooks is a bad driver. I’d assume Debian, or likely more accurately the Linux kernel itself was updated following some matter of CVE that Nvidia was quietly abusing.

Frustrating, but a good example of why those kinds of proprietary drivers are such a nightmare. You really just don’t know what techniques they’re using.

Biggest difference is that wormhole will pass traffic between devices on different networks as long as both are routable. So it’s not limited to a local network connection.

Ah, I see where I got confused. Yeah, CGNAT isn’t very common around here. I don’t think I’ve ever run into an ISP that uses it. I can see how that complicates things.

You really don’t though. I use wireguard myself under the same scenario without issue. You just need to use some form of dynamic DNS to mitigate the potentially changing IP. Even if you’re using Tailscale you’ll still need to have something running a service all the time anyways, so may as well skip the proxy.

Oh yeah, at the time there was no support for my current registrar. It was a fun enough project to put my own script together anyways.

This is probably not what you’re looking for, but I found registering a cheap domain name and using a dynamic DNS script that checks every hour or so against your public IP to be a good way to mitigate issues. It also depends on your ISP. Mine typically only renews upon a reboot of the modem or a new PPPoE authentication.

Others have also suggested Tailscale, and I think that’s also a worthwhile option. It’s a pretty easy thing to set and forget, working like any oher VPN client. This is the least complex option to navigate, and if Plex was the only service you were forwarding then it’s likely the best option.

I use Wayland exclusively, but unfortunately I don’t think I have an answer for you since I’m not entirely familiar with this idea. Is your concern just for the configuration of a universal set of hotkeys configured within the compositor rather than a desktop environment?

I wasn’t aware that x11 facilitated this. I’d have figured keyboard mappings are abstracted from the compositor and left to the DE to handle, aside from core binds that allow dropping back to tty

I think the complaint is that it got linked in the linux community? Idk

What would be the difference between Fedora Kinoite and this?

Because you’re serving the website on a non-standard port, you will always need to provide the port in the web browser.

That said, I don’t see anything wrong here. It looks like you’ve got the right ports set, TCP should be correct. You may not get a ping, because ICMP is likely not enabled at the modem. When you ping, you ping the first device that’s exposed to the internet, not an open server.

Just to be sure, when you’re on your phone, you’re using data? If you’re on wi-fi, the modem/router may not be configured to perform NAT reflection, so you won’t be able to access anything via your WAN IP.