1 From: Boris Kraut <krt@nurfuerspam.de>
\r
2 To: undisclosed-recipients: ;
\r
3 Date: Thu, 30 Jan 2014 22:57:14 +0100
\r
4 Message-ID: <20140130225714.dF_d7l@busy.local>
\r
5 Reply-To: Boris Kraut <krt@nurfuerspam.de>
\r
6 Subject: [.plan] Zitat des Tages
\r
9 > XMPP was not designed for modern-day smartphone-based instant
\r
10 > messaging. However, it is the best tool we have to counter the
\r
11 > proprietary silo-based IM contenders like WhatsApp, Facebook
\r
12 > Chat or Google Hangouts.
\r
16 > The only conclusion from that debacle can be: do not save any
\r
17 > logs. This imposes a strong conflict of interest on Android,
\r
18 > where the doctrine is: save everything to SQLite in case the
\r
19 > OOM killer comes after you.
\r
23 > On Apple iOS, background connections are killed after a short
\r
24 > time, the app developer is "encouraged" to use Apple's Push
\r
25 > Service instead to notify the user of incoming chat messages.
\r
27 > This feature is so bizarre, [...] you need to send all the
\r
28 > content you want displayed in the user notification as part
\r
29 > of the push payload. That means that as an iOS IM app author
\r
30 > you have the choice between sacrificing privacy (clear-text
\r
31 > chat messages sent to Apple's "cloud") or usability [...].
\r
35 > In the second group, there are apps that use their own custom
\r
36 > proxy server, to which they forward your XMPP credentials (yes,
\r
37 > your user name and password! [...]) [...] Unfortunately, your
\r
38 > privacy falls by the wayside, leaving a trail of data both with
\r
39 > the proxy operators and Apple.
\r
41 > So currently, iOS users wishing for XMPP have the choice
\r
42 > between broken security and broken usability -- well done,
\r
46 [0] http://op-co.de/blog/posts/mobile_xmpp_in_2014/
\r
projects / krt-msg / blob