Don't need HTTPS if everyone agrees to not intercept your traffic. 
Idiot threatening to sue over an article about his insecure app sends us confirmation his software can be MITM'd. Sunk by his own hand 
pic.twitter.com/6wfDAEgc0y
-
Thanks. Twitter will use this to make your timeline better. Undo
-
-
-
Let it go, dude. Next time, use strong HTTPS and cert pinning for backend connections.
-
No. You made a major error. How deceptive not showing the full picture. Being honest is better than deceptive. You did not take me seriously
-
Tweet unavailable
-
HTTPS and cert pinning would have stopped that attack but the problem was more dumb: parsing untrusted JavaScript in a privileged context.
- End of conversation
New conversation -
-
It's a good job people never use insecure public wifi.
Thanks. Twitter will use this to make your timeline better. Undo -
-
Where is the article? Been searching but not finding anything.
New conversation -
-
Oh do I even need to guess this is Simon's bullshit? heh
Thanks. Twitter will use this to make your timeline better. Undo -
If you look closer you will see that "Simon Smith" and his "security" pops into existence on May 7 2017. Before that mostly nothing.
Thanks. Twitter will use this to make your timeline better. Undo -
There are still people that don't use HTTPS?!
Thanks. Twitter will use this to make your timeline better. Undo -
it would've been by his own hand, but someone else's hand got in the middle
Thanks. Twitter will use this to make your timeline better. Undo
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.