moved dictionaries to a seperate repo

README.md

@@ -4,8 +4,11 @@ Twitter Brute Force is a little script that takes a new-line-seperated dictionar
 
 To avoid rate limiting, this script does __not__ use the Twitter REST API, it instead queries for the presumed profile's status code. As a result it generates false-positives on reserved account names.
 
+
 ## Usage
 
+### brute.js
+
 The main script, brute.js takes multiple dictionaries as arguments.
 
 Available handles go to a file called ```available```.
@@ -16,6 +19,9 @@ node brute.js dictionary1 dictionary2 dictionary3
 
 brute.js responds to ```SIGUSR1``` with the current number of handles processed.
 
+
+### generate.js
+
 The other script, generate.js generates all permutations of the alphebet up to k characters.
 
 Takes some number k and the output file.
@@ -26,6 +32,16 @@ node generate.js 3 permutations3
 
 _note that this is O(n^k) runtime_
 
+
+### brute_names.js
+
+A name generation script was further added by [FlavFS](https://github.com/FlavSF). It requires a ```first.csv``` and ```last.csv``` to be in the imediate directory.
+
+## Dictionaries
+
+I've pushed the dictionaries that I've been using to a seperate repo called [Twitter-Brute-Force-Dictionaries](https://github.com/dpeticol/Twitter-Brute-Force-Dictionaries)
+
+
 ## Results
 
 In case you're interested, here are some results.