►
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).
A
A
A
A
B
B
Okay,
yeah
there
was
a
there's,
a
WebSocket
bug
which
was
manifesting
as
people
na'kal.
None
of
the
data
channel
or
you
know,
bridge
channels.
Messages
would
go
so
that
was
breaking
pinning
and
a
bunch
of
things.
So
that's
now
fixed
and
then
there
was
an
issue
with
edge
ice.
Connecting
would
fail
some
amount
of
the
time
somewhere
some
percentage
of
the
time
and
that's
fixed
I'm
gonna.
Do
some
more
work
here
about
looking
at
the
final
blockers
to
see
what's
preventing
edge
from
joining.
C
A
D
Digression
on
their
system
and
they
are
also
working
on
integrating
our
SDK
on
their
mobile
app.
So
that's
pretty
cool
to
know,
and
also
some
other
community
related
aspects.
I
think
it
was
last
week
or
two
weeks
ago,
some
users
launched
the
unofficial
did
say:
users
community
in
Spanish,
it's
in
Google,
Groups
and
well-beings
planning
it
as
I
am
I,
joined
and
there's
some
discussion
happening
there
and
I'm
already
grabbing
some
things.
D
D
D
A
A
So
I'm
going
to
open
the
microphone
any
questions
or
comments
from
the
community.
A
C
C
C
A
C
Could
look
at
your
email,
I,
really
I
think
we
should
talk
about
all
of
the
other
school
with
it?
I
will
do
that
so
I'm,
while
working
on
my
continued
quest
to
see
if
it's
possible
to
reduce
the
amount
of
client
connections
in
a
by
some
way,
I
came
across
a
question
and
which
I'm
gonna
ask
him
which
is
gonna
sound,
perhaps
judgmental
and
I
don't
mean
it
in
that
way
whatsoever.
C
So,
with
that
into
account,
I've
been
asking
I've
been
looking
at
the
code,
I've
been
asking
myself:
what
is
the
the
development
perspective
of
creating
the
jitsi
stuff?
So
is
it?
Are
you
guys
building
a
open-source
product
that
is
intended
to
be
very
versatile
and
usable
in
many
different
ways
and
designed
to
be
built
upon
by
third-party
developers,
or
are
you
guys
more
leaning
towards
a
developing
application
suite
that
serves
your
instances
that
you
run
yourself
or
anywhere
in
the
middle
that
do
I
make
that
question?
Is
that
likely
a
question
to
you
guys?
C
A
C
Know
what
I
I'm
an
open
source
developer
myself
and
I
built
something
without
even
running
it
myself.
So
what
I
build
is
designed
to
run
on
a
variety
of
platforms
and
I?
Try
to
make
it
easier.
That's
my
primary
focus
to
make
it
easier
for
others
to
install
stuff
and
to
build
stuff
on
top
of
it
if
I'm
successful
in
that
that's
a
whole
different
question.
A
I'm
still
not
sure
what
I
fully
understand,
but
here's
here's
one,
here's
what's
sort
of
resonating
already
it's
I
wouldn't
say
so.
Yes,
the
fact
that
we're
doing
this
open
source
is
opposed
to
just
developing
with
innovation
is
because
we
want
and
to
solve
other
people's
problems.
We
do
not,
however,
want
it
to
solve
every
possible
problem,
so
we
have
made
choices
about
problems
that
resolving
and
if
other
people
have
problems,
have
the
same
problems.
We
hope
it
will
serve
them
for
them
as
well,
and
if
they
don't,
then
you
have
to
make
quizzes.
A
You
have
to
have
focused
there
so,
but
this
is
all
way
too
abstract.
If
you,
if
you
can
talk
about
specific
things,
then
it
would
be
easier
to
say.
Yes,
we
consider
this
to
be
a
problem
that
we
don't
want
to
solve,
or
actually
we
do
want
to
solve
that
problem.
So,
let's
go
and
see
why
it's
not
working
for
you.
So.
C
A
A
A
Not
the
case,
if
you're,
but
really
good,
to
ring
our
own
services,
we
wouldn't
be
making
it
open
source
because
that
doesn't
help
run
our
own
services.
It
is
primarily
geared
to
solving
a
certain
set
of
problems:
okay,
because
we
don't
that
we've
only
died.
So
more
than
that,
you
just
lose
focus
and
we
cannot
go
forward.
I
was.
C
C
Okay,
how
many
people
are
actually
would
actually
be
doing
that
and,
and
is
that
primarily
to
serve
your
own
interest
or
the
interest
of
a
couple
of
I
I
volume
customers,
or
is
this
something
that
should
go
in
a
broad
open
source
project
and
I'm
still
not
saying
that
if
you
choose
a,
you
should
do
X
or
the
other
way
around,
but
I'm
just
wondering
what
is
the
perspective
here?
I
think
you're
already
answering
quite
a
bit
on
that.
Well,.
A
Let's
say
that
what
is
not
the
goal
here
so
XMPP
in
this
entire
project
is
not
a
goal
and
it
used
to
be
that
XMPP
was
this
toolbox
and
there
was
value
in
Oh
Union,
just
generically
implementing
parts
of
X
and
P
being
generically
compliant
with
XMPP,
and
that's
not
a
goal
here.
Xmpp
in
this
case
is
just
a
tool
that
solves
problem
for
us,
so
there's
no
debate
around.
A
C
A
C
A
Absolutely
thank
you.
Thank
you
for
being
so
considerate.
Another
thing
that
I
wanted
to
point
out
is
that
we're
not
completely
carefree
about
what
it
what
happens
to
people
who
actually
want
to
run
components,
so
we
were
actually
having
an
argument
a
couple
weeks
ago
about
once
we
make
the
bridge
connect
with
client
connections.
Would
we
remove
the
code
that
allows
it
to
connect
their
components,
which
I
expect
that
we
were
doing
and
actually
on
this
call
Boris
said,
but
no,
maybe
we're
not
going
to
remove
that
and
then
he
appreciated
mean.
C
A
C
No,
this
is
exactly
I'd.
Much
rather
have
clarity
in
an
answer
that
I
might
not
fully
hope
for
then
not
ask
Larry
at
all,
because
then
I
don't
know
what
I'm
yeah.
What
lay
of
the
land
is.
So
this
was
very
helpful
that
said,
I
did
have
another
question,
but
I
totally
forgot
it.
I
should
write
these
things
down
before
joining
this
call.
So
that's
it
for
me.
I'm,
not
sorry,
remember
what
I
was
gonna
ask
next
sure
anyone.
C
F
F
It's
not
better
now
that
is
excellent.
Much
okay,
so
most
of
you
probably
have
been
noticing
that
I've
been
working
on
the
snack
for
branches
and
thanks
to
Brian
and
I.
Think
Aaron
I've
got
my
own
instance
now
to
test
with,
because
I
didn't
succeed,
compiling
the
client
stuff,
so
I
was
able
to
connect
the
bridge
and
Chico
photo
and
using
my
mobile
phone
and
the
browser
and
I
succeeded
in
creating
a
call
with
smack
for
sewing
yeah.
F
F
B
F
F
To
run
it,
I
can
help
with
that
yeah,
so
yeah
in
general.
How
are
we
going
to
proceed?
Actually,
they
create
a
pull
request
and
since
there's
a
release
today,
it
might
actually
be
possible
to
merge
that
in
a
feasible
time
line,
or
is
there
some
general
position
that
you
want
to
wait
until
the
next
release
or
yeah
just
how
we
going
to
proceed.
A
F
Repeated
well
that
the
branches
are
at
least
for
the
video
bridge
and
for
Chico,
fo
and
JT
desktop
I.
Think
the
branches
are
in
a
state
where
I
could
create
a
pull
request.
There's
certainly
some
work
needed
and
stuff
that
I
can't
test,
for
example.
But
yet
basic
question
is:
should
I
create
the
pool
requests
now
or
do
you
wanna
have
a
look
at
the
branch
before
creating
them
and
yeah
just
generally.
A
F
I
can
guarantee
you
that
the
automated
tests
are
gonna
fail
because
there's
quite
a
bit
of
interdependencies.
First
of
all,
we
need
to
merge
or
I
get
that
JT
desktop
there
or
actually
the
jingle
notes
plug-in
then
JT
desktop.
Then
the
video
bridge
then
Chico,
fo
and
then
the
other
component.
So
if
I
just
trade,
the
pool
request
for
the
wheelie
rich
now,
for
example,
it
doesn't
have
the
components
or
the
classes
necessary
necessary
from
chitti
desktop
and
so
on.
You
name.
The
branch
is
the
same
I
think
it'll.
G
B
A
H
A
F
The
first
thing
to
do
when
that
doesn't
affect
anything
in
either
case
would
be
then
to
publish
the
jingle
know
it's
API
and
maybe
publish
it
in
maven.
Central
in
any
case,
that's
something
I
can
do
by
myself.
Then,
if
you
don't
disagree,
then
I'll
merge,
JT
desktop
or
maybe
we
can
do
a
release
there
as
well
before
pushing
other
that
because
I'm
sure
there's
a
also
box
left
I
to
do
that
with
Damien.