[noize]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

[Psycho_Coder]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

[Psycho_Coder]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

[Psycho_Coder]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

[Deque]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

[Deque]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

[Deque]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

[noize]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

I've sent a pull request that fixes the bug for that "0"s become "o"s after a leet encode/decode.

I've got no problem for you to write the descriptions of my encodings, but it's sure fair for me to write them myself. I'm doing it tonight.

[noize]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

I've sent a pull request that fixes the bug for that "0"s become "o"s after a leet encode/decode.

I've got no problem for you to write the descriptions of my encodings, but it's sure fair for me to write them myself. I'm doing it tonight.

[noize]

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

I haven't even touched base64. I didn't use it and so there was no question of finding errors. See the logs I provided but I did gave a look to your "leet.py" I actually that there is some problem with that.

@Deque I have something else to say. Since most of the encodings don't have descriptions so I would ask that if @noize or @Ex094 allows then I will write up the description for the encodings or I would be overjoyed if they themselves provide the description.

I am sorry to say this but Ex094 has been very inactive lately.

Thanks, Psycho.

I believe it is the base64 algorithm that is giving the problem. Of course, my function is fucking up original cases, this might hurt the encoding, but I don't think it's the leet algorithm to cause some error.

No, it's the leet. The base64Variant throws the error, because it gets a character that isn't recognized. It is no valid base64 string that is given by the leet function, which means it doesn't decode the same as it encodes (note that it got a perfect base64 string but after decoding the same it returned something different, you can see that in the output).

---

I haven't even touched base64.

No, you have used atom128 and zong22 which are base64 variants (same algorithm, same alphabet, but different order of the characters).

I agree with the descriptions. They really should be added.

I've sent a pull request that fixes the bug for that "0"s become "o"s after a leet encode/decode.

I've got no problem for you to write the descriptions of my encodings, but it's sure fair for me to write them myself. I'm doing it tonight.