I've edited the thread's title so that we can again go to pages 1 and 2.
It seems that browsers couldn't read discussion/32307/./p1 or discussion/32307/./p2 - that dot prevented browsers from opening anything except the last page.
No, unfortunately no online tool you use will translate this and I highly doubt any method you try will figure out what this says--it is an encryption algorithm of my own design. I won't give away any secrets but I will say that a simple procedure iterated several times becomes dizzyingly complex.
Wow. Binary --> Morse --> plaintext. Working....but is a work in progress which will have to continue at the house.
I am pretty certain that my spreadsheet macro was converting the binary to decimal then to characters to get dots, dashes, and spaces but it was the concatenating that was troubling me. So far, the first part translates as HFWVITSIHFWVINSAHFWVIKR4HFE so I have *clearly* done something incorrectly....unless you have another layer going on once you reach text.
I've tried Binary->Morse->Base32 and I'm still not getting anything, though the online Base32-to-text tools are a lot less good than for the other codes.
I didn't think of trying base32. It can be difficult to reverse-engineer what someone else has done and it appears that @CrevsDaak has done something I cannot yet figure out. I have full text now but since it didn't make sense I tried a simple letter shift but nothing turned up, whether I went forward or backward covering the entire alphabet. I tried looking at the text backward, every other letter, every third letter, increasing shifts (first letter, shift once to get second letter, shift twice to get third letter, etc). I haven't tried stacking the text--perhaps it decodes vertically rather than horizontally. Morse doesn't cover non-ASCII letters, does it? Truthfully, I don't know. Could the dots and dashes themselves stand in place of 0s and 1s for the numbers 1 to 26, thus translating to letters? For example, . . - . would be 0010 = 2 = b or 1101 = 13 = m. *shrug* Don't know yet.
If you break the text into chunks of 8 they show a fair amount of repeating structures, but the entire string is 434 long, so I got 54 chunks of 8 with 2 left over, and I took the remainder as a bad sign.
HFWVITSI HFWVINSA HFWVIKR4 HFWVI4SU ...
However, dumping the 8-chunks into excel and sorting show quite a lot of outright repeats. I'm guessing something like the first 4 & last 2 chars of each chunk are purely for grouping and should be discarded, but no actual words have appeared yet. Dammit, I do have actual work to do here
434 will break down into 31 blocks of 14 characters each, or 62 of 7 but I can't tell which just yet. There are some repeating letter patterns, like the hfwv early on, but also "jzed" and "coja" later on. I concur with @The_Potty_1--it is distracting trying to work on this when actual work keeps intruding on my time.
OK so I massaged the text into 434 lines of single characters, imported them into SQL server, and did a select count to get the occurrence of each character. Note no 0,1,7,8,9, and severely skewed occurrences of the rest. Most significant is we have a 31-character alphabet, so I would say we need to convert this to binary-5, but from there I'm still pretty lost. I tried stringing it all together and then converting the binary-8 to chars, but no joy.
Char Count 2 16 3 18 4 16 5 1 6 4 A 5 B 16 C 10 D 16 E 11 F 21 G 7 H 18 I 20 J 12 K 32 L 5 M 9 N 16 O 8 P 3 Q 11 R 5 S 27 T 5 U 25 V 38 W 31 X 1 Y 5 Z 22
D'oh got it, converted it to binary-5, replaced 1 with -, 0 with . and dumped it in the morse converter. The answer is clearly: QY8???7?QY8???7GQY8??6?MQY8??M7?QY8?6?TKQY8??87/QY8??87/QY8??6?MQY?89DO/QY8???7?QY8??M7?QY8???7CQY8??M7?QY8?6?TKQY8?TB7?/0?X7N6???6X7N6?/0?X7TN/??8X7N6?Z0GX7N6?Y?KX7N6?Y?KX7N6???6X7N6??0CX7N6?Z0GX7N6?=?ZX7N6?/0?X7TN/??8X7N6??0CX7N6?Z9Z???O0??6CC?O0??6QC?O0??6QC?O0??6B??O0??6Y??O0??6B??O0??8Q?=O0??6CM7O0??6CM7O0??6B??O0??6?8??0??6CC?O0??6Z/?O0??6Y??O0O?YZT?B??GM88NX?Y?M8T?B??GM8T?BB??M8T?X76?M8T??N=9M8T?BT??M8T?BT??M8T??N=9M8T??N=9
D'oh got it, converted it to binary-5, replaced 1 with -, 0 with . and dumped it in the morse converter. The answer is clearly: QY8???7?QY8???7GQY8??6?MQY8??M7?QY8?6?TKQY8??87/QY8??87/QY8??6?MQY?89DO/QY8???7?QY8??M7?QY8???7CQY8??M7?QY8?6?TKQY8?TB7?/0?X7N6???6X7N6?/0?X7TN/??8X7N6?Z0GX7N6?Y?KX7N6?Y?KX7N6???6X7N6??0CX7N6?Z0GX7N6?=?ZX7N6?/0?X7TN/??8X7N6??0CX7N6?Z9Z???O0??6CC?O0??6QC?O0??6QC?O0??6B??O0??6Y??O0??6B??O0??8Q?=O0??6CM7O0??6CM7O0??6B??O0??6?8??0??6CC?O0??6Z/?O0??6Y??O0O?YZT?B??GM88NX?Y?M8T?B??GM8T?BB??M8T?X76?M8T??N=9M8T?BT??M8T?BT??M8T??N=9M8T??N=9
Hehe, it's crevs, so that's probably the actual answer :P
Reading all of this i can't help but to think you're all just writing stuff down and no one has any clue what you're doing. It's like trying to watch Xzar scribe a scroll into his spellbook, the only person in my party who had any idea what Xzar was doing, was Minsc.
On the contrary, we know *exactly* what we are doing. It may not all make sense--even to us--but we definitely know what we are doing.
That also remains a possibility--he could have encoded gibberish, in which case we can never tell if what we are doing is going to be useful or not. I want to say that this was a standard tactic used in the past--make every third encoded message nothing but nonsense so that when your enemies successfully decode it they think they made a mistake--but I am uncertain about this. It definitely sounds like something *I* would do, though, because that is how I think.
To stay one step ahead of your opponents' attempts to decode your messages, though, you begin with a preset key based on the month, the day of the month, and the date of the week. For example, today is Friday 6 June, so it is (on the calendar I use) the 6th day of the week, the 6th day of the month, and the 6th month of the year. hrm....a certain subclass of numerologists might not like today, but that is neither here nor there. Anyway, when you send your first message you include, as part of the message, the key that the sender should use when replying. The sender then includes in his message the new key that you should use, and so on and so forth. Thus, the encryption changes with every message sent, so no two messages are sent using the same key. If your opponents are not able to decrypt the first message sent they will never be able to catch up, except by a statistically-improbable lucky guess. Clearly, though, you wouldn't want to base your key on the Gregorian calendar--that is too easy. Refer to the old Julian calendar or, ideally, use the Hebrew or Chinese calendars (in which case it is not the year 2014).
(which I couldn't decipher BTW), probably it would be more difficult as I would be following a variable subjective to changes for the algorithm (e.g. if it is A=rt38 in the first line, in the second line it would be rt40 and so on, but with a variation depending on the column axis too, so a letter A in the 2nd column and first line, it would be rt48).
It was binary->morse->base32->ascii85->base64->hex->oct->text.
I would send you a Guinness but I am afraid it would be warm by the time it arrived and there are some things which simply are *not* done, one of which is drinking Guinness warm. 7 simple iterations to arrive at a more complex destination--well done.
I could tell you how I did it but only under certain conditions: 1) not in public like this, 2) I would have to be certain you wouldn't tell anyone else. The beauty of my system dies, like all great secrets die, as more people know them. This is also why conspiracy theories are never (well, almost never) true--even if the probability of one person telling the secret in any given month is really low if too many people know then after enough time the secret gets revealed.
Comments
http://morsecode.scphillips.com/jtranslator.html
http://www.asciitohex.com
........______-----........>>>>><<<<<........-----______........
I've edited the thread's title so that we can again go to pages 1 and 2.
It seems that browsers couldn't read discussion/32307/./p1 or discussion/32307/./p2 - that dot prevented browsers from opening anything except the last page.
Now it works!
FtbnApCrHmAcFmHuBuDpIoBxeieoawbjbmahEiEsAdCqauAvBjDjAnEpfiaaCnabAtEaEfAbCkDfAkejAralCuCpAoAgAfAwLbIxEt!
No, unfortunately no online tool you use will translate this and I highly doubt any method you try will figure out what this says--it is an encryption algorithm of my own design. I won't give away any secrets but I will say that a simple procedure iterated several times becomes dizzyingly complex.
@Erg
30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 30 31 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 31 30 30 30 31 30 31 31 30 31 30 30 31 30 31 31 30 31 30 30 31 30 30 30 30 30
@Mathsorcerer
Gung'f purngvat
histay siay ymay astlay esortray
Iay ikelay histay neoay
I am pretty certain that my spreadsheet macro was converting the binary to decimal then to characters to get dots, dashes, and spaces but it was the concatenating that was troubling me. So far, the first part translates as HFWVITSIHFWVINSAHFWVIKR4HFE so I have *clearly* done something incorrectly....unless you have another layer going on once you reach text.
Morse doesn't cover non-ASCII letters, does it? Truthfully, I don't know. Could the dots and dashes themselves stand in place of 0s and 1s for the numbers 1 to 26, thus translating to letters? For example, . . - . would be 0010 = 2 = b or 1101 = 13 = m. *shrug* Don't know yet.
But i won't tell anyone!!!!
It's a secret!!!!
HFWVITSI
HFWVINSA
HFWVIKR4
HFWVI4SU
...
However, dumping the 8-chunks into excel and sorting show quite a lot of outright repeats. I'm guessing something like the first 4 & last 2 chars of each chunk are purely for grouping and should be discarded, but no actual words have appeared yet. Dammit, I do have actual work to do here
Char Count
2 16
3 18
4 16
5 1
6 4
A 5
B 16
C 10
D 16
E 11
F 21
G 7
H 18
I 20
J 12
K 32
L 5
M 9
N 16
O 8
P 3
Q 11
R 5
S 27
T 5
U 25
V 38
W 31
X 1
Y 5
Z 22
QY8???7?QY8???7GQY8??6?MQY8??M7?QY8?6?TKQY8??87/QY8??87/QY8??6?MQY?89DO/QY8???7?QY8??M7?QY8???7CQY8??M7?QY8?6?TKQY8?TB7?/0?X7N6???6X7N6?/0?X7TN/??8X7N6?Z0GX7N6?Y?KX7N6?Y?KX7N6???6X7N6??0CX7N6?Z0GX7N6?=?ZX7N6?/0?X7TN/??8X7N6??0CX7N6?Z9Z???O0??6CC?O0??6QC?O0??6QC?O0??6B??O0??6Y??O0??6B??O0??8Q?=O0??6CM7O0??6CM7O0??6B??O0??6?8??0??6CC?O0??6Z/?O0??6Y??O0O?YZT?B??GM88NX?Y?M8T?B??GM8T?BB??M8T?X76?M8T??N=9M8T?BT??M8T?BT??M8T??N=9M8T??N=9
That also remains a possibility--he could have encoded gibberish, in which case we can never tell if what we are doing is going to be useful or not. I want to say that this was a standard tactic used in the past--make every third encoded message nothing but nonsense so that when your enemies successfully decode it they think they made a mistake--but I am uncertain about this. It definitely sounds like something *I* would do, though, because that is how I think.
To stay one step ahead of your opponents' attempts to decode your messages, though, you begin with a preset key based on the month, the day of the month, and the date of the week. For example, today is Friday 6 June, so it is (on the calendar I use) the 6th day of the week, the 6th day of the month, and the 6th month of the year. hrm....a certain subclass of numerologists might not like today, but that is neither here nor there. Anyway, when you send your first message you include, as part of the message, the key that the sender should use when replying. The sender then includes in his message the new key that you should use, and so on and so forth. Thus, the encryption changes with every message sent, so no two messages are sent using the same key. If your opponents are not able to decrypt the first message sent they will never be able to catch up, except by a statistically-improbable lucky guess. Clearly, though, you wouldn't want to base your key on the Gregorian calendar--that is too easy. Refer to the old Julian calendar or, ideally, use the Hebrew or Chinese calendars (in which case it is not the year 2014).
If I use actual encodings like this (which I couldn't decipher BTW), probably it would be more difficult as I would be following a variable subjective to changes for the algorithm (e.g. if it is A=rt38 in the first line, in the second line it would be rt40 and so on, but with a variation depending on the column axis too, so a letter A in the 2nd column and first line, it would be rt48).
...
Ohhhhkay then.
.. - ... / -. --- - / .- -. / ... / .. - ... / - .... . / .- .-- -.- .-- .- .-. -.. / .--. .- ..- ... . / - .-. .. .--. .-.. . / -.. --- -