Our great sponsors
-
Signal-Android
Fork from the JohanW fork of Signal, a private messenger for Android. It adds the option to import Whatsapp conversations. The purpose of this fork is to make the transition to Signal easier. It was created out of a personal need and might not be supported or extended in the long run. (by jukefoxer)
-
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.
-
Signal-Android
Fork from a private messenger for Android with extra options added: full backup and (partial, ony text) xml backup of messages. Restore can happen at any time, not only after a fresh install. Import SMS database. Import of (unencrypted) WhatsApp databases. Removed apk expire. Choose between passphrase protection and the Android screenlock. Choice for the backup location (internal or removable storage on Android < 11 (on 11 and higher this is already possible)). Set the maptype in the place picke (by johanw666)
-
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.
> The repository mentions [0] the Wassenaar agreement, and that I must consult with the laws of my country on whether I am allowed to import/use software which includes encryption algorithms developed in other countries.
> Wat?
> In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Internet and use encryption libs to talk via HTTPs. Is mentioning The Wassenaar Arrangement [1] in terms of software even necessary nowadays?
> Linux, Windows, MacOS - all have encryption libs built in (at least on the kernel level). They have been made in various countries, yet they are used all over the world. Do they fall under the terms of The Wassenaar Arrangement?
> --------
> [0] https://github.com/jukefoxer/Signal-Android/tree/feature/wa-...
> [1] https://www.wassenaar.org
It's also mentioned in the original signal repo.I guess they have their reasons to include it and the fork just left it there.
I've tried https://github.com/xeals/signal-back and it's 95% of the way there but could use more attention - maybe it's my backup but the xml-formatted convos were formatted differently than the ones that the sms backup/restore app emitted. I compared just to sanity check it would import correctly but currently I'm unsure if it's a good idea.
FWIW it's nice to have a plain text backup anyway, and a lot better than nothing. Maybe it works fine but I'd rather not import a backup that has "weird" results.
If the backup restore is a merge rather than a nuke and pave it might make sense to do whatever Molly[1][2] does to allow it to be installed alongside Signal, so it's install this, import from WhatsApp, then backup/restore without having to do the uninstall/reinstall dance.
[1] https://github.com/mollyim/mollyim-android
[2] https://news.ycombinator.com/item?id=25743852
I believe the Signal devs expressed a lack of interest in doing this since it would mean embedding secret Whatsapp encryption keys in Signal.
See: https://github.com/signalapp/Signal-Android/issues/1014
https://news.ycombinator.com/item?id=25686179
This fork has the ability to export to encrypted zip, plain text, and the full database [1]. There seems to be a general theme of the dev's not supporting export/import functionality [2].
[1] https://github.com/johanw666/Signal-Android
On that note, this feature - https://github.com/signalapp/Signal-iOS/issues/1567 - to allow bulk saving of media to my device also hasn’t been addressed.
Whatsapp allows media from specific chats to be auto saved to the iOS camera. It is a very important feature, not sure how these aren’t making the priority bar.
See: https://github.com/LibreSignal/LibreSignal/issues/37#issueco...