News for hackers. Stuff that matters.

eddyg

Re:The SEC Should Block Anthropic's IPO to Protect the Public on Tuesday November 03, 2026 @08:05AM (#50351517)
The U.S. Census Bureau runs a Business Trends and Outlook Survey⁽¹⁾ (aka BTOS) every two weeks. It goes out to 200,000 U.S. businesses (out of 1.2 million total). One of the questions asks about AI (now SI) usage, and it's a steady climb.

⁽¹⁾ https://www.census.gov/hfp/btos/data

Thank you for jumping in to the fray and providing additional context, data and updates!
Re:TLP Is Not a Suggestion on Thursday October 29, 2026 @07:10AM (#50287216)
And worth noting, Amazon’s MadPot started detecting exploit attempts four days before disclosure⁽¹⁾, so there were other leaks long before “the video”.

⁽¹⁾ https://aws.amazon.com/blogs/security/amazon-threat-intellig...

You should look at Pragmata Pro⁽¹⁾.

Hand-hinted by Fabrizio: ”More than 9000 characters optimized from 9pt to 48pt to guarantee the best possible readability.”

It is the ultimate “programmer’s font” and well worth the money for something you stare at every day and the next best thing to a bitmap font in today’s “Retina resolution” world.

Accept no imitations.

⁽¹⁾ https://fsd.it/shop/fonts/pragmatapro/

Re:Keyboard differences between Windows and Macs on Friday October 09, 2026 @08:13AM (#50019391)
macOS supports emacs-like bindings natively: Ctrl-A/Ctrl-E for line start/end, Ctrl-K to kill, Ctrl-Y to yank, Ctrl-F/Ctrl-B for forward/back, etc.

They are defined in /System/Library/Frameworks/AppKit.framework/Resources/StandardKeyBinding.dict. You can create ~/Library/KeyBindings/DefaultKeyBinding.dict to augment or override those.

Anything built on AppKit that uses the standard text system (NSTextView, NSTextField, and the field editors that back them) supports those bindings “for free”.

For non-native apps, Karabiner Elements⁽¹⁾ is the answer, using a config like this⁽²⁾.

⁽¹⁾ https://karabiner-elements.pqrs.org/

⁽²⁾ https://github.com/pdelfino/karabiner-config

Reminder that if you have Apple News, you can use the sharrow from Safari (not an in-app WebView) and “share” paywalled news articles to News.app.
Re:DeepSeek v4.1 Flash Uncensored on Friday September 11, 2026 @07:58AM (#49656945)
“Available knowledge” is not “usable capability”.
Re:Ask GitHub SRE: How serious is the situation there? on Friday August 07, 2026 @07:53AM (#49209032)
For some context, GitHub COO back on April 3, 2026: https://x.com/kdaigle/status/2040164759836778878
Re:Artificial Intelligence used to design new viruses on Friday August 07, 2026 @07:28AM (#49208779)
You hope it’s “far-fetched”.

As noted in this paper⁽¹⁾, ”Publicly releasing model weights is an act of irreversible proliferation. Once weights are released, they can never be recalled.”

Do you really want to risk it on your off-the-cuff reasoning that it’s “far-fetched”?

⁽¹⁾ https://www.lesswrong.com/posts/qmQFHCgCyEEjuy5a7/lora-fine-...

Re:ASCII Today on Monday August 03, 2026 @06:56PM (#49162489)
Needs a (2020) tag. (The 2023 commit was just a Google Analytics update).

A badge of honor these days!

Re:Relaxin Jailbreak for iOS 17.0-17.3.1 Released on Wednesday July 29, 2026 @12:27PM (#49099586)
iOS 17.0 was released in September 2023, with support for the new iPhone 15 models.

iOS 17.4 was released in March 2024.

Additional updates to 17.5, 17.6 and 17.7 followed.

Any devices released after the iPhone 15 couldn't run iOS 17.

It makes me wonder how many devices exist that are still running "iOS 17.0 to 17.3.1"...

Re:TWC Classics on Tuesday July 28, 2026 @09:50AM (#49083882)
If you miss the classic WeatherStar look-and-feel from the cable days of The Weather Channel, be sure to check out https://github.com/netbymatt/ws4kp
Re:OpenAI's rogue model attack is just the beginning on Tuesday July 28, 2026 @08:55AM (#49083087)
All of which are easily bypassed in open weight models; see my previous comment about K2.5.
Re:OpenAI's rogue model attack is just the beginning on Tuesday July 28, 2026 @08:30AM (#49082826)
Classifiers are policy enforced by the process serving the model.

Input classifiers get applied before it reaches the model so somebody hacking an open-weight model would skip this. Streaming classifiers get polled during decoding; hackers delete this check in the sampling loop.

But both are always applied in closed weight models.

Set Llama Guard to 1.0 and nothing is ever unsafe.

Re:OpenAI's rogue model attack is just the beginning on Tuesday July 28, 2026 @08:00AM (#49082530)
Constitutional classifiers go a long way to reducing unsafe usage in closed-weight models. And like we saw with Fable, closed models can be revoked and classifiers updated when “jailbreaks” are found.

Having the weights gives you the exact affordance an unlearning attack requires, without rate limits.

Re:OpenAI's rogue model attack is just the beginning on Tuesday July 28, 2026 @07:36AM (#49082341)
A change in kind is not the same as a change in degree. Ten orchestrated LLM PhD advisors is a genuinely different thing from a library.
Re:OpenAI's rogue model attack is just the beginning on Tuesday July 28, 2026 @06:32AM (#49081877)
If nothing else, the article has a really good timeline of the OpenAI/HuggingFace “incident”.

But to me, it underscores the impending cliff of doom from the continued release of open-weight models: there's no cryptographic or architectural way to give someone full weights while withholding the nefarious capabilities those weights encode.

As noted in this paper⁽¹⁾, “publicly releasing weights is an act of irreversible proliferation”.

I’m sure this will be an unpopular opinion on HN, but open weights are the thing that scares me the most about “A.I.”. There is a lot of research in this area⁽²⁾, and I think most of HN is unaware of it or ignores it. Stripping refusals from Kimi K2.5 took under $500 of compute and about 10 hours, taking HarmBench refusals from 100% to 5% while retaining nearly all capability; the resulting model gave detailed chemical-weapons synthesis instructions.

The gate is only as strong as the least-cautious releaser...

⁽¹⁾ https://www.lesswrong.com/posts/qmQFHCgCyEEjuy5a7/lora-fine-...

⁽²⁾ https://arxiv.org/html/2604.03121v1

Re:"Opus 5 is a really bad model" on Tuesday July 28, 2026 @04:25AM (#49080974)
The guidelines⁽¹⁾ make it clear the OP did the correct thing: ”Please submit the original source.”

⁽¹⁾ https://news.ycombinator.com/newsguidelines.html

Re:Em dashes are fucking amazing on Friday July 24, 2026 @10:48AM (#49036523)
How do you feel about the Tironian Sign Capital Et? https://www.unicodecharacter.org/U+2E52

I mean the triple-em-dash has been around since Unicode 6.1; The Tironian Sign Capital Et wasn't added until Unicode 13.

Re:Em dashes are fucking amazing on Friday July 24, 2026 @10:21AM (#49036102)
"It is (and, increasingly, was) used to signify that a bibliography entry has the exact same author(s), editor(s), translator(s), or corporate author(s) as the previous bibliography entry."

https://danieljtortora.com/blog/3-em-dashes

What's massive is the amount of water used for a handful of almonds. Not daily AI use.

https://www.andymasley.com/visuals/ai-prompt-footprint/

This is a great data-backed resource to refute made-up claims about data centers:

https://www.andymasley.com/visuals/ai-prompt-footprint/

It’s all about the harness, not just calling the API.
Re:The lost joy of music piracy on Thursday July 16, 2026 @07:05AM (#48932894)
If you’re gonna capitalize the “D” you should also capitalize the “G” (since it’s the first letter of his last name…)
Thanks for the reply!

I went to make the change, and all the sudden it started working with “>” again (not URL encoded) so this appears to have been a transient issue.

From 27 years ago... you could almost search-and-replace "PCs" with "agents" and re-publish it today...

Dig more coal -- the PCs are coming

https://www.forbes.com/forbes/1999/0531/6311070a.html

Older »