Difference between revisions of "Talk:2445: Checkbox"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
(JS works now)
Line 52: Line 52:
  
 
Parsed the JS (morse obfuscation, weird) and cut this small bit out:
 
Parsed the JS (morse obfuscation, weird) and cut this small bit out:
  const e = await fetch(`/2445/morse/.../${morse.decode('pog')}`);
+
  e = await fetch(`/2445/morse/.../${morse.encode('pog')}`);
  const f = await e.text();
+
  f = await e.text();
 
  [state, ...respMorse] = f.split('/');
 
  [state, ...respMorse] = f.split('/');
 
  morse.decode(respMorse.join('/'));
 
  morse.decode(respMorse.join('/'));
 
Use this if you'd like to play around with inputs. (replace pog, obviously) :) [[User:Ezist|Ezist]] ([[User talk:Ezist|talk]]) 23:53, 1 April 2021 (UTC)
 
Use this if you'd like to play around with inputs. (replace pog, obviously) :) [[User:Ezist|Ezist]] ([[User talk:Ezist|talk]]) 23:53, 1 April 2021 (UTC)

Revision as of 23:55, 1 April 2021

If left alone, the morse code produced spells "WHAT" (.-- .... .- -) Ezist (talk) 22:50, 1 April 2021 (UTC)

I'm early enough that there isn't a summary yet, and I'm not confident enough to start one, so I'll just drop my thoughts. If you click the checkbox repeatedly, at some point it starts playing Morse code. Presumably, there are a whole lot of different sequences. So far, I've gotten .- - .-- .... (which translates to ATWS; no idea what that means) and ..... (just 5, I think). Meanwhile, the mouseover text is ... --- ..., which is SOS. Any thoughts? What other sequences are there? Or am I totally missing something? (Edit conflict. Looks like Ezist has another one.) Aerin (talk) 22:56, 1 April 2021 (UTC)

I got something like ATWS at first, but that's just cause I misheard one of the letters, and misinterpreted where the word started/ended. Ezist (talk) 23:03, 1 April 2021 (UTC)

Wait, sorry, I'm back. It apparently has to do with user input. No idea what I pressed to get those results lol. Aerin (talk) 22:57, 1 April 2021 (UTC)

Just a note, but a Morse code legend as well as translations of your input and the website's output are available in the console in browser DevTools. Helpful for those that don't know Morse. Toadtoad (talk)

It looks like Samuel Morse died on April 2, 1872, so that might be why this comic appears today. 162.158.212.218 23:07, 1 April 2021 (UTC)

"Hi" returns [.... . .-.. .-.. --- -.-.-- / .- -. -.-- -... --- -.. -.-- / --- ..- - / - .... . .-. . ..--..] "HELLO! ANYBODY OUT THERE?" Piano (talk) 23:09, 1 April 2021 (UTC)

a sequence of repeating "T", or at least more than one "E" [ - - - ] or [ . . . ] will respond back the same sequence, just one "E" will give "WHAT" 172.68.25.253 23:18, 1 April 2021 (UTC)

"QTH" gives "QTH ARES VALLIS". "QTH" is a code used to ask for position, and Ares Vallis is a place on Mars. Ezist (talk) 23:27, 1 April 2021 (UTC)

"CHECK" replies "MATE." "CHECKMATE" and "MATE" each reply "WHAT." 162.158.126.146 23:34, 1 April 2021 (UTC)


The js: has anyone tried viewing the JS? There seems to be a file that is just filled with undecipherable Morse. Can anyone interpret this? Just press f12 and look for comic.js or morse.js 162.158.62.161 23:35, 1 April 2021 (UTC)

I tried decoding it. Certainly looks like something binary encoded into text. 162.158.183.153 23:36, 1 April 2021 (UTC)

Adding onto that, what does the ';D' in .split(';D') (at the very end of morse.js) do? AFAIK it's not a special character in JS

morse.js decodes comic.js into the following script: [1] (Also, pretty sure the .split(';D') is just an emoji - it results only in an array of 1 element, so no splitting really occurred.) 108.162.219.78 23:52, 1 April 2021 (UTC)

running window.BeepComic.hurryUp() in console gives you immediate response in logs, without waiting for all the beeping to cease

Ah so that's where that script comes from 162.158.183.153 23:40, 1 April 2021 (UTC)

`BeepComic.send(morse.encode('sudo make me a sandwich'))` <-- convenience, in addition to the hurryUp --rcombs

Does someone else get this uuid DB334AAB-92A1-11EB-8001-8C16454FB02A? 162.158.238.228 23:42, 1 April 2021 (UTC)


Audio does not work on Safari as of right now - however, inputting `const AudioContext = webkitAudioContext;` into the browser console before unmuting will allow audio to work on Safari. May want to note this as a 'fix' for the experience? --162.158.63.6 23:44, 1 April 2021 (UTC)

In addition to muting/unmuting, BEEP and MUTE reply CQM (I can't find a reference to what that means). 162.158.126.146 23:51, 1 April 2021 (UTC)

The statements at line 458 of the gist mentioned earlier seem interesting.

   handleAction(text) {
       if (text.startsWith('//')) {
           this.client.open(text.substr(2));
       }
   }

172.68.189.101 23:52, 1 April 2021 (UTC)


Parsed the JS (morse obfuscation, weird) and cut this small bit out:

e = await fetch(`/2445/morse/.../${morse.encode('pog')}`);
f = await e.text();
[state, ...respMorse] = f.split('/');
morse.decode(respMorse.join('/'));

Use this if you'd like to play around with inputs. (replace pog, obviously) :) Ezist (talk) 23:53, 1 April 2021 (UTC)