The ASUS logo is visible in the photo of the innards.
3,384 karma · joined October 19, 2016
Anyway, this is a disaster. It was extremely irresponsible to share the exploit with the world before the distributions shipped the fix. Who knows how many shared hosting providers were hacked with this.
It's also worrying that it seems there's no communication between the kernel security team and distribution maintainers. One would hope that the former would notify the latter, but apparently it's the responsibility of whoever finds the vulnerability.
https://access.redhat.com/security/cve/cve-2026-31431 "Moderate severity", "Fix deferred"
https://security-tracker.debian.org/tracker/CVE-2026-31431
So this means that for bad actors it's more efficient to manufacture brand new fake stories instead of trying to distort the real ones. Don't produce fake articles absolving yourself of a crime, instead produce fake articles accusing your opponent of 100 different things. Then people will fact-check the accusations using LLMs, and since all the sources mentioning those accusations are controlled by you, the LLMs will confirm them.
git init --bare foo.git
git clone user@yourserver.com:~/foo.git
If you stay in the happy path, it's decent, better than it used to be. Microsoft does seem committed to it, they're slowly converting Windows apps to WinUI 3.
That said, the team is clearly understaffed; there are long-standing unresolved bugs, just search for "memory leak" on their GitHub issue tracker. Also, native, non-.NET support is definitely an afterthought, it's barely documented and the tooling is super awkward. But at least, unlike WPF, it exists.
It seems the last edit of the page was in 2019, so I'm not sure how up to date it is.
This is no longer true, a prior solution has just been found[1], so the LLM proof has been moved to the Section 2 of Terence Tao's wiki[2].
[1] - https://www.erdosproblems.com/forum/thread/281#post-3325
[2] - https://github.com/teorth/erdosproblems/wiki/AI-contribution...
It's very annoying. Put this in a search query to filter them out: -inurl:?tl=
They take a 5.5% fee whenever you buy credits. There's also a discount for opting-in to share your prompts for training.
What does "typical web image quality" even mean? I see lots of benchmarks with very low BPPs, like 0.5 or even lower, and that's where video-based image codecs shine.
However, I just visited CNN.com and these are the BPPs of the first 10 images my browser loaded: 1.40, 2.29, 1.88, 18.03 (PNG "CNN headlines" logo), 1.19, 2.01, 2.21, 2.32, 1.14, 2.45.
I believe people are underestimating the BPP values that are actually used on the web. I'm not saying that low-BPP images don't exist, but clearly it isn't hard to find examples of higher-quality images in the wild.
The open-source community, generally speaking, is a high-trust society and I'm afraid that LLM abuse may turn it into a low-trust society. The end result will be worse than the status quo for everyone involved.
I agree. At best, short videos can be entertainment that destroys your attention span. Anything more is impossible. Even if there were no bad actors producing the content, you can't condense valuable information into this format.
You can see it for yourself here (in Part 4): https://ecma-international.org/publications-and-standards/st...
Perhaps the first approved by FDA, I don't know. In many countries, metamizole is the first-line drug for postoperative pain.
(It should be noted that metamizole may very rarely cause agranulocytosis. It is suspected that the risk varies depending on the genetic makeup of the population, which would explain why it is banned in some countries but available OTC in others.)
2001: Radeon 8000 series
2013: Radeon HD 8000 series
2025: Radeon 8000S series
-inurl:?tl=But what AI brings to the table is how much easier it makes it to combine and analyse all that data, build peoples' profiles. It scales infinitely better than hiring human analysts to track someone. It's too cheap and too tempting.
Simple example: no legitimate user has "GPTBot" in their user agent string.
Not if you're targeting x86-64-v3 or higher. Haswell (Intel) and Piledriver (AMD) introduced the LZCNT instruction that doesn't have this problem.
Mirror: https://archive.ph/R39hz