Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
jfinn 22e95c1a6f auto acp scripted 5 gadus atpakaļ
.github what have I done? 5 gadus atpakaļ
android what have I done? 5 gadus atpakaļ
connection_optimization what have I done? 5 gadus atpakaļ
css what have I done? 5 gadus atpakaļ
debian what have I done? 5 gadus atpakaļ
doc what have I done? 5 gadus atpakaļ
flow-typed/npm what have I done? 5 gadus atpakaļ
fonts what have I done? 5 gadus atpakaļ
images what have I done? 5 gadus atpakaļ
ios what have I done? 5 gadus atpakaļ
lang what have I done? 5 gadus atpakaļ
modules auto acp scripted 5 gadus atpakaļ
rdev auto acp scripted 5 gadus atpakaļ
react auto acp scripted 5 gadus atpakaļ
resources what have I done? 5 gadus atpakaļ
rldjs auto acp scripted 5 gadus atpakaļ
service what have I done? 5 gadus atpakaļ
sounds what have I done? 5 gadus atpakaļ
static what have I done? 5 gadus atpakaļ
.buckconfig what have I done? 5 gadus atpakaļ
.editorconfig what have I done? 5 gadus atpakaļ
.eslintignore what have I done? 5 gadus atpakaļ
.eslintrc.js what have I done? 5 gadus atpakaļ
.flowconfig what have I done? 5 gadus atpakaļ
.gitattributes what have I done? 5 gadus atpakaļ
.gitignore what have I done? 5 gadus atpakaļ
.travis.yml what have I done? 5 gadus atpakaļ
.watchmanconfig what have I done? 5 gadus atpakaļ
CONTRIBUTING.md what have I done? 5 gadus atpakaļ
ConferenceEvents.js what have I done? 5 gadus atpakaļ
LICENSE what have I done? 5 gadus atpakaļ
Makefile what have I done? 5 gadus atpakaļ
README.md what have I done? 5 gadus atpakaļ
analytics-ga.js what have I done? 5 gadus atpakaļ
app.js what have I done? 5 gadus atpakaļ
base.html what have I done? 5 gadus atpakaļ
body.html what have I done? 5 gadus atpakaļ
conference.js what have I done? 5 gadus atpakaļ
config.js what have I done? 5 gadus atpakaļ
connection.js what have I done? 5 gadus atpakaļ
favicon.ico what have I done? 5 gadus atpakaļ
fqdn_conf.js auto acp scripted 5 gadus atpakaļ
fqdn_conf_i0.js auto acp scripted 5 gadus atpakaļ
head.html what have I done? 5 gadus atpakaļ
i0.html what have I done? 5 gadus atpakaļ
i0_conf.js auto acp scripted 5 gadus atpakaļ
i1.html what have I done? 5 gadus atpakaļ
i1_bak.html what have I done? 5 gadus atpakaļ
i2.html what have I done? 5 gadus atpakaļ
i3.html what have I done? 5 gadus atpakaļ
i4.html what have I done? 5 gadus atpakaļ
i5.html what have I done? 5 gadus atpakaļ
i6.html auto acp scripted 5 gadus atpakaļ
i6_v2.html auto acp scripted 5 gadus atpakaļ
i7.html what have I done? 5 gadus atpakaļ
i8.html auto acp scripted 5 gadus atpakaļ
i8_v2.html auto acp scripted 5 gadus atpakaļ
i9.html auto acp scripted 5 gadus atpakaļ
i10.html auto acp scripted 5 gadus atpakaļ
iconf.js auto acp scripted 5 gadus atpakaļ
index.android.js what have I done? 5 gadus atpakaļ
index.html what have I done? 5 gadus atpakaļ
index.ios.js what have I done? 5 gadus atpakaļ
index_bak2.html what have I done? 5 gadus atpakaļ
index_dev.html what have I done? 5 gadus atpakaļ
index_old.html what have I done? 5 gadus atpakaļ
index_orig.html what have I done? 5 gadus atpakaļ
index_orig_fix.html what have I done? 5 gadus atpakaļ
inline_script.js what have I done? 5 gadus atpakaļ
inline_script_eapi_mod.js auto acp scripted 5 gadus atpakaļ
interface_config.js what have I done? 5 gadus atpakaļ
interface_config_dev.js what have I done? 5 gadus atpakaļ
logging_config.js what have I done? 5 gadus atpakaļ
meet.jit.si_fqdn_conf.bak.js auto acp scripted 5 gadus atpakaļ
meet.jit.si_fqdn_conf.js auto acp scripted 5 gadus atpakaļ
meet.jit.si_iconf.js auto acp scripted 5 gadus atpakaļ
metro.config.js what have I done? 5 gadus atpakaļ
package-lock.json what have I done? 5 gadus atpakaļ
package.json what have I done? 5 gadus atpakaļ
plugin.head.html what have I done? 5 gadus atpakaļ
redir_index.html what have I done? 5 gadus atpakaļ
rldjs.js what have I done? 5 gadus atpakaļ
t0.html what have I done? 5 gadus atpakaļ
title.html what have I done? 5 gadus atpakaļ
webpack.config.js what have I done? 5 gadus atpakaļ

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!