Signal-iOS
Converse.js
Our great sponsors
Signal-iOS | Converse.js | |
---|---|---|
130 | 17 | |
10,442 | 3,011 | |
0.6% | 0.4% | |
10.0 | 9.2 | |
4 days ago | 3 days ago | |
Swift | JavaScript | |
GNU Affero General Public License v3.0 | Mozilla Public License 2.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-iOS
- Signal 7.0 released for iOS – Private Phone s
- Police Can Spy on Your iOS and Android Push Notifications
- 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...
-
Telegram raises $210M through bond sales
I also use both extensively and I agree, Telegram has the best UX of any messaging app. The desktop app is QT I think so it feels very snappy compared to Signal's electron app.
Signal's iOS app is a native Swift/UIKit app and open source however, so I'd encourage you to report any bugs or issues you find: https://github.com/signalapp/Signal-iOS
-
App crashes on open | iOS 16.5 | will stop donation
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).
- I have absolutely had it with Signal (lack of basic backup options)
-
Rewriting the Messenger codebase for a faster, smaller, simpler messaging app
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.
- Camera quality during video call
Converse.js
- ConverseJS 10.1.7 with an important XEP-0474 support fix used in ejabberd – XMPP
-
How to build an AI chatbot with Openfire and OpenAI Chat Completion
ConverseJS is a popular Javascript XMPP client that implements a full range of XMPP extensions. Also available as a plugin for openfire — inverse-openfire-plugin and can be installed on openfire with a few clicks.
- Converse.js 10.1.2
-
An actually private messaging self hosted server
I agree. IMHO the best variant is then to use something that is truely free. Like XMPP. There are a lot of servers and many clients to chose from and I can strongly recommend converse.js as a web client. It supports different ways of end to end encryption but I would recommend OMEMO which is basically the same encryption idea that you find in Signal.
-
Xmpp Bot with its own address.
Hello, I recently started exploring xmpp, with snikket app and conversejs.org
-
Matrix was worth the effort to self host.
It is Converse.js (https://conversejs.org/) packaged into a one-click install for openfire (from the web admin). So, one-click install for an xmpp web client.
-
Ask HN: What is your recommended stack for real time chat?
My choice, because it's the stack I know very well, would be Prosody ( https://prosody.im/ - I'm one of the devs) and a web client such as Converse.js ( https://conversejs.org/ ). XMPP is highly extensible, Prosody is highly modular, which make them a good foundation for building on top of.
That said, the right stack is generally the one that matches your requirements, and (if this isn't primarily a learning exercise) whatever you're most familiar with. The hardest part of building a Discord or Slack-like in 2022 is actually not the technical stuff. There are many comprehensive open-source products already out there that compete with these companies, such as Mattermost, RocketChat and Element.
-
No white list registering with conversejs.org
Tried to register with conversejs.org today and got an error "your IP is not whitelisted".
- Best open source protocol to fork?
-
NEEE HELP!
Maybe you are remembering this bug from some months ago? It appeared exactly as if this was (accidentally) uploading keys to the user's XMPP server (not Converse.js's server) and publishing them.
What are some alternatives?
mollyim-android - Enhanced and security-focused fork of Signal.
JSXC - :speech_balloon: Real-time xmpp chat application with video calls, file transfer and encrypted communication.
simplex-chat - SimpleX - the first messaging network operating without user identifiers of any kind - 100% private by design! iOS, Android and desktop apps 📱!
Movim - Movim - Decentralized social platform
LibreSignal - LibreSignal • The truly private and Google-Free messenger for Android.
Candy - JavaScript-based multi-user chat client for XMPP.
wire-ios - 📱 Wire for iOS (iPhone and iPad)
Kaiwa - [UNMAINTAINED] A modern XMPP Web client
Unigram - Telegram for Windows
Kontalk - Kontalk official Android client
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
CHVote - Electronic vote system, version 1.