b25db3ce2e
Config.js will allow to specify both BOSH and Websocket URLs. In such case the web app will prefer Websocket over BOSH. The reason is that it appears to be more stable and a bit fast on web, while on mobile websocket is dropped fast(killed by the OS) on network changes. |
||
|---|---|---|
| .github | ||
| android | ||
| connection_optimization | ||
| css | ||
| debian | ||
| doc | ||
| flow-typed/npm | ||
| fonts | ||
| images | ||
| ios | ||
| lang | ||
| modules | ||
| react | ||
| resources | ||
| service | ||
| sounds | ||
| static | ||
| .buckconfig | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .flowconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| .watchmanconfig | ||
| CONTRIBUTING.md | ||
| ConferenceEvents.js | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| analytics-ga.js | ||
| app.js | ||
| base.html | ||
| body.html | ||
| conference.js | ||
| config.js | ||
| connection.js | ||
| favicon.ico | ||
| head.html | ||
| index.android.js | ||
| index.html | ||
| index.ios.js | ||
| interface_config.js | ||
| logging_config.js | ||
| metro.config.js | ||
| package-lock.json | ||
| package.json | ||
| plugin.head.html | ||
| title.html | ||
| webpack.config.js | ||
README.md
Jitsi Meet - Secure, Simple and Scalable Video Conferences
Jitsi Meet is an open-source (Apache) WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, secure and scalable video conferences. Jitsi Meet in action can be seen at here at the session #482 of the VoIP Users Conference.
The Jitsi Meet client runs in your browser, without installing anything on your computer. You can try it out at https://meet.jit.si .
Jitsi Meet allows very efficient collaboration. Users can stream their desktop or only some windows. It also supports shared document editing with Etherpad.
Installation
On the client side, no installation is necessary. You just point your browser to the URL of your deployment. This section is about installing a Jitsi Meet suite on your server and hosting your own conferencing service.
Installing Jitsi Meet is a simple experience. For Debian-based system, following the quick-install document, which uses the package system. You can also see a demonstration of the process in this tutorial video.
For other systems, or if you wish to install all components manually, see the detailed manual installation instructions.
Download
| Latest stable release |  |
|---|
You can download Debian/Ubuntu binaries:
You can download source archives (produced by make source-package):
Mobile apps
You can also sign up for our open beta testing here:
Development
For web development see here, and for mobile see here.
Contributing
If you are looking to contribute to Jitsi Meet, first of all, thank you! Please see our guidelines for contributing.
Embedding in external applications
Jitsi Meet provides a very flexible way of embedding in external applications by using the Jitsi Meet API.
Security
WebRTC does not (yet) provide a way of conducting multi-party conversations with end-to-end encryption. Unless you consistently compare DTLS fingerprints with your peers vocally, the same goes for one-to-one calls. As a result, your stream is encrypted on the network but decrypted on the machine that hosts the bridge when using Jitsi Meet.
The Jitsi Meet architecture allows you to deploy your own version, including all server components. In that case, your security guarantees will be roughly equivalent to a direct one-to-one WebRTC call. This is the uniqueness of Jitsi Meet in terms of security.
The meet.jit.si service is maintained by the Jitsi team at 8x8.
Security issues
We take security very seriously and develop all Jitsi projects to be secure and safe.
If you find (or simply suspect) a security issue in any of the Jitsi projects, please send us an email to security@jitsi.org.
We encourage responsible disclosure for the sake of our users, so please reach out before posting in a public space.
Acknowledgements
Jitsi Meet started out as a sample conferencing application using Jitsi Videobridge. It was originally developed by ESTOS' developer Philipp Hancke who then contributed it to the community where development continues with joint forces!