►
From YouTube: Intro, Welcome, Overview - Dietrich Ayala
Description
This talk was given at IPFS Camp 2022 in Lisbon, Portugal.
A
Thank
you
so
much
for
joining
the
browsers
and
platforms
track.
If
you
were
here
yesterday
or
even
on
Monday,
you
may
have
heard
us
talking
about
the
challenges
of
getting
ipfs
and
even
protocols
or
features
like
it
into
places
like
browsers
into
places
like
open
source
command
line
tooling,
having
it
working
on
mobile.
The
initial
architectures
of
ipfs
are
really
designed
around
this
monolithic
service
that
runs
on
a
desktop
computer
or
in
a
server
when
most
of
the
billions
of
people
using
the
internet,
use
it
in
very
different
ways
every
single
day.
A
So
we
need
to
be
able
to
have
this
protocol
be
in
those
places
and
operate
in
a
way
that
users
can
expect
that
developers
can
actually
work
with,
and
hopefully
that
actually
brings
you
some
of
the
characteristics
of
the
protocol.
Things
like
content,
addressing
transport,
agnostic,
networking
and
the
ability
for
people
to
interact
directly
with
each
other.
So
I'm
going
to
kick
it
off
with
a
little
bit
of
examples
of
the
type
of
work
that
we've
done.
Some
of
the
things
that
the
people
we
work
with.
A
We
work
with
a
bunch
of
different
browsers
users
on
the
team
that
I
that
I
have
browsers
and
platforms
team
at
vertical
Labs.
We
also
work
with
open
source
libraries
we
integrate
into
open
source
communities
and
we
bring
things
like
ipfs
or
parts
of
that
stack
out
into
places
like
the
space
industry.
We
work
with
metaverse
projects,
basically
anywhere
that
HTTP
is
today
and
can
be.
We
have
as
a
Target
where
we
think
that
things
like
ipfs
should
be
able
to
run
oftentimes.
A
A
couple
of
interesting
things
happened:
we
had
to
rewrite
the
ipfs
companion
extension,
so
running
ipfs
inside
browsers,
not
even
as
a
native
protocol,
but
even
inside
of
browser
extension
is
pretty
challenging
and
Google
has
a
new
format
for
extensions
called
manifest
V3,
which
obliterates
all
of
the
API
set
and
models
that
you
had
before
extensions
before
and
most
extension
developers
are
having
to
rewrite
their
extensions
from
scratch.
David
on
our
team
did
that
this
year,
only
because
Google
really
pushed
their
deadline
on
that
they're
like
you're
gonna,
have
to
do
this.
A
We
also
shipped
along
with
metamask
they
ship,
the
new
architecture
for
metamask
called
flask,
which
is
the
idea
of
extensibility
inside
metabask
itself,
and
so
we
work
with
them
to
ship
an
extension
or
they
call
it
a
snap
inside
metamask
that
adds
filecoin
support
to
it.
This
is
another
Inception
kind
of
thing
where
you
have
an
extension
inside
an
extension
inside
a
browser,
and
it's
going
to
be
interesting
to
see
when
flask
actually
goes
to
production,
how
this
model
plays
out
and
they're.
A
A
A
There
is
really
really
high
leverage
for
the
protocol
itself
and
makes
it
available
for
products
like
browsers
to
be
able
to
choose
Brave
you'll
hear
from
only
today
about
a
bunch
of
the
features
that
they've
shipped
he's
going
to
give
a
wide
overview
of
everything
from
how
we
added
schemes
in
there
IPS
local
news
support
and
the
filecoin
support.
Some
of
the
things
upcoming
are
things
like
automatic
pinning
of
nfts
when
you
have
them
in
your
wallet
inside
Brave.
A
So
more
and
more
features
of
people's
experience
online
being
integrated
into
the
browser
experience
in
different
ways.
We
also
work
a
lot
on
trying
to
figure
out
what
the
right
pattern
is
on
mobile
people
to
get
some
of
the
characteristics
of
ipfs
in
people's
hands.
You
can't
really
realistically
run
an
ipfs
node
on
a
mobile
device
because
it
opens
up
hundreds
of
sockets,
which
is
not
really
possible.
A
Over
something,
like
a
you
know,
SIM
card
connection,
an
actual
mobile
connection
and
a
lot
of
the
use
cases
too,
like
is
going
to
bring
your
battery
down
anyways,
which
is
which
is
a
real
challenge.
So
there's
a
number
of
challenges
around
getting
it
to
actually
bring.
You
know
getting
it
working
mobile
to
in
a
way
that
actually
brings
some
of
these
features
and
we're
experimenting
in
ways
like.
Maybe
we
talk
to
a
bunch
of
different
gateways
to
be
able
to
get
a
bunch
of
blocks
as
opposed
to
just
one
Gateway.
A
So,
even
though
you're
not
running
lib
P2P,
you
are
actually
decentralizing
how
you're,
using
the
HTTP,
ipfs
Network
so
having
to
get
creative
on
mobile
you'll,
hear
probably
three
or
four
different
approaches
of
getting
creative
on
mobile
from
projects
that
are
going
to
be
speaking
today.
We
also
work
with
open
source
libraries,
so
things
like
curl.
What
would
ipfs
support
inside
curl
actually
look
like?
Well,
if
you
have
a
local
ipfs
node,
then
it
might
be
kind
of
straightforward
if
Coral
knew
about
it
and
knew
where
to
look.
A
But
if
you
don't
have
a
local
ipfs
node,
can
you
still
pull
from
a
Gateway
or
from
multiple
gateways?
These
are
some
of
the
experiments
that
we're
doing
with
open
source
projects
like
curl
and
ffmpeg
to
be
able
to
have
those
tools,
pull
video
audio
Network
assets
in
the
way
that
developers
do
today,
but
maybe
with
some
like
environment
variables
and
configuration,
maybe
a
little
bit
of
glue
in
there
to
talk
to
local
nodes,
taking
a
bunch
of
different
routes
to
try
to
figure
out
how
that
might
actually
work.
A
We
we
need
this
to
work
in
a
different
way.
We
need
it
to
work
where
developers
are
where
end
users
are
holding
devices
in
their
hands
or
sometimes
in
a
satellite
roving
around
the
planet.
Ipfs
needs
to
function
differently
and
it
needs
to
be
more
available
and
accessible,
and
so
this
was
a
really
big
turning
point
in
how
we
thought
about
what
ipfest
is
and
how
it
works,
and
so
you're
going
to
hear
today
a
bunch
of
stories
of
different
people
doing
this
type
of
work.
A
One
of
the
one
of
the
big
accomplishments
that
we
had
this
year
was
the
fact
that
this
is
now
getting
close
to
50
50
green
versus
red.
It's
really
really
long
painstaking
work
to
be
able
to
do
things
like
add
a
paradigmatically
different
protocol
with
different
security
model,
different
privacy
model,
different
capabilities
to
something
like
the
web
platform.
This
is
probably
a
10-year
path
to
get
this
green,
if
not
more
and
we're
bringing
in
some
of
these
timelines
right
pretty
rapidly
like
just
between
the
difference
between
March
and
October.
A
That
I
animated
here
in
GIF
fashion,
is
kind
of
amazing
and
and
I
think
as
ibfs
gets
more
well
known
and
we
hammer
out
some
of
these
new
patterns
and
Pathways.
Maybe
we
can
make
it
less
than
10
years
five
years,
we'll
see.
Who
knows
what
happens
but
you'll
hear
about
some
of
the
little
spikes
in
the
activity
and
some
of
the
accomplishments
that
we
made
in
2023.
A
So
things
like
this
ipfs
and
content,
addressing
where
you
don't
have
to
worry
about
where
the
data
is
or
who
has
it,
and
you
can
ask
the
network
generally:
hey
I
got
the
CID
based
on
this
ipns
key
anybody.
Have
this
block
inside
this
larger
graph.
Ipvs
aligns
really
well
to
these
semi-offline,
often
disconnected
or
disjoint.
Data
sets
scenarios
so
there's
a
lot
of
interest
in
the
space
industry
around
using
ipfs
for
more
easily
available
and
less
complex
application.
Architectures.
So
you'll
hear
some
more
about
that
over
probably
the
next
couple
of
years.
A
The
team
that
I
work
on
right
now
is
a
very
small
group
of
people,
but,
as
you
can
see,
a
very
expensive
focus
and
we
work
a
lot
across
a
lot
of
different
areas
and
we
work
a
lot
of
organizations
and
projects
and
people
outside
our
core
team.
As
you
saw
in
the
beginning,
there
are
kind
of
you'll
recognize
a
few
of
these
people.
They
will
be
speaking
here
today.
If
you
see
any
of
them
walking
around
reach
out
and
say
hi
introduce
yourself
we're
also
hiring
for
a
bunch
of
different
roles.
A
If
you're
interested
come
and
talk
to
me
about
some
of
these
ones
at
the
bottom,
there
and
our
strategy
really
enlarge
as
a
team
is
to
make
it
so
that
ipfs
is
available
in
places
so
that
developers
and
users
can
choose
it.
The
developer
adoption
oftentimes
is
around
hey
I'm,
going
to
build
a
thing
and
the
people
will
be
just
so
awesome.
People
will
come
to
me
and
they
will
want
it,
but
the
way
we
want
to
address
Target
markets
like
iot
or
video
as
a
category
or
games.
A
You
have
to
be
in
the
places
where
those
people
are
doing
their
work,
and
that
is
the
strategy
that
we
have
as
a
team
is
to
make
ipfs
something
that
in
these
environments,
it
is
available
for
them
to
choose
and
that's
a
real
different
way
of
operating.
It
means
you
need
to
engage
those
communities.
You
need
to
work
with
those
projects.
You
need
to
understand
their
everything
from
their
like
Community
process,
to
their
coding
styles,
to
like
the
ebb
and
flow
of
decision
making
and
open
source
communities
or
even
inside
private
companies.
A
So
it's
it's
interesting
and
challenging
and
fun.
One
of
the
challenges
that
we
have
is
that
when
you
have
a
world
where,
like
everybody,
has
HTTP
blinders
on
and
that's
the
only
lens
to
which
they've
evaluated,
what
the
risks
trade-offs,
privacy,
security
or
capabilities
of
a
protocol
are
PFS
seems
kind
of
crazy.
A
So
we
spend
a
bunch
of
time
working
with
folks
who
are
interested
in
ipfs
and
then
the
more
they
learn
about
it
at
first,
like
that,
they
crazier
it
seems,
and
after
a
while,
once
they
kind
of
rock
the
value
of
content
addressing
and
transport
agnostic
application.
Architectures
they're,
like
I,
get
where
that
value
is
and
I
understand.
Why.
The
trade-offs
that
you're
making
are
different
compared
to
what
you
would
do
with
HTTP
the
trade-offs
you
would
have
to
make
the
relative
risks
and
capabilities
that
you
get
and
return
for
those
thanks.
A
Everybody
who
showed
up
to
well
one
to
this
event
and
also
to
the
ipfs
Iceland
Summit,
PDP
Paris,
and
a
bunch
of
the
other
different
events
that
we
had
this
year.
Where
people
came
together
to
really
explore
what
would
what
it
would
look
like
for
ipfs
to
be
in
places
where
it
isn't?
Today,
some
of
those
folks
are
still
in
line
so
I'm
going
to
change
up
the
speaker
order
a
little
bit
and
we're
going
to
start
with
Lytle.
Who
will
tell
you
about
the
state
of
ipfs
gateways.