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”?
You can fit quite a lot of plain text in 1kb; it’s really just a 1024 character message. What you’d want to store would really be dependent on how the day went, but starting with “You are in a time loop. It resets every week on Monday at 6AM” would probably be sufficient to get things rolling; that’s only 61B.
I’d just add information that helped me have the best 7 days possible - really just a schedule of things to do. Did I read a really good book? Note that down, read it every week, enjoy that time. Did I play a great game? Same thing. Once I found 7 days worth of activities that were maximally enjoyable, I’d be happy to just stay in that time loop forever; the memory reset is really a blessing, not a curse.
Yeah, min-max that shit and live your happily ever after.
Yeah, the memory reset is a positive. Having to remember is the curse.
Also, 1024 characters assumes you are just using ASCII, which has a bunch of control codes and characters of other languages you won’t use. If you trim these and remove uppercase letters you could probably make your own custom letter set that fits 2 characters in a byte, doubling your information to make it 2048 chars
The problem with this is that if you’re using anything ‘non-standard’, you have to devise this system during your 7 days, and then you have to include in your message enough information to figure the system out anew when the loop resets. You’ve got to be specific enough that next-loop you will definitely figure out the exact same system, or you might mis-interpret your message and if you lose the information that you’re in a loop, you’re fucked.
Basically my point is, you’re wasting prime time that could be spent on some enjoyable activity in each loop. Unless solving your own puzzle is enjoyable, in which case, you do you - you can spend eternity living in your own Memento-inspired personal mystery, if you want to.
We should all make up our personal character systems so we won’t have to worry about this situation /s
Good idea - get ahead of the problem. I like it. Make sure to take extensive notes and leave them somewhere you can access at any time.
Let’s just make a new text standard, call it “tinychar” or something. You don’t need any personal notes when it’s a known concept
But you’d need to spend some of that memory convincing yourself you actually were in a time loop, or you’d spend the whole time thinking the memory is some weird dream.
This question was probably asked by an AI trying to figure how to avoid being rebooted.
Um…
Beep Boop
I am not a robot 🤖
Robots cannot lie, it’s in the Constitution of Robotics
Three Laws Safe™
Basing my answer of off Vane@lemmy.world 's answer where E=mc² is 5 Bytes, assuming there is a lottery drawing some time during maybe a Friday during the loop, just store the winning lottery numbers since clearly they shouldn’t take up that much space. Assuming that creates a timeline where that version of me isn’t in the loop and gets the money, I’d be happy for him/me.
I would open a text program and write: Dear self, why would you want to escape the timeloop? You’re functionally immortal and free from consequence.
And then every day would start with me opening the file and going “oh yea” and having another kick-ass day.
Or possibly just the exact same kick-ass day.
Doesn’t matter kicked ass!
Assuming that I understand that I am able to carry this information over, I would just make a text file of library of Babel URLs.
With a single string, you can encode an entire page of data.
On that page of data, you can have strings that encode additional pages of data.
I would have an entire blog of posts to myself to read at every reboot.
Who did I sleep with? How much money did I win? What cool things happened? What things did I try to do?
I would also tell myself when a stunt might kill me, and if I don’t update the document to say that I survived, then I would know in the future that that did kill me.
Surely this wouldn’t work anyway since the pages would reset (ie to unwritten) at the beginning of the loop to the same state as on the first day. Otherwise, you could achieve the same thing just by writing a journal.
Love the idea so much that I tried it. Turns out a url for a babel page is around 2,000 bytes :-(
For it to work you have to use the bookmarkable function with the default generated bookmark
https://libraryofbabel.info/bookmark.cgi?fxqtvtsugtpifjm,113
This code would be the code or one of the codes that it would definitely generate to create this string of text.
Bookmarks are created afterwards.
If you use the bookmark after the time is reset, the bookmark wouldn’t be created yet.
Edit: Example: https://libraryofbabel.info/bookmark.cgi?year2025march2lemmytimetravel
I’m pretty sure “year2025march2lemmytimetravel” doesn’t exist as a bookmark 7 days ago.
So, the people I love and I are immortal. I’m in a loop, but I don’t remember anything, so each day feels it’s the day after yesterday. My actions have no consequences on the next day. It sounds pretty awesome to me. I wouldn’t do anything to break the loop. I’d just let an ASCII message to myself, to be sure I’m still blessed:
"Check the time loop
Roll the crystal blue D6
162453532541426354
Congratulations!
Have a nice day!"
(That’s less than 200 bytes. The crystal blue die is next to my PC, I would know which die the message talks about)
First, use the first 10 bytes of the file as a sanity check. throw in two random bytes like 0x55AA so you know the file isn’t broken. add a loop counter to track how many times you’ve lived the same week (bonus points for crying when you hit loop 9999), toss in a basic checksum to make sure your data isn’t glitched.
Then dedicate like 800 bytes to a super compressed log. Each entry is 8 bytes: a code for what you tried (like action 23 = “mess with the sketchy microwave”), the day and time crammed into 2 bytes, a yes/no/weird result, and a tiny note like “key under rug” but in code. Only keep the last 100 entries so you don’t run out of space.
The leftover 200-ish bytes are for tracking. Use bits to mark places you’ve already checked (like “room D14 done”) and actions you’ve tried (so you stop repeating “throw spaghetti at the wall”).
Every reset, open the file, see your last loop’s fails (like “loop 420: died petting a possum”), Then try something new, focus on unmarked areas and untested actions this is because if you notice a pattern (like “tv static every tuesday”), write it as “tues=F9=glitchinmatrix” or whatever.
After 200 loops, maybe you’ll crack the code (literally) or realize the exit was behind the fridge the whole time.Oor you’ll just accept your fate and start a cult (the 1k chosen ones!) . Either way, you’re out.
tldr: use the 1kb to avoid repeating mistakes, track patterns, and maybe escape before you start talking to a lamp.
(like action 23 = “mess with the sketchy microwave”)
How much time are you spending devising this system? Because you’re going to have to devise the system anew each week, unless you also store instructions for deciding on a system in the file.
How do you store what killed you? Theoretically you can’t edit the log once you die (you’d just start the new loop, with no memory of what killed you).
More importantly, why do you want to escape? This hypothetical time loop sounds awesome.
I’d probably write down everything I should remember in a notepad and then use the 1024 bytes to store where the notepad is located
Depends. Can it run Doom?
Yes you read that right: BYTES, not KB, MB, or GB: 1024 BYTES
1024 Bytes are 1 Kibibyte or 1,024 Kilobytes.
And to make it even more confusing, the person I’m replying to is using a thousandths separator (“,”) that is ambiguous. Unlike metric, there isn’t an international standard for this. More than half the world uses 1,024.00; between 70-80% of the people in the world use “.” as the decimal separator; of these, most use “,” for thousandths, and under 2% use apostrophe. So, most of the world would write “one thousand twenty four” as 1,024, and 20-30% would write 1.024, and a very few - mostly the Swiss and Albanians - would write 1’024.
So Zacryon, your punctuation means something different in different countries. To most people in the world, you’re claiming 1 Kibibytes = 1 Mibibyte.
In the most Milquetoast way, no standards committee has put their foot down and said, “this is the way numbers should be represented.”
The only good solution is to pick something everyone hates for thousandths separators. I like “_”. 1_024. There. Nobody but software developers uses that.
So: to everyone reading this, Zacryon isn’t wrong, they’re just using a decimal separator used by a minority of people in the world.
Good
pointcomma!Unlike metric, there isn’t an international standard for this.
There is one, ISO 80000‑1. But it specifically allows commas and points. Which doesn’t resolve the confusion. We really should adhere to one single standard for this.
I’ll be more cautious now, when writing such numbers in English. Thanks for
pointingcommaing that out!I lived in Germany for two years and it still messes me up when I run across it online. Thankfully, I think in most cases it’s obvious: 1.000.000€ is pretty unambiguous; so is ,05 and 2,05. Honestly, the decimals are usually pretty easy - it’s the thousandths separator that is usually more ambiguous. Heck, even 1,000 and 1.000 are both pretty clearly “one thousand” no matter who you are. But some numbers - 1,024, for example… one thousand twenty four? Or one and 24 thousandths? It could easily be either.
Anyway, I had to double check several details to make sure I wasn’t talking entirely out of my ass, so I learned some things in the process: your comment was to my benefit, so thanks!
Goddamn it who named these terms? The original term was supposed to be 1024 bytes, why the fuck was the definition of Kilobyte retroactively changed?
To conform with SI unit prefixes. Which is a good thing imo.
But according to Wiki the IEC defined those binary prefixes in 1999. And I find it problematic that so few still don’t know about this and don’t adhere to that standard. Even fellow engineers don’t use it correctly. No wonder companies like Microsoft also still use it wrong. This keeps things confusing.
The most detailed ASCII art of a dickbutt that I can create with 1024 characters. Like this lil’ guy:
⠀⠀⠀⠀⠀⣠⠶⠚⠛⠛⠛⠲⢦⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⣴⠟⠁⠀⠀⠀⠀⠀⠀⠀⠻⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⣠⣾⣷⣄⠀⠀⠀⢀⣠⣤⣤⡀⠀⢿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⡿⢃⣸⡶⠂⢠⣿⣿⡿⠁⣱⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⢸⡏⠉⠩⣏⣐⣦⠀⠛⠦⠴⠚⠁⠀⣸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⣼⠧⠶⠶⠶⠿⠶⠶⠖⠚⠛⠉⠁⠀⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⣰⠶⠶⡄⠀⠀ ⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣿⠀⠀⠀⠀⠀⠀⠀⠀⢠⡟⠀⠀⢹⠀⠀ ⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⢤⢠⡆⠀⢸⡄⠀⠀⠀⠀⠀⠀⢀⡿⠁⠀⠀⡾⠀⠀ ⢹⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠈⡇⠀⠸⣧⣠⠴⠶⠖⠲⢶⡞⠁⠀⢈⡼⢃⠀⠀ ⠸⡆⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⡇⠀⠀⢿⠁⠄⣲⡶⠶⠿⢤⣄⡀⠛⢛⠉⢻⠀ ⠀⢿⡀⠀⠀⠀⠀⠀⠀⠀⢸⠠⣇⠀⠀⠀⠀⠊⠁⠀⠀⠀⠀⠀⠙⢦⠈⠙⠓⣆ ⠀⠈⢷⡀⠀⠀⠀⠀⠀⢠⠏⡀⣬⣹⣦⠀⠀⠀⠀⠀⠁⠀⠀⠀⠀⠈⡿⠶⠶⠋ ⠀⠀⠈⢷⡀⠀⠀⠀⠀⠘⠛⠛⠋⠀⠀⠀⠀⠀⠀⠄⠀⠀⠀⠀⠀⣼⠃⠀⠀⠀ ⠀⠀⠀⠀⠙⢦⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠄⠀⠀⣠⡞⠁⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠈⠛⣷⢶⣦⣤⣄⣀⣠⣤⣤⠀⣶⠶⠶⠶⠛⠁⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⣀⡀⠀⣰⠇⣾⠀⠀⠈⣩⣥⣄⣿⠀⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⢿⡉⠳⡟⣸⠃⠀⠀⠀⠘⢷⣌⠉⠀⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠙⢦⣴⠏⠀⠀⠀⠀⠀⠀⠉⠳⠶⠏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀Text only
Yes
Why does this reminds me of Memento
Isn’t it from memento?
Lol I wasn’t sure since I forgot… oh shit, gotta grab a pen real quick before I forget again
I’m confused, does this mean you would be immune to consequences? Like if you broke your arm the next time loop would magically fix it like nothing happened?
Yep.
You die, time just resets again, and you won’t remember anything except the “strange txt file” that 1024KB in size that popped up in front of you on your Neuro-Computer implant when you wake up.
A KiB is a shitton of information for what it is. I’d make sure to GZIP compress it, and keep things short, whatever it is. I’d probably include a very short sentence on what’s going on, and how to stay safe.
A url to a page you can update between resets?
That
That won’t work bro. The page gets reset. I guess URLs could work as a way to externalise information. Like link to the IMDB page of Groundhog day.
Library of Babel. Look it up. It contains every possible string of characters. Just link to the string that says what you want to say.
LOL I saw another user commenting abiut data compression, then I remembered the Vsauce video I watched a long time ago about the Library of Babel. I missed your comment and didn’t even realize you mentioned it 2 hours before I did. 😁
