did you know there's a sufficient, probably complete simulacrum of you inside a newcomb predictor? HANG ON WE'LL GET YOU OUT OF THERE
-
Show this thread
-
Replying to @allgebrah
I'm looking at the description of the Newcomb paradox & don't understand why "take box A and storm out" isn't a considered option
1 reply 0 retweets 1 like -
Replying to @mcclure111
purely formally, you could choose A+B for an at least equally good outcome
2 replies 0 retweets 0 likes -
Replying to @allgebrah @mcclure111
I was thinking though, maybe you could coax computation worth more than $1M out of the predictor
2 replies 0 retweets 1 like -
Replying to @allgebrah @mcclure111
this is hard though since the effort is symmetrical; maybe if works if the predictor classically simulates quantum decisions?
1 reply 0 retweets 0 likes -
Replying to @allgebrah
the problem I see with your proposal really is it may assume we get multiple gos to extract multiple bits
2 replies 0 retweets 0 likes -
Replying to @mcclure111
'(·) Retweeted '(·)
one bit only https://twitter.com/allgebrah/status/796846552925016064 … you could probably pull major shenanigans with more than one
'(·) added,
1 reply 0 retweets 0 likes -
Replying to @allgebrah
here is an analysis i wrote once on a related subjecthttp://ask.fm/mcclure111/answers/117203677762 …
1 reply 0 retweets 0 likes -
Replying to @mcclure111
B is also really useful in case the sidewalk is a light-year long but you need to know now
1 reply 0 retweets 1 like -
Replying to @allgebrah
hm. there is one of us on each interstellar ship; we answer the question to the navigator before everyone goes in storage
1 reply 0 retweets 1 like
exactly, it's a bit expensive for an ansible system but if you need that one bit shipped *quick*
-
-
Replying to @allgebrah @mcclure111
actually, why not make the sidewalk a light-year wide instead of long, we wouldn't have to use a navigator for each bit
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.