►
From YouTube: Signed exchanges in Chrome - Kinuko Yasuda & Jim Pick
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
So
I'm
very
excited
to
be
here
to
talk
about
what
I
could
to
learn
about
ipfs
and
the
committee,
and
also
to
explore
what
browsers
and
the
web
standard
can
do
for
decent
rise.
The
content
consumption
on
web,
so
I'd
like
to
talk
about
our
recent
web
standard
proposal,
which
is
called
signed,
HTTP
extents,
it's
a
kind
of
simple
concept:
it's
a
format
that
represents
an
HTTP
request/response,
but
it's
cryptographically
signed
with
a
certificate
so
that
the
content
can
tell
the
true
origin
of
content
over
like
what
plasm.
A
Well,
what
organization
has
published
the
content
and
also
like
I,
can
tell
the
intuited
of
the
content
so
that
you
can
verify
it's
not
modified
from
the
original
content.
So
what
does
this
mean?
The
culprits,
content,
distribution
and
the
content,
attribution
I.
Think
I
probably
sounds
natural
to
you
too.
You
may
be
natural
to
you,
but
lemme
know
that
this
is
a
web
standard
proposal
where
things
are
basically
things
between.
A
It
will
rely
on
the
situation
and
thisis
connection
to
the
origin
server
to
be
able
to
verify
the
origin,
and
we
are
trying
to
propose
a
new
alternative
architecture
to
the
web,
so
that
the
winner
brought
a
lot
this
content
or
the
signature.
It
can
actually
show
the
true
origin
in
the
address
bar
and
also
it
can
give
the
right
permission
to
that
origin.
A
So
here
are
a
little
bit
more
details
about
Zionists.
It
be
exchanged
the
basically
resource
in
the
certificate,
and
so
signature
told
we
are
we
Europe
certificate,
information
and
integrity
information
wherever
our
skip
was
other
details.
So
I
mentioned
that
it's
a
new
web
standard
proposal,
but
it's
actually
also
implemented
in
the
ship
in
chrome
so
that
you
can
try
it
on
Chrome
today
and
the
gym
it's
going
to
show
always
on
them
how
this
can
work
with
IPSS.
B
Okay,
so,
okay,
we
recorded
this
video
and
it
might
loop
so
I'm,
making
a
webpage
I'm
just
going
to
upload
it
to
ipfs,
pretty
standard
static,
HTML
based
website
and
it's
been
uploaded.
Ipfs
and
I
created
a
web
service.
You
can
go
to
it's
just
prototype
login
with
you
github
account,
so
anybody
can
try.
It
create
a
site
name
so
I'm
calling
this
SXG
demo
and
as
my
github
and
put
this
the
idea
in
there
and
hit
publish
this
is
sped
up.
B
But
it's
going
to
read:
read
the
static
site
from
IVFs
sign
it
with
signed
exchanges,
aren't
using
SSL
cert
that
I
own,
and
then
it
published
it
to
ipfs
and
then
I
can
load
it
in
chrome.
It
loops
it
published
a
site
and
when
you
click
on
it
in
chrome,
it
was
there
and
which
is
really
neat
because
it
doesn't
exist
on
an
HTTP
web
site
anywhere.
It
just
only
exists
in
ipfs,
but
it
has
all
the
security
benefits
of
running
it
on
a
hosted
website.