Privacy-preserving offline delivery (avoiding all metadata) is a hard problem.
For now, the @cwtch_im groups experiment makes use of slow but explicitly untrusted servers that learn nothing about the messages they host.
Making them trivial to self-host is a critical goal:
For now, the @cwtch_im groups experiment makes use of slow but explicitly untrusted servers that learn nothing about the messages they host.
Making them trivial to self-host is a critical goal:
https://twitter.com/OpenPriv/status/1459214054728220676
If you read our recent roadmap update carefully you might have surmised that there are two main directions of work taking place @cwtch_im
1. Development of protocols that avoid intermediate hosting (hybrid groups)
2. Making shared infrastructure as simple to host as possible.
1. Development of protocols that avoid intermediate hosting (hybrid groups)
2. Making shared infrastructure as simple to host as possible.
Certain features and use cases will always require some form of offline-delivery, so we need to provide options e.g.
1. Host an always online p2p bot (trusted and quick)
2. Use one of many public, decentralized server instances (private and untrusted but slow)
1. Host an always online p2p bot (trusted and quick)
2. Use one of many public, decentralized server instances (private and untrusted but slow)
Either of those options require making self-hosting of infrastructure as accessible, easy and as trivial as possible.
The server hosting experiment in @cwtch_im beta 1.4 is the start of building out that functionality.
The server hosting experiment in @cwtch_im beta 1.4 is the start of building out that functionality.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
