Yes, nix complements your system’s package manager, but doesn’t replace it

Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒

This is how I would read it. But if you have Mesa do it, it’s in software, and you might just be using a software coded directly then, it’s much easier.

From my understanding, it’s the hardware that produces bad results. There’s no encoding logic in the drivers itself. That’s why the encoding is accelerated in the first place.

E.g. if the hardware doesn’t support b-frames – which for long it didn’t – a new driver won’t do jack. This is just about how video data gets into and out of the card, any encoding logic is handled by the hardware.

Haha I still remember finding that out

Good how dumb

What made the release exciting for you?

I just roll along on NixOS-unstable, so for me changes just trickle in over time.

On the last day actually, haha

For anyone interested, this was due to a curl regression AFAIK. 24.11 was supposed to release a week ago but a lot of stuff had to be rebuilt.

Foobar2000

Dang dude, I had just gotten over foobar2000.

Ahh! It was such a step up from Winamp. I think I started using that around 0.7… and actually used it with Wine when I started using Linux as my main OS in about 2008. But there is nothing quite like it.

The only good distribution is my distribution.

If I had a different specialisation, I’d probably care. But my job is mostly reading and writing documents, and they installed Miktex on my office machine, so I don’t want to complain.

We do have formal security requirements to meet though, and I think in general locking down machines in your network is the correct choice. But it’s probably not needed in every job

Their higher-end models seem of nice build quality at least, but that’s something I just expect at a certain price point.

Linux isn’t even an option at my current job, it’s WSL if anything. And that on the development machines only. Office work machines are Win 10 without any privileges, which I’m fine with. Employer pays for the time I take longer for certain things. His choice.

Unfortunately, there aren’t that many great European options, so buying somewhat domestic is hard.

Ah, okay. I do have thinkpads for work, same at my previous employer, I’d say they’re pretty forgettable, not sure I’d buy Lenovo for anything that needs to be particularly secure, just read the English wiki entry for Lenovo about security incidents, but I’d be more careful when procuring for work, especially in certain fields.

Excuse my smugness, but being excited for your premium laptop maker to bring back a feature that is standard basically everywhere (all of my four laptops have HDMI, and out of those, my two non-work ones also come with DisplayPort) is such an Apple thing

It’s like these people claiming that you need that connectivity for a lot of work were right.

Currently, there’s no serious discussion about removal from mainline. And LTS won’t remove it.

Should it happen, you can still use Kent’s kernel tree as before. Whether distributions ship it - who knows.

If there’s no mainline or dkms support, I’ll move my storage away from it in favor of btrfs that I’ve successfully used the years before instead of switching to LTS. Just because of future maintainability and migration options.

Nobody forced him to apologize. On the other hand, the Linux community isn’t forced to take his patches.

While I understand the sentiment, I’d argue that an apology should be made in the same context as what you’re apologizing for. Kent made his statements on the LKML - if his apology is sincere, I don’t think it’s too much to ask to put it there as well

The way I do it with webservices is that I serve them all from virtual hosts. Scan my IP on port port 80? 301 moved permanently to same host port 443. 443? Welcome to nginx! Which webservice is actually served depends on the hostname being requested. The hostnames are just part of a wildcard subdomain with a matching wildcard certificate, so you can’t derive the hosts from the blank landing page’s cert. Though one option would be to disable https when no matching virtual host is found.

I know this isn’t protection against sophisticated attackers, but nobody uses my home services except me when I’m not home so the exposure is very limited.

Anyhow, with Plex you have a central provider who, if I’m not mistaken, knows a lot about how their customers use their product. The angle of attack is different.

Are you talking about TPM 2? Because I don’t think that makes classic ransomware more difficult. Also it doesn’t have to be strictly a motherboard feature, e.g mine comes without a fixed hardware TPM, but my processor supports fTPM, which has up- and downsides. But it works as a TPM.

Also MS: Sadly, if your tech doesn’t have these features you cannot upgrade and it will be insecure because I will not make updates for it.

Technically, this isn’t true, MS will continue to update Windows 10 and even individual users can receive these officially through the Windows 10 ESU program: https://learn.microsoft.com/en-us/windows/whats-new/extended-security-updates

Not that I’m in favor of what they’re doing, I think they should rather support older hardware with Win 11 and require modern features only on modern systems. But from a security standpoint, their decision is actually good, as it builds a secure foundation. Most private users will just do whatever on that foundation (e.g. run random stuff from the Internet), but I think going forward, this is the right choice, though probably for the wrong reason of doing Intel a favor.

The problem I have with this is that there’s no definition of what “owning” means. Never have individuals bought a game and then owned all rights associated with it. It was always a license that included personal use and nothing much else.

However, due to how media distribution worked, this license was generally valid forever and could be transferred to another party, and these two factors - especially the first one - make a good point: why would I enter such a license if the other side can factually nullify it at any point, while I lose that option after a certain time?

Apart from that, media piracy was never stealing in the first place. It’s about unlicensed usage and distribution of media. And rightholders can’t be surprised if people don’t license it if the construct is so stacked to their disadvantage.

I think if LetsEncrypt went away, so would ZeroSSL’s free offer.

However, I do think not having limitations on the API is good; automation is good practice and I guess this is a concession to customers /users who have no automation in place (though this is a sad state by now). LE doesn’t offer anything comparable AFAIK.

Never used them, but they state at https://zerossl.com/features/acme/ that their free acme certs include wildcards.