SaaSHub helps you find the best software and product alternatives Learn more →
Quiet Alternatives
Similar projects and alternatives to quiet
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
real-world-onion-sites
This is a list of substantial, commercial-or-social-good mainstream websites which provide onion services.
-
alternative-front-ends
Overview of alternative open source front-ends for popular internet platforms (e.g. YouTube, Twitter, etc.)
-
-
kubo
IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API
-
superhighway84
Discontinued USENET-inspired, uncensorable, decentralized internet discussion system running on IPFS & OrbitDB (https://tty.fail/mrus/superhighway84)
-
-
-
-
-
-
-
-
-
denarius
Denarius [$D] is a PoW/PoS Hybrid Cryptocurrency with Tribus a new PoW Hashing Algo built specifically for D, one of a kind hybrid masternodes called Fortuna Stakes, atomic swaps, staking, mining, IPFS, optional Native Tor and I2P, and much more!
-
-
-
-
auth
Discontinued Decentralized authentication and authorization for team collaboration, using a secure chain of cryptological signatures. (Formerly known as 🌮 Taco.) (by local-first-web)
quiet discussion
quiet reviews and mentions
-
Filecoin Foundation Successfully Deploys IPFS in Space
> because, right here right now, that is such a hypothetical situation that I have absolutely no idea why it needs a real-world demonstration of proof of concept using currently-available technology.
So I just want to point out that IPFS was fairly deliberately designed to have numerous, forward-compatible features that could be swapped out in the future : like https://multiformats.io/ and in particular https://multiformats.io/multiaddr/ .
In the IPFS community, there's always been a fairly heated discussion about which bit of the entire system should be stuck with the term IPFS. Like, if you took away the libp2p protocol, and just served CIDs over http, would it be IPFS? What if you took away CAR files (the merkle-tree file format used to define multi-item content)? What if you're a private IPFS network, with no shared nodes with the public network (like https://github.com/TryQuiet/quiet ). What if you didn't use bitswap, the file transfer protocol (Filecoin doesn't use bitswap, and mostly doesn't interconnect with the main public IPFS network). What about if you didn't use a DHT to find providers of a CID. What if you're not using any of the "IPFS" software stack, but your implementation still uses bits and pieces of content-addressability as defined in the standard?
Interestingly, right now, there are a bunch of experiments going in all of these directions: I think it's fair to say that if you wanted to test out content-addressable networks across the solar system, they probably wouldn't be IPFS as it is now, but their nature could probably be described using the primitives the IPFS stack uses, and learning about what needs to change would give a useful direction to some part of the extended IPFS ecosystem.
-
Anyone using decentralized slack alternative called Quiet?
Their website is at https://www.tryquiet.org
- Open source P2P alternative to Slack and Discord built on Tor and IPFS
- Quiet – A private, P2P alternative to Slack and Discord built on Tor and IPFS
-
Tor’s shadowy reputation will only end if we all use it
My team is building Quiet, an alternative to team chat apps like Slack and Discord that works as you describe:
https://github.com/TryQuiet/quiet/#readme
> Granted, sending a message would require all parties to be online at the same time, but there could be a set of relay servers to hold messages until they get fetched.
We actually do a bit better than this! We use a gossip network (libp2p gossipsub) so all peers don't have to connect directly, and a CRDT over a private IPFS network so that everyone in a community eventually syncs all messages. As long as there's a continuity of online peers, the availability of messages is the same as a central server, and with a few Android users in the mix it's pretty easy to get to that level of continuity.
(The battery impact of staying connected all the time isn't as bad as you'd think, and we haven't even begun to optimize it.)
And yes, it builds on the maturity of Tor rather than trying to roll its own onion routing layer as Session is doing.
-
A note from our sponsor - SaaSHub
www.saashub.com | 11 Nov 2026
Stats
TryQuiet/quiet is an open source project licensed under GNU General Public License v3.0 only which is an OSI approved license.
The primary programming language of quiet is TypeScript.