This. Just setup fail2ban or similar in front of Jellyfin and you’ll be fine.

Exactly, I don’t understand why so few articles covering the trial suggest Chrome going independent as an option.

I don’t know why, somehow it just feels different to me. Or maybe it’s just the state of the world that tries to dehumanize everything with “AI” that depress me.

Just the thought of sex robots depressed me even more than the state of the world already had.

It’s like regular Fedora KDE, except that it avoids this problem of traces of past experiments everywhere.

Kinoite is much more than that: it is an atomic and immutable spin of Fedora KDE. This has big implications but the gist of it is that:

1. You can roll back to any previous version if anything breaks

2. The base system cannot be modified

3. If you need to install RPM packages, you do that by adding “layers” on top of the base system, and these can be removed if needed to go back to a clean base system

4. You can switch from one spin to another by “rebasing”, but it is recommended that you remove any additional layer first and that you stick to the same desktop environment

My experience on other distros was that upgrading in place a system that deviated too much from “stock” would wreck the install. I would personally play it safe and backup my home folder and do a fresh install.

Just don’t forget to test your backup before formatting your drive!

Android has always been developed in a closed-source manner by Google engineers, the recent changes only reduces the visibility of ongoing changes and the ability for developers outside of OEMs to contribute to Android (such contributions were already rare).

This is explained further in this article:

While some OS components, such as Android’s Bluetooth stack, are developed publicly in the AOSP branch, most components, including the core Android OS framework, are developed privately within Google’s internal branch. Google confirmed to Android Authority that it will soon shift all Android OS development to its internal branch, a change intended to streamline its development process.

Do it! Do it! Do it!

I was going to play the first one on PS3 before playing through Part II, but if the Collection comes out on PC before then, I might buy it and play both games on PC instead.

Most likely they use a translation layer (think Wine, Proton or DXVK) rather than emulation, since the Switch 2 hardware is not completely different from Switch 1 and it’s not as costly as emulation, so I would say neither.

Edit to clarify emulation vs translation layer:

Emulation re-creates the entire hardware, while translation layer translates programming instructions intended for one platform to another, just like you would translate “one plus two” from English into “um mais dois” in Portuguese for exemple.

Since both Switch don’t have completely different hardware (unlike PS3 and PS4 for example) it’s probably easier and much more efficient to simply translate instructions that were specific to Switch 1 into Switch 2 instructions.

Edit 2: also Yuzu and Ryujinx are designed to emulate Switch on the x86 architecture, and since Switch 2 (and Switch 1) run on ARM, I’m pretty sure these emulators wouldn’t run on Switch 2 without massive re-engineering efforts. Also, as someone else said, these projects are reverse-engineered, it makes much more sense that Nintendo engineers create an emulator from scratch using their own internal documentation of Switch 1 architecture (again, it’s unlikely they went for emulation as I stated above) so the result is much more reliable than both Yuzu and Ryujinx.

That sentence intrigues me

we did something that’s somewhere in between a software emulator and hardware compatibility

What do they emulate vs. what was added in hardware to ensure compatibility?

Haha yes, the Mario Party Jamboree minigames using the Switch Camera felt very EyeToy-like.

I might be lucky, my Gen 1 Pebble still works (though I have not tested how long the battery lasts in use, I only know it stayed on for under a week idle).

Only restic snapshots are backed-up to B2. ZFS snapshots are for undoing mistakes, though I enabled them recently and I have yet to use them.

My work flow is pretty similar to yours:

For my desktop and laptops: systemd timer and service that backups every 15 minutes using restic to my NAS.

For my NAS : daily backup using restic + ZFS snapshots.

All restic backups are then uploaded daily to Backblaze B2.

I believe Linux Server builds images every day for most of their containers, even though there has been no code changes.

Chrome and Firefox do as well

I believe the anticheat for Fortnite it the kernel-level flavor or Easy Anti Cheat the article mentions, and I think that by its nature it cannot be easily ported to Linux, Epic would have to drop it altogether in favor of the “vanilla” flavor of EAC.

Epic putting the work to make their anticheat compatible with Windows-on-ARM but cannot be bothered to do the same for Linux… 🙄

The first one also has better code coverage and way more pulls on Docker Hub.