Synapse
Synapse | ||
---|---|---|
24 | 367 | |
1,178 | 11,720 | |
1.8% | - | |
8.6 | 9.8 | |
19 days ago | 5 months ago | |
Go | Python | |
GNU Affero General Public License v3.0 | 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.
- Open Letter to WhatsApp: Need for a Linux Desktop App
-
Show HN: Beeper Mini – iMessage Client for Android
The best you can do now is run whatsapp apk on an emulator or spare device, then auth that with the matrix bridge, then you can avoid needing to use whatsapp clients on daily drivers. Works decently well: https://github.com/mautrix/whatsapp
-
Whatsapp for KaiOS 3+
For WhatsApp, there's a thing called 'bridges' that can link your WhatsApp chats to other chat services that you can access from the device. One example is this bridge that bring chats to open-sourced Matrix protocol, which you can use Hydrogen browser interface to access on the phone. Another bridges to a Discord server that might suit well with this community-made interface.
- Selfhosted application for joining chat services?
- Neue EU-Regel: WhatsApp muss sich für alle Messenger öffnen
-
Anyone heard of WhatsApp Web To Go?
I suggest you to take a look at matrix and its bridges, like Mautrix Whatsapp. If you don't have competence / time to setup a matrix server, Element Matrix Services host it for you, and you can use WhatsApp, telegram and signal all with a client, without tracking or shitty things from fb
-
Welcoming Rocket.Chat to Matrix
I use it as a one-stop-shop for messaging. I setup a Synapse server ~5 years ago and since then have convinced many of my close family and friends to join my server (or another). Now many of the folks I want to chat with are regular users of Matrix. For some of my stone-age friends that are still on WhatsApp, I run a bridge [1] so that I don't need to look beyond my Matrix client to see WhatsApp messages. For other random SMS messages, I use the dated SmsMatrix [2] to push text messages so I can see/reply from Matrix. Beyond that, I also use Matrix to connect to several open source communities (e.g. Mailu.io [3]).
1. https://github.com/mautrix/whatsapp
-
Mautrix-whatsapp configuration
you might be looking for this? https://github.com/mautrix/whatsapp/blob/master/example-config.yaml
- PinePhone community poll results | PINE64
-
The people deciding to ditch their smartphones
One option could be to have an old phone tuning android WhatsApp and enable the multi-device beta to use that for web access and access on that other phone, although I don't know if they support the multi device feature either. If you're somewhat technical you could also use an android VM instead of a physical phone, and if you're comfortable with self hosting docker you can use the matrix whatsapp bridge to use WhatsApp without having to install it on your device. https://github.com/mautrix/whatsapp and https://github.com/spantaleev/matrix-docker-ansible-deploy
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?
whatsmeow - Go library for the WhatsApp web multidevice API
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
conduit
whatsie - Feature rich WhatsApp Client for Desktop Linux
Rocket.Chat - The communications platform that puts data protection first.
Shelter - A Free and Open-Source (FOSS) app that leverages the "Work Profile" feature of Android to provide an isolated space that you can install or clone apps into.
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
SchildiChat-android - Matrix client / Element Android fork
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
maubot - A plugin-based Matrix bot system.