signalbackup-tools
Synapse
Our great sponsors
signalbackup-tools | Synapse | |
---|---|---|
38 | 367 | |
664 | 11,720 | |
- | - | |
9.4 | 9.8 | |
5 days ago | 5 months ago | |
C++ | Python | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
signalbackup-tools
-
Autogenerating a Book Series from Three Years of iMessages
I just do a research and there is a GitHub repo. Will try it later.
https://github.com/bepaald/signalbackup-tools
- Signalbackup-tools: Tool to work with Signal Backup files
- Signal Backup Tool
-
Backup messages
If you'd like to browse your backup file on the desktop, I recommend using an external tool, like this
-
to signal software engineers, data preservation, full fidelity html export of all conversation
signalbackup-tools seems to be the best at getting the data out into something more usable, and seems to still be actively developed.
-
Backup to PDF
Thank you! If this one won't work, I also have this here, hahaha. https://github.com/bepaald/signalbackup-tools Still trying to get anything to work, but there must be a way.
- Offline chat backup
-
Extracting Signal conversations
Signal is actually one of the easier ones to work with without even needing to obtain a full extraction of the phone. https://github.com/bepaald/signalbackup-tools
-
View .backup file outside of Signal
Maybe https://github.com/bepaald/signalbackup-tools
-
Is there some way to create an archive of all my messages that I can view outside of Signal?
This github link works for windows Github
Synapse
-
Organizing OpenStreetMap Mapping Parties
What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.
Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).
If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.
-
GrapheneOS is moving off Matrix
some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...
-
Non-profit Matrix.org Foundation seems to be moving funds to for-profit Element
Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.
This is honestly really disappointing behaviour from a platform owner.
[0]: https://github.com/matrix-org/synapse/issues/14481
-
The Future of Synapse and Dendrite
> That doesn't make this situation any less bad to the rest of the community.
How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.
You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.
And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.
The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.
[0]: https://github.com/matrix-org/synapse/graphs/contributors
- Synapse v1.95.0 Released
- Matrix Synapse how use python scripts?
- Synapse v1.91.2 Released
- Synapse v1.89.0 is out
- Synapse v1.88.0 is out
- Synapse v1.87.0 (Matrix Server) Released
What are some alternatives?
signal-backup-exporter - Python-based Signal app backup exporter.
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
signal-back - Decrypt Signal encrypted backups outside the app
conduit
signal-export - Export your Signal chats to markdown files with attachments
Rocket.Chat - The communications platform that puts data protection first.
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 picker. Option to treat view-once media as normal media. Option to ignore remote deletion. Choose between FCM or websocket notification delivery.
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
signal-backup - Signal-backup is a python3 script to backup signal conversations, as html pages.
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
pakadali - Basic services for developers including placeholder generation, QR code generation
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker