►
Description
Emil and Saul deliver a keynote on the OpenSuse summit that just occurred in Nuremberg.
00:00 Privacy and the mission of Jitsi
11:39 Deploying Jitsi
21:33 Coming soon
A
A
A
I'd
also
like
to
believe
that
jitsi
is
likely
the
easiest
way
to
conduct
meetings
themselves
during
the
rest
of
this
talk,
I'd
like
to
show
you
exactly
how
easy
it
is
to
get
jitsi
up
and
running
on
your
own
installation,
but
before
that
I'd
like
to
talk
a
little
bit
about
our
history
and
our
mission,
why
we
do
the
things
that
we
do
through
its
nearly
20-year
existence?
Jitsi
has
gone
through
many
transformations.
A
A
A
To
this
day,
we
are
proud
to
count
people
like
edward
snowden,
amongst
our
users.
We
it's
been
a
topic
that
has
always
mattered
for
us.
We
weren't
an
isolated
case
in
the
early
2010s
when
edward
snowden
made
his
revelations
in
2013.
Specifically
many
people
realized
that
the
new
technologies
that
we
were
using
more
and
more
to
communicate
were
not
actually
acting
in
a
way
we
thought
they
did.
We
didn't
have
the
privacy
constraints
or
guarantees
that
we
thought
we
had
and
so
work
started
on
that
topic.
A
A
Companies,
large
and
small,
had
to
make
sure
that
they
were
compliant,
which
often
cost
considerable
effort.
They
had
to
make
sure
that
the
right
contracts
were
in
place.
While
all
of
this
was
happening,
it
wasn't
obvious
that
we,
the
users,
had
reclaimed
our
confidence
in
our
privacy
being
protected
on
the
internet.
A
Believe
this
became
particularly
clear
in
the
early
months
of
the
pandemic
of
2020,
we
had
a
very
substantial
proportion
of
the
population
moved
to
online
communication
as
their
primary
tool
for
activities
that
were
up
until
that
point
direct
face-to-face
communication,
and
when
that
happened,
there
were
incident
after
incident
of
people
finding
out
that
the
tools
they
were
using
were
not
really
behaving
the
way
they
expected
to.
It
was
still
the
same
problem
that
we
had
in
2013..
A
A
So
the
way
that
end-to-end
encryption
was
initially
working
was
the
following:
the
entity,
company
or
community.
That
was
providing
you
with.
Let's
say
your
email
client
was
going
to
encrypt
the
content
of
your
messages,
and
then
it
was
going
to
assert
that
the
other
entity,
the
service
provider,
giving
you
your
email
service,
hasn't
had
access
to
the
content
of
your
messages.
A
A
A
Many
exciting
changes
happened
in
the
2010s.
We
many
of
our
apps
moved
to
a
more
web
oriented
model
and
the
entire
world
moved
toward
the
cloud
that
had
implications
for
this
separation,
this
division
of
responsibilities
between
clients
and
their
providers,
and
then
servers
and
services
and
their
providers
more
and
more.
In
the
2010s.
When
you
were
getting
a
service,
you
were
getting
everything
from
the
same
entity
when
you're
getting
email
it.
A
A
A
I
believe
that
the
privacy
constraints
we
face
are
so
individual
and
specific
to
our
different
use
cases
they're
so
different,
even
for
ourselves,
depending
on
whether
we're
having
a
work
or
a
personal
conversation
that
it
is
very
unlikely
for
global
solutions
to
just
emerge,
even
as
as
an
enumeration
of
options.
I
I
don't
think
that
this
is
likely
to
happen,
so
I
believe
that
the
way
we
can
address
them
is
by
making
sure
that
we
give
ourselves
the
ability
to
define.
A
Our
privacy
configurations-
and
I
think
that
this
is
the
primary
proposition
of
value
that
that
jitsi
has,
and
it
fits
particularly
well
with
the
people
in
this
community
having
your
own
communication
server
is
likely.
The
the
best
way
to
address
the
specificity
of
our
privacy
concerns
and
what
we
work
really
hard
at
jitsi
to
achieve
is
to
make
sure
that
deploying
that
solution
of
your
own
is
a
very,
very
easy
process
and
we're
going
to
show
you
exactly
how
easy
it
is.
B
Thanks
male
hey
everyone
saul
here
I
want
to
show
you
how
to
deploy
jitsi
mint
to
your
own
server.
So,
let's
jump
right
in
real,
quick.
First,
I'm
going
to
go
into
our
handbook
to
show
you
our
self-hosting
guide.
We
have
comprehensive
setups
for
debian
systems,
stalker
and
whoever
community
contributed
opensuse
guide
even
now.
Today,
I
want
to
show
you
the
docker
setup,
because
I
find
it
it's
the
most
universal
is
the
one
that
will
work
with
any
underlying
operating
system.
So
let's
go
for
that
one.
B
B
So
here
is
what
we
have.
We
have
an
open-source
elite
virtual
machine
and
we
have
a
clone
of
the
git
repository
that
is
right
here.
Here
you
get
all
the
files
we
recommend
using
stable
releases,
but
I'm
running
unstable
just
to
maybe
show
you
a
cool
trick
or
two
so
we're
in
our
terminal
and
the
one
thing
that
we
need
to
do
is
customize.
B
B
A
B
We
got,
let's
encrypt,
enabled
my
domain
here:
email,
a
public
url
and
default
ports.
So
let's
go
all
we
need
to
do,
is
logger
compose
up,
and
this
will
take
care
of
booting.
The
four
default
containers,
the
web
container,
prosody
for
the
xmbp
server
g-coffer
world
conference
focus
and
the
video
bridge
as
the
as
the
media
router
and
after
all,
this
logs
are
printed
and
the
first
time
you
run
it
will
fetch
the
alerts
and
group
certificate
and
so
on.
B
A
A
B
Let's
test
it
real
quick,
so
we
can
go
in
there
hello
and
join
our
meeting.
We
already
have
a
bunch
of
stuff
that
works
out
of
the
box.
They're,
like
you
know,
we
can
just
copy
this
link,
send
it
to
somebody
and
they
can
join
our
meeting.
In
fact,
if
we
open
a
new
tab
here,
I'm
going
to
mute,
though
not
to
kill
the
machine
in
the
process.
B
So
yes,
in
our
in
our
documentation,
we
do
have
instructions
on
how
to
make
your
setup
more
complete
and
add.
Other
services
change
your
config
and
this
range
from
simple
things
like
I
want
to
disable.
This
feature
enable
this
other
tiny
feature
in
the
ui
to
more.
You
know,
involve
setups
for
recording
pstn
access
and
transcriptions
popular
one,
of
course,
is
authentication,
allows
you
to
to
use
internal
authentication
or
ldap
or
job
authentication.
B
What
have
you
and
another
one
is,
for
instance,
shared
document,
editing,
which
is
some
etherpad
integration
that
we
have.
So
let
me
show
you
that
real
quick,
let's
go
to
the
terminal
first,
because
we're
going
to
want
to
stop
the
containers,
change
our
config,
real,
quick
and
then
go
back
to
the
browser.
B
So
we
can
see
the
results.
So
all
we
need
to
do
is
uncomment
this
independent
url
base,
and
then
we
need
to
run
the
docker
compose
with
a
slightly
different
command
line.
This
is
all
documented,
so
we
will
spin
up
a
new
container
that
will
have
etherpad
in
it
as
well,
and
so
now
that
this
is
started,
we
can
go
back
to
the
website
and
join
a
meeting.
B
B
B
But
let
me
take
it
one
step
further
and
kind
of
work
with
with
a
hybrid
setup
here,
where
we
are
going
to
introduce
jazz
components,
so
we're
going
to
run
a
pst
and
access
outside
of
our
setup
but
connected
to
this
docker
setup
that
we
have
right
here.
The
first
step
is:
we
need
to
go
into
the
into
our
into
js
console
to
enable
just
components.
B
Once
you
go
into
your
into
your
jazz
console,
instead
of
selecting
gta
as
a
service
you're
going
to
select
gtc,
mid
components
and
you're
going
to
configure
your
domain
over
here.
So
my
domain
is
already
configured
we
are
all
set
and
then
all
we
got
to
do
is
well
obviously
go
back
to
the
terminal
and
we're
going
to
stop
our
our
setup
once
again.
B
The
idea
here
is
once
you
configure
it,
you
no
longer
need
to
touch
it
and
I'm
actually
going
to
disable
etherpad
now
that
we
have
shown
it
off
and
we
are
going
to
enable
jazz
components
and
remember
all
we
did
was
some
short
setup
on
our
website
and
then
we
turned
on
one
flag
now
what
happens
when
we
do
this?
Well
now
we
we
go
back
to
the
browser
and
we're
going
to
join
a
meeting
here.
B
B
B
B
And
just
like
that,
we
have
a
new
participant,
so
this
is
a
very
simple
kind
of
setup
that
we
came
up
with
to
add
this
functionality
here.
The
important
thing
I'd
like
to
highlight
is
how
it
took
us
very
little
effort
to
get
started,
and
then
we
just
kept
adding
more
stuff,
because
everything
is
configurable
and
flexible
and
you
can
keep
enlarging
your
setup
to
be.
B
A
Thank
you
very
much,
so
I
think
this
really
makes
the
point
and
clearly
shows
how
easy
it
is
to
deploy
your
own
meeting
server.
Hopefully,
the
audience
is
satisfied.
We
had
promised
that
we'll
talk
a
little
bit
about
features
that
are
going
to
soon
arrive
in
gt.
So
let's
do
this
a
little
bit.
Can
you
tell
us
what
are
the
the
the
things
big
or
small
that
you're
excited
about
seeing
in
jits
in
the
near
future,.
B
Well,
thanks
mill.
Actually
I
think
that
since
we
are
back
at
google
summer
of
code
this
year,
I
I
will
take
a
minute
to
highlight
a
few
projects
that
I
feel
will
greatly
improve
jitsi
and
have
been
things
that
the
community
has
requested
for
a
long
time
and
we
we
could
kind
of
never
find
a
way
to
do
them.
And
now
we
have,
we
have
kind
of
found
the
avenue
for
them
to
happen,
and
I'm
hoping
a
lot
of
them
are
completed
to
fruition.
B
So,
for
example,
first
one
I
would
highlight
is
a
different
meaning
recordings
back-ends
right
now,
as
many
of
you
may
know,
we
can
record
the
dropbox
because
we
integrate
with
their
api
or
we
constantly
get
requests
for
like
hey.
Why
don't
you
also
record
to
next
cloud
or
some
other
storage
providers,
even
raw
s3
or
whatever?
A
B
Absolutely
another
one
is
we're
going
to
do
a
react
native
sdk,
so
those
who
might
be
more
familiar
with
our
code
base
know
that
we
are
using
react
native,
but
we
don't
kind
of
expose
it
in
a
consumable
way
for
other
react
native
applications.
We
have
traditionally
catered
for
native
ios
and
android
apps
in
objective-c
and
java
and
we're
going
to
packetize
it
so
that
it's
it's
usable
from
a
react
native
app,
and
this
should
allow
developers
to
integrate
jits
into
their
react
native
applications
much
faster
and
much
more
effectively.
B
A
Second,
real-time
streaming
is
an
interesting
solution
to
that
problem,
so
that
that's
something
that
I'm
looking
forward
to
and
then
there's
there's
another
one
which
is
in
general.
I
think
that
there's
opportunities
for
meetings
applications
to
help
people
beyond
just
providing
a
new
medium
beyond
just
taking
your
face
and
putting
it
on
the
wire.