►
From YouTube: 2021-10-14 meeting
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).
C
A
Working
on
some
something
that
we
talked
sunday
time
ago
about
the
you
know:
ntp,
synchronization
and
that
stuff.
Do
you
remember
that.
D
A
Implemented
sending
the
date
in
your
phone
in
order
to
synchronize
the
network
request
with
the
backend.
Oh.
A
Yeah
yeah,
I
was
just
creating
a
yeah,
an
an
ntp
clock
cool,
so
it
was
really
easy,
as
I
expected.
A
Yeah,
because
it
has
support
for
adding
your
own
clock
so
yeah
I
I
was
just
just.
I
found
a
limitation
with
the
library,
but
it
was
using
that
it
only
can
run
on
the
main
thread,
but
for
the
rest,
it
has
been
really
really
easy.
So
nice
yeah,
I
was
even
thinking,
but
it
it
uses
a
third-party
library.
So
adding
that
to
the
examples
was
maybe
adding
just
a
library,
because
you
want
to
show
some
examples.
Sounds
a
bit
yeah
yeah
a
bit
high,
but
yeah.
C
A
Yeah,
I
don't.
I.
A
I
I
added
just
one
topic
that
I
was
working
now
and
it
was
so
we
see
that
I
didn't
know
if
at
that,
to
the
documentation
as
an
example
code
or
something
that
because
it
was,
it
was
really
easy
to
do.
But
I
don't
know,
let
me
share
the
screen.
E
F
A
Then
maybe
my
my
code
can
be
can
be
useful
on
your
on
your
tutorial,
because
it's
something
that
is
a
basic
but
interesting
topic
that
can
be
easily
solved.
Also.
A
Yeah
so
let's
start
then
yeah
yeah,
I
have
another
topic.
I
will
put
the
first
one.
A
Something
I
did,
but
I
wanted
just
your
confirmation.
I
okay
last
meeting
actions.
Let's
see
yeah,
we
checked
the
latest
pr's
and
short
term
updates
that
I
think
that
all
of
them
were
merged.
We
had
the
and-
and
we
talked
about
xcode
13
status,
okay
about
the
pr's.
I
think
that
we
talked
about
then,
and
they
are
already
merged.
A
Now
working
with
the
otlp
exporter
missing
is
the
broadband
exporter,
for
example,
doesn't
support
it
currently
and
also
datalog,
isn't
supporting
that,
but
I
created
a
a
bit
of
issues
in
the
project
to
track
that
and
the
other
thing
I
did
was
releasing
a
beta
version
and,
oh
sorry,
and
also
there
was
the
x
code
13
status
on
mac
os
that
we
were
talking
that
it
was
needed
the
beta
to
work
on
that.
A
I
changed
the
code
to
make
it
work
on
xcode13.
I
had
to
update
the
libraries
that
we
were
depending
on
because
they
were
not
compiling
with
mac
os
version,
but
they
were
compiling
with
ios.
I
don't
know
what
they
had
in
them,
but
after
updating
them
and
updating
some
of
the
code
of
the
library,
it
was
building
again
with
xcode
13
the
standard
version
b.
Not
so,
if
you
spend
10
hours
downloading
the
beta.
A
So
well,
then,
as
that
was
working
with
that
version,
I
I
I
thought
that
it
was
a
good
time
to
release
a
a
new
version
of
the
library
with
yes,
the
xcode
13
working
officially
and
with
the
instagram
metrics.
A
So
I
decided
maybe
a
bit
on
my.
So
I
wanted
to
check
with
you
if
you
are
okay
with
the
decision,
or
I
can
just
put
it
again,
so
I
changed
the
rhythm
to
say
that
it
was
not
so
better
as
expected,
because
I
think
it's
not
so
better
as
it
was
in
the
rhythmic.
Currently
we
have
people
using
metrics
also,
so
we
could
say
that
metrics
is
working,
even
a
pr
appeared
from
a
user
that
is
using
that.
A
So
if
it
was
not
working,
they
wouldn't
create
new
new
types
of
metrics,
so
that
was
the
only
source
code
that
was
not
really
tested.
So
we
can
consider
that
it's
also
working.
So
I
changed
the
rhythm,
so
it
shows
the
state
better.
A
I
removed
the
experimental
label
from
there,
so
they
now
doesn't
show
us
dangerous
to
work
with
and
they
should
be
working
as
expected,
and
also
this
version.
I
I
removed
the
beta
version
from
the
version
live
label.
So
now,
instead
of
one
zero
six
beta,
it
shows
one
zero
six
plane,
because
I
think
that
now
I
mean
all
of
the
areas
have
been
tested
and
everything
is
working
more
or
less
in
a
respected
way.
It
can
have
boxes
all
software,
but
it's
being
used
or
in
production
or
almost
in
production
by
several
several
people
now.
A
Maybe
I
should
have
waited
for
today
before
doing
that,
but
just
thought
that
having
instagrams
and
xcode
13
was
good
enough
for
having
a
version
and-
and
I
think
the
code
is
in
a
very
good
state-
it
was
better
than
we
expected
then,
when
we
leveled
this
beta,
because
we
have
almost
no
received
issues
with
it,
but
people
is
using
and
having
good
results.
So
we
can
expect
that
to
be
now
quite
stable,
so
yeah,
I
don't
think
if
you
have
any
objections
to
that.
D
B
I
think
it's
yeah,
I
think
it's
a
good
change.
The
only
the
only
thing
that
I
want
to
bring
up
is
just
using
minor
version
rather
than
the
hotfix
version,
because
I.
A
A
Okay
but
yeah
I
I
can
release
an
mineral
version
if
you
think
it
it
deserves
it
yeah.
It
was
just
using
mineral
version,
because
people
will
operate
easier.
Yeah.
A
I
can
we
can
release
that
as
a
that's,
a
mineral
version,
if
you
want.
B
A
Okay,
yeah,
that's
true,
and
if
we
don't
have
the
beta
label,
we
we
should
follow
yeah
semantic
versioning,
better,
okay,
yeah,
okay,
so
yeah.
A
Okay-
okay-
oh
sorry,
this
should
be
instead
of
here.
A
Yeah,
okay,
yeah
the
rest
of
the
topics.
I
I
had
one
topic
here
about
talking
about
something
I
had
work.
I
I
was
working
on
that
we
talked
before
with
bryce
about
yeah
the
problem
with
having
your
servers
clock
having
a
different
plug
than
your
clients.
A
I
think
that
bryce
use
a
a
way
of
reporting
that,
by
using
the
time,
differences
between
the
server
and
the
client
or
something
like
that.
But
the
other.
A
B
C
D
A
Yeah
yeah,
this
is
my
ntp
synchronized
clock,
it's
using
a
library
in
swift
that
is
very
common
for
ntp
synchronization,
and
it
has
its
own
clock
that
you
just
have
to
call
sync
first
time
and
it
starts
loading
the
time
and
it
just
returns
that
as
when
you
just
yeah
the
thing
is:
I
have
to
use
the
name
of
the
library
here,
because
we
have
both
a
clocking
up
and
telemetry
sdk
a
clock
in
the
chronos
module.
A
So
I
have
to
have
the
name
before,
but
just
this
just
calling
here
the
synchronization
and
on
the
and
implementing
this
method
of
the
clock
that
it's
a
protocol
yeah.
It
just
has
this
new.
This
now
sorry
method.
Just
implementing
this
and
using
the
now
method
of
the
this
kronos
library
it
works.
The
only
limitation
here
is
that
it
needs
to
work
on
the
main
thread.
A
Synchronization
always
happen
on
the
main
thread,
but
you
have
to
call
it
on
the
main
thread.
So
here
I
have
to
check.
If
it's
the
main
thread
I
use
it
directly
or
if
it's
running
another
thread
make
it
running
on
the
main
thread.
It
was
the
simplest
implementation,
but
just
with
this
and.
A
A
How
to
say
yeah
in
open
telemetry
we
have
this.
The
span
has
its
own
sorry.
In
yeah,
we
have
here
the
clock
yeah.
We
have
here
the.
A
A
So
even
if
the
original
clock
changes
time,
because
usually
the
ntp
clock
will
be
maybe
updating
or
synchronizing
in
the
future,
the
expanse
will
can
change
the
start
time,
but
they
will
never
use
a
different
duration,
so
that
was
already
implemented.
A
D
A
Just
using
the
just
using
this
and
setting
us
the
active
clock-
oh
sorry,
that
was
not
it
so
yeah
just
having
this
class
using
a
library,
of
course,
but
just
using
that
and
setting
it
in
the
tracer
provider
once
you
create
it
before
getting
the
the
tracer
sdk
just
works.
So
it's
very
easy.
Maybe
it's
something
that
you
can
add
to
the
example.
We
not
that
you're
talking
after
this,
it's
just
yeah,
it's
just
20
lines
of
code
for
having
the
the
clock
synchronized
with
an
ntp
server.
E
So
so
this
is
on
the
tracer
right,
so
you're
you're
setting
it
up
when
you're
yeah
the
setting
is
called
in
the
literature
provider.
E
Yeah,
so
so,
if
you
have
this
on
a
device,
the
first
first
time
it
actually,
you
know
if
you
have
an
interaction
or
not.
A
A
A
E
Maybe
that
what
if
it
doesn't
what
if
it
doesn't
have
access,
you
know
it's
not
able
to
sync
with
the
ntp
clock.
A
Yeah,
if,
if
it
doesn't,
has
a
value,
it
will
take
the
the
default
time.
If
it
couldn't
connect
to
the
servers,
it
would
use
the
default
time.
A
B
If,
if,
if
the
device
can't
connect
to
the
internet
yeah,
then
we're
not
going
to
have
any
clock
skew
issues,
because
it's
not
sending.
A
Yeah,
maybe
yeah,
maybe
you
can
have
the
problem,
that
you
are
offline,
recovering
data
and
sending
that
after
so
maybe
then
your
clock
wouldn't
be
the
best
so
yeah,
I
don't
know
how
how
that
will
work.
E
A
A
The
library
itself
connects
to
the
server
several
times.
It
makes
a
different
connection,
so
it
updates
the
offset
and
the
and
the
current
date
cool.
So
as
we
have
the
other,
I
mean
this.
This
could
change.
I
mean
this
could
have
some
time
differences
between
if
you
check
now
or
you're,
checking
maybe
10
seconds
but
as
the
span
only
uses
it
on
creation
time
and
not
right.
B
B
A
A
So
I
was
not
very
sure
about
yeah
what
to
do
with
that,
because
that
will
mean
that
all
the
yeah
all
the
project
will
will
have
yeah.
Let's
what
is
this?
No
all
open
telemetry,
it
will
add
a
dependency
to
all
the
users
of
open
telemetry.
B
A
Yeah,
the
current.
It
only
has
this
swift
atomics
dependency,
that
it's
an
apple
library
but
having.
C
A
E
E
I
tested
you
know
with
the
data
xcode
for
that
service
name,
and
I
still
don't
see
it.
Actually,
I
just
updated
it
with
the
xcode
13
and
even
though
the
order
of
service
name
right
is,
it
still
shows
up
as
unknown.
E
A
F
A
B
Okay,
I
don't
think
we
have
service
name,
it's
it's
not
that's,
not
what
it's
looking
for!
It's
looking
for
hotel
resource
attributes
in
var
and
you
need
to.
B
E
B
Hold
on
no,
so
we
only
do
the
the
top.
One
is
the
only
one
that's
implemented.
B
B
Yeah
yeah
check
it
check
the
yeah
yeah.
E
E
C
A
B
Yes,
I
I
went
to
the
client
side
sig
yesterday
and
they
are
working
on
kind
of
defining
all
the
issues
with
client-side
monitoring
and
that
sort
of
thing
so
they're
discussing
like
what
sessions
are
and
that
sort
of
thing.
So
I
thought
it
might
be
good
for
you
all
to
review
it
just
so
that
you're
up
to
date
on
what's
going
on
in
that
and
that
sig
is
gonna,
probably
affect
what
we're
doing.
B
A
Yeah
great
yeah
thanks
a
lot
I
I
am
not
directly
doing
any
ram
work
but
yeah.
I
know
there
are
yeah
there
are
people
interested
in
it
and
also
the
project
will
need
to
support
all
the
all
this
stuff,
because
I
think
that
yeah
problem
is
what
people
is
more
interested
to
do
with
open
telemetry
on
you
definitely
yeah.
B
Yeah,
I
think
I
think
mobile.
You
know
anything
that
has
users
right
like
browser.
It's
like
we're,
not
gonna,
get
away
with
it
or
get
a
get
away
with
ignoring
it,
because
it's
what
everybody
kind
of
gets.
It's
weird,
because
you
know
the
the
the
apm
kind
of
gets
blurred
with
user
monitoring
and
user
analytics
on
this
side
of
things.
So.
G
B
E
B
That's
weird
because
when
I
in
my
pr
I
was
testing,
I
was
using.
E
D
G
A
Okay,
so
I
think
it's
any
other
topic
that
you
want
to
talk.
E
A
E
So,
let's
the
client
side
is,
you
know
there
is
also
the
people
from
the
node
or
the
javascript
site
right
on
the
on
that.
B
Yeah
browser
it's
yeah
browser,
yeah,
the
whole
client
side,
kind
of
kind
of
group,
browser
ios,
android,
there's
a
couple
of
there's.
Actually
it's
quite
funny
because
it's
a
large,
it's
a
pretty
large
sig.
There
are
a
lot
of
people
in
there.
E
E
Issue
with
you
know
the
swift
clients
right
I
mean
because
these
guys
these
devices
are
gonna,
be
out
there
right.
So
so
they
all
need
yeah
if
they're
using
otlp
or
these
endpoints
are
all
cannot
do.
Grpc
right,
they'll
have
to
do
http
connect.
D
D
E
You
know
what
I
mean
is
you
know
they
have
to
have
you
know
either
you
need
to
have
the
exporter.
That
is,
for
you
know
a
specific
vendor
back
end
or,
if
you're
using
oplp
you
need,
I
mean
not.
All
of
all
the
projects
have
most
of
the
tlp.
Endpoints
are
grpc
endpoints
right.
They
don't
right.
E
B
The
collector
will
be
able
to
accept
both
gr's,
pc
and
http
traffic.
I
don't
know,
maybe
not
not
not
sure
you
might
be
a
little
bit
more
familiar.
Oh
okay,
okay,.
A
C
D
G
B
I
know
that
we're
using
what
we're
doing
is
we're
wrapping
the
hotel
collector
with
our
own
service,
and
it
does
handle
http
and
grpc.
A
I
mean
we
are
using
that
because
they
were,
I
mean
there,
were
people
interested
in
having
that.
I
think
I
I
don't
know,
and
it
was
a
third
party.
A
Someone
created
those
the
otlp
json
exporter.
A
A
Yeah,
okay,
because
you
you
needed
it
for
years,
but
I
don't
think
that
was
in
the
spec
I
mean
or
tlp.
If
it
had
been.
Probably
I
would
have
implemented
it
because
I
I
I
implemented
all
the
things
needed
for
the
for
the
spec
in
order
to
have
a
better
version
yeah
at
the
beginning.
So
I
didn't
remember
having
that
on
the
plan
for
implementing
that
right.
Maybe
it
was
not.
I
don't
know,
supports
http
of
directly
so.
E
Is
you
know
assumption
is
there
will
be
a
collector?
Is
that
what
the
assumption
is.
A
I
would
say
so,
but
maybe
the
collector
can
be
in
your
back
end,
wrapped
in
a
service
or
something
like
that
and
receive
the
grpc
directly
yeah.
B
So
maybe
I'm
mixing,
oh,
you
know
I'm
mixing
up
what
elastic
is
doing
so
with
what
tlp
is
doing
so
I'll
just
be
quiet.
A
A
C
A
Connection
with
through
internet
doesn't
seem
like
the
best
approach.
I
mean
it
has
lots
of
communication
right
synchronization
packets
between
the
services,
not
something
like
you-
send
information
as
internally
easily
so.
E
So
grpc
requires
http
2
right,
that's
another.
I
think
requirement
so
yeah,
but
yeah.
A
It
should
be
supported
in
yeah,
but
yeah.
That's
true,
I
don't
know
but
yeah
for
for
a
mobile
device
having
the
collector
is,
doesn't
look
like
the
best
option,
probably
using
something
like
what
price
I
think.
Bryce
is
using
otl
pjson
right
for
sending
your
results
to
a
compatible
backend.
I.
B
Think
I'm
using,
I
think,
I'm
using
grpc.
B
Yeah
yeah
yeah
yeah,
so
the
the
implementation
that
we
have
is.
We
have
like
a
collector
kind
of
object
that
contains
the
hotel
collector
in
it
and
that
processes
all
the
hotel
data
that
the
mobile
agent
sends
and
it
yeah.
It
looks
good
yeah.
C
C
A
Server
or
or
having
local
yeah
I
mean
that
the
delays
you
have
in
the
mobile
can
be
more
or
less
painful
in
that
respect,
but
maybe
it's
not
maybe
it's
much
better
than
what
I
thought
about
it
early
on
I
mean
I
have
not
used.
I
remember
ipc.
That
is
what
year
pc
is
based
on
and
it
was
quite
heavy,
but
I
don't
know
if
that.
G
B
Yes,
I
think
they've
only
had
about
three
meetings
so
far
and
I
missed
the
first
two
so
I
went
to
I
went
to
my
first
one
yesterday
and
I
intend
to
I
intend
to
go
to
that
weekly,
but
I'll
keep
I'll
keep
you
all
updated
on.
What's
going
on
over
there.
A
Yeah,
the
thing
is
that
we
will
probably
have
to
implement
some
of
the
things
that
they
will
are
planning
there,
because
yeah,
I
can
expect
many
users
of
wanted
ram
implemented
with
open
telemetry
entry
that
that's
absolutely.
G
A
High
market,
I
expect
more
people
wanted
that
than
just
implementing
companies
implementing
themselves
their
telemetry
yeah.
B
Yeah
for
sure,
there's
a
lot
of
browsing
people
a
lot
of
android
people
over
there,
a
lot
of
ios
people,
so
maybe
yeah
more
yeah
coming
over
there
and
yeah,
giving.
A
A
Yeah
they
they
connected
to
the
project
because
they
had
some
issues.
Do
you
remember
with
the
third-party
libraries
that
and
the
right
cocoapods
thing,
but
they
were
using
it,
they
hadn't
say
that
they
were
using
it,
but
they
were
in
fact
using
it
and
they
it
was
working
well
for
them.
So
yeah
we
have
several
more
users
than
we
expect
and
are
happily
using
it,
and
no,
this
is
appearing
that
that's
surprising.
I
mean
I
I
could
expect.
A
Okay,
so
I
think
we
probably
can
leave
it
here
for
today.