Standalone Signal Desktop
101–110 of 320 posts
Re: Standalone Signal Desktop
#102Design is somehow looking related to Telegram...
Chrysler shouldn't make their tires square just because Ford was first to the circle.
I'm happy they're not burning cycles reinventing the wheel.
Re: Standalone Signal Desktop
#103> Linux distributions supporting APT, like Ubuntu or Debian Oh come on guys. Don't forget Fedora. Fedora means SELinux. SELinux means you are getting the people who value security.
I think you underestimate the number of people whose first post-installation task is setenforce 0
Re: Standalone Signal Desktop
#104Earlier quoted context omitted.
No.
This comment is not helpful.
source https://gizmodo.com/why-you-should-stop-using-telegram-right...
Re: Standalone Signal Desktop
#105Another 205MB Electron App to the collection, at least it's 50MB smaller than Wire.
eul is a light (4 MB) native desktop client for all popular messengers: https://eul.im Signal support is coming later this year. Right now it supports Slack, Skype, Facebook, and Gmail.
Re: Standalone Signal Desktop
#106Why no web app? Moxie closed https://github.com/WhisperSystems/Signal-Desktop/issues/723 without giving any reasoning. Can someone link me to a blog post that explains why Signal is refusing to release a web version? I cannot run another Electron app on my computer, I simply do not have the RAM left. Signal as a web-app would allow me to put it inside of Franz or Rambox, where all my other chat services live. Right n…
Not sure what I'm missing here, but I see Signal using 37.5MB of memory. That doesn't seem egregious, but I'm also not familiar with what other Electron apps use.
A fresh launch without logging in or having it run for any period of time immediately uses 211.2MB:
1. Signal: 58.3MB
2. Signal Helper: 128.6MB
3. Signal Helper: 24.3MB
After logging in and starting a few conversations I quickly see the total rise to over 350MB.Re: Standalone Signal Desktop
#107Earlier quoted context omitted.
You mean Facebook?
They are referring to companies like GitHub [1] and Slack [2]. [1] https://githubengineering.com/how-four-native-developers-wro... [2] https://slack.engineering/growing-pains-migrating-slacks-des...
Re: Standalone Signal Desktop
#108Using Electron is a bad idea: it's not secure. Electron has many security vulnerabilities. The latest version is still based on old Chromium (58 & 59) so it inherits many of the security vulnerabilities published in Chromium 60, 61 and 62
https://chromereleases.googleblog.com/2017/07/stable-channel...
https://chromereleases.googleblog.com/2017/09/stable-channel...
https://chromereleases.googleblog.com/2017/10/stable-channel...
Re: Standalone Signal Desktop
#109Earlier quoted context omitted.
> I am very privacy conscious How did you evaluate Telegram to decide that you trust it?
I don't trust them, it's just that I can use them. The real problem is requiring a smartphone.
Re: Standalone Signal Desktop
#110Why no web app? Moxie closed https://github.com/WhisperSystems/Signal-Desktop/issues/723 without giving any reasoning. Can someone link me to a blog post that explains why Signal is refusing to release a web version? I cannot run another Electron app on my computer, I simply do not have the RAM left. Signal as a web-app would allow me to put it inside of Franz or Rambox, where all my other chat services live. Right n…
The service (either intentionally or by virtue of being hacked) can serve up Javascript crypto code that either uploads plaintext, or subtly backdoors the crypto so it can be decrypted. And they can do this to just a single user, so unless you audit the Javascript every single time you load the page, you'd never know.
A signed app is more secure, because a backdoor would have to be distributed to everyone, greatly increasing the chances of it being discovered.