This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.
Why do small things that cause a lot of grief like this always happen to me? I built out my whole workflow and ran it only to find out it failed when passing through the macro. So I redid basically everything only to realize the only reason it was failing was because I created my own Text Input file that I called Field1 when the macro was expecting a field called data. *facepalm*
I created a dictionary of ~800 UTF-8 characters and performed a random character substitution for half of the letters in the string. With 10 differently encoded versions of the original text it can be cracked easily using the decoder.
I assumed that the number of rows would be equal to the number of characters in the message. I played a bit with the sampling rate (what percentage of the values to hold at the original value) just to see when the encoding would start to break. For this 70 character example, I started getting random errors at less than 25% sampling. I'm sure this would change based on the number of rows of encoding.