In response to comment by [deleted] on Morality should be Moral
Comment author: Petruchio 17 May 2013 06:22:28PM 0 points [-]

A green sky will be green. A pink invisible unicorn is pink. A moral system would be moral. All tautologies, none are true.

Comment author: benelliott 18 May 2013 09:57:59AM -1 points [-]

A green sky will be green

This is true

A pink invisible unicorn is pink

This is a meaningless sequence of squiggles on my computer screen, not a tautology

A moral system would be moral

I'm unsure what this one means

Comment author: ArisKatsaris 17 May 2013 02:58:43PM 3 points [-]

I still wonder, however, if there is any possible rational reason to not choose to sacrifice oneself in the scenario.

Of course there is -- e.g. if you care more for yourself than for other people, rationality doesn't compel you to sacrifice even a cent of your money, let alone you life, for the sake of others.

People must REALLY REALLY stop confusing what is "rational" and what is "moral". Rationality says nothing about what you value, only about how to achieve it.

They must also stop confusing "should" "would" and "I would prefer to".

Comment author: benelliott 17 May 2013 05:59:43PM 0 points [-]

I'm not sure what 'should' means if it doesn't somehow cash out as preference.

Comment author: Petruchio 17 May 2013 01:17:47PM 2 points [-]

Myself, I am not a utilitarian, but a deontologist. I would flip the switch, because I have been given the choice to choose between two different losses, inescapably, and I would try to minimize this loss. As for pushing someone else in front of the trolley, I could not abide someone doing that to me or a loved one, throwing us from relative safety into absolute disaster. So I would not do it to another. It is not my sacrifice to make.

As for throwing myself in front of the trolley...

I would want to. In the calm state I am in right now, I would do it. In the moment, there is a more than probable chance that fear will take hold and I would not sacrifice myself for five others. But in this scenario, I would probably be too stressed to think to throw another person into a train, let alone myself. So if we are taking the effects of stress out of my cognitive calculations, I will take the effects of stress out of my moral calculations.

I would do it.

Comment author: benelliott 17 May 2013 05:56:36PM 2 points [-]

I could not abide someone doing that to me or a loved one, throwing us from relative safety into absolute disaster. So I would not do it to another. It is not my sacrifice to make.

I could not abide myself or a loved one being killed on the track. What makes their lives so much less important.

Comment author: ArisKatsaris 09 May 2013 09:25:37PM 2 points [-]

only this time when we update on the mugger telling the truth, we radically change our estimate of the number of people who were 'in the lottery', all the way up to 3^^^^3. We then multiply 1/3^^^^3 by the probability that we live in a universe where Pascal's muggings occur

How does this work with Clippy (the only paperclipper in known existence) being tempted with 3^^^^3 paperclips?

That's part of why I dislike Robin Hanson's original solution. That the tempting/blackmailing offer involves 3^^^^3 other people, and that you are also a person should be merely incidental to one particular illustration of the problem of Pascal's Mugging -- and as such it can't be part of a solution to the core problem.

To replace this with something like "causal nodes", as Eliezer mentions, might perhaps solve the problem. But I wish that we started talking about Clippy and his paperclips instead, so that the original illustration of the problem which involves incidental symmetries doesn't mislead us into a "solution" overreliant on symmetries.

Comment author: benelliott 09 May 2013 11:16:30PM 0 points [-]

How does this work with Clippy (the only paperclipper in known existence) being tempted with 3^^^^3 paperclips?

First thought, I'm not at all sure that it does. Pascal's mugging may still be a problem. This doesn't seem to contradict what I said about the leverage penalty being the only correct approach, rather than a 'fix' of some kind, in the first case. Worryingly, if you are correct it may also not be a 'fix' in the sense of not actually fixing anything.

I notice I'm currently confused about whether the 'causal nodes' patch is justified by the same argument. I will think about it and hopefully find an answer.

Comment author: benelliott 09 May 2013 09:13:25PM 1 point [-]

Random thoughts here, not highly confident in their correctness.

Why is the leverage penalty seen as something that needs to be added, isn't it just the obviously correct way to do probability.

Suppose I want to calculate the probability that a race of aliens will descend from the skies and randomly declare me Overlord of Earth some time in the next year. To do this, I naturally go to Delphi to talk to the Oracle of Perfect Priors, and she tells me that the chance of aliens descending from the skies and declaring an Overlord of Earth in the next year is 0.0000007%.

