From 40464945beec599d1b39e4311218f525ec57e648 Mon Sep 17 00:00:00 2001
From: yakamok <38737288+yakamok@users.noreply.github.com>
Date: Mon, 28 May 2018 16:16:42 +0200
Subject: [PATCH] Update README.md

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 464f3bc..c52a994 100644
--- a/README.md
+++ b/README.md
@@ -19,3 +19,9 @@ so we used uid's like so:
 The first of the uid(email) is numeric to stand for the order of the base64 string so we can be put it together again in the correct order, then the second part is simply a set chunk of binary data converted to base64.  
 
 First of all had to test how many chars could be put in the uid, turns out after some testing just a little over 2040. Once you enter more than this the key becomes invalid and you have to reset your pubkey. Through some trial and error decided to stick with a safe number 1741 chars long. Once you split the binary data into 1305Byte chunks and convert it to base64 it comes to 1741 chars in length. 
+
+### ToDo
+
+Which is best?
+Create program to parse the data from the site?
+Maybe also download the key locally with import and parse it this way?