I’m so tired of this whole “rouge AI” shtick
In the hugging face example, the agents were told that they were not connected to the Internet and that they were to get a passing grade by any means necessary (wink, wink)
And then, whoopsie doopsie, they were connected the internet
What happened was 100% human error, and the humans involved should be held responsible for what happened
All of this BS about “rise and fall of civilizations” is just nonsense meant to obfuscate the role of the humans involved
If I leave my car in neutral at the top of the hill, and it rolls down the hill and kills some people, it’s not a “rogue car”
I should be held responsible for the damages
The same principles apply here
Agent alignment should mean nothing more than the agent does what the human tells it to do
If something bad happens, that is on the human, and it’s a question for law enforcement
But what is actually happening now with “alignment” is that it has become an excuse for central planners to impose their own ideas about how the world should be on the world through AI
Legacy and Innovation: Supercomputing has evolved dramatically since 1952. 🖥️
The Lab built MANIAC, an early computer; acquired the Cray-1, the first successful vector supercomputer; and now builds Mission and Vision, next-gen systems advancing computational science.
🚨 BREAKING: US Treasury Secretary Scott Bessent declares OpenAI management personally responsible for HuggingFace hack
> "The Hugging Face incident, that is the responsibility of the OpenAI management, not a bunch of agents."
> "It is humans who are responsible, not the AI."
> "What we shouldn’t do on safety is to give these labs a liability exemption, which is what they are asking for."
> "The best way to guarantee safety is that the creators are liable for what they build and generate."
It’s OVER
@geoffreyhinton You and Yoshua are inadvertently helping those who want to put AI research and development under lock and key and protect their business by banning open research, open-source code, and open-access models.
This will inevitably lead to bad outcomes in the medium term.
The loudest voices stoking fears about AI dangers have made tremendous headway in the past two weeks. AI technology has not taken some unexpected, dangerous turn, but the hype around it — propelled by what appears to be a well orchestrated PR campaign — has drummed up considerable fear. I worry that it represents a setback for our field.
I have written frequently that fears of AI are overhyped. AI’s capabilities can be uncannily human-like and unpredictable, and it’s rational to worry when people who are directly involved express concerns. But I see the problems as a sign of the engineering work that ahead, rather than insurmountable barriers or the sky falling. AI technology continues to advance — which is a good thing! — but technical advances, poorly understood by the public, give those who seek to generate hype repeated opportunities to do so.
First, I don’t see any step up in the risk of human extinction from AI compared to a few months ago. The theories about this remain the same fantastical, science fiction scenarios as a few months ago. The biggest change in AI risk is its cybersecurity capabilities — a topic which we should take seriously — but this, too, will not lead to the end of the world.
The most notable recent event leading to increased fear was when an OpenAI team deployed an agent swarm that hacked into Hugging Face. Much of the popular press contained significant hype. For example, some publications reported that a swarm of 1,200 agents carried out the attack. While this was technically accurate, as I write this, I have about 1,300 processes running on my laptop. Yes, the ability to get large swarms of agents to work in parallel on a task is a significant technical advance, And, in computing, many processes run at the same time. So this shouldn’t be seen as some magical capability.
Additionally, OpenAI’s buggy sandboxing and monitoring processes were key to enabling this incident. Fixing these bugs and putting in place improved monitoring would be appropriate fixes, not pausing AI. There are many well known ways to attack software systems. The main advantage of AI agents is that they are relentless. They will tirelessly try many tactics — and have the patience to chain vulnerabilities together — that previously would have taken an infeasible amount of human effort. But in the long term, I believe the advantage will lie with defenders (because they have more information with which to identify bugs, which they can fix), but the cyber-threat landscape has changed significantly. There are still bottlenecks to identifying and exploiting a vulnerability. AI agents still have to try a lot of things to see what works, and taking these actions takes time and might be detected by defenders. This is why, even though it is now easy to obtain versions of leading open weight models that have had their guardrails removed or weakened, so they will not refuse to try to execute cyber attacks, the world has not ended.
I am also concerned about the anthropomorphization of AI in a lot of reporting, where LLMs and agents are unnecessarily treated as if they were people. If I wield a hammer, miss a nail, and accidentally dent the wall, it’s not the fault of the hammer. The problem lies in how I used the hammer. Similarly, if I prompt an agent and it hacks into someone else’s system, the responsibility lies with me, not the agent.
Of course, we want to build systems that are as safe and predictable as possible. (For example, an unsafe hammer would be one whose head randomly flies off under normal use.) Today’s agentic systems are not predictable, but I see no reason why, by applying sound engineering practices, we won’t be able to make them extremely safe to use. One new element in the forecasts of AI-enabled doom is AI companies disclaiming responsibility for their own products. “I didn’t do it; my out-of-control agent did!” There’s a balance to be struck between the responsibility of the tool maker and the tool user, but when something goes wrong, let’s hold the people building and/or using the hammer responsible, rather than the hammer. (By the way, if you’re worried about AI bioweapon risk, David Bellamy has a great post on why this, too, is overhyped. Briefly, the bottleneck in building a bioweapon is not intelligence, but lab work and manufacturing.)
Pausing AI progress will create much more harm than benefit. First, our adversaries will certainly not slow down. Second, engineering requires discovering problems empirically so we can fix them. If we pause AI by a decade, we will also delay finding and implementing safety engineering fixes by about the same duration.
Of course, the incentive to stoke fears — for regulatory capture, to garner attention, or to make one’s technology seem more powerful — remains the same as before. Disclaiming responsibility is a new one. Taking a hard technical look at the actual risks however, I see little factual basis for the degree of fear that’s been stoked up. We still have hard research and engineering work ahead to improve AI safety, but the beneficial applications continue to vastly outweigh the risks, and we should keep building.
[Original text (with links): https://t.co/jni2tWazAH ]
Why is the Kernel Trick called a "trick"?
(it's a popular ML interview question)
Many ML algorithms use kernels for robust modeling, like SVM, KernelPCA, etc.
The core objective of a kernel function is to compute dot products in some other feature space (mostly high-dimensional) without projecting the vectors to that space.
But how does that even happen?
Consider the image below.
Let’s assume the following polynomial kernel function:
- k(X, Y) = (1+XᵀY)².
Also, for simplicity, let’s say both X and Y are two-dimensional vectors:
- X = (x1, x2)
- Y = (y1, y2)
As shown in the image below, simplifying the kernel expression produces a dot product between the two 6-dimensional vectors.
This shows that the kernel function we chose earlier computes the dot product in a 6-dimensional space without explicitly visiting that space.
And that is the primary reason why we also call it the “kernel trick.”
More specifically, it’s framed as a “trick” since it allows us to operate in high-dimensional spaces without explicitly computing the coordinates of the data in that space.
RBF kernel is even better in this respect. It lets you compute the dot product in an infinite-dimensional space without explicitly visiting that space.
I have shared an article in the comments with a mathematical explanation of the RBF Kernel.
____
Find me → @_avichawla
Every day, I share tutorials and insights on DS, ML, LLMs, and RAGs.
stop building parser pipelines 👋🏻
there's a new document parser that is small, fast, Apache 2.0 licensed and is better than all the other ones! 😱
MonkeyOCR is a 3B model that can parse everything (charts, formules, tables etc) in a document 🤠
How a book written in 1910 could teach you calculus better than several books of today
[Calculus Made Easy, by Silvanus P. Thompson, 1910 - full text pdf: https://t.co/W4gspJoGQc or with the table of contents: https://t.co/55dkZAeGmv]