Hell seems to be freezing over at an alarming rate these days; climate change is getting pretty extreme down there too huh?

More likely is the device firmware and you likely can’t fix that.

If you have a reasonably up to date mesa and use a Proton version with a new enough DXVK, DXVK can utilise Graphics Pipeline Libraries to link shaders just like a d3d11 driver on Windows would, eliminating stutter.

I believe shader precomp is used for some video codec edge cases though, so YMMV depending on the game.

No, it wouldn’t make any sort of difference.

And also in any other filesystem’s code or the block layers below the filesystem. As I said, unlikely scenario.

Until the situation now, this was limited to the server, not the clients. You could replace the server with Vaultwarden and build it without enterprise features. Not ideal but fine because the server isn’t the critical part. It never handles your secrets in any way.

What they tried to do now was integrate proprietary code into the clients that everyone uses. This is a lot more critical as it can access the secrets in plain text.

This also wasn’t a “mistake” or “bug”, they openly admitted to doing this with the intention of subverting the client code’s GPL.

There aren’t any “extra access checks” to my knowledge. It’s just the same regular access checks applied to a different set of circumstances.

Flatpaks are containers. They do have a lot of holes though.

As long as the hardware functions as it should (e.g. respects barriers) and there is no software bug in the stack, no.

That’s a highly unlikely scenario though. Make backups.

Please stop trying to interpret the SMART data report. Even if you’re knowledgeable it can easily mislead you because this is vendor-specific data that follows no standard and is frequently misinterpreted by even the program displaying the data.

If the self-test passed, it’s likely the cable or the controller. Try a different cable.

They meant the SMART self-test, not SMART data readout. Those are not meant to be interpreted by laymen and often not even experts.

the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

The fact that they would even think about attempting to subvert the GPL (much less actually pulling through with it) makes me think they have stopped being an open source company a while ago.

It would break a lot, require a new API, and devs reworking a lot of programs.

As I understand it, this would have been a perfectly backwards compatible change. You’d only get the events if you explicitly asked for them.

The most important features when handwriting IMHO are selection tools and then being able to manipulate the selected strokes.

Write implements a multitude of selection tools such as lasso which most tools have but much more useful to me were ruled selection which selects based on lines on a ruled paper and path selection which selects every stroke you touch with your selection stroke.

You can then move the selected strokes in a ruled manner, so for example I’d select a whole line of strokes and move them down a few lines. This is incredibly useful and brings many of the freedoms we enjoy in editing text on a computer to handwriting.

Re-flowing using stroke divisors is an amazing feature in theory but I’ve never been able to make it work reliably enough for my purposes, so I personally disabled that particular feature.

The undo/redo dial is also pretty neat.

Once you actually try to take real notes or solve some mathematical problems, you’ll really come to appreciate such features and will dread using any note taking application supposedly made for handwritten notes that does not implement such features.

While that’s certainly true, using NixOS usually does not involve many advanced concepts or requires you to understand them.

You can set foo = bar in a .conf file without knowing what a variable is either.

I don’t know about rnote but Xournalpp was very underwhelming when it came to actual handwriting features back when I tried it.

It was an old Fujitsu Q755, not something I’d recommend you buy.

Had a wacom tablet built into the touch screen though which is the only thing I’d watch out for.

(nixos more or less requires you understand programming syntax for writing your system config)

It’s technically not a real programming language but an expression language. The difference is that the former is a series of commands to execute in the specified order to produce arbitrary effects while the latter is a declaration of a set of data. You can think of it like writing a config file i.e. in JSON format.

The syntax isn’t really the hard part here. You can learn the basics that comprise 99% of Nix code in a few minutes.
The actually hard part is first figuring out what you even want to do and then second how the NixOS-specific interface for that thing is intended to be used. The former requires general Linux experience and the latter research and problem solving skills.

Because the only way to have a functioning NixOS system is to have it be reproducible. That’s the only way it works; Nix is reproducible by design.

The ability to reproduce a system implies the ability to replicate it.

Freetube won’t have anything to do with h265 as youtube does not serve that format in any way.