path: root/wiki/src/blueprint/replace_Pidgin.mdwn
diff options
author127.0.0.1 <>2016-01-26 22:37:55 +0100
committeramnesia <>2016-01-26 22:37:55 +0100
commitae615411fdbdcea0079476094520dd45180800cc (patch)
treea0a82f64bc6689dd5f077f7dcef422c153e3d52c /wiki/src/blueprint/replace_Pidgin.mdwn
parentb90e53c6aee4f1198adae66c30175ea5f9abdd04 (diff)
slightly edited version of
Diffstat (limited to 'wiki/src/blueprint/replace_Pidgin.mdwn')
1 files changed, 13 insertions, 0 deletions
diff --git a/wiki/src/blueprint/replace_Pidgin.mdwn b/wiki/src/blueprint/replace_Pidgin.mdwn
index 0aa416d..12681a6 100644
--- a/wiki/src/blueprint/replace_Pidgin.mdwn
+++ b/wiki/src/blueprint/replace_Pidgin.mdwn
@@ -15,6 +15,19 @@ TODO: Would a pair of two separate client (XMPP and IRC) also be okay, or are we
## General requirements
+### Use cases
+The client SHOULD support the following use cases:
+1. Contributing to Free Software projects that use IRC chatrooms (and won't switch to anything else any time soon)
+2. Contributing to Free Software projects that use XMPP chatrooms
+3. One-to-one chat that is compatible with currently widespread practice. That basically means XMPP + OTR, nowadays.
+4. Participation in public chatrooms for Tails user support.
+The client MAY support the following use cases:
+* One-to-one chat that protects metadata end-to-end (that is: "who is chatting with whom")
### Documentation
### Internationalization