update README

README.md

@@ -1,5 +1,44 @@
 # IPFS Boards
 
+Image and discussion boards, forums and the like have many problems:
+
+- Centralized
+  - What if it gets shut down?
+  - What if the servers are down?
+  - What if a phisical network link breaks and the data is on the other side?
+  - What if the owners of the board get eaten by aliens?
+
+- Fragile
+  - what if there's a DoS attack?
+  - what if there is a usage explosion and the servers can't handle it?
+  - what if the datacenter is flooded and data is lost?
+
+- Closed Down, limited in possibilities
+  - What if I want to write a custom client?
+  - What if I want to change the user interface?
+  - What if I want a name that someone else already has?
+  - What if I want to move my data to another service/subreddit/forum ?
+  - What if I want more control (think a private forum), or less control (think 4chan) ?
+  - What if I want <feature> ?
+
+This project was conceived to solve that. With the help of modern web technologies, the IPFS and IPNS protocols
+and some optional cache servers, we can solve these problems and create a true universal platform which can act as:
+
+- Discussion board
+- Wiki
+- File Sharing platform
+- E-Learning platform
+
+With security, control, reliability, rock solid stability, fully distributed architecture or, optionally, none of these!
+
+## How
+
+To be continued...
+
+## Faq
+
+To be continued...
+
 ## Components
 
 - __Client__
@@ -55,4 +94,9 @@ possible for lange texts without duplicating data.
 
 ### Versioning
 
-The protocol should be versioning once it's stable enough to be useful
+a `version` file or something should be included in the user's files to ensure compatibility between different
+versions or forks.
+
+### License
+
+GPLv3? MIT? Something else? Needs to be chosen