►
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
Hey,
okay
is
this:
can
you
see
the
presentation?
Yeah?
Okay,
so
I'm
gonna
start
with
a
controversial
topic
which
is
fun.
A
So
this
is
about
the
navigation
start
time
and
who
needs
to
know
the
navigation
start
time,
and
we
touched
a
little
we're
touching
this
in
the
last
worker
call
and
it
seemed
like
a
good
idea.
It
seemed
like
it
was
just
a
start
of
a
conversation
and
also
and
there's
a
lot
of
discussion
on
the
issue.
A
I
would
say
kind
of
a
polarized
someone,
four
hours
conversation
about
this.
Oh,
we
should
definitely
do
this
or
we
should
definitely
not
do
this,
which
makes
it
interesting,
yeah
so
yeah.
I
would
like
to
do
a
short
presentation
about
this
and
then
get
to
the
discussion.
A
If
the
global
object
is
a
window,
the
time
origin
is
the
time
of
starting
the
navigation,
where
starting
a
navigation
is,
for
example,
when
you
click
a
link
or
when
you
submit
the
form,
it's
something
that
happens
on
some
origin.
That
is
not
necessarily
related
to
where
you're
going
it's
before
the
unload
events.
It's
before,
whatever
you're
doing
in
the
server
so
the
time
origin
is
our
zero,
our
epoch
for
everything.
So
all
the
performance,
timing
numbers
their
zero
point.
Is
that
time,
origin
really
everything
performance
that
now
uses
time
origin.
A
A
A
A
A
In
other
case,
I
submit
a
form
at
site:
a
dot
com
site,
a
dot
com.
I
process
the
post
request
from
the
form
and
only
after
I
process
the
post
request.
I
send
back
a
response
with
location
to
sitep.com,
so
the
pre-history
time
has
grown,
and
maybe
I
can
extrapolate
that
there
was
a
post
request
that
something
happened
there.
A
Maybe
there
was
some
expensive
database
put
before
a
before
the
server
sent
the
response
to
my
to
my
site
and
another
thing
doesn't
even
have
to
be
a
redirect
because
navigation
start
happens
before
a
bunch
of
events.
A
Now
also,
all
of
those
are
combined.
So
this
prehistoric
time
is
actually
a
big
cloud
of
many
many
things
a
submit
a
form
on
the
first
domain.
You
get
all
the
events,
then
you
process
the
submit.
Then
you
get
a
redirect
to
another
domain,
that
domain
redirects
to
your
domain
and
you
get
this
big
bunch
of
time.
That
is
your
really
the
time
between
zero
and
your
redirect
start
or
fetch
start.
A
Now
this
is
two
sides
of
problem.
First
of
all,
in
site
b.
Maybe
there
are
things
I
can
figure
out:
okay,
usually
extrapolating
them
from
statistics
which
is
like
how
people
were
reacting
in
the
responding
in
the
on
the
github
issue.
A
A
A
I
can
maybe
extrapolate
that
there
was
a
an
ad
broker
or
something
like
that
on
the
way,
and
now
one
thing
that
is
maybe
extrapolatable
in
a
more
direct
way
is
the
some
sort
of
implicit
session
sharing
between
site
a
and
site
b.
Let's
say
I
have
an
regular
a
anchor
link
from
site
a
to
site
b.
It
has
nothing
on
it,
just
an
href
to
my
site,
but
when
the
link
is
clicked,
I
send
the
beacon
just
with
performance.time
or
something
like
that
and
on
site
b.
A
A
A
A
You
just
don't
know
if
some
websites
redirected
to
you
and
how
there's
a
very
long
page
hide
event
like
how
is
that
your
responsibility,
so
people
complain
my
numbers
dropped
because
some
site
linking
to
me
had
a
long
unload
event.
A
People
can
even
do
a
malicious
effects
on
other
sites,
loading
time
by
doing
slow
redirects
to
them,
not
that
we're
seeing
that
in
practice
right
now,
but
it
raises
the
question
of
other
destination
site.
Is
that
my
responsibility
to
optimize
my
redirect
my
cross-origin
redirect
times
when
I
don't
even
know
it
don't
even
know
who
redirected
to
me.
A
So
I
see
this
problem
as
a
graph
between
potentially
harmful
and
potential
potentially
useful
things
that
are
either
on
one
corner
of
it
or
on
the
other
corner.
If
I,
if
I
can
figure
out
what
happened,
then
I
can
also
extrapolate
cross-origin
information
and
that's
the
only
way
where
this
information
can
also
be
valuable.
To
me
on
the
other
corner
of
it
is
one
of
many
things
could
have
happened,
and
I
don't
know
what
I
just
know
know
that
prehistoric
time
was
long
or
short
and
then
it's
not
really
useful
information.
A
A
A
A
A
The
other
option
is
to
move
the
time
origin
to
the
redirect
start
time
of
the
current
origin,
meaning
if
I
still
have
some
same
origin
redirects,
I
can
have
a
redirect
start
and
when
they
start-
and
I
just
don't
know
if
I
was
redirected
here
by
something
that
took
a
long
time
either.
If
I
unload
long
island,
unload
events,
or
course,
stories
or
redirects
or
posts
or
whatnot
or
quarks,
is
and.