Pathetic excuse. They could achieve same UX goal by probing if it's blocked & notifying the user before falling back.
-
-
Replying to @RichFelker @thegrugq
Better would be actively working around the firewall, e.g. making it computationally expensive to distinguish encrypted calls.
1 reply 1 retweet 1 like -
Replying to @RichFelker @thegrugq
the data flow pattern of a call is unique and hard to change. Steady stream of encrypted data is most likely a call
1 reply 0 retweets 0 likes -
Suppose as an example the call were mp3 streams. Encode the ciphertext as quantized DCT coeffs in valid mp3 streams.
1 reply 0 retweets 0 likes -
Now you need audio analysis (moderately expensive for firewall) to determine if the call is encrypted.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @thegrugq
you can block any audio stream which are not known protocol. If I understand you correctly, you pay a lot BW for stegn
2 replies 0 retweets 1 like -
Steganography to fool humans or smart analysis tools costs a lot in BW. OTOH what I described is just a few % BW cost.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @thegrugq
then I don't understand why can't you sample the mp3 and block ones with high entropy in DCT coeff
1 reply 0 retweets 0 likes -
Roughly the same reason gzipping an mp3 doesn't get you much.
1 reply 0 retweets 0 likes -
Of course more advanced analysis is possible, but there are development and runtime costs, hopefully high.
1 reply 0 retweets 0 likes
I don't claim this is a fully-developed solution, just a possible framework for how it could be done.
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.