libsignal
axolotl
libsignal | axolotl | |
---|---|---|
24 | 21 | |
2,952 | 315 | |
3.3% | - | |
9.8 | 9.0 | |
2 days ago | 8 days ago | |
Rust | Rust | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
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.
libsignal
- Police used Cellebrite to break into my phone, how do I prevent this in the future?
- EU haluaa kieltää vahvan salauksen - vaatii takaportteja viestisovelluksiin
- Signal has begun it's transition towards post-quantum key exchanges
-
libsignal-go built for go1.20+
I am in the process of building a Go implementation of the libsignal-protocol, which powers the Signal app.
-
End-to-end encrypted messages need more than libsignal
How is twitter intending to use libsignal? I doubt it would be via the primary AGPL license[1], forcing them to publish the source code of their server source code. Does signal sell private licenses?
[1] https://github.com/signalapp/libsignal/blob/main/LICENSE
-
Twitter Will Adopt Signal Protocol for Encrypted DMs
The Signal Protocol is licensed under AGPLv3 (see here).
Signal protocol is AGPL3 https://github.com/signalapp/libsignal
- Twitter to Encrypt Direct Messages Using Signal Protocol, Shows Code
- Elon Musk says he wants 'Twitter 2.0' to have video chat, voice calls, and encrypted DMs — and has enlisted the help of Signal's founder
-
Snap Store administrators removed signal-desktop from Ubuntu Snap
This is the license for libsignal: https://github.com/signalapp/libsignal/blob/main/LICENSE
The only reference to trademark is:
> Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
axolotl
-
Is anyone really using this?
While searching around a bit more I found another unofficial Signal client for arm64 Linux optimized for mobile called Axolotl. The github page makes it look promising, but once installed I couldn't log in successfully. I intend to put more effort in there. Axolotl appears to be the most promising looking option for Signal on mobile Linux - assuming it works..
- Axolotl.chat - First cross-platform Signal client
-
Axolotl: First cross-plattform Signal client
> Only a small thing, but due to Signals strict phone-desktop pairing mechanism, when registering Axolotl, both phone and regular Desktop wont work anymore.
> Also, you cant use Axolotl on Desktop together with Signal mobile.
> After deleting the Axolotl registration I had to wait a while to be able to register on Signal again, I didnt loose any backups and my codes didnt change.
> Nonetheless a warning should be displayed at the beginning, that users wanting to use regular mobile (iOS, Android) and Desktop (Windows, macOS, Flatpak or Snap), they should use a second phone number for testing.
https://github.com/nanu-c/axolotl/issues/811
-
Why Not Signal?
>Signal also notably isn't self-hostable: there's no way to run your own signal server, and control your data. Marlinspike ruthlessly shuts down anyone attempting to build alternate clients or servers that could communicate with the main one.
That is perfectly wrong. As a maintainer of https://axolotl.chat, a third-party signal client initially built for Ubuntu Touch but which runs on almost everything now, I can tell you that our client is speaking without any problems to the official Signal servers, and also that the code of the server is available and is running fine, we used it to test our code.
-
Stories Are Coming to Signal
Wouldn't Signal Desktop be a way to make backups?
I moved my home directory to a new computer and Signal Desktop started like if something changed. Sure you lose your messages on your phone, but you can still access them on your computer if needed.
On a rooted Android phone, you could use oandbackup to backup Signal. If you care about these things, maybe consider using a rooted Android phone?
I agree with you on the centralized platform aspect and the use of phone number (which is both a blessing (this makes it easy for new users to join) and a curse). I also agree with you on Element's UX, but it's getting better and most people can use it fine. I have a few groups on both apps.
I personally prefer Element, which seems more open than Signal and which I can actually use correctly on the PinePhone. Axolotl [1] still needs some work.
[1] https://github.com/nanu-c/axolotl
- Signal experiences on any of the Linux-based phones
-
PureOS - a pure Linux phone experience
I think the best option to communicate through Signal will be Axolotl. Because the original desktop client of Signal might work as well but it's not optimized for touch input.
-
I just bought a PinePhone
If you go to the git repo for Axolotl (https://github.com/nanu-c/axolotl), you will see links to the deb among other formats.
-
starting a native adaptive Linux client for Signal
Ah well then I applaud you. :) Perhaps some ideas could come from past efforts like Axolotl, which I've had working in a basic way in the past.
What are some alternatives?
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
status-mobile - a free (libre) open source, mobile OS for Ethereum
GrapheneOS-Knowledge - This is a short description of some of the knowledge I've collected on GrapheneOS and some common questions I've been asked and my answers to them.
openpgpjs - OpenPGP implementation for JavaScript
signald
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
nheko - Desktop client for Matrix using Qt and C++20.
org.signal.Signal