Anonymous ID: f2f497 July 21, 2026, 11:51 a.m. No.24852426   🗄️.is 🔗kun   >>2451 >>2469

https://x.com/lord_jones_1911/status/2017956852638609477

 

This is the issue with sending messages back in time.

The sound track has a morse code at the beginning.

It decodes to

 

BELLBARNADAVEDCOLLEERMARTENGALWAYTONYPOMFRETSTEVEWAHED

 

The E's in the decode are a mistake they should have been I's, so it should have decoded to

 

BILLBARNADAVIDCOLLIERMARTINGALWAYTONYPOMFRETSTEVEWAHID

 

If a signal was sent back in time to correct this, the world would only know the message containing the I's and the mistake message would not exist.

 

You would not have to change any C64 tapes or what people hear from the speaker, you only need to change 1 character in Martin Galway’s Morse code generator that made the mistake so it makes two dots instead of a single dot.

 

1985 would be the target year. 0% future impact. 0% risk. No one would ever know, perfect test candidate? …

Anonymous ID: f2f497 July 21, 2026, 12:02 p.m. No.24852477   🗄️.is 🔗kun   >>2539

>>24852451

apt install UTF2morriscode?

 

That's part of what makes the scenario elegant, the fix has to be applied at the exact point where the error was created, because there were no external “correct” solutions available at the time in 1985

Anonymous ID: f2f497 July 21, 2026, 12:28 p.m. No.24852585   🗄️.is 🔗kun

>>24852560

>can still see 𝕏

 

Obviously it hasn’t been executed yet. That's why you can still see the buggy version right now. If someone sends the fix back in time later, the error would’ve never happened in the first place.