hmm I’m not sure, I think that would throw sequential read/write performance out of the window, surely on HDD, maybe even on SSD to an extent. but, such a thing can probably be added with a device mapper device.

That is block based encryption

isn’t all the disk encryption standards supported by cryptsetup are like that? so LUKS1, veracrypt, bitlocker, etc

How does the encryption affect the wear-leveling of the SSD and what should be considered to ensure a safe encryption?

LUKS, or rather Device Mapper for crypto devices does not enable trim by default, you need to enable it separately.

https://wiki.archlinux.org/title/Dm-crypt/Specialties#Discard/TRIM_support_for_solid_state_drives_(SSD)

the LUKS wiki also has some general tips, and some for SSDs specifically: https://gitlab.com/cryptsetup/cryptsetup/-/wikis/FrequentlyAskedQuestions

I have also experienced your first problem. It’s probably that the game bugs out in some way. apparently gamescope helps to fix it, bit I wasn’t able to get it to work on an nvidia based system.

touchscreen use?? what health risks does it have? I can only think of brainrot, but that’s not due to touchscreens, but to specific parts of the internet

I have a similar convertible device, and it’s almost good with KDE. KDE components switch to a layout with more whitespace and bigger icons so they are easier to touch, and some KDE programs like the file manager also opens a special menu on long press on files that is an easier to use version of the right click menu.

firefox also handles it well, I can easily scroll a page with momentum, but I can also select text.

my device also has a plastic pen (no buttons or battery in it), and linux knows to ignore touch input when the pen is near the screen so that I can rest my palm on it while writing.

but a major pain point is that so far I haven’t found a real touch keyboard. there is Maliit, which is much harder to build locally than other programs, and if you get it to work it is hard to use. then there is squeakboard, but last time I was looking into it that depended on wayland protocols that were not implemented yet in KDE’s compositor

first I read “AI Qaida”, but maybe there’s something to that too

Event 41 Task 63? what’s that?

but to repeat: windows dies not understand linux partitions to any extent. it shows them as “uninitialized space” or something like that, so that it looks like it’s gone. It’s always best to check the partitions with gparted on a live system (e.g. systemrescue linux)

that’s not the only feature of v2. it also hels a lot with swarm merging (which with v1 only biglybt implemented), and it has updatable torrents. it also stores torrent information more efficiently and the incoming pidces can be verified immediately. afaik today torrent clients don’t verify downloaded torrents by default. qbittorent has an option, default off, to verify after a torrent completed. this is slow because everything needs to be read again from disk. I’m not totally sure about this, but I think a malicious peer could be sending crafted pieces that contain something else and you wouldn’t know it.

https://torrentfreak.com/libtorrent-adds-support-for-bittorrent-v2-a-potential-game-changer-200912/

ok that makes sense and if it is not too limiting, at least its a bit self documenting, you aready know what changes did you made. hmm maybe I should try it out someday on a spare laptop

well now I understand why is suse transitioning to a different installer instead of improving it

I don’t think that’s true. Administration tools could build on top of it, like snapshotting, which even if it does not work the best that way, it will work. and that can just run in the background, automatically, just like it does with snapper on btrfs now on some systems.

yeah, but they use immutable system images that you can’t change even if you wanted to. KDE’s update system is integrated with a systemd component that does the installation after a reboot, I think nowadays that’s the best of both worlds

but does it load all libraries into ram at startup? there’s also all the resource files, including omni.ja that has a bunch of javascript code

It’s interesting because instead of “display manager” it should be “graphical login manager”, and the current “login manager” should be called “session manager”. I don’t know the origin of the name, though.

it can be skinned

and while we are at that, MPV also has a working reverse play implementation (though that’s like a slideshow), and it can very seamlessly do frame by frame playback, the hotkey of which just does normal playback perfectly while it’s long pressed

it literally has a lower CPU consumption, even when using hardware decoding. and even when playback is paused.

lower CPU consumption means more free resources for other programs, and lower power usage, which is more battery life.

it also seeks much smoother, I mean quicker with less delay

it tells you on a new tab. if you continue without restarting it you’ll see its already falling apart

what is P2P? I thought that’s the category the others fit into