jfinn
/
jitsi_corner4
Beobachten 1
Favorisieren 0
Fork 0
Code Issues 0 Pull-Requests 0 Releases 0 Wiki Aktivität
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
8052 Commits
3 Branches
Branch: dev
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „dev“
${ noResults }
jfinn e49302bfe6 auto acp scripted vor 5 Jahren
.github what have I done? vor 5 Jahren
android what have I done? vor 5 Jahren
connection_optimization what have I done? vor 5 Jahren
css what have I done? vor 5 Jahren
debian what have I done? vor 5 Jahren
doc what have I done? vor 5 Jahren
flow-typed/npm what have I done? vor 5 Jahren
fonts what have I done? vor 5 Jahren
images what have I done? vor 5 Jahren
ios what have I done? vor 5 Jahren
lang what have I done? vor 5 Jahren
modules auto acp scripted vor 5 Jahren
rdev auto acp scripted vor 5 Jahren
react auto acp scripted vor 5 Jahren
resources what have I done? vor 5 Jahren
rldjs auto acp scripted vor 5 Jahren
service what have I done? vor 5 Jahren
sounds what have I done? vor 5 Jahren
static what have I done? vor 5 Jahren
.buckconfig what have I done? vor 5 Jahren
.editorconfig what have I done? vor 5 Jahren
.eslintignore what have I done? vor 5 Jahren
.eslintrc.js what have I done? vor 5 Jahren
.flowconfig what have I done? vor 5 Jahren
.gitattributes what have I done? vor 5 Jahren
.gitignore what have I done? vor 5 Jahren
.travis.yml what have I done? vor 5 Jahren
.watchmanconfig what have I done? vor 5 Jahren
CONTRIBUTING.md what have I done? vor 5 Jahren
ConferenceEvents.js what have I done? vor 5 Jahren
LICENSE what have I done? vor 5 Jahren
Makefile auto acp scripted vor 5 Jahren
README.md what have I done? vor 5 Jahren
analytics-ga.js what have I done? vor 5 Jahren
app.js what have I done? vor 5 Jahren
base.html what have I done? vor 5 Jahren
body.html what have I done? vor 5 Jahren
conference.js what have I done? vor 5 Jahren
config.js what have I done? vor 5 Jahren
connection.js what have I done? vor 5 Jahren
favicon.ico what have I done? vor 5 Jahren
fqdn_conf.js auto acp scripted vor 5 Jahren
fqdn_conf_i0.js auto acp scripted vor 5 Jahren
head.html what have I done? vor 5 Jahren
i0.html what have I done? vor 5 Jahren
i0_conf.js auto acp scripted vor 5 Jahren
i1.html what have I done? vor 5 Jahren
i1_bak.html what have I done? vor 5 Jahren
i2.html what have I done? vor 5 Jahren
i3.html what have I done? vor 5 Jahren
i4.html what have I done? vor 5 Jahren
i5.html what have I done? vor 5 Jahren
i6.html auto acp scripted vor 5 Jahren
i6_v2.html auto acp scripted vor 5 Jahren
i6_v3.html auto acp scripted vor 5 Jahren
i7.html what have I done? vor 5 Jahren
i8.html auto acp scripted vor 5 Jahren
i8_v2.html auto acp scripted vor 5 Jahren
i9.html auto acp scripted vor 5 Jahren
i10.html auto acp scripted vor 5 Jahren
iconf.js auto acp scripted vor 5 Jahren
index.android.js what have I done? vor 5 Jahren
index.html what have I done? vor 5 Jahren
index.ios.js what have I done? vor 5 Jahren
index_bak2.html what have I done? vor 5 Jahren
index_dev.html what have I done? vor 5 Jahren
index_old.html what have I done? vor 5 Jahren
index_orig.html what have I done? vor 5 Jahren
index_orig_fix.html what have I done? vor 5 Jahren
inline_script.js what have I done? vor 5 Jahren
inline_script_eapi_mod.js auto acp scripted vor 5 Jahren
interface_config.js what have I done? vor 5 Jahren
interface_config_dev.js what have I done? vor 5 Jahren
logging_config.js what have I done? vor 5 Jahren
meet.jit.si_fqdn_conf.bak.js auto acp scripted vor 5 Jahren
meet.jit.si_fqdn_conf.js auto acp scripted vor 5 Jahren
meet.jit.si_iconf.js auto acp scripted vor 5 Jahren
metro.config.js what have I done? vor 5 Jahren
package-lock.json what have I done? vor 5 Jahren
package.json what have I done? vor 5 Jahren
plugin.head.html what have I done? vor 5 Jahren
redir_index.html what have I done? vor 5 Jahren
rldjs.js what have I done? vor 5 Jahren
t0.html what have I done? vor 5 Jahren
title.html what have I done? vor 5 Jahren
webpack.config.js what have I done? vor 5 Jahren

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!