It's your job to gather the pizza orders for everyone in the lab you work at in New Mexico, but it appears that the order for Richard has become corrupted and scrambled. He attempted to send it over some newfangled digital communication channel, and while you got plenty of data, it appears to just be gibberish. You could just ask him to resend his request, but that may also get garbled, not really clearing things up. You know he's a very busy person, so you don't want to bother him in person.
Here's the terminal output. Can you fix the errors and rearrange the data to figure out what type of pizza Richard wants?
Parsing as ASCII...FAIL
Inverting ENDIAN and reattempting...FAIL
View raw data (Y/N)?...>Y
Select format (B/O/H)...>H
The corruption didn't add or remove any bytes/nibbles/bits, though it may have mutated some of them.
Data corruption has been a common issue on this network in the past. Has Richard has found a way to let data be reconstructed, even if it has been corrupted?
The plaintext will be in ASCII, though before the corruption is fixed and the correct data is extracted, there are 12 bits per character.
If only there was a real-world researcher, named Richard, that worked at a lab in New Mexico. Maybe looking into his achievements would give us a clue as to how to correct the errors in the bitstream.
Hint 5 (BIG SPOILER):
I didn't realize that there were so many possible ways to order parity/data bits with this sort of Error Correction Code. I just went with the process I learned in my Digital Logic class, where the rightmost bit has the lowest index, and wasn't anticipating or intending this much confusion once we reached that point in the puzzle. That said, here's which bits are which in the puzzle, along with the encoded binary for the first character (to remove any possibility of confusion about direction, endian-ness, and so on):
|--Leftmost Bit Rightmost Bit --| D8 D7 D6 D5 P4 D4 D3 D2 P3 D1 P2 P1 0 1 1 0 0 0 0 0 0 0 1 0