HACKERBOT

shotting.cc

DEFCON-1

HOME

WELCOME TO SHOTTING.CC

Second instalment of a series regarding chat bot construction (Part 2)

In this part of the tutorials we will be using pseudo-code throughout. Why? Because specialising in a single language makes for dormancy and people will not bother with converting the source code to say, from C# to Java. Using pseudo-foo will enable us to focus on the concepts behind the code, rather than on admiring eloquent code sequences themselves. Lets move on, shall we?

This begins how chat bots are made. In communications studies crossing over the language paradigm of Artificial Intelligence (A.I.) and interaction study developing your sociology skills.

Let our outline be thusly laid out for the transaction mechanism of the tx/rx paradigm where tx = transmissions and rx = receptions.

The code below uses drop loading a database to find relevant matches.

START FOR EACH c as string in Query
FOR EACH DB as String in DataBase
IF c == DB THEN
Array[index] = DB
index += 1
END IF
NEXT DB
NEXT c
END

This code permits the Array to be filled with matches from the database, it is then just a case of extrapolating the data against an OutPutDB. The outputDB contains string sentence variables constructed from the previous variety pack matches. See code below;

SET Code = Array[index]
FOR EACH out in OutputDB ASSOC
IF Array[index] == out.Text THEN
OutArray[index] = Out
END IF
NEXT out
NEXT SET

WHILE OutArray.Length != up

FOR EACH outer as string in OutputDB
IF Out.Text = outer.text
SET Fin[index] = Out
index += 1
NEXT outer

up += 1
END WHILE

This concludes our section here. The last piece of code above collated sets of out from the outputDB by cycling through ALL outputDB out strings (E.g. "Hello World") if a match was found input it into the FinArray. This means lots of juicy (and needed) redundancy in the message to be output. Then, using all possible combinations of such a message, we find out.