Its basically like a cloud storage, and your local storage (your brain) gets wiped every loop. You can edit this file any time you want using your brain (you can be tied up and it still works). 1024 Bytes is all you get. Yes you read that right: BYTES, not KB, MB, or GB: 1024 BYTES

Lets just say, for this example: The loop is 7 days form a Monday 6 AM to the next Monday 5:59 AM.

How do you best use these 1024 Bytes to your advantage?

How would your strategy be different if every human on Earth also gets the same 1024 Bytes “memory buffer”?

  • FaceDeer@fedia.io
    link
    fedilink
    arrow-up
    7
    ·
    2 days ago

    If it’s just me; I’d increment it by one at the start of each loop. That is, I’d increment the underlying 8192-bit number that the 1024 bytes represents. On some loops this will form a coherent ASCII text, on most it’ll be gibberish. But I have infinite retries and it doesn’t bother me how many loops I go through. So there will be 2^8192 “initial states” it’s in, or about 10^2467 different states in base ten. If anything is going to get me out of that time loop then I’ll hit on it eventually.

    If I see that the integer is maxed out, I think I won’t overflow it back to 0 again. The whole point of this is to avoid trying exactly the same thing over and over again indefinitely. I think I’d have to resort to a leap of faith - that quantum effects are still random. I’d go to random.org and generate something bigger than 1024 bytes to use as “inspiration” instead. Maybe a megabyte? It’d have to be a lot bigger to be on the safe side, since this is the last resort.

    • Unbecredible@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 days ago

      I think I’d have to resort to a leap of faith - that quantum effects are still random.

      My brother in Christ, at the point at which you’re incrementing incomprehensibly large numbers and hoping one of them decodes into ASCII text that is the specific answer to your problems…you have already taken the leap, fallen, impacted with the earth, and died.

      RIP.

      • FaceDeer@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        I’m not hoping, I know that every possible 1024-character ASCII text file is going to be generated over the course of all this. I’m just hoping that one of them will tell me to do something that will get me out of the loop. If I reach the end of the possible 1024-character text files without escaping, that means that either the solution takes more than 1024 characters to encode or there is no solution at all.

        It’s important to increment the count and record it for next time before I read it, just in case one of those 1024-character strings contains an argument that convinces me to do something other than that.