►
From YouTube: Jitsi Community Call (Oct 24 2016)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
B
A
A
Let's
hope
yeah,
so
I
have
been
working
on
on
the
adaptivity
features
in
the
bridge.
A
very
big
factoring
of
the
simulcast
implementation
is
this:
well,
it's
not
committed,
but
it's
done
and
I
have
tested
it
with
and
I'm
currently
testing
it
with
with
a
small,
selenium
great
that
I
have
set
up.
Maybe
this
will
go
into
arm.
A
Gt
me
torture
eventually,
but
it's
not
it's
not
integrated.
Yet
so
they're.
The
refactoring
is
about
moving
a
wave
well,
not
moving
away
but
generalizing
the
notion
of
the
notions
of
simulcast
streaming.
Things
like
that.
It
takes
into
account
now
temporal
and
spatial
scalability
that
our
features
in
in
vp9
and
temporal
scalability
p8
as
well.
So
we're
going
to
have
that
it
also.
A
A
I'm
making
room
for
Boris,
yes,
so
eventually
we're
going
to
be
even
and
this
week
I'm
going
to
actually
play
with
that
activity,
all
the
most
of
the
previous
time.
It
was
the
laying
the
groundwork
for
for
for
the
revised
simulcast
implementation
of
this
week,
we're
going
to
test
the
adaptivity
features
and
see
how
it
works
so
yeah,
that's
what
I've
been
doing
next,
we
can
go
to
Crystal
a
week
and
he
can.
He
can
tell
us
a
bit
more
about
what
he
did
last
week.
So
crystal
all
yours,
so.
D
Maybe
maybe
something
interesting
and
important
is
like
we,
so
I
changed
a
little
bit
the
logic
than
a
factor
a
little
bit.
The
cult
about
GT
conference
leaking
legitimate
project.
Also,
we
changed
a
little
bit
de
la
G
and
again
change
the
code
for
the
change-up
functionality.
So
now
the
feedback
dialog
is
displayed
independently
of
anything
else
that
we
are
doing
like
leaving
the
chat
room
and
so
on
fix
the
prom
is
that
was
returned
the
budgets
conference
Lee
and
yeah.
D
Now
now
the
functionality
should
work
better
than
before
other
than
that
there
was
some
issues
with
the
with
our
iframe
API.
Some
comments
were
not
working,
so
I
merged
one
PR
that
fixes
some
of
them
and
fix
the
screen
sharing
command
for
the
iframe
API
other
than
that
there
was
some
small
fixes
about
go
scoffs
and
I
had-
and
I
think
that's
it.
E
F
Say
I've
still
been
working
for
the
last
week
on
a
rewrite
of
still
working
on
the
rewrite
of
jubrey
to
hopefully
make
the
recording
infrastructure
a
little
more
stable
and,
as
Jordan
suggestion
have
been
struggling
with
pythons,
complete
lack
of
any
sort
of
basic
concurrency
support
at
all,
and
the
kind
of
all
of
the
random
libraries
that
have
been
tacked
on
to
try
and
deal
with
that
pitch
are
all
terrible
thinking
right.
That's
that's
right!
It's
coming
along
and
hopefully
we'll
be
ready
soon.
D
A
C
Hour
right
so
in
the
last
week,
I've
been
working
on
identifying
and
fixing
some
of
the
infrastructure
related
to
the
way
we're
proxying
two
different
copies
of
meat
behind
the
scenes.
Our
update
process
was
not
as
much
as
we
would
like,
and
so
we've
identified
some
improvements
and
I'm
trying
to
bring
those
introductions
so
that
specifically,
to
make
me
to
jitsi
service,
run
more
smoothly.
I
hope
to
be
able
to
deploy
about
this
week.
Sometime
and
I
think
that's
that
back
to
him.
You.
B
And
Rob
I
would
just
make
a
quick
update
for
Jana
cuz
she's,
currently
sick,
but
she
is
working
on
solving
the
user
interface
around
the
black
thumbnail
that
we
see
for
the
active
speaker,
so
that
should
be
we've
received
feedback
that
this
is
confusing.
People
think
it's
broken,
not
much
surprise
there,
so
we're
trying
to
make
it
into
something
more
intuitive.
Then
there's
there's
been
some
work
around
the
menus
that
should
land
soon
and
what
else
is
there?
The
dialogues
I've
been
slightly
worked.
B
A
B
B
Another
thing
as
well:
we've
removed
h.264
from
the
duty
clients
we
felt
that
was,
that
was
going
to
help
us
scope
our
efforts
a
little
bit
more
because
there's
really
very
limited
time
and
effort
for
for
the
GT
client.
My
almost
nothing
and
people
were
mostly
using
it
for
SIBO
do
cause
anyway,
so
so
there
it
is
now
open
floor.
G
H
I'm
here
sure
I
guess
that's
got
to
go
now.
I've
been
working
with
a
couple
of
you
guys
didn't
have
some
fixes
for
oh
no
fire
plug
in
and
video
bridge
as
a
whole.
That's
working
well
I've
got
a
lot
of
very
small,
commit
and
pull
requests
and
love
those
to
be
evaluated
because
I'm
a
bit
blocked
by
Oh.
Either
I
go
left
or
right
depending
on.
If
you
guys
accept
no
spool
requests
so.
H
B
H
H
B
H
B
You
mean
that,
though,
how
would
it
work,
then
we
would
bundle
everything
in
the
same
plug-in
or
I.
Remember
a
discussion
we
della
that
we
had
where
I
think
we
might
have
said
that
GT
video
bridge
would
be
a
standalone
plug-in
together
with
you,
come
home
and
actually
no
because
the
off
me
wasn't
needing
jacoco
because
it
was
acting
as
a
focus.
H
B
H
H
B
But
the
question
is
I.
Guess
we
need
just
need
to
be
careful.
What
happens
if
the
port
443
on
the
machine
where
you're
installing
that
is
already
taken,
then
we
oh
and
obviously
there's
the
root
permissions
thing
so
the
so.
These
are
things
to
consider,
because
if
you
don't
do
that,
then
that
basically
means
that
you
have
a
much
less
reliable.