worewood

There was a recent vulnerability, where researchers were able to extract information from an encrypted chat session from an LLM, by analyzing packet size/timings of the underlying SSL connection. A classic side-channel attack. Seems possible to draw a parallel between the two.

A badly programmed Kalman filter perhaps

They could've blocked just the comments, allowing at least read-only access to the site, instead of blocking it off entirely

If you run emulated Windows 98 in the browser with e.g. v86, it is faster to open the start menu on the emulated Windows 98 than on the real Windows 11 running it. Windows user experience really went downhill after 7.

The entire text reads like multiple AI-produced excerpts glued together

In that case you issue a recall, which is the correct way of dealing with potentially fatal manufacturing defects.

I think users wouldn't be so resistant to security updates of they were just that and not bundled with feature removal, unwanted new features, and other things.

Or if they were properly done. Example: Intel and the plundervolt vulnerability. To fix that they removed the ability for undervolting in ny laptop. If I don't use SGX there's no reason for the block. They could've restricted undervolting only when SGX is enabled but no, they had to "fix" it in the worst way possible.

Maybe just re-tuning the timing, if he's using high performance sticks. Because parts are hard to get by where I live, I usually stick 10+ years with a PC. With usage I found that I have to relax the timings a bit after some years.

Encrypted Client Hello and DNS over HTTPS.

My experience with academia is that most of this hard work is done by undergrads, and conception and management by professors; developers aren't hired to do this. So besides "going back to school", there's no way in for an outsider.

Except that driving at a speed significantly different from the surrounding traffic increases the risk of a crash.

There is a tension, but it's between paying enough to developers to actually produce decent code or pay a 3rd-party to firewall the application.

environmental "awareness" doesn't mean dog poo; environment-friendly will only be prioritized when it's cheaper to do so. That's why government subsidies and taxing are REQUIRED.

The western world should have subsidized it too, now you can't dismiss it because it wasn't organic--because it NEVER would be organic.

That's why environmental "awareness" doesn't mean dog poo; environment-friendly will only be prioritized when it's cheaper to do so. That's why government subsidies and taxing are REQUIRED for the switch to more environmentally friendly alternatives--this applies to everything, from fossil fuels to packaging.

I agree. That documentation really needs some love. But if you see the discussions on github issues about quadlet features a common theme is maintainers dismissing requests because "that shouldn't be done in production" or "that won't scale". It seems they can't wrap their head around people wanting to do simple things or someone doing things by themselves at home and not for work at a big company or corporation, and that reflects on that documentation.

Working for one myself, which does have a support contract wit Red Hat, I kinda get where they're coming from--if they make it easy to shoot yourself in the foot, dumb people shoot themselves in the foot in production and they have to fix the mess later. But for that they could have a sanctioned build for clients and a community build for everybody else, just like they have Fedora and RHEL.

Running a very similar setup here, also have issues with networking. Pasta worked, but has bugs and replied UDP packets on the wrong ports. The pasta version from debian packages is too old. Also, I tried making the networking work but now I just slap --network=host on everything and call it a day--works perfectly.

Case in point: .NET's garbage collector which is a single 54k loc C++ file.

I think an alternative to local root certs would be to use a public cert + dnsmasq on your LAN to resolve the requests to a local address.

The "a guy texting while driving is gonna rear end someone, sue him and actually win" type.

Seamonkey needs more love. The best one for me, does not try to be "modern" - keeps the interface unchanged and only updates real functionality.

Only 5th and 6th to be believed. Every time a manufacturer says vague descriptions like "security" or "performance" fixes, be wary - they probably removing perfectly working functionality for "reasons".

If it was something that really added value to the user they would mention it specifically (like on the 5th and 6th items).

I have a Dell laptop that mentioned such vague "improvements". After updating the firmware I couldn't undervolt anymore. Luckily I was able to downgrade.

It sounds bad, but the alternative is policy makers making decisions out of their arses, so maybe this really is a tool that can improve public management.

Problem is that the owner of the AI service has power over the model and thus can influence government decisions.

Maybe we should require that government use of AI should be required to use open models only.

Besides what others said, realistically, the effort to support N versions is not O(n). I think it's something like O(log n), because code will largely be shared between versions - you're not doing a rewrite every release.

Looks similar to what was Boeing and McDonnell Douglas. They even said McDonnell bought Boeing with Boeing's money. Looks like CA bought Broadcom with Broadcom's money

It probably has a heuristic for it

It's because this is standard practice since the early days - there's nothing newsworthy in this at all.

Good. Shows that engineering is on the driver seat, not marketing.

My 1070 is currently running with tape covering half of the PCIe pins so it works on x8 instead of x16.

One day it stopped working. During troubleshooting it would work only on a 10 year old PC I had lying around. The difference? Despite being full-size, the GPU slot on the old mobo was wired only for x8.

I reckon that the GPU die lost connection on some pins. Not worth fixing, x8 works fine.

Probably the third-party solution offers functionality not available from Microsoft, for example integrating with other management software they may have, enabling automated blue-green scheme for applying updates, so they can accurately measure the impact of updates for example.

At least in my experience, when I've heard that the "mainframe is going to die", it's specifically referencing the IBM ecosystem - COBOL and friends.

To me it looks like the author is grasping for straws when saying "well, a server rack is just like a mainframe, so the mainframe is not dying!".

To me it's the opposite: yes, a server rack is just like a mainframe. That's why the mainframe is dying - a bunch of servers can do the same work much more cheaply.