News for hackers. Stuff that matters.
Re:Why I won't recommend Signal anymore by lucb1e on Sunday November 06, 2016 @05:53AM (#12884528)
> I invite those who have opinions about Signal to start by getting involved in the project.

Yeah we've been there. Do you remember someone on Github complaining about the Google dependency? You closed that issue as a wontfix. Or LibreSignal? I read the post where you basically told them to go away on Github too.

That's why I haven't recommended Signal ever since trying it myself a year or two ago.

Re:Why I won't recommend Signal anymore by lucb1e on Sunday November 06, 2016 @07:57AM (#12884874)
Downvotes but no comments. What is wrong with what I said?
Re:Why I won't recommend Signal anymore by haffenloher on Sunday November 06, 2016 @09:19AM (#12885167)
> You closed that issue as a wontfix

Not sure what you're talking about, because the issues in question, #127 and #1000, are open.

> you basically told them to go away on Github

Quite the opposite [1]:

"I would consider a clean, well written, and well tested PR for websocket-only support in Signal. I expect it to have high battery consumption and an unreliable user experience, but would be fine with it if it comes with a warning and only runs in the absence of play services."

[1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...