

What do we know about
The unknown knowns
The things we don’t know we know?


What do we know about
The unknown knowns
The things we don’t know we know?


Pretty much all invasive kernel level anti cheat detects and blocks VMs


You don’t need Thunderbolt for Displayport alt mode. It’s a separate spec that can also be implemented independently. I have a dock that’s not Thunderbolt but supports DP alt mode.
But Thunderbolt has some additional stuff too


Last I heard Cinnamon does not have stable Wayland support yet. One of the reasons Wayland was made is because multi-screen support on the old X11 is an ugly hack. Unlike wayland, it doesn’t play well with screens of different resolutions, refresh rates, adaptive sync compatibility or HDR.


Mint isn’t wayland yet and X11 does not support adaptive sync if multiple monitors are connected


No. The Rust code in the kernel is GPLv2 just like the rest of the kernel. The licence of the compiler has nothing to do with that, that’s nonsense Rust haters make up.
You can argue against independent projects like the Rust coreutils not using a copyleft license, but that has nothing to do with Rust or the kernel. There are independent C projects without non-copyleft licenses too.


We know that it started as a fork of Waydroid
But:
Update: While Lepton was based from Waydroid at the beginning
It seems to be a lot more custom now. To the point where it’s being described as “not really Waydroid anymore” from those who are working on it


The open source server allows unlimited connections I think. The point of the paid server is user & device management, shared address book and some other enterprise features
Systemd’s version is run0. It’s broken on selinux systems though (at least fedora)


A DDoS that brings down the biggest(?) DDoS protection provider?


Love that channel :(


tldr


Nvidia doesn’t support vaapi, so when I still had an nvidia card I needed to install a compatibility layer like this. You might have more problems if you want to use a Chromium based browser though
Jujutsu (which is compatible with git) has a nice conflict resolution flow that doesn’t break you workflow.
Conflicts are encoded into the commits, so that there is never a weird in between state that you have to deal with immediately before being able to do anything else.
Then you can use Jujutsu’s easier history manipulation to resolve the conflict in the conflicted commits.
https://steveklabnik.github.io/jujutsu-tutorial/branching-merging-and-conflicts/conflicts.html
And you could always jj undo if you did something you didn’t want to.
With Jujutsu (which is compatible with git), you can just
jj undo
That’s VSCode
I thought the main reason was that they changed the license
ESNI has largely been dropped in favor of ECH