If I then declare this to be my probability of become Overlord of Earth in an alien-backed coup, this is obviously wrong. Clearly I should multiply it by the probability that the aliens pick me, given that the aliens are doing this. There are about 7-billion people on earth, and updating on the existence of Overlord Declaring aliens doesn't have much effect on that estimate, so my probability of being picked is about 1 in 7 billion, meaning my probability of being overlorded is about 0.0000000000000001%. Taking the former estimate rather than the latter is simply wrong.

Pascal's mugging is a similar situation, only this time when we update on the mugger telling the truth, we radically change our estimate of the number of people who were 'in the lottery', all the way up to 3^^^^3. We then multiply 1/3^^^^3 by the probability that we live in a universe where Pascal's muggings occur (which should be very small but not super-exponentially small). This gives you the leverage penalty straight away, no need to think about Tegmark multiverses. We were simply mistaken to not include it in the first place.

Comment author: 9eB1 07 May 2013 02:34:54PM 1 point [-]

I agree with your analysis regarding the difference between systematic naming systems and merely similar naming. That said, the justification for more clearly separating Pascal's mugging and this other unnamed situation does strike me as a political decision or rationalization. If the real world impact of people's misunderstanding were beneficial for the AI friendly cause, I doubt if anyone here would be making much ado about it. I would be in favor of renaming moissanite to diamand if this would help avert our ongoing malinvestment in clear glittery rocks to the tune of billions of dollars and numerous lives, so political reasons can perhaps be justified in some situations.

Comment author: benelliott 07 May 2013 03:42:26PM -1 points [-]

I would agree that it is to some extent political. I don't think its very dark artsy though, because it seems to be a case of getting rid of an anti-FAI misunderstanding rather than creating a pro-FAI misunderstanding.

Comment author: DSimon 07 May 2013 12:28:51AM 1 point [-]

Hm, that's a good point, I've changed my opinion about this case.

When I wrote my comment, I was thinking primarily of words that share a common prefix or suffix, which tends to imply that they refer to things that share the same category but are not the same thing. "English" and "Spanish", for example.

But yeah, "diyer" is too close to "die" to be easily distinguishable. Maybe "rubemond"?

Comment author: benelliott 07 May 2013 09:00:25AM 0 points [-]

But yeah, "diyer" is too close to "die" to be easily distinguishable. Maybe "rubemond"?

I could see the argument for that, provided we also had saphmonds, emmonds etc... Otherwise you run the risk of claiming a special connection that doesn't exist.

Comment author: 9eB1 06 May 2013 06:34:26PM 3 points [-]

Chemistry would not be improved by providing completely different names to chlorate and perchlorate (e.g. chlorate and sneblobs). Also, I think English might be better if rubies were called diyermands. If all of the gemstones were named something that followed a scheme similar to diamonds, that might be an improvement.

Comment author: benelliott 07 May 2013 12:10:39AM 0 points [-]

Chemistry would not be improved by providing completely different names to chlorate and perchlorate (e.g. chlorate and sneblobs).

Okay, thats actually a good example. This caused me to re-think my position. After thinking, I'm still not sure that the analogy is actually valid though.

In chemistry, we have a systemic naming scheme. Systematic name schemes are good, because they let us guess word meanings without having to learn them. In a difficult field which most people learn only as adults if at all, this is a very good thing. I'm no chemist, but if I had to guess the words chlorate and perchlorate to cause confusion sometimes, but that this price is overall worth paying for a systemic naming scheme.

For gemstones, we do not currently have a systematic naming scheme. I'm not entirely sure that bringing one in would be good, there aren't all that many common gemstones that we're likely to forget them and frankly if it ain't broke don't fix it, but I'm not sure it would be bad either.

What would not be good would be to simply rename rubies to diyermands without changing anything else. This would not only result in misunderstandings, but generate the false impression that rubies and diamonds have something special in common as distinct from Sapphires and Emeralds (I apologise for my ignorance if this is in fact the case).

But at least in the case of gemstones we do not already have a serious problem, I do not know of any major epistemic failures floating around to do with the diamond-ruby distinction.

In the case of Pascal's mugging, we have a complete epistemic disaster, a very specific very useful term have been turned into a useless bloated red-giant word, laden with piles of negative connotations and no actual meaning beyond 'offer of lots of utility that I need an excuse to ignore'.

I know of almost nobody who has serious problems noticing the similarities between these situations, but tons of people seem not to realise there are any differences. The priority with terminology must be to separate the meanings and make it absolutely clear that these are not the same thing and need not be treated in the same way. Giving them similar names is nearly the worst thing that could be done, second only to leaving the situation as it is.

