Signal-Desktop
Signal-iOS
Our great sponsors
Signal-Desktop | Signal-iOS | |
---|---|---|
322 | 130 | |
13,954 | 10,414 | |
0.7% | 0.8% | |
9.9 | 9.9 | |
6 days ago | 3 days ago | |
TypeScript | Swift | |
GNU Affero General Public License v3.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Signal-Desktop
-
Privacy is Priceless, but Signal is Expensive
If you only have the phone app then yes they are instantly downloaded and removed from their servers.
But if you have Desktop client(s) registered, then they need to hold onto those messages until you open your client(s).
That is why they have a 2 week (from memory) login limit on Desktop clients. If they didn't they'd potentially have to hold onto messages forever.
Love the product. Had a monthly recurring donation for many years. Dropped it over what I consider to be their serial mishandling of open source. See https://github.com/signalapp/Signal-Desktop/pull/6186 for the latest chapter in the, "we won't implement desktop GIPHY that we announced in 2016, and also won't merge it when someone else thoughtfully implements it for us" saga.
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].
[0] https://github.com/electron/electron/pull/39824
-
Signal Desktop messaging app having trouble with IPv6
Issues have been ongoing for the past couple weeks. It's not clear if this is the client or backend. Dual stack works again with v6.20.2, but IPv6-only with NAT64 still doesn't. Actively being worked on, and hopefully some good learnings. Issue link thread: https://github.com/signalapp/Signal-Desktop/issues/6439
-
Desktop Client takes minutes to send messages
Fix1, Fix2, Fix3, Fix4
-
Please help me to clone project locally
not able to do so after going through the CONTRIBUTING.md and following each and every step i am getting this error tried to search it on google and asked chatgpt too still not able to figure out
the CONTRIBUTING.md has steps using yarn tried using npm also still not able to do so
-
Testing a new encrypted messaging app's (Converso) extraordinary claims
Compare https://github.com/signalapp/Signal-Desktop/commits/main with https://github.com/DrKLO/Telegram/commits/master
Signal-iOS
- Police used Cellebrite to break into my phone, how do I prevent this in the future?
-
Governments spying on Apple, Google users through push notifications -US senator
Fortunately, they did foresee this! The push notification only contains enough information to tell the phone that it should fetch the actual notification content from Signal's servers.
Here's a Signal dev talking about it on the Signal-Android GitHub: https://github.com/signalapp/Signal-Android/issues/12961#iss...
And similarly for Signal-iOS: https://github.com/signalapp/Signal-iOS/issues/962#issuecomm...
-
Privacy is Priceless, but Signal is Expensive
This was a nice, detailed read. I was happy to note this about employee compensation since paying them well is a good thing apart from their personal motivation to work on this (even at a comparatively lower pay than in other companies/projects):
> When benefits, HR services, taxes, recruiting, and salaries are included, this translates to around $19 million dollars per year.
> We are proud to pay people well. Our goal is to compensate our staff at as close to industry wages as possible within the boundaries of a nonprofit organization.
That said, I really dislike Signal for a few reasons. The first is what many people have already talked about very often — forcing to use a phone number to register. Since the SMS or call costs are quite high, Signal could adopt the iMessage approach to verification, which is having the user send an SMS to the service (this will cost the user some money depending on which country the SMS is sent to). This could be decided based on the country code so that the current SMS OTP model can coexist.
Signal is obstinate on a few aspects on user experience, more so on iOS/iPadOS. Firstly, it refuses to provide a data backup mechanism for iOS/iPadOS. If someone loses their devices, there is no way to restore older messages. Even setting up a new device requires the old device to be in physical proximity to transfer the data. Signal does integrate with CallKit (to act like a phone app) and with Apple’s notification services, but refuses to allow the user to backup the data with a password to encrypt it.
Secondly, I found this paragraph in this post to be disingenuous:
> Such practices are often accompanied by “growth hacking” and engagement maximization techniques that leverage dark patterns to keep people glued to feeds and notifications. While Signal is also free to use, we reject this kind of manipulation, focusing instead on creating a straightforward interpersonal communications app. We also reject business models that incentivize such practices.
Signal on iOS/iPadOS wants the user to enable notifications and to share contacts. If notifications are disallowed and if contacts upload is disallowed, it will pester every few days about it. One might think this is a silly mistake that Signal isn’t aware of. But it was reported some years ago and Signal responded that it will not fix it because it believes this is the only way. [1] Not even an option where this is a toggle for those who want no notifications or don’t want to share contacts (Signal does have a toggle for contact joining notifications).
Signal is also not that reliable in delivering messages in a timely manner compared to other apps (the GitHub repo has many repetitive issues on this topic over all these years).
Finally, since Signal has poorer UX in general, which isn’t an easy or cheap thing to handle, I use it only with less than a handful of people who I know and who use it.
I’d donate occasionally so that Signal can continue to exist, but I don’t feel like supporting it every month with all these issues, some of which look like Signal showing me the middle finger.
[1]: https://github.com/signalapp/Signal-iOS/issues/4590#issue-72...
-
App crashes on open | iOS 16.5 | will stop donation
However, this is not unique to my setup, some others have opened a github issue as well https://github.com/signalapp/Signal-iOS/issues
Yeah I was able to find a few tasks that might be similar to your issue, though I don't know the exact details how the app behaves in your case, as in if you get error message or something like in this issue, or if it just closes on open like in this issue comment. Regardless, the generated crash report from the phone itself is probably good to add in your email to support (which is different from the debug log, just to specify in case you have been sending only that, here's a link for more details).
-
Rewriting the Messenger codebase for a faster, smaller, simpler messaging app
Can anyone shed light on where the complexity is coming from? Even 360kloc for a chat client seems excessive - its original size, 1.7Mloc, is hard to accept. How does it break down - e.g. 120kloc UI, 120kloc networking/data, and 120kloc other?
(For comparison I dl'd https://github.com/signalapp/Signal-iOS and ran cloc. It's about 400kloc of Swift, so I guess it's in the ballpark. I just wouldn't have guessed it was so big, and I'd like to know why.)
My bet is on "object-oriented obfuscation" and bloat caused by "modern" coding styles. Looking through the Signal source you linked to, I see tons of the former. There is an absolutely insane amount of boilerplate-looking code in here, for example: https://github.com/signalapp/Signal-iOS/tree/main/Signal/src...
I don't know Swift or the iOS UI API, but a lot of that code seems to be manually creating and positioning UI elements and otherwise implementing UI functionality that I'd expect the OS to handle. It's a lot of code that should really be data (arrays, structures).
To offer a huge contrast, a long time ago I wrote an MSNP chat client in pure Win32, and it was around 2kloc. The binary was 24KB. Of course it only supported contacts, presence, and text messaging, but I still can't see features like audio/video or the crypto that Signal has needing 100x more, especially if they use OS functionality for much of them.
-
Voice messages are not using headphones microphone
GitHub link: https://github.com/signalapp/Signal-iOS/issues/5399
- Signal will exit the UK rather than comply with onerous new restrictions on end-to-end encryption
What are some alternatives?
mollyim-android - Enhanced and security-focused fork of Signal.
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
axolotl - A Signal compatible cross plattform client written in Go, Rust and Vuejs
session-desktop - Session Desktop - Onion routing based messenger
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
webclient - Angular webclient (with Linux, macOS and Windows desktop clients) for CTemplar's encrypted email service.
simplex-chat - SimpleX - the first messaging network operating without user identifiers of any kind - 100% private by design! iOS, Android and desktop apps 📱!
telegram-bot-api - Telegram Bot API server
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
nodegui - A library for building cross-platform native desktop applications with Node.js and CSS 🚀. React NodeGui : https://react.nodegui.org and Vue NodeGui: https://vue.nodegui.org
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
Signal-Android - Patches to Signal for Android removing dependencies on closed-source Google Mobile Services and Firebase libraries. In branches whose names include "-FOSS". Uses new "foss" or "gms" flavor dimension: build with "./gradlew assemblePlayFossProdRelease".