{{ code }}111 |
{{ status }}113 |
23 | Welcome to Briefing. Yet another secure video chat. 24 |
25 |26 | Privacy is the driving force behind this project. It uses secure 27 | technologies like 28 | WebRTC 29 | to directly connect between participants. The website that provides the 30 | web app and mediates the communication stores as few data as possible 31 | and does not know anything about the contents of established 32 | conversations. No accounts are required. No cookies are used. 33 |
34 |35 | The difference between Briefing and most similar projects is, that it 36 | does not use a central server that distributes the video streams (SFU). The advantage of an SFU is that it saves bandwidth due to the fact 39 | that the own video does not being uploaded to each participant but only 40 | once. The SFU can also do more optimizations the clients might not 41 | support. But then the video signal is not end-to-end encrypted any more 42 | i.e. you have to trust the SFU provider. Briefing instead sends data 43 | from peer to peer directly ("Mesh") and therefore the data 44 | does not travel over the server under normal operation. The WebRTC peers 45 | however still trust the signaling server for the authenticity of the 46 | peer-to-peer communications encryption in place. 47 |
48 |49 | 50 | Learn more about details at 51 | github.com/holtwick/briefing 52 | 53 |
54 |56 | (C)opyright 2020-2023 by 57 | Dirk Holtwick | 58 | Privacy Policy | 59 | Imprint 60 |
61 |