Theory: Making Our Own Encoder!

Alright, I've seen lots of famous people make encoders such as Base64, Brainf***, Hex, Etc.

 

I was inspired and thought of myself, why not make my own encoder? It's actually medium-hard to develop one.

 

First off, you wan't to make your own decoder as well, because you can't really do anything with encoded stuff.

Here's the vocabulary list (doesnt support symbols yet):

A = 1
B = 2
C = 3
D = 4
E = 5
F = 6
G = 7
H = 8
I = 9
J = 10
K = 12
L = 14
M = 16
N = 19
O = 15
P = 17
Q = 19
R = 20
S = 23
T = 26
U = 27
V = 29
W = 666
X = 420
Y = 999
Z = 69

 

We have to make words in group that make no sense.

 

Pretend a user has done 'AI' or '19', since 19 is actually the letter 'Q', it would replace letter's Q with the letter's 'AI', and it would brainf**** the whole system. So we would replace the letters AI or 19 with 18.

 

Keep in mind this would encode only letters, we will have to do quotations and etc. We haven't even built our encoder/decoder yet!

 

To make the encoder, we would need a lot of 'if' statments, I wrote this in C# since it's easiest.

 

My encoder's name is going to be called Intcode - Integer Encoded String.

 

string normal = "abc";//a example text
string addon;//what string to addon to
            if (normal.Contains("a"))
            {
               addon += "1";//add on a number
            }
            else if (textBox1.Text.Contains("b"))
            {
               addon += "2";//add on a number
            }
            else if (textBox1.Text.Contains("c"))
            {
               addon += "3";//add on anumber
            }

This is not completed but if we run the sample code, our output should be -> "ABC".

 

This is not the best way to do it, as there are backsides on how it can be broken and bypassed.

 

Encoder means to difficultize, to make it harder for us to read but for code it's easier.  

 

Let me know if I should continue this series :) Tell me your opinions in the replies!