The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of signal.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning signal yet.
Tracking mentions began in Dec 2020.
signald
Posts with mentions or reviews of signald.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-13.
-
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.
What are some alternatives?
When comparing signal and signald you can also consider the following projects:
imessage - A Matrix-iMessage puppeting bridge
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.