Closed Diapolo closed 8 years ago
I verified current master with upstream master and wasn't able to find strange code in it (remember I'm not a Java dev at all ^^). If I found something I didn't understand I commented in the source or in older pulls, so perhaps some of you guys get some mails from GitHub ;).
Closing in favor of https://github.com/JavaJens/TextSecure/issues/72.
I'd love to see a more verifiable and more transparent process to keep this repo up-to-date with master and also would love to better understand if other patches appart from websocket support get merged and so on.
So perhaps we could start discussing in this issue to get ahead with the above. You all could add further suggestions, outline problems and all that. I'd like to help this fork, as long as Moxie refuses to integrate websocket support into the upstream master.