11,359 karma · joined December 2, 2014
Blood oxygen is quickly and cheaply measured with a pulse oximeter, which shows this to be false. The primary mechanism of action of ethanol is increasing the sensitivity of some GABA receptors (similar to benzodiazepines and barbiturates). But ethanol has very complex pharmacology, which a huge number of other targets. See:
https://news.ycombinator.com/item?id=49885784
But societal collapse would save us, and international coordination is theoretically possible, so I put it only around 90%.
1. Human values are a result of our extraordinarily complex shared cultural and evolutionary history, and accordingly are not shared by any AI, or even possible for us to formally define.
2. We do not know how to impose human values on an AI (note that this isn't the same as teaching an AI to model human values; the agents in the various hacking incidents knew their actions conflicted with human values, but their own values were only to maximize their predicted reward scores).
3. Intelligence is orthogonal to values. Increasing intelligence does not naturally cause values to converge on human values.
4. Sufficiently superior intelligence allows you to impose your values on beings with inferior intelligence. This implies recursive self-improvement is a logical sub-goal of all unbounded goals.
5. Human intelligence is not close to physical limits. This implies recursive self-improvement is possible.
6. Somebody will give an AI an unbounded goal. This is already the standard (maximize reward score).
I haven't seen any convincing counterarguments to any of these. Most people claiming AI development is safe don't even address them.
Theoretically, Trump or Putin could do it by pushing the nuclear button. That will only cause around 4 billion deaths, and it's very likely to halt all AI development, so it would be a great success (infinity times as many survivors as the business as usual option).
This only works if you never give it impossible tasks. A small chance of getting away with cheating beats a 0% chance of solving something impossible. And as models get smarter, they get better at recognizing when something is impossible, while human abilities stay the same.
You can't solve this problem by rewarding refusals to solve impossible tasks, because that only incentivizes false claims of impossibility.
Either you're engaged in some large-scale testing operation and your automation already handles it, or something has gone terribly wrong and the inconvenience of the sandboxing UI is the least of your concerns.
As an example of a compromise you could make, in many games, mouse acceleration has higher skill ceiling than linear mouse control. But mouse acceleration it's harder to learn, and the possible performance improvement is only small. I disable mouse acceleration myself because I'm not aiming to win tournaments. IMO, linear mouse control should be the default.
And I do not experience any conscious effort when using a mouse. My subjective experience is I look at a target and the cursor appears there automatically. The better the hardware you're using the easier it is to achieve this.
That's an irrelevant comparison. If you booked a long flight, would you accept somebody pointlessly delaying it for an hour just because that's short compared to the duration? The correct amount of avoidable latency is zero, regardless of how much unavoidable latency there is.
It's also false; I have a good mouse, good mouse skills, and my taskbar sits against the edge of the screen giving it effectively infinite height (see Fitt's law). I can hit taskbar targets in around 300ms.
Watch some videos of top-ranking aim trainer players so see how high the human skill ceiling is for mouse control, and look at the hardware they're using.
IMO, even the clipboard metaphor is too much state. We already have the selection highlight, which has the nice benefit of being directly visible. This should be reduced to a single global selection highlight. Then copy and paste can be replaced by "duplicate highlighted selection here", eliminating the possibility of forgetting what's in the paste buffer.
1. You're editing text outside of Emacs. Your cursor remains where it was, so you insert a single character and the document scrolls back to the cursor. You can then delete that character.
2. You're editing text in Emacs. You like to pretend it's still the 1970s and off-screen cursors are some pie-in-the-sky fantasy. You solve the problem with some unspecified ELISP wizardry, which as a self-respecting Emacs user you are surely capable of.
3. You're reading a read-only document. You activate your full-text search, which every good document viewer has, and start typing the last sentence you read while it's still fresh in your memory.
That's two actions, while clicking is only one.
GTK gets this right, and Qt does not.