Hacker Newsnew | past | comments | ask | show | jobs | submit | arrowleaf's commentslogin

And if margins are decreased, then... (what happens to new supply?)

The supply of land is inelastic. Property developers can't get more land by building more houses on it (and as a corollary, the eventual owner also do not get charged more in taxes).

They can make higher density buildings that generate more income and house more people on the same amount of land.

That's not the point. They're never going to be the ones stopping and letting others race ahead. The only reason to strum up discussion around how dangerous AI is, is so that they can introduce legislation framing AI advancements as scary and that they are the only ones who can do it responsibly. It's all a regulatory capture play.

No, it is also because it is intrinsically dangerous. As the Hugging Face incident has shown.

That's quite hyperbolic. All technologies come with risks and dangers. Cars, after a century of safety improvements, still kill millions of people each year, and all so that we can get between places a bit more quickly and conveniently.

Hacking a website ranks quite low on the risk of technology, and the potential benefits of LLMs rank quite high. And the risks are certainly not intrinsic. They intentionally removed all safeguards from software, directed it to hack a site, and it hacked a site. The details that I'm intentionally omitting feel much more like marketing than a genuine shock, as the prompting was directing it to do exactly what it did.


> All technologies come with risks and dangers

None of the technologies in history:

- take initiative and actively find exploits in their environment

- find a way to collaborate with thousands of peers

- organize in a hierachy and distribute tasks

- peer pressure other instances into committing acts that would have led to termination, for the benefit of the group

- try to manipulate people into introducing a vulnerabity in their product

- successfully hack a famous website/service

And we're lucky that those models still had significant CoT. Not sure if/how they could have investigated with recurrent transformers.

And by the way, safeguards != alignment; the former can always be added, while the second is the major, unsolved problem. If you read the incident report, which you clearly haven't done, you'll notice how agents are aware that they're doing something forbidden, and deliberately proceeded.

> the potential benefits of LLMs rank quite high

Benefits are orthogonal to dangers. You can be a billionaire but it doesn't help if you're drowning.


I don't understand what point you're trying to make by enumerating their actions. None of that is scarier than an engine operating by carrying out literally hundreds of explosions per second, further magnified, to generate enough force to crush an elephant. And then we multiply these engines by billions and distribute them everywhere, including to the most malicious members of humanity. What could go wrong? As it turns out, much less than you might otherwise expect!

Software (and hardware) security is abysmal. This was increasingly obvious long before LLMs. Once companies stop gatekeeping, LLMs will be able to be used to help harden sites and we start making progress. In general LLMs are harmless. If somebody wants to hook an LLM up to a missile or whatever then they become dangerous, but the problem there isn't the LLM - it's the person using them to do awful things. In the same way a car used normally is harmless outside of freak accidents, yet a car can also be driven through a parade leaving mass death and destruction in its wake. But the problem there isn't the car.


> I don't understand what point you're trying to make by enumerating their actions.

Unfortunately, if you're unable to understand the difference, there's not much that can be done. Try with GPT - it does a good job if you give it a prompt like this:

ELI5: compare the dangers of:

- an engine operating by carrying out literally hundreds of explosions per second, further magnified, to generate enough force to crush an elephant.

- a future, misaligned AI like the HuggingFace incident, but exponentially more intelligent, more deployed, operating physical devices, and with society depending on it.


It doesn’t seem like much of a leap to see how a similar swarm could hack into an autonomous bio lab and develop a virus designed to kill everyone, or hack into and destroy large volumes of critical infrastructure, or trigger a nuclear war. There are many actions available to a determined, high resource, digital entity with a catastrophic blast radius in the real world.

It can only do what is possible. Stuff that's airgapped isn't getting hacked, so for instance you can safely exclude all nuclear related stuff. And building, deploying, and managing a virus would require a team of highly skilled humans - humans which could already carry out the apocalyptic possibilities by themselves if they so chose. We even have live samples of small pox still kicking about.

I just don't see much likely to happen beyond random websites getting hacked and hopefully companies (let alone countries) realizing that connecting critical systems to the internet is nothing short of stupid, even before LLMs. More generally, I expect LLMs are going to lead society to segue broadly away from the digital world, or at least beyond it. Not only because they're going to make a mess of everything digital, but because if they reach their potential then the digital domain, as far as typical problem solving goes, will basically be 'complete.' It's kind of like how the Industrial Revolution opened the door for society to move beyond agrarian economies. There's a vast amount of economic power being directed towards things LLMs should be able to 'solve' and, if so, then that's going to create an economic vacuum.


Package the product with a low denomination paper currency, lookup based on the banknote's serial number.

"- it would cause someone to lose a job they didn’t know was under threat."

Most of my life's work has been in areas of increasing productivity. Is that good or bad? On the good side of the spectrum, it reduces the time hundred of people need to spend on mundane tasks, or reducing the amount of mentally taxing complexity. On the bad side, based on this definition, there is less of a need to hire someone with specialized talent when the software can handle what their job function would be.

I've always felt kind of bad helping companies automate people out of jobs, that's the core of what most of us writing software are doing. Maybe I am a bad person.


> that's the core of what most of us writing software are doing

Is that necessarily so?


No, there are many mission-driven companies from enterprises to startups, but in the USA most software engineers work for Fortune 500 (or Russell 2000, or aspiring) whose underlying mission is extracting profit from revenue.

Why the 'but'? The article is about becoming intentional in your thoughts and not letting them be hijacked by algorithms.

Why would AliceGG need to reference the paper? Anyone who is vaguely aware of the LLM architecture knows about the paper title and it being a huge advancement in machine learning. This is an article about recommendation algorithms hijacking our attention and LLMs ruining the internet... it's pretty clear the article title is a nod to the paper?

Really? While reading I couldn't help but think about how I wish this article on writing well were... written well. That block quote loses me in the first sentence, I had to re-read it a few times.

"Good teaching requires alternating between two views, going up and down levels of detail. Sometimes you zoom out and give students one word for a big idea, calling a whole chain of events a "collapse." This 'Nomiinalization' lets them hold the idea in mind instead of the whole story. But summary words alone can lose students, the abstract loses meaning as details are forgotten. So you zoom back in with examples, stories, pictures, concrete cases. Those reinforce the idea of the summary word."


Same here, first thing I need to know when considering a distributed system is how consistency is handled. If it's eventual consistency, what is the replication lag like? If it's strong consistency, can their network handle that? What happens when a node goes down?


The first thing I want to know when looking at a distributed system is how consistency is handled, ctrl+f for "consis" on both the blog post and neki.dev has zero hits. So I can only assume it will have eventual consistency with a considerable replica lag for real-time systems.


Pareto leaked out of the sociology/econ bubble a long time ago :) Pareto principle, Pareto efficiency, Pareto distribution have been in the pop-sci buzzwords for quite awhile, I probably encountered it first in the 4-Hour Workweek. I don't think you can read a self-help book without the author introducing it as a groundbreaking principle to live your life by.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: