signald
axolotl
Our great sponsors
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.
signald
-
Critical New 0-day Vulnerability in Popular Log4j Library - List of applications
Signald : https://gitlab.com/signald/signald/-/issues/259
- signald - A daemon that facilitates communication via Signal Private Messenger. Unofficial, unapproved, and not nearly as secure as the real Signal clients.
-
Signald: Unofficial Daemon for Interacting with Signal
This is neat.
I looked at the install instructions ("from source") and i while there were instructions, there was no download link for the tarball or even the git repository.
You have to click on the "gitlab" widget that shows the number of stars on the start page to get to the gitlab repository at https://gitlab.com/signald/signald
-
starting a native adaptive Linux client for Signal
I've been using Signald for the last few months and then bridging it to Matrix. I think building exactly the same thing based off the Rust client is the most compelling option (and probably something I'd be interested in working on as well!). Given that a double-puppeted Signal account can be used with Matrix today, it'd be a shame to invest in Signal-specific UI. There are multiple "nearly there" Matrix clients that can work on the pinephone and others. You could even bridge libpurple to Matrix if you're into that ecosystem.
- PinePhone Beta
-
Signal API
As Signal does not have a real API, it uses signald for communication with Signals server, which is also open source: https://gitlab.com/signald/signald
-
Is Elon Musk right about Signal? I need your Help!
It looks like you just need a client that uses https://gitlab.com/signald/signald, and the matrix-signal bridge /u/anakinfredo posted is one of them.
-
An implementation of the Signal client protocol in Rust
When I wanted to use Signal on my PinePhone and realized how restrictive Signal was in a lot of ways I started looking at Matrix. Matrix feels a lot more like what chat "should" be, if it weren't for reality - there's an existing Java client (https://gitlab.com/signald/signald) that I've used for a few weeks and been impressed with. Now I bridge my Signal account to Matrix as the first step towards migrating away.
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.
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
gomuks - A terminal based Matrix client written in Go.
SmsMatrix - A simple SMS <--> Matrix bridge.
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.
libsignal-service-java - A Java/Android library for communicating with the Signal messaging service.
nheko - Desktop client for Matrix using Qt and C++20.
semaphore - A simple (rule-based) bot library for Signal Private Messenger.
org.signal.Signal