Unless I misunderstood, most of your comment was just another justification for preferring 1A to 1B.
It doesn’t seem to support simultaneously preferring 2B to 2A. Further, as near as I can tell, none of what you’re saying stops the vulnerability that’s opened up by having those two preferences simultaneously. I.e. the preference reversal issue is still there and still exploitable.
Haven’t followed too closely, but I think Nick’s saying that the preference reversal issue doesn’t apply and that’s OK, because as we’ve defined it now 2A is no longer the same thing as a 34% chance of 1A and a 66% chance of nothing, because in the context of what thomblake said we’re assuming you get the information at different times. (We’re assuming the 34% chance is not for your being certain now of getting 1A, but for your being certain only later of getting 1A, which breaks the symmetry.)
Unless I misunderstood, most of your comment was just another justification for preferring 1A to 1B.
It doesn’t seem to support simultaneously preferring 2B to 2A. Further, as near as I can tell, none of what you’re saying stops the vulnerability that’s opened up by having those two preferences simultaneously. I.e. the preference reversal issue is still there and still exploitable.
Haven’t followed too closely, but I think Nick’s saying that the preference reversal issue doesn’t apply and that’s OK, because as we’ve defined it now 2A is no longer the same thing as a 34% chance of 1A and a 66% chance of nothing, because in the context of what thomblake said we’re assuming you get the information at different times. (We’re assuming the 34% chance is not for your being certain now of getting 1A, but for your being certain only later of getting 1A, which breaks the symmetry.)
Yes, that’s what I meant.