ricochet
Synapse
Our great sponsors
ricochet | Synapse | |
---|---|---|
12 | 367 | |
3,680 | 11,720 | |
0.1% | - | |
0.0 | 9.8 | |
over 2 years ago | 4 months ago | |
C++ | Python | |
GNU General Public License v3.0 or later | 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.
ricochet
-
Open source P2P alternative to Slack and Discord built on Tor and IPFS
This looks like a much more polished alternative to Ricochet: https://github.com/ricochet-im/ricochet
-
Where is there a tutorial for Ricochet Relay?
Ricochet seems dead. It's been five years since its last commit to their git repo, and their website's certificate expired last year. This is probably why you can't find much information.
-
The Code the FBI Used to Wiretap the World
I think something like Ricochet (if it were still actively maintained) could be a good solution.
https://github.com/ricochet-im/ricochet
Every user is their own Tor onion service, so you get E2E encryption and no centralized servers. The whole thing hinges on the security of Tor itself which is probably a safe enough bet.
-
Ricochet reborn: A user friendly TorChat for everybody available for GNU/Linux and in the Mac Store and Windows Store.
With that being said, if I had just one piece of advice - try to avoid ostentatious phrases like Speek is by far the most secure way to converse or 100% anonymous. Tor itself is not 100% anonymous, so that should immediately make anyone cautious. One of the things that I admired about the original Ricochet was that the developers never made brazen claims about their software. In fact, quite the opposite.
-
How to build large-scale end-to-end encrypted group video calls
Check out https://github.com/ricochet-im/ricochet/blob/master/doc/prot.... It is metadata-free. It does not require a centralized server. It uses Tor.
-
Documents Shows Just How Much The FBI Can Obtain From Encrypted Communication Services
[1] https://cwtch.im/ [2] https://ricochet.im/
- Darknet chat
-
Why don't we have a privacy-compliant peer-to-peer communication platform yet? (something like the bittorrent of messaging and chat and blogs etc)
Abandoned, unmaintained, deprecated or unreleased: Ricochet, TOR Messenger, Cwtch
-
TOR Messenger
ricochet.im website not working (??)
-
A Statement on Recent Events Between Signal and the Anti-Censorship Community
> there isn't a currently easily available obvious way to have private secure conversations.
Ricochet[1] works really well. It uses Tor hidden services to communicate. Your Ricochet ID is your onion address. To add a contact, you input their Ricochet ID and a short message, and Ricochet connects to their onion address and sends a contact request. If the contact request is accepted then you'll each show up as a contact on each other's client and can chat whenever you want.
Tor is really perfect for this, you can't get more private or censorship-resistant than Tor.
The UI is currently not great, but that's not a protocol problem.
The biggest problem with Ricochet is that hardly anyone is using it.
[1] https://ricochet.im/
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?
Tox - The future of online communications.
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
session-desktop - Session Desktop - Onion routing based messenger
conduit
ricochet-refresh - Anonymous peer-to-peer instant messaging
Rocket.Chat - The communications platform that puts data protection first.
Speek - Privacy focused messenger that doesn't trust anyone with your identity, your contact list, or your communications
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
Signal-TLS-Proxy
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
jami-cli - Jami client for terminal
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker