Domi

Thanks!

Steam does as well.

I found out recently that KDE has a “Focus stealing prevention” in their settings and it has been glorious.

I “vibe code” anything that is throwaway.

Same here. It’s surprisingly easy to get quick results with a few prompts for one-time scripts without putting any effort in.

I recently got a 80% keyboard without numpad and bought a separate numpad to put on the left side of the keyboard.

Game changer.

I always chuckle when Jellyfin shows subtitles as “Full ASS”.

I have wondered this for a while, what is it you do that requires such intensive editing of PDFs?

Both at work and at home PDF is sort of a “read only format” for me.

I get it for things that should not be edited (e.g. invoices) and export it myself for things that should not be edited (e.g. finished documentation). The only “editing” of PDF files that I rarely do is filling out PDF forms or signing a PDF, which most readers can do.

In case you didn’t know, you can send a YouTube URL to Kodi by sharing it from your phone to the Kore app.

So you can do your browsing on your phone/tablet and when you want to watch something on the big screen, you just share it with the Kore app and it will start playing.

Did you ever get checked for sleep apnea or similar conditions?

One of the symptoms is waking up and feeling like a bulldozer just ran you over.

I’m on AMD but I already play in HDR without gamescope with Proton-Tkg (Wine master).

For games I then only have to set DISPLAY= ENABLE_HDR_WSI=1 %command%.

The HDR layer is here: https://github.com/Zamundaaa/VK_hdr_layer

It should not be needed anymore pretty soon.

My tip is to play the game until you find it fun, while developing it.

That’s a good tip, if your testing sessions get longer and longer because playing the game is fun you’re on the right track.

Hunt works perfectly fine on Linux, played a few rounds yesterday.

Tarkov still does not.

Also works well for the opposite use case.

I’m a good programmer but bad at math and can never remember which algorithms to use so I just ask it how to solve problem X or calculate Y and it gives me a list of algorithms which would make sense.

So what’s the big fuggin’ problem here? That Intel won’t use the term “recall”?

Would you say the same thing about a car?

“We know the door might fall off but it has not fallen off yet so we are good.”

The chances of that door hurting someone are low and yet we still replace all of them because it’s the right thing to do.

These processors might fail any minute and you have no way of knowing. There’s people who depend on these for work and systems that are running essential services. Even worse, they might fail silently and corrupt something in the process or cause unecessary debugging effort.

If I were running those processors in a company I would expect Intel to replace every single one of them at their cost, before they fail or show signs of failing.

Those things are supposed to be reliable, not a liability.

Sodium-based batteries currently have a lower energy density than lithium-based batteries so they are only useful in some applications.

The RFC you linked recommends that no new X- prefixed headers should be used.

The paragraph you quoted does not say you should use the X- prefix, only comments on how it was used.

See section 3 for the creation of new parameters: https://datatracker.ietf.org/doc/html/rfc6648#section-3

I still work on software that extendively uses X- headers.

I wouldn’t worry too much about it. The reason they give is mostly that it is annoying if a X- header suddenly becomes standardized and you end up having to support X-Something and Something. Most likely a non-issue with real custom headers.

We don’t have many unit tests that test against live APIs, most use mock APIs for testing.

The only use for this header would be if somebody sees it during development, at which point it would already be in the documentation or if you explicitly add a feature to look if the header is present. Which I don’t see happening any time soon since we get mailed about deprecations as well.

I don’t really get the purpose of a header like this, who is supposed to check it? It’s not like developers casually check the headers returned by an API every week.

Write them a mail if you see deprecated functions being used by a certain API key, probably much more likely to reach somebody that way.

Also, TIL that the IETF deprecated the X- prefix more than 10 years ago. Seems like that one didn’t pan out.

My first sentence when I get connected to a chat bot is always “Let me speak to a human”.

Yes, because Docker becomes significantly more powerful once every container has a different publicly addressable IP.

Altough IPv6 support in Docker is still lacking in some areas right now, so add that to the long list of IPv6 migration todos.

There is this notion that IPv6 exposes any host directly to the internet, which is not correct. When the client IP is attacked “directly” the attacker still talks to the router responsible for your network first and foremost.

While a misconfiguration on the router is possible, the same is possible on IPv4. In fact, it’s even a “feature” in many consumer routers called “DMZ host”, which exposes all ports to a single host. Which is obviously a security nightmare in both IPv4 and IPv6.

Just as CGNAT is a thing on IPv4, you can have as many firewalls behind one another as you want. Just because the target IP always is the same does not mean it suddenly is less secure than if the IP gets “NATted” 4 times between routers. It actually makes errors more likely because diagnosing and configuring is much harder in that environment.

Unless you’re aggressively rotating through your v6 address space, you’ve now given advertisers and data brokers a pretty accurate unique identifier of you. A much more prevalent “attack” vector.

That is what the privacy extension was created for, with it enabled it rotates IP addresses pretty regularily, there are much better ways to keep track of users than their IP addresses. Many implementations of the privacy extension still have lots of issues with times that are too long or with it not even enabled by default.

Hopefully that will get better when IPv6 becomes the default after the heat death of the universe.