fixed spelling in README and added mission statement to docs

openspace42 · Jul 14, 2014 · 876a076 · 876a076
1 parent d0f5c9c
commit 876a076
Show file tree

Hide file tree

Showing 2 changed files with 26 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -127,7 +127,7 @@ longer necessary. Using priorities to route OTR messages isn't pratical either
 because they are not changeable on the fly. Metrics like last active client
 (the client which sent the last message) are much better.
 
-Unfortunatly these modern replacement for lagecay XMPP featurs are not widely
+Unfortunatly these modern replacement for legacy XMPP featurs are not widely
 adopted. However Conversations should be an instant messanger for the future and
 instead of making Conversations compatible with the past we should work on
 implementing new, improved technologies into other XMPP clients as well.

diff --git a/docs/MISSION.md b/docs/MISSION.md
@@ -0,0 +1,25 @@
+Conversations is a messanger for the next decade. Based on already established
+internet standards that have been around for over ten years Coversations isn’t
+trying to replace current commercial messangers. It will simply outlive them.
+Commercial, closed source products are coming and going. 15 years ago we had
+ICQ which was replaced by Skype. MySpace was replaced by Facebook. WhatsApp and
+Hangouts will disapear soon. Internet standards however stick around. People are
+still using IRC and e-mail even though these protocols have been around for
+decades. Utilizing proven standards doesn’t mean one can not evolve. GMail has
+revolutionized the way we look at e-mail. Firefox and Chrome have changed the
+way we use the Web. Conversations will change the way we look at instant
+messaging. Being less obstrusive than a telephone call instant messaging has
+always played an importent role in modern society. Conversations will show that
+instant messaging can be fast, relialbe and private. Conversations will not
+force its security and privacey aspects upon the user. For those willing to use encryption
+Conversations will make it as uncomplicated as possible. However Conversations
+is aware that end-to-end encryption by the very principle isn’t trivial. Instead
+of trying the impossible and making encryption easier than comparing a
+fingerprint Conversations will try to educate the willing user and explain the
+necessary steps and the reasons behind them. Those unwilling to learn about
+encryption will still be protected by the design principals of Conversations.
+Conversations will simply not share or generate certain information for example
+by encouraging the use of federated servers. Conversations will always
+utilize the best available standards for encryption and media encoding instead
+of reinventing the wheel. However it isn’t afraid to break with behavior patterns
+that have been proven ineffctive.