Omega has appeared to us inside of puzzles, games, and questions. The basic concept behind Omega is that it is (a) a perfect predictor and (b) not malevolent. The practical implications behind these points are that (a) it doesn’t make mistakes and (b) you can trust its motives in the sense that it really, honestly doesn’t care about you. This bugger is True Neutral and is good at it.
(a) is correct.
(b) does not apply, in many cases Omega is a benefactor, but can be used in scenarios where Omega causes a net harm. The important point is that Omega is perfectly honest, the rules of the scenario are exactly what Omega says they are.
For the sake of the point in the article, claiming that Omega is not malevolent cleans up annoying, irrelevant questions. Any application of this point would only apply to non-malevolent Omegas, sure, but I am happy with that. Once we deal with the non-malevolent Omegas we can take care of the malevolent ones.
In other words, I am not trying to strictly define Omega. I am trying to find a stepping stone to solving non-malevolent Omega problems.
The reason I stated it the way I did in the article is because most of the articles using Omega include some such clause. Solving end cases helps solve all cases.
You are missing the point of Omega, which is to factor out considerations of uncertainty. Omega is a perfect predictor so that we can be certain that its predictions are accurate. Omega is perfectly honest, and explains the rules of the scenario, so that we can be certain of the rules.
We don’t have to worry about Omega’s motivations at all, because, in a proper Omega scenario, Omega’s actions in repsonse to every possible state of the scenario is exactly specified.
We don’t have to worry about Omega’s motivations at all, because, in a proper Omega scenario, Omega’s actions in repsonse to every possible state of the scenario is exactly specified.
Right. I used the term “not malevolent” for this. What term would you have used?
(a) is correct. (b) does not apply, in many cases Omega is a benefactor, but can be used in scenarios where Omega causes a net harm. The important point is that Omega is perfectly honest, the rules of the scenario are exactly what Omega says they are.
Omega is not malevolent in that it isn’t out to get you. Not malevolent is different than benevolent.
Sometimes, Omega is malevolent.
For the sake of the point in the article, claiming that Omega is not malevolent cleans up annoying, irrelevant questions. Any application of this point would only apply to non-malevolent Omegas, sure, but I am happy with that. Once we deal with the non-malevolent Omegas we can take care of the malevolent ones.
In other words, I am not trying to strictly define Omega. I am trying to find a stepping stone to solving non-malevolent Omega problems.
The reason I stated it the way I did in the article is because most of the articles using Omega include some such clause. Solving end cases helps solve all cases.
You are missing the point of Omega, which is to factor out considerations of uncertainty. Omega is a perfect predictor so that we can be certain that its predictions are accurate. Omega is perfectly honest, and explains the rules of the scenario, so that we can be certain of the rules.
We don’t have to worry about Omega’s motivations at all, because, in a proper Omega scenario, Omega’s actions in repsonse to every possible state of the scenario is exactly specified.
Right. I used the term “not malevolent” for this. What term would you have used?
“Has exactly specified behavior” would work.
Sure, that works. How about, “(b) has explicitly defined behavior.” Does that translate okay?