Synapse
TextSecure
Our great sponsors
Synapse | TextSecure | |
---|---|---|
367 | 985 | |
11,720 | 24,864 | |
- | 0.7% | |
9.8 | 9.9 | |
4 months ago | 6 days ago | |
Python | Java | |
Apache License 2.0 | GNU Affero General Public License v3.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.
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
TextSecure
-
The xz sshd backdoor rabbithole goes quite a bit deeper
Moxie's reasons for disallowing Signal distribution via F-droid always rang a little flat to me ( https://github.com/signalapp/Signal-Android/issues/127 ). Lots of chatter about the supposedly superior security model of Google Play Store, and as a result fewer eyes independently building and testing the Signal code base. Everyone is entitled to their opinions, but independent and reproducible builds seem like a net positive for everyone. Always struggled to understand releasing code as open source without taking advantage of the community's willingness to build and test. Looking at it in a new light after the XZ backdoor, and Jia Tan's interactions with other FOSS folk.
- WhatsApp forces Pegasus spyware maker to share its secret code
-
Signal: Keep your phone number private with Signal usernames
Signal has documentation on how to reproduce their Play Store builds and compare them with what you've installed locally:
https://github.com/signalapp/Signal-Android/blob/main/reprod...
-
Signal v7.0.0 with phone number privacy
There's nothing on Signal blog as of yet, but Signal's git repository was tagged with v7.0.0 yesterday and we can see from the commit history since the previously tagged version (v6.74.4) that there will be a setting to hide one's phone number [1], as well as disabling the previous default behavior of advertising that one is on Signal to all their contacts already using it [2].
[1] https://github.com/signalapp/Signal-Android/commit/8797236b5... (PNP stands for "Phone Number Privacy")
[2] https://github.com/signalapp/Signal-Android/commit/6097e6c30...
-
What are you shocked people are still doing nowadays?
Signal works the same but without the user tracking from Meta/Facebook. Many people use it as well but I'm surprised that a majority sticks to WhatsApp.
-
Apple has seemingly found a way to block Android’s new iMessage app
Telegram and Signal solve this.
-
Apple Just Confirmed Governments Are Spying on People’s Phones With Push Notifications
Sadly yes: Looks like an open issue 13290 for Signal, sounds like they were/are indeed still interacting through google's push notification service, wat, and per a link at that issue it was a chore for Tutanota to break away once they realised it was a problem some years ago (though at least they thought about it years ago? wtf Signal...)
-
Building end-to-end security for Messenger – Engineering at Meta
Here is one: https://github.com/signalapp/Signal-Android/tree/main/reprod...
- Are Signal Notifications Encrypted ?
-
Facebook & Messenger finally get end-to-end encryption
Rule 1: Posts to r/signal must relate to Signal.
What are some alternatives?
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
undiscord - Undiscord - Delete all messages in a Discord server / channel or DM (Easy and fast) Bulk delete
conduit
Signal-TLS-Proxy
Rocket.Chat - The communications platform that puts data protection first.
duckduckgo-locales - Translation files for <a href="https://duckduckgo.com"> </a>
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
session-desktop - Session Desktop - Onion routing based messenger
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
MaterialAudiobookPlayer - Minimalistic audiobook player
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
TelegramAndroid - Fork client of Telegram app for Android.