►
From YouTube: IPFS, Browsers & The Web - Turning the Biggest Ship - Dietrich Ayala - Browsers and the Web Platform
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
This
is
kind
of
like
just
triangulating
what
our
team
does
we're,
not
just
browsers.
We
do
things
extra
browser
as
well,
and
a
bunch
of
other
things
related
to
fatcoin
library
is
tooling.
You've
probably
seen
this
slide
before.
I
think
I've
showed
it
four
times
in
the
last
two
days,
but
it's
a
pretty
good
yeah.
It's
a
mostly
accurate
state
of
things
with
regards
to
browsers
on
the
web.
Today,
there's
like
an
entire
universe
of
like
alt
browser,
I
guess
alternative
browser.
A
That's
really
exploding
right
now
and
we're
going
to
hear
from
movon
about
aggregator
later,
but
there's
all
kinds
like
really
I'm
just
seeing
a
huge
amount
of
activity
and
investment
around
things
that
are
not
these
browsers,
and
that
is
super
super
exciting.
That's
something
we're
like
we're
not
really
going
to
get
into
much
today,
but
I
encourage
you
like
join
our
browsers
and
platforms
channel
on
the
file
coin
slack.
It's
also
bridge
to
matrix,
also
bridge
to
the
fps
discord,
and
we
talk
about
a
bunch
of
those
things.
A
Whenever
we
see
new
browser-related
things
or
web-related
things,
we
drop
them
in
that
channel
and
hang
out
and
chat
about
it.
So
you
are
welcome
to
join
that
conversation.
This
is
way
more
green
than
I
think
I
expected
it
to
be,
even
after
being
at
pl,
for
just
over
three
years,
we've
made
some
pretty
significant
strides.
A
We
have
some
very
aligned
partners
in
browsers,
like
brave,
but
also
some
areas
where,
in
some
of
the
biggest
browsers,
you'll
see
a
lot
more
red,
and
you
know
there's
a
number
of
reasons
why
why
that
is
everything
from
architectural
differences
to
our
lack
of
participation
in
standards
bodies
and
things
like
that?
But
some
oddly
interesting
supporters,
champions
and
strange
places
as
well
and
so
I'll
cover
I'll
cover
a
little
bit
of
that
that,
from
a
challenges,
standpoint,
there's
a
lot
of
them.
A
Work
are
really
paradomatically
different
than
how
we
envision
trust
and
security
in
ipfs,
the
composability
of
ipfs
and
the
you
know
stack
all
the
way
down
to
the
bottom
is
a
radical
re-envisioning
kind
of
of
how
you
would
build
an
internet
as
opposed
to
maybe
just
the
www
part
of
the
web
today,
and
that
means
that
there's
no
no
shortage
of
places
where
we
might
have
differences
either
architecturally
or
from
some
of
these
really
specific
sticking
points
when
it
comes
to
privacy.
Specifically,
the
ipfest
public
network
is
exactly
that.
A
It's
public,
you
can
see
everything
that
happens
on
it,
but
oftentimes
too
there's
a
a
gulf
between
the
the
places
which
we
are
coming
from
and
the
end
user
problems
that
we
are
trying
to
solve.
When
we
are
looking
to
implement
our
protocols
inside
web
browsers,
to
make
them
more
broadly
available
to
application
developers
and
to
publishers
of
data,
then
the
you
know
traditional.
A
I
guess
the
institutional
web's
not
the
right
way
to
describe
it,
but
the
set
of
people
who
are
decision
makers
at
standards
bodies
today
around
what
browsers
can
encounter
you.
So
a
lot
of
this
comes
down
to
a
ongoing
clash
of
cultures
and
philosophies
and
politics
around
what
the
web
should
be.
A
Who
and
who,
who
even
gets
to
decide
that
when
somebody
like
the
the
you
know,
amount
of
skepticism
and
almost
fear
in
some
places
around
using
the
phrase,
web3
is
really
telling
around
that
who
has
or
who
or
how
many
people
have
their
hands
on
the
ability
to
change
what
the
definition
and
meaning
of
the
web
is.
A
If
you
spend
some
time
reading
through
a
very
interesting
document
written
by
the
technical
architecture
group,
the
w3c,
which
is
called
the
ethical
web
principles,
it's
very
interesting
to
look
at
that
document
and
look
at
the
web
as
it
is
today,
the
web,
the
http
web,
and
look
at
the
vision
that
it
paints
and
what
some
of
the
protocols
like
ours
are
trying
to
do.
A
You
know,
I
think,
a
lot
of
the
way
that
developers
think
about
the
web
and
what
we're
trying
to
do
is
a
little
bit
like
this,
even
though,
as
martin
will
show
us,
that's
a
little
more
complicated
than
this
these
days,
even
when
developing
http,
and
when
we're
approaching
the
problems
that
we
want
to
solve
in
browsers
today
that
we
want
end
users
to
be
able
to
really
access
really
lower
the
barriers
to
be
able
to
access
architectures
like
this,
where,
if
you're
in
the
same
room,
you
can
build
applications
that
work
together
and
talk
to
each
other
without
having
any
data
having
to
leave
the
room
which,
which
with
dns,
is
basically
already
impossible
for
the
most
part,
unless
you're
hacking
things
locally
and
really
like
thinking
about
how
humans
interrelate
on
the
internet.
A
And
how
can
we
build
applications
that
connect
them
in
ways
that
really
slowly
telescope
out
in
in
this
way
and
architecture's
the
support
this
like
a
mix
and
matching
type
of
ways
that
people
can
communicate
with
each
other?
It's
it's
really
not
easy
and
it's
a
difficult
thing
to
communicate
this
to
people
who
really
fundamentally,
even
though
the
network
doesn't
operate
like
this
still
think
about
it
like
this
and
that
that's
a
challenge,
not
just
you
know
socially,
but
also
you
know
technically
and
politically.
A
I've
done
a
talk
called
ipfs
in
weird
places
and
honestly
like
they're.
Just
not
that
weird
and
one
of
the
interesting
things
about
the
areas
and
the
environments
that
our
team
codes
too.
Is
that
when
you
look
at
a
list
like
this,
when
you
think
the
web,
you
think
browsers,
but
really
the
web
ends
up
in
all
of
these
different
places,
and
I
removed
a
few
that
you
could
maybe
stretch
and
argue
that
the
web
gets
into
iot
and
satellites
a
bit.
But
the
rest
of
these.
A
You
really
you're
like
all
right
yep
the
web
is
in
almost
all
of
these
other
places
and
pretty
deeply
one
of
the
groups
that
we
work.
A
A
lot
with
and
I'll
talk
a
bit
about
is
the
galia
and
they
are
the
maintainers
of
a
embedded,
webkit
implementation
and
that's
a
web
rendering
engine
that
renders
the
user
interface
that
you
see
on
washing
machines
and
refrigerators
and
coffee
machines
and
one
of
the
probably
most
of
the
most
widely
deployed
web,
rendering
engines
in
the
world,
but
nobody's
ever
really
heard
of
it
very
few
number
of
contributors.
It's
not
really
considered
the.
A
We
can't
interact
with
it
in
ways
that
are
outside
of
that
appliance
generally
and
that
changes
the
nature
of
how
accessible
it
is
to
us
as
builders
or
people
who
want
to
solve
end
user
problems
that
are
relevant
to
us
and
our
mission.
But
the
web
is
broader
than
just
browsers,
and
that
means
more
challenges
sometimes,
but
also
some
opportunities,
and
so
we
really
kind
of
lean
into
that
as
well.
Also
and
really
like-
that's
not
well
represented
in
this
right
like
when
we
think
about
browsers
in
the
web.
A
Today
we
kind
of
think
of
these
very
familiar
icons.
I
guess
I
probably
should
put
the
safari
icon
up
there.
Instead,
webkit
and
more
people
would
have
recognized
it,
but
the
web
really
does
expand
far
far
far
beyond
these.
A
These
set
of
entities,
but
those
are
what
I'm
going
to
talk
about
today,
what
the
gains
that
we've
made
some
of
the
things
that
we've
actually
shipped
over
the
last
couple
of
years
and
then
hand
it
off
to
other
folks
to
talk
about
new
directions
that
we're
going
to
go
new
challenges
that
we're
trying
to
tackle
so
opera
browser
was
the
first
major
browser.
A
Well,
I
don't
know
anybody
that
uses
operant
browser,
it's
because
most
of
their
users
are
in
other
places
like
televisions
and
other
different
types
of
appliances
or
opera
mini
on
smart
feature,
phones,
things
that
aren't
maybe
things
that
you
and
I
are
holding
our
hands
every
day,
but
billions
of
people
around
the
planet
do
so
it's
a
very
interesting
company
in
that
regard,
so
they
shipped
ipfs
and
ips
scheme
support
where
it
redirected
to
a
remote
gateway
to
dewey
like
before
anybody
else
did
they
actually
did
it
across
their
ios
browsers,
their
android
browsers
and
their
desktop
browser.
A
The
company
itself
has
been
bought
by
a
investment
conglomerate.
So
there's
not
really
like
a
a
lot
of
the
people
who
are
like
deep
web
champions
that
were
at
opera
for
many.
Many
years
have
now
since
moved
on
to
other
companies,
but
there's
still
some
some
folks
there
and
we
try
to
keep
the
door
open
and
take
advantage
of
these
opportunities
as
they
come
about.
But
there's
not
really
a
lot
happening
right
now.
It's
definitely
definitely
slowed
down
firefox.
A
I
was
there
for
13
years
building
firefox
web
browser
back
in
the
day,
firefox
os
mobile
operating
system,
and
I
spent
the
last
four
years
doing
developer
relations
and
strategies
so
working
on
things
like
mdn
doing
a
lot
of
talks
and
building
out
kind
of
community
developer
relations
groups.
Like
the
mozilla
tech
speakers,
I
was
had
a
side
project
there
to
add
apis
to
the
browser
that
were
like
the
common
denominator
that
you
would
need
for
browsers
to
be
full
participants
in
distributed
systems
like
ipfs.
A
So
we
said
okay,
what,
if,
as
like
a
a
way
to
do
some
innovating
in
this
space,
we
added
extension
apis
instead
and
that
allowed
a
little
bit
more
kind
of
explicit
user
consent
and
a
model
for
that.
For
those
elevated
privileges
that
you
have
from
an
extension
there's
a
lot
of
interest
in
you
know
the
d
web
world
and
projects
like
ethereum
folks
and
ipfs
super
interested.
A
But
there
were
not
really
a
lot
of
support
inside
mozilla
to
be
able
to
develop
that,
and
that's
one
of
the
challenges
that
we
still
have
today
is
that,
even
though
mozilla
has
a
lot
of
value
alignment
when
you
look
at
like
the
the
mission
of
protocol,
labs
or
ipfs,
or
something
like
that,
and
you
look
that
like
right
next
to
the
mozilla
bishop
you're
like
blew
your
eyes
like
these
look
kind
of
similar,
but
from
an
architectural
standpoint
and
the
what
does
it
mean
to
be
part
of
the
web
standpoint,
they're
really
universes
apart
and
there's
not
really
a
lot
of
interest
there
to
be
doing
the
kind
of
experimentation
that
we
want
to
do
in
browsers
today.
A
So
we
haven't
really
made
a
lot
of
ground
there
and
maybe
even
backwards
when
it
comes
to
things
like
the
even
something
like
the
did.
Spec
at
the
w3c,
where
mozilla
is
one
of
the
formal
objectors
objected
to
the
group
being
formed
and
objected
to
it
being
a
proposed
standard
of
the
w3c.
So
a
lot
of
a
lot
of
friction
in
that
relationship,
but
also
some
opportunities
and
still
obviously
talking
to
folks
there
on
a
pretty
regular
basis,
webkit
and
apple,
no,
no
clear
signals
from
apple.
A
You
know
we
know
some
of
the
developers
on
the
webkit
team.
We
know
people
that
work
in
other
parts
and
try
to
keep
some
back
channels
open
there,
but
not
really
a
lot
of
direct
engagement.
So
we
worked
with
agalia
to
do
some
things
like
interoperability
of
local
host
security
model
handling
in
webkit,
and
even
there
was
just
really
a
lot
of
walls
and
really
difficult
to
make
change.
So
it's
very
slow
going.
A
But
you
know,
of
course,
maybe
the
broader
environment
changing
around
them
sometimes
can
have
like
three
to
five
year
effects
on
the
decision
making
that
apple
makes
about
the
web
and
what
we've
seen
recently
is
like
they've,
hired
up
a
bunch
of
people
that
work
on
webkit
and
safari
and
really
accelerated
things
like
pwa
support
and
also
the
movement
in
european
union
regulations
around
allowing
non-web
kit
rendering
engines
on
ios.
A
I
think
also
might
want
to
be
one
of
those
levers
that
get
things
moving
a
little
bit
so
definitely
in
a
place
to
watch,
but
really
not
a
lot
material
happening.
A
Brave
is
one
of
the
you
know,
as
the
name
implies
they're
very
interested
in
taking
big
experimental
risks
with
what
the
nature
of
the
web
is,
and
that's
a
big
opportunity
for
us.
So
we've
known
folks
there
for
for
way
back
from
going
way
back.
They
bundled
ipfs
extension
quite
over
three
years
ago,
at
this
point
now
or
the
ipvs
companion
extension
and
since
then,
we've
really
engaged
more
deeply.
A
We
have
a
engineer
embedded
on
their
team,
who
only
focuses
on
things
related
to
the
work
that
we're
doing,
and
so
now
we
have
ipfs
and
ipns
game
support.
We
have
a
whole
bunch
of
other
features.
Like
kind
of
peripheral
to
these.
We
have
interesting
experimentation
and
work
in
the
security
ui
of
the
browser.
So
basically,
every
time
we
take
one
of
these
non-http
protocols
and
we
put
it
in
an
http
place.
You
have
to
think
about
what
you
visualize
to
the
user
so
that
they
can
make
decisions
that
keep
them
safe.
A
That's
kind
of
what
the
browser's
job
is,
and
I
think,
if
you
don't
work
on
browsers
full
time,
you
don't
really
think
about
it.
That
way,
but
there's
huge
teams
of
designers
and
security
experts
that
work
together
to
come
up
with
the
things
you
never
really
even
notice
might
be
in
a
url
or
address
bar
in
a
browser.
Every
little
piece
of
user
interface
there
is
is
intricately
designed
very
intentionally
designed
and
there's
a
lot
of
a
lot
of
human
hours.
A
A
Is
that
calculus
that
every
end
user
of
the
web
has
every
time
they
load
a
page
and
it's
one
of
the
reasons
why
we
have
to
take
great
care
even
when
we're
working
with
the
bravest
of
experimenters
in
thinking
about
what
that
user
interface
looks
like,
so,
we've
done
some
great
work
with
them.
A
We're
going
to
be
adding
a
whole
bunch,
more
things
like
nft
features,
and
we
just
added
falco
support
to
their
native
native
wallet
in
the
browser
and
there's
more
stuff
that
we
want
to
do,
especially
in
the
area
of
moving
web
2
data
onto
ipfs
or
allowing
end
users
to
be
able
to
capture
and
save
web
2
data
in
a
way
that
lets
them
share
it.
With
other
people,
save
it
locally
things
like
that,
so
more
to
come
there,
they
now
have
they're
growing,
really
really
fast.
A
So
I
think
yes,
last
week
was
62
million
monthly,
active
users
and
20
million
daily
users.
So
as
a
person
who
worked
as
at
a
not
the
default
browser
at
an
operating
system
for
a
long
time,
it's
difficult
to
underscore
how
much
of
an
accomplishment
that
is
from
a
user
acquisition
and
growth
standpoint.
It's
it's
unbelievable
how
fast
they
are
growing.
A
So
it's
really
good
that
we
have
a
good
relationship
with
them
and
we
can
do
things
together
so,
and
this
is
kind
of
what
I
was
talking
about
like
some
of
the
things
that
work
but
then
also
some
of
the
places
where
we
have
to
be
very,
very
careful,
http
things
and
not
hp
things
co-living
together,
it
can
get
awkward
in
the
same
space.
A
Chromium-
and
you
know,
I
think,
as
well
like
over
90
of
the
web
today
ends
up
being
chromium
rendering
engine
under
the
under
the
covers,
regardless
of
whatever
the
top
level
project
product
is,
and
then
chromium
chrome
browser
itself
being
a
massive
shower
of
of
browsers.
Now
we
work
with
the
golly,
and
so
again
as
a
consultancy,
they've
worked
on
web
rendering
engines
for
about
20
years.
I
think
they
had
their
like
20-year
anniversary
party
last
year,
they've
added
a
bunch
of
accessibility
apis
to
the
web.
A
They've
worked
on
things
like
mathml
they've
worked
with
a
number
of
css
grid
for
bloomberg.
They've
done
a
bunch
of
things,
though
most
web
developers
may
have
never
hear
their
name
ever,
but
you
might
very
likely.
If
you
are
web,
valver
has
used
have
used
code
that
they've
written
they
contribute
to
webkit,
gecko
and
blink,
and
they
are
part
of
the
like
the
deciding
the
decision
makers
of
the
web
a
little
bit.
They
participate
in
w3c
for
a
long
time,
and
so
we
have
a
contract
with
them.
A
Where
we
have
a
full-time
team.
Member
now
focused
on
all
the
things
that
we
want
to
do
on
the
web,
so
we
want
to
be
able
to
add
the
ability
to
register
non-http
protocols
to
chrome
based
web
browsers.
They
worked
with
us
on
that.
They've
worked
with
us
on
a
bunch
of
like
security
and
compat
issues.
How
do
we
make
sure
that
that
would
say,
gecko
and
blink
handle
schemes
the
same
way
that
they
handle
local
host
security
restrictions?
A
When
you
go
that
route,
even
if
you,
if
you
redirect
with
a
remote
gateway,
you
can
maybe
go
an
oddly
http
ish
path
up
and
down
the
permissions
stack,
but
it's
not
really
native,
and
we
really
want
to
reimagine
what
native
ipfs
support
in
the
web
would
look
like
and
to
be
able
to
do
that
in
chromium.
A
Everything
from
like
handing
off
to
the
graphics
pipeline
security
checks,
css
engine,
all
of
the
different
parts
of
these
things
that
are
basically
operating
systems
themselves.
At
this
point,
really
really
massive
code
bases
and
really
massive
communities
of
developers
and
with
chromium,
specifically
a
large
community
of
businesses
that
are
also
building
on
it,
are
all
part
of
like
the
decision-making
tree
and
the
daily.
A
You
know,
operations
of
developing
the
thing,
and
so
again
has
been
our
kind
of
representative
in
that
way,
and
we
haven't
really
poked
so
far
at
things
that
are
specifically
ipfs,
but
we're
just
about
to
turn
that
corner.
So
I
think
it's
gonna
be
an
interesting
like
next
six
to
twelve
months
as
we
lean
a
little
harder
into
doing
actual
ip
fest
things
with
them
in
chromium,
as
opposed
to
just
kind
of
smoothing
out
the
bumps
or
creating
space
for
non-http
protocol
development.
A
Ipf's,
companion
you're
going
to
hear
a
little
bit
today,
probably
from
lytle
and
also
from
david
justice
about
where
it's
been
and
where
it's
going.
So
I'm
not
going
to
spend
a
lot
of
time
there
other
than
it's
a
really
challenging
environment
like
web
extensions
were
first
many
years
not
compatible
across
browsers
now
they're
like
generally
compatible
across
browsers,
but
the
kind
of
like
capability
and
feature
space
has
really
decreased
in
size
with
a
couple
of
major
changes
and
dave.
A
We'll
talk
about
those
changes,
but
it's
made
it
really
difficult
and
it
means
that
it
kind
of
makes
us
have
to
re-evaluate
what
is
the
purpose
of
an
ipfs
extension?
What
can
an
ipfs
extension
be?
What
can
it
do
in
that
available
space
where,
instead
of
kind
of
like
fighting,
what
that
space
has
to
offer?
How
can
we
lean
into
what
that
space
has
to
offer,
maybe
using
it
as
a
broader
acquisition
channel
for
users
or
really
verticalizing?
A
What
ipfs
can
bring
to
the
extension
space
by
doing
things
like,
maybe,
like
I
heart
wikipedia
extension,
where
it's
not
directed
towards
ipfs
users,
it's
directed
towards
wikipedia
lovers,
who
want
to
click
a
button
and
support
wikipedia
by
saving
and
serving
a
copy
through
the
ips
network,
so
really
rethinking
what
we
do
in.
In
the
extension
space,
so
what
comes
next
you're
going
to
hear
today
from
a
couple
of
different
speakers
looking
at
how
we
can
do
deeper
integration
building
alternate
browsers,
like
ones
that
are
not
household
names?
A
A
So
while
we
can
build
a
new
web,
how
do
we
ensure
the
safety
and
and
accessibility
of
all
of
the
bazillions
of
web
pages
that
have
existed
since
1994
5
6
onward,
as
the
usage
really
started
to
explode,
we're
doing
some
work
with
old
dominion
university
and
in
an
archive
that
measures
what
the
average
lifetime
of
a
web
page
is
going
back
to
the
beginning
of
the
web,
and
just
even
in
1996,
trying
to
find
a
million
web
pages
was
really
really
not
easy
and
so
we're
measuring
like
what
is
the
level
of
threat
of
the
web
today
of
the
http
web?
A
How
long
is
data
actually
available
when
you
publish
a
web
page?
Does
that
data
get
published
and
then
die?
Is
it
taken
down?
Does
it
move?
Does
it
shift?
How
can
we
have
a
record
of
the
human
experience
over
this
last
30
years
and
preserve
that
moving
forward,
so
we're
pretty
interested
in
connecting
these
worlds
in
interesting
ways
too,
and
we
might
hear
a
little
bit
about
that
from
the
web
recorder
project
and
then
you
know
what
you've
seen
really
this
weekend
earth
this
week
was
experimentation
with
new
ipvs
architecture,
so
really
re-envisioning.
A
What
ipfs
can
be
when
it's
not
just
a
monolithic,
daemon
running
on
a
fully
capable,
you
know
desktop
or
enterprise
class
server
system?
What
does
it
need
to
be
to
be
able
to
serve
some
of
these
environments?
You'll
see
people
asking
those
questions
and
also
some
of
the
ways
that
they've
developed.
So
that's
the
short
view
of
where
browsers
are
today
and
then
some
hints
of
where
things
are
going
to
be
over
the
next
six
to
twelve
months.
Thanks.