Requiring GCM means you are forcing users to give potential PII to Google, which is a heavy-handed way of violating privacy.
-
-
Replying to @bkero
What PII? The messages are empty. People would probably take this crowd more seriously if it didn't grossly exaggerate everything.
1 reply 0 retweets 0 likes -
Replying to @signalapp @whispersystems
Doesn't matter that messages are empty. Metadata. Leaks time, app ID, receiver device IDs, and is PII with associated G data
1 reply 0 retweets 0 likes -
Replying to @bkero
Can you see how "Google knows when a background app receives a wakeup" is very different from "Signal hands your identity to Google?"
3 replies 0 retweets 0 likes -
Replying to @signalapp @whispersystems
and the combo of 1) refusing 3rd party client support, and 2) not providing a G-free APK leaves many out in the cold
3 replies 0 retweets 0 likes -
Replying to @bkero
We don't feel we can support clients out of our control, but we'd love it if you proved us wrong. Let us know if we can help w/ setup
1 reply 0 retweets 0 likes -
Replying to @signalapp @whispersystems
I don't think anyone would expect you to actively support alternate clients, but letting them on the network is a good start
1 reply 0 retweets 0 likes -
Replying to @bkero
Having them on the network is supporting them. If our users are communicating with them, then when they break our users are effected.
2 replies 0 retweets 1 like -
Replying to @signalapp @bkero
However, we'd love to be proven wrong. The source is available, so feel free to do it differently if you disagree.
1 reply 0 retweets 2 likes -
Replying to @signalapp @whispersystems
You conveniently version libsignal-protocol-java for compatibility (and in theory interoperability). Isn't that enough?
2 replies 0 retweets 1 like
Versioning doesn't really help if you're in the past, and most changes don't happen at that layer.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.