= 27d567bc2d48d9f40e9ccc20ea370b15)
Nick_Tarleton comments on How Not to be Stupid: Adorable Maybes - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (54)
Because there's a larger jump in expected utility between certainty (up to breach of contract, etc.) of future money and 99% than between (n < 100)% and (n-1)%. However, this means that the outcome of 1A and the winning outcome of 2A are no longer the same (both involve obtaining money at time t_1, but 1A also includes obtaining, at t_0, certainty of future money), and choosing 1A and 2B becomes unproblematic.
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.