►
From YouTube: Jitsi Live Stream
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).
B
Hello,
everyone
I'm
joining
from
mobile
today,
so
I'll
have
my
idiot
video
offer
most
of
the
of
the
call
to
beautiful
day
here
in
Austin,
it's
great
to
have
you
all
joining
today.
Now
a
quick
update,
I,
don't
believe
we
did,
we
have
a
call.
Does
anyone
remember
we
having
a
call
with
the
vertical
film
strip?
I,
don't
believe
we
did
so
I'm
going
to
enjoy
that
a
little
bit
we
as
you
as
you're,
seeing
now
we
are,
would
consume
ship.
B
Well,
our
surf
strip
is
vertical
now,
and
we
like
that,
because
we've
had
a
number
of
occasions
where
it
felt
like
the
horizontal
thin
strip
was
taking
too
much
of
the
limited
height
that
we
had.
On
the
other
hand,
we
do
have
significant
width
on
most
modern
screens,
so
that's
a
choice
that
we
made
there.
Also
we
changed
the
one-to-one
layout.
Now
you
don't
see
a
second
thumbnail
when
you're
in
a
one-to-one
layout,
because
that
you're
not
to
be
confusing
to
many
people.
B
It
sort
of
felt
like
there
was
one
more
person
in
the
column
too
many.
So
now
you
want
to
see
you're
pretty
much
like
with
most
major
other
video
apps
that
mainly
support
one-to-one
calls.
You
only
see
your
own
local,
video
and
and
the
remote
participant.
Obviously,
and
then
you
have
some
nice
transitions
when
you
click
on
yourself,
the
local
view
is
separated
from
that
of
everyone
else,
which
also
gives
us
the
option
to
to
get
nice
scrolling
behavior.
B
The
film
strip
tugs
nicely
talks
nicely
under
the
local
view,
the
local
preview-
and
we
are
thinking
about
potentially
optimizing
by
turning
off
video
for
people
who
are
not
currently
showing.
But
that's
going
to
be
down
the
road
see
how
that
works
out.
So
thanks
by
the
way
to
Lenny
for
for
working
on
that
and
he's
currently
working
on
sort
of
making
all
that
clean
and
reactive
fiying,
our
entire
film
strip,
which
is
important
as
it's
also
going
to
make
it
compatible
with
mobile.
B
B
Obviously
we're
doing
it
because
further
experimentation
spirit
reasons
primarily
here
on
me
to
tea,
and
for
many
of
you
this
might
be
interesting
from
the
perspective
that
gee
gassy
is
moving
closer
and
closer
to
something
that
we
consider
stable
production
work,
which
is
pretty
much
there
and
that's
pretty
cool.
Unfortunately,
we
have
yet
to
get
servers
like
three
switch
and
asterisk
to
support
multiple
SSRC
mode,
which
means
that
the
gassy
has
to
do
the
heavy
weight,
lifting
I'm.
B
B
I'm
going
again
I'm
getting
a
little
bit
of
wind,
so
I
might
turn
the
ball
over
to
someone
else,
but
we
got
a
new
website,
there's
a
few
glitches
around
it.
For
example,
our
previous
website
is
supposed
to
we'll
move
to
desktop
je
t'adore
org,
and
we
will
remove
the
bits
and
pieces
there
that
were
dedicated
to
GTV.
B
Do
bridging
do
to
meet
so
so
that
website
would
only
be
dedicated
to
the
client
which
it
was
really
good
for
and
if
you
guys
know
this
thing's
missing
or
broken
on
a
new
website
in
the
in
the
coming
days
or
weeks.
Please
let
us
know
on
the
mailing
list
hits
we
only
have
limited
resources
to
working
on,
but
I
think
it
turned
out
pretty
good,
it's
substantially
more
geared
toward
to
TVD
region
due
to
need
which
are
the
primary
topics
of
this
community
anyway.
So
we're
very
excited
for
that
reason.
B
Also,
you
have
a
nice
calendar
integration
for
this
call
on
the
front
page
and
in
the
following
news,
we'll
be
running
a
number
of
news
articles
around
all
these
recent
optimizations
that
we
did
the
telephony
integration,
the
peer-to-peer
four
one.
One
and
the
vertical
jump
ship
and
one
that
I
didn't
mention
so
far.
The
work
on
that
activity
that
George
has
been
working
very
hard
on
is
now
in
a
very
in
a
very,
very
good
shape.
B
I
think,
there's
still
a
bunch
of
patches
that
got
in
late
last
week
around
the
exact
strategy
in
which
we
turned
thumbnails
off
and
on
the
strategy
now
is
that
we
would
always
turn
on
people
in
the
way
they're
appearing
last
n
and
as
opposed
to
previously,
we
were
trying
to
be
smarter
and
say:
maybe
maybe
someone
hasn't
hadn't
spoken
recently,
but
would
still
plug
them
in
just
because
they're,
the
only
ones
that
fit
in
the
available
bandwidth.
Well,
that
turned
out
to
be
confusing.
So
we're
not
going
to
do
that
anymore.
B
However,
the
the
bandwidth
estimations
are
working
pretty
well,
and
this
is
a
pretty
major.
This
is
a
pretty
major
news,
because
bandwidth
consumption
is
something
that
people
often
raise
is
a
concern
with
with
sa
fuse.
So
now
we
have
some
pretty
smart
behavior
there
and
we
use
the
same
bandwidth
estimation
algorithm
as
it's
Google,
with
a
common
filter.
We're
now
thinking
about
potentially
replacing
the
common
filter
with
neural
networks
and
seeing
how
that
behaves.
We're
going
to
keep
everyone
here,
updated
on
that.
E
B
C
B
Should
be
mentioning,
we
have
some
interface
improvements
coming
in
for
specifically
for
adaptive
last
10.
That
would
give
us
clear
indications
when
you're
not
seeing
someone
else's
video,
because
they're
being
turned
off
for
optimization
reasons
you
get
this
ninja
icon
in
the
call
for
the
oh.
Yes,
of
course,
we
have
an
audio-only
mode
as
well.
B
Now,
if
you
hover
on
top
of
the
HD
tag,
HD
or
SD,
depending
on
what
you're
getting
in
the
top
right
corner,
you
can
now
turn
on
audio
only
mode,
which
means
that
not
only
is
your
camera
blocked,
but
you're
also
not
getting
any
video
from
the
video
bridge,
so
that
might
be
a
pretty
cool
addition
for
many
I'm
using
it
now
actually
on
mobile
and
that's
about
it
yeah.
If
anyone
can
think
of
something
that
I'm
missing,
please
just
go
ahead
and
it's
not,
then,
let's
do
open
mic.
D
B
B
G
Guess
if
we're
lacking
in
things
to
mention
I
can
mention
that
we
made
a
small
change
to
support
reporting
your
local
deployment
info
via
JavaScript,
if
you
plugged
into
your
analytics
with
Google
Analytics
or
something
else,
you
can
now
make
your
media
instance
report
extra
facts
along
with
your
events,
mostly
that's
not
going
to
back
anyone
here,
but
I.
Just
thought:
I'd
mention
it
as
an
extra
change.
B
D
D
B
This
is
work
in
progress,
so
don't
expect
it
before
a
month,
but
it's
going
to
come
there.
This
is
basically
useful
for
if
you
have
presence
related
applications
you
integrating
Duty
such
as
rocket
chat
or
HipChat,
for
example,
you
can
use
their
database
of
presents,
fed
information
and
just
call
your
contacts.
E
We
have
ten,
oh
yeah.
We
have
Henry
asking
whether
what
determines
if
you
receive
as
the
original
video-
and
this
is
so
the
the
the
bridge-
is
running
a
bond
with
estimation
algorithm
it's
fairly
complicated,
so
you
can
read
more
about
it.
In
the
there
is
an
internet
internet
draft
that
describes
this
and
Google
Chrome
runs
the
same
algorithm.
So
the
bridge
is
running
this
and
it
determines
how
much
available
bandwidth
you're
having
and
if,
if
you
have
enough
bandwidth,
it's
going
to
send
you
HD.
E
F
I
posted
my
name's
bill,
I
posted
a
issue
and
Lib
jitsi
meet
about
a
month
ago.
I
was
just
going
to
ask
about
potentially
supporting
having
multiple
video
tracks
per
endpoint.
F
So
being
able
to
support
something
like
a
screen
sharing
and
having
a
webcam
at
the
same
time
coming
from
one
participant,
I,
don't
know
if
this
is
something
that
y'all
can
support
or
want
to
support.
I
guess
I
just
wanted
to
see
what
well
y'all
stats
are
on
that.
So.
B
H
H
B
H
F
Yeah
I
think
that
there's
some
checks
right
now
at
least
and
legitimate,
that
a
check
like
it
pretty
much
says.
No,
you
can't
add
more
than
one
video
track.
I,
an
older
version
of
and
love
jitsi
made
I've
changed
up
some
things
so
that
I
can
do
it.
But
there's
a
lot
of
things
like
dealing
with
a
participant
selection
and
whatever
screen
share
layers,
and
that
kind
of
thing
that
doesn't
seem
to
quite
make
sense.
In
those
cases
right.
B
So
yeah,
that's
sort
of
clumsiness
would
have
been
my
expectation
as
well,
and
the
reason
is
that
being
able
to
do
that
poses
so.
These
questions
that
you're
mentioning
right
now,
specifically.
B
Ux
choices
about
what
do
you
do
with
actor
speaker
detection
at
that
point,
and
so
it's
not
something
that
we're
we're
going
to
use
and
we
don't
have
any
work
planned
on
it
that
sat
on
a
Lipschitz
we
meet
Level
III
I,
wouldn't
say
that
we
were
opposed
to
it
if
someone
else
wanted
to
to
do
the
work,
but
we
have
no
work
planned
on
that.
Okay,.
F
B
F
B
C
B
I
B
B
Yeah
I,
don't
think
we're
back
to
the
levels
from
before
the
jitter
buffer
rewrite,
and
specifically,
we
still
have,
for
example,
there's
this
issue
where
that
also
came
with
the
jitter
buffer
rewrite
in
Chrome,
where
now
the
decoder
seems
to
get
stuck
sometimes,
and
it
would
just
show
a
black
frame
or
freeze
on
the
last
image
and
then
it
would
start
sending
fi
ours
and
and
but
it
would
never
get
unstuck.
B
I
I
I
A
And
he
also
reports
crashing
three
times
during
this
call.
He
has
a
question
about
using
multiple
cameras
in
a
single
computer
and
I.
Think
that's
what
the
discussion
from
a
few
minutes
ago
was
so
screen.
Sharing
in
the
camera.
Here
is
one
option.
Two
camera
feeds
is
another
option
and
I
think
the
discussion
was
about
either
of
them.
B
Yeah,
to
summarize,
the
answer
is
wow:
we're
open
to
having
someone
contribute
support
for
that
in
Lib
GT
meat,
although
it
would
be
an
intricate
piece
of
work,
because
we
have
to
decide
what
we
do
with
all
the
dominant
speaker,
detection
and
out
to
focus
and
all
these
things,
and
it's
that
it's
even
worse
for
for
GT
meat
itself
in
terms
of
the
amount
of
work
that
would
be
necessary.
So
we
have
no
work
planned
around
support
of
any
of
these
things.