nhubbard

PDFs are just absurdly complicated in general. Dumbing down the parser might be the right idea. I wonder what consequences that would have with how intertwined PostScript and PDF in general are with macOS/iOS; maybe that's why the PostScript engine was removed with macOS Sonoma/iOS 17? I don't know if that was only user facing behavior and Apple is still working to remove the internal usages.

It does let you run things as root.

I do recall that Fujitsu had a very... unique approach to exposing the Setup option in their firmware. It was just a UEFI boot entry. If that entry was removed, you couldn't get back into the firmware setup; you had to find the name of the setup EFI file and then run that from the EFI console.

What, people don't just recall those from memory? I fall asleep saying -Xmx and -Xms every night

Would love to see the source code for this and the underlying details like Classic or Carbon, and the libraries mentioned on Tinker Different for TLS, HTTP/2, and Unicode

Correct, but they stylized it as "eyePhone" (from MomCorp, the all powerful, caring conglomerate), and that episode is the origin of the famous "Shut up and take my money!" meme.

And something similar still happens if you install more than one drive in your machine with fresh Windows installations. Ugh.

I'd guess some constraint on their end related to the Zero Data Retention (ZDR) mode? Maybe the 1M context has to spill something onto disk and therefore isn't compliant with HIPAA.

That's what I figured. Some day eventually it will be possible. Until then, it's only LM Studio or Ollama as a potential hookup.

I've got some ideas inspired by this project. It's promising.

How practically could we drop in Apple Intelligence once it's using Gemini as its core for a 100% local AI agent in a box?

They did it in the 1990s and it failed so hard that it almost took down the company.

Maybe a better title would say "Asian nations [independently] roll out 4-day weeks, WFH to solve fuel crisis"?

This is the official Wikimedia Foundation status page for the whole of Wikipedia, so it's a reliable primary source.

I wouldn't be surprised either. But the original formatting of the worm makes me think it was human written, or maybe AI assisted, but not 100% AI. It has a lot of unusual stylistic choices that I don't believe an AI would intentionally output.

Wow. This worm is fascinating. It seems to do the following:

- Inject itself into the MediaWiki:Common.js page to persist globally, and into the User:Common.js page to do the same as a fallback

- Uses jQuery to hide UI elements that would reveal the infection

- Vandalizes 20 random articles with a 5000px wide image and another XSS script from basemetrika.ru

- If an admin is infected, it will use the Special:Nuke page to delete 3 random articles from the global namespace, AND use the Special:Random with action=delete to delete another 20 random articles

EDIT! The Special:Nuke is really weird. It gets a default list of articles to nuke from the search field, which could be any group of articles, and rubber-stamps nuking them. It does this three times in a row.