AI Risk Skepticism
📖 Description
1 AI Risk Skepticism Roman V. Yampolskiy Computer Science and Engineering University of Louisville [email address redacted] Abstract In this work, we survey skepticism regarding AI risk and show parallels with other types of scientific skepticism . We start by classifying different types of AI Risk skepticism and analyze their root causes. We conclude by suggest ing some intervention approaches, which may be successful in reducing AI risk skepticism , at least amongst artificial intelligence researchers. Keywords: AI Risk, AI Risk Skeptic ism, AI Risk Denialism , AI Safety, Existential Risk . 1. Introduction to AI Risk Skepticism It has been predicted that if recent advanceme nt in machine learning continue uninterrupted , human -level or even superintelligent Artificially Intelligent (AI) systems will be designed at some point in the near future [1]. Currently available (and near -term predicted) AI software is subhuman in...
📊 Game Impacts
Not verified in gameWhich variables this event was proposed to move, and in which direction. The magnitudes are held in the corpus but are not shown here, because they have not been verified against the shipped game. They come from pdoom-data. They describe what an event was proposed to do, not what the shipped game does with it. Most events in the corpus are flavour: they are shown for colour and do not move any game variable. Only a small minority reach the systems below, and several of the variables listed here are not read by the game at all yet. Treat this table as a design proposal under review, not as a measurement of play. Corrections and arguments are welcome — the suggestion links at the foot of this page go straight to the data repo.
| Variable | Direction | Condition |
|---|---|---|
| Research | proposed: up | Always |
| Papers | proposed: up | Always |
| Vibey Doom | proposed: up | Always |
💭 Reactions
"Notable work on AI safety"
"Peer-reviewed publication"
🔗 Sources
🤝 Found an Issue?
This event data is sourced from the pdoom-data repository. If you notice errors or want to suggest improvements:
GitHub Issue (Preferred) 📧 Email (No GitHub)