Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
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". (by tw-hx)
Even if the Signal Foundation turned evil and changed its non-profit status, it would immediately loose its assets. The source code would be available under GPL V3, so anyone would be able to fork and distribute the "good" Signal. The Foundation does not have much user data or means to collect user data. All employees (less than 40 people) are basically privacy and security activists, who would leave the company the moment it goes sour.
That being said, we can see that a lot of things are coming from OWS recently. The Rust lib is mature, and a binding to nodejs just appeared in your repository. Also, the desktop client is greatly improving, now allowing calls etc, and it is built using web technologies embed in electron. That could be reused easily, even if it doesn't support ARM (yet).
Here's a quote from the Signal CEO about their stance on decentralization and modifying the client source code 0.
Is there a public roadmap for the open source work I could follow/subscribe to? Really interested in the Node client: https://github.com/signalapp/libsignal-client-node. If not I could just turn on some release notifications for GitHub.
I would love to see a bot api, like the one telegram has. See here and here. Are there any plans on this regard? Are pull requests related to this welcome?
Generally using the best matrix client for the current purpose: gomuks, nheko, neochat, element, hydrogen, curl, python, etc.
Please just take the Flatpak build available here: https://github.com/flathub/org.signal.Signal and build/sign/host it yourselves.
It means that there is a specific section defined in the Tox ID for use with spam. So, you can give out your Tox ID to everyone, but essentially revoke it for some people. You can see some documentation here: https://github.com/wdbm/dendrotox#tox
However, I also stopped using Android (and never used iOS) due to privacy issues and I am now an Ubuntu Touch user. Signal isn't available on that OS and I don't expect it to be officially available there due to the small number of users (yet), but I didn't want to stop using it, so, thanks to the sources being open, with other contributors we built Axolotl, an unofficial Signal client for GNU/Linux (working on desktop and mobile distribution). It is a full client : unlike the official Signal desktop, it allows you to register and manage your contacts.
Did I say Fdroid? sorry I meant FOSS, here is the link https://github.com/tw-hx/Signal-Android/
Related posts
- Webinstall.dev – install developer tools effortlessly
- Webinstall: Effortlessly install developer tools with easy-to-remember URLs
- Simulate an Ubuntu-like VM inside macOS
- GPSBabel: Convert, upload, download data from GPS and Map programs
- Is macOS’s new XProtect behavioural security preparing to go live?