If you were to propose a systematic terminology for decision-theoretric dilemmas, that would be a different matter. I think I would disagree with you, the field is young and we don't have a good enough picture of the space of possible problems, a systemic scheme risks reducing our ability to think beyond it.

But that is not what is being suggested, what is being suggested is creating an ad-hoc confusion generator by making deliberately similar terms for different situations.

This might all be rationalisation, but thats my best guess for why the situations feel different to me.

Comment author: DSimon 06 May 2013 04:27:26PM -1 points [-]

Would the English language really be better if rubies were called diyermands?

I suspect it would be. The first time one encounters the word "ruby", you have only context to go off of. But if the word sounded like "diamond", then you could also make a tentative guess that the referent is also similar.

Comment author: benelliott 06 May 2013 11:48:56PM *  1 point [-]

Do you really think this!? I admit to being extremely surprised to find anyone saying this.

If rubies were called diyermands it seems to me that people wouldn't guess what it was when they heard it, they would simply guess that they had misheard 'diamond', especially since it would almost certainly be a context where that was plausible, most people would probably still have to have the word explained to them.

Furthermore, once we had the definition, we would be endlessly mixing them up, given that they come up in exactly the same context. Words are used many times, but only need to be learned once, so getting the former unambiguous is far more important.

The word 'ruby' exists primarily to distinguish them from things like diamonds, you can usually guess that they're not cows from context. Replacing it with diyermand causes it to fail at its main purpose.

EDIT:

To give an example from my own field, in maths we have the terms 'compact' and 'sequentially compact' for types of topological space. The meanings are similar but not the same, you can find spaces satisfying one but not the other, but most 'nice' spaces have both or neither.

If your theory is correct, this situation is good, because it will allow people to form a plausible guess at what 'compact' means if they already know 'sequentially compact' (this is almost always they order a student meets them). Indeed, they do always form a plausible guess, and that guess is 'the two terms mean the same thing'. This guess seems so plausible, they never question it and go off believing the wrong thing. In my case this lasted about 6 months before someone undeluded me, even when I learned the real definition of compactness, I assumed they were provably equivalent.

Had their names been totally different, I would have actually asked what it meant when I first heard it, and would never have had any misunderstandings, and several others I know would have avoided them as well. This seems unambiguously better.

Comment author: Jiro 06 May 2013 01:05:14AM *  4 points [-]

If someone suggests to me that they have the ability to save 3^^^3 lives, and I assign this a 1/3^^^3 probability, and then they open a gap in the sky at billions to one odds, I would conclude that it is still extremely unlikely that they can save 3^^^3 lives. However, it is possible that their original statement is false and yet it would be worth giving them five dollars because they would save a billion lives. Of course, this would require further assumptions on whether people are likely to do things that they have not said they would do, but are weaker versions of things they did say they would do but are not capable of.

Also, I would assign lower probabilities when they claim they could save more people, for reasons that have nothing to do with complexity. For instance, "the more powerful a being is, the less likely he would be interested in five dollars" or :"a fraudster would wish to specify a large number to increase the chance that his fraud succeeds when used on ordinary utility maximizers, so the larger the number, the greater the comparative likelihood that the person is fraudulent".

the phrase "Pascal's Mugging" has been completely bastardized to refer to an emotional feeling of being mugged that some people apparently get when a high-stakes charitable proposition is presented to them, regardless of whether it's supposed to have a low probability.

1) Sometimes what you may actually be seeing is disagreement on whether the hypothesis has a low probability.

2) Some of the arguments against Pascal's Wager and Pascal's Mugging don't depend on the probability. For instance, Pascal's Wager has the "worshipping the wrong god" problem--what if there's a god who prefers that he not be worshipped and damns worshippers to Hell? Even if there's a 99% chance of a god existing, this is still a legitimate objection (unless you want to say there's a 99% chance specifically of one type of god).

3) In some cases, it may be technically true that there is no low probability involved but there may be some other small number that the size of the benefit is multiplied by. For instance, most people discount events that happen far in the future. A highly beneficial event that happens far in the future would have the benefit multiplied by a very small number when considering discounting.

Of course in cases 2 and 3 that is not technically Pascal's mugging by the original definition, but I would suggest the definition should be extended to include such cases. Even if not, they should at least be called something that acknowledges the similarity, like "Pascal-like muggings".

Comment author: benelliott 06 May 2013 02:49:15PM 1 point [-]

Even if not, they should at least be called something that acknowledges the similarity, like "Pascal-like muggings".

Any similarities are arguments for giving them a maximally different name to avoid confusion, not a similar one. Would the English language really be better if rubies were called diyermands?

View more: Prev | Next