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 10a0f39726 auto acp scripted 5 anni fa
.github what have I done? 5 anni fa
android what have I done? 5 anni fa
connection_optimization what have I done? 5 anni fa
css auto acp scripted 5 anni fa
debian what have I done? 5 anni fa
doc what have I done? 5 anni fa
flow-typed/npm what have I done? 5 anni fa
fonts what have I done? 5 anni fa
images what have I done? 5 anni fa
ios what have I done? 5 anni fa
lang what have I done? 5 anni fa
modules auto acp scripted 5 anni fa
rdev auto acp scripted 5 anni fa
react auto acp scripted 5 anni fa
resources what have I done? 5 anni fa
rldjs auto acp scripted 5 anni fa
service what have I done? 5 anni fa
sounds what have I done? 5 anni fa
static auto acp scripted 5 anni fa
.buckconfig what have I done? 5 anni fa
.editorconfig what have I done? 5 anni fa
.eslintignore what have I done? 5 anni fa
.eslintrc.js what have I done? 5 anni fa
.flowconfig what have I done? 5 anni fa
.gitattributes what have I done? 5 anni fa
.gitignore what have I done? 5 anni fa
.travis.yml what have I done? 5 anni fa
.watchmanconfig what have I done? 5 anni fa
CONTRIBUTING.md what have I done? 5 anni fa
ConferenceEvents.js what have I done? 5 anni fa
LICENSE what have I done? 5 anni fa
Makefile m4 5 anni fa
README.md what have I done? 5 anni fa
analytics-ga.js what have I done? 5 anni fa
app.js auto acp scripted 5 anni fa
base.html what have I done? 5 anni fa
body.html what have I done? 5 anni fa
conference.js auto acp scripted 5 anni fa
config.js what have I done? 5 anni fa
connection.js what have I done? 5 anni fa
favicon.ico what have I done? 5 anni fa
head.html what have I done? 5 anni fa
i0.html what have I done? 5 anni fa
i1.html what have I done? 5 anni fa
i1_bak.html what have I done? 5 anni fa
i2.html what have I done? 5 anni fa
i3.html what have I done? 5 anni fa
i4.html what have I done? 5 anni fa
i5.html what have I done? 5 anni fa
i6.html auto acp scripted 5 anni fa
i6_v2.html auto acp scripted 5 anni fa
i7.html what have I done? 5 anni fa
i8.html m4 5 anni fa
i11.html auto acp scripted 5 anni fa
i11_bak.html auto acp scripted 5 anni fa
i11s.html auto acp scripted 5 anni fa
index.android.js what have I done? 5 anni fa
index.html what have I done? 5 anni fa
index.ios.js what have I done? 5 anni fa
index_bak2.html what have I done? 5 anni fa
index_dev.html what have I done? 5 anni fa
index_old.html what have I done? 5 anni fa
index_orig.html what have I done? 5 anni fa
index_orig_fix.html what have I done? 5 anni fa
inline_script.js auto acp scripted 5 anni fa
inline_script_bak.js auto acp scripted 5 anni fa
interface_config.js auto acp scripted 5 anni fa
interface_config_dev.js auto acp scripted 5 anni fa
logging_config.js what have I done? 5 anni fa
metro.config.js what have I done? 5 anni fa
package-lock.json what have I done? 5 anni fa
package.json what have I done? 5 anni fa
plugin.head.html what have I done? 5 anni fa
redir_index.html what have I done? 5 anni fa
rldjs.js what have I done? 5 anni fa
t0.html what have I done? 5 anni fa
title.html what have I done? 5 anni fa
webpack.config.js what have I done? 5 anni fa

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!