You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
jfinn 22e95c1a6f auto acp scripted 5 years ago
.github what have I done? 5 years ago
android what have I done? 5 years ago
connection_optimization what have I done? 5 years ago
css what have I done? 5 years ago
debian what have I done? 5 years ago
doc what have I done? 5 years ago
flow-typed/npm what have I done? 5 years ago
fonts what have I done? 5 years ago
images what have I done? 5 years ago
ios what have I done? 5 years ago
lang what have I done? 5 years ago
modules auto acp scripted 5 years ago
rdev auto acp scripted 5 years ago
react auto acp scripted 5 years ago
resources what have I done? 5 years ago
rldjs auto acp scripted 5 years ago
service what have I done? 5 years ago
sounds what have I done? 5 years ago
static what have I done? 5 years ago
.buckconfig what have I done? 5 years ago
.editorconfig what have I done? 5 years ago
.eslintignore what have I done? 5 years ago
.eslintrc.js what have I done? 5 years ago
.flowconfig what have I done? 5 years ago
.gitattributes what have I done? 5 years ago
.gitignore what have I done? 5 years ago
.travis.yml what have I done? 5 years ago
.watchmanconfig what have I done? 5 years ago
CONTRIBUTING.md what have I done? 5 years ago
ConferenceEvents.js what have I done? 5 years ago
LICENSE what have I done? 5 years ago
Makefile what have I done? 5 years ago
README.md what have I done? 5 years ago
analytics-ga.js what have I done? 5 years ago
app.js what have I done? 5 years ago
base.html what have I done? 5 years ago
body.html what have I done? 5 years ago
conference.js what have I done? 5 years ago
config.js what have I done? 5 years ago
connection.js what have I done? 5 years ago
favicon.ico what have I done? 5 years ago
fqdn_conf.js auto acp scripted 5 years ago
fqdn_conf_i0.js auto acp scripted 5 years ago
head.html what have I done? 5 years ago
i0.html what have I done? 5 years ago
i0_conf.js auto acp scripted 5 years ago
i1.html what have I done? 5 years ago
i1_bak.html what have I done? 5 years ago
i2.html what have I done? 5 years ago
i3.html what have I done? 5 years ago
i4.html what have I done? 5 years ago
i5.html what have I done? 5 years ago
i6.html auto acp scripted 5 years ago
i6_v2.html auto acp scripted 5 years ago
i7.html what have I done? 5 years ago
i8.html auto acp scripted 5 years ago
i8_v2.html auto acp scripted 5 years ago
i9.html auto acp scripted 5 years ago
i10.html auto acp scripted 5 years ago
iconf.js auto acp scripted 5 years ago
index.android.js what have I done? 5 years ago
index.html what have I done? 5 years ago
index.ios.js what have I done? 5 years ago
index_bak2.html what have I done? 5 years ago
index_dev.html what have I done? 5 years ago
index_old.html what have I done? 5 years ago
index_orig.html what have I done? 5 years ago
index_orig_fix.html what have I done? 5 years ago
inline_script.js what have I done? 5 years ago
inline_script_eapi_mod.js auto acp scripted 5 years ago
interface_config.js what have I done? 5 years ago
interface_config_dev.js what have I done? 5 years ago
logging_config.js what have I done? 5 years ago
meet.jit.si_fqdn_conf.bak.js auto acp scripted 5 years ago
meet.jit.si_fqdn_conf.js auto acp scripted 5 years ago
meet.jit.si_iconf.js auto acp scripted 5 years ago
metro.config.js what have I done? 5 years ago
package-lock.json what have I done? 5 years ago
package.json what have I done? 5 years ago
plugin.head.html what have I done? 5 years ago
redir_index.html what have I done? 5 years ago
rldjs.js what have I done? 5 years ago
t0.html what have I done? 5 years ago
title.html what have I done? 5 years ago
webpack.config.js what have I done? 5 years ago

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 else 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 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!