no-name-here

1. Is there no “silicon in the world” available to anyone other than frontier AI companies?

2. Which frontier AI leaders are demanding they are the only place to run inference?

Most people who don’t want to do the things you listed can/will use the big, cheap services, sure. But do you really believe that people who want to produce ‘free’ copies of licensed software, or hack, etc won’t use open models, especially as RAM supply catches up with supply? (And even more so as long as open models don’t suddenly stop improving.)

The U.S. labs may try to prevent their LLMs to be used for large-scale replicating of all software, hacking, etc, but I don’t understand the view that those things are history - I think they will become incredibly commonplace, especially if there aren’t any cross-industry standards. Do you really believe that it won’t become more commonplace over time?

It's very impractical, agreed, and even USB sticks, etc. have carried viruses.

In this scenario, is the Network-Attached Storage attached to the network (and so theoretically vulnerable)?

It seems like the only “safe” option is a PC (+storage) that never attaches to a network, but that extremely limits its usefulness.

> Anthropic really dropped the ball on signaling that this was an unofficial third party tool

Had the tool been up longer than the 11 hours the malware was live? If not, then why would Anthropic try to get it marked as unofficial, as opposed to take it down?

Or are you saying that every author and publisher should request Cursor to mark their extensions on the Cursor vsx pass-through as unofficial?

I think GP’s objection to the claim that Cursor allowing non-Anthropic to do it for 11 hours was partly “an Anthropic problem.”

Cursor explicitly claims "Before an extension is shown in search or served as a download, Cursor runs automated malware and supply-chain analysis using commercial security tooling. Extensions that fail review are blocked. Cursor also monitors extension-ecosystem threat intelligence and updates its blocklist over time."

However, the bad extension was live for ~11 hours.