►
From YouTube: Web3 Browsers Are Ready for Decentralized Storage
Description
The Filecoin Ecosystem Team has been extending the protocol's relationships with Web3 browsers, including Brave, Opera and several others. Learn more about the work we're doing to make sure Web3 has native decentralized storage capabilities.
B
I
need
freak
first
of
all
thanks
a
lot
for
having
me
here.
This
is
actually
the
second
time
we
are
in
conversation
now.
The
previous
one
was
in
browser
3000,
something
like
that,
a
couple
of
months
back
by
ipfs
and
yeah.
So
I'm
really
excited
to
be
here,
so
you
introduce
myself.
My
name
is
annie,
I'm
a
quality
engineer
at
brave
where
I'm
working
on
a
crypto
wallet,
that's
natively,
part
of
the
brave
web
browser.
B
So
I
have
a
background
in
crypto
previous
to
that.
I
I
worked
at
ledger
on
financial
on
a
custody
software
for
financial
institutions,
so
we
had
clients
starting
from
exchanges
to
even
banks
or
family
offices,
so
that
was
a
fun
experience.
Now,
I'm
back
to
more
being
closer
to
the
community
and
building
stuff
for
end
users,
which
was
a
lot
different
from
what
I
used
to
do
before
that
yeah.
A
You
know
one
of
the
first
things
that
happened
this
year,
I
think,
was
late
january
brave,
launched
the
first
ipfs
native
node
functionality
inside
of
a
major
desktop
browser.
This
is
really
a
big
moment
for
the
availability
and
accessibility
of
ipfs
to
regular
web
users
in
a
truly
decentralized
way,
where
their
browser
actually
was
a
participating
node
in
the
in
the
ipvs
public
network.
A
We've
been
working
with
brave
ever
since,
on
smoothing
out
that
functionality
figuring
out
what
we
can
build
on
top
of
it
and
really
determining
what
is
the
end
user
experience
for
a
native
ipfs
web?
What
does
it
mean
when
your
web
browser
might
be
sharing
some
of
the
stuff
that
you
have
browsed
to?
What
does
it
mean
again
now
with
the
advent
of
nfts?
A
So
you
can
load
ipfsets
directly
from
from
dapps
using
that
address
format
and
it
forwards
the
request
out
to
a
ipfs
http
gateway,
so
it
actually
uses
the
d-web
gateway
there
to
proxy
those
requests.
So
that's
really
an
improvement
for
developers
and
especially
again,
as
you
know,
different
platforms
are
loading
ips
assets
off
iphones
natively
really
reduces
the
frictions
for
them.
A
A
It's
really
important
and
part
of
the
mission
of
protocol
labs
and
one
of
the
you
know
core
use
cases
of
ibps
protocol
is
about
taking
data
that
might
be
under
threat
of
not
being
available
at
some
point
and
making
sure
that
it's
available
for
as
long
as
people
need
it.
So
we're
working
with
folks,
like
rev
recorder
to
one
standardized
kind
of
like
the
format
and
stack
for
web
2
to
web
3
data
migration
inside
of
browsers,
but
also
outside
of
browsers
and
looking
at
large-scale
crawling
and
archival
use
cases.
A
We're
also
doing
some
research
on
that
and
too
with
internet
archive
and
ultimate
university
around
really
just
how
under
threat
is
the
web
today
and
and
web
2,
is
the
web
growing
or
shrinking
how
much
of
the
web
is
actually
moving
off
of
the
web
into
unarchivable
places
like
either
gate.
You
know
behind
a
login
gateway
like
instagram
or
facebook,
or
enter
into
native
apps,
so
doing
research
just
to
understand
still
just
how?
A
How
big
of
a
problem
is
this
the
availability
of
our
our
human
effluent
online
being
available
for
future
generations
or
even
our
immediate
uses?
When
you
know
things
like
politicians,
maybe
take
down
their
tweets
or
or
change
their
their?
You
know
the
message
on
their
website
to
obscure
what
things
they've
said
before.
So
a
lot
of
different
reasons
use
cases
why
this
web
2
to
wed
3,
stack
and
migration
path
for
archiving
and
making
sure
that
that
data
stays
secure.
It's
really
is
really
really
important.
A
A
A
Even
the
constraints
of
extractive
platforms,
like
android
and
ios,
with
experimentations
like
a
fork
of
ios
that
has
a
bundled
metamask
and
actually
supports
ipfs
protocol
natively,
so
you
could
actually
have
a
web3
device
that
is
running
an
operating
system.
That's
basically
the
web
platform
plus
web3
functionality.
So
we're
really
interested
in
understanding
what
opportunities
are
there
for
a
more
web
three
native
web
experience
moving
forward
and
we're
going
to
see
a
lot
more
of
that
stuff
in
2022.
A
So
you
know
we
can
push
hard
on
these
things
in
individual
products
like
like
brave
or
puma
or
opera,
but
without
a
level
of
interoperability
and
standardization,
the
barriers
for
developers
and
their
daily
pain
points
that
they
experience
is
still
really
really
high.
So
maybe
we'll
talk
about
that
if
we
have
time
before
this
half
hour
is
over,
what's
going
on
at
brave,
so.
B
One
of
the
things
that
people
are
like
a
lot
of
outsiders,
but
not
used
to
brave
as
the
company.
The
thing
is
that
it's
just
a
browser
company,
which
is
which
is
not
it's
more
like
an
internet
company,
so
browser
being
the
primary
first
product
that
we
ship,
the
other
ones
being
search.
We
have
our
own
search
engine.
We
have
a
brief
talk
for
video
conferencing
and
the
latest
addition
to
the
brave
suite
of
products
is.
B
B
I
know
that
my
dad
has
brave
install
on
his
phone
and
voila
he's
going
to
have
a
crypto
wallet
by
default
without
even
having
to
install
it,
and
that's
that's
really
the
kind
of
the
power
of
browsers
and
what
they
can
bring
to
this
ecosystem
and
just
to
speak
a
few
things
about
this
wallet.
So,
first
of
all,
it's
it's
not
a
browser
extension,
which
is
something
that
we
are
you
know
usually
using
for
accessing
dabs.
B
So
this
is
a
core
part
of
your
browser
and
implemented
in
c
clusters,
which
makes
it
more
secure.
So
it's
not
an
extension
and
it's
also
low
on
cpu
and
memory
because
it
doesn't
have
to
rely
on
an
additional
background
process.
That's
always
you
know
pulling
things
also
improves
the
user
experience
overall.
So,
overall,
I
think
it's
it's
it's
going
to
give
a
very
fast
user
experience,
something
that
people
are
you
used
to
people
are
familiar
with,
but
which
is
available
out
of
the
box
in
the
browser.
B
B
That
is
because
we
wouldn't
like
to
take
a
stance
on
what's
our
favorite
currency,
that
we
provide
as
a
you
know,
for
users
to
access
on
our
wallet,
it's
whatever
they
feel
like
using,
because
all
of
these
are
open
protocols
and
we
have
to
support
them
in
our
in
our
wallets
and
something
that
could
be
of
interest
to
the
file
coin.
Community
is
that
we
are
having.
B
B
So
that's
what
we
have
right
now
we
are
going
to
make
we're
going
to
have
a
lot
of
updates
in
and
around
wallet.
So
always
stay
tuned
feel
free
to
try
it
out
on
the
nightly
channel.
If
you
have
any
feedback,
you
can
always
reach
out
to
me
or
anyone
at
brave
really
on
twitter.
That's
the
best
place
to
send
your
feedback
to
us
and
I'm
really
looking
forward
to
it.
B
B
A
A
What
you
know
there's
a
couple
things
that
I
think
would
be
interesting
for
people
who
are
watching
to
to
learn
about.
I
think,
even
if
you're
a
web
developer
a
lot
of
times,
you
don't
spend
a
lot
of
time.
Thinking
about
why
a
you
know,
browser
is
popular.
It's
a
single
channel
too,
or
you
know
one
of
the
channels
that
you
have
to
your
users,
but
when
you're
making
a
browser,
you
have
a
different
set
of
responsibilities,
both
around
user
safety,
but
also
around
the
broader
ecosystem.
A
I
think
something
you
said
when
you're
talking
about
the
wallet
was
really
interesting,
which
is
when
developing
that
wallet.
You
don't
necessarily
want
to
pick
a
winner
of
any
of
these
cryptocurrencies.
The
idea
is
to
support
what
the
users
need
most.
This
is
one
of
the
challenges
that
we
have
in
ipfs
and
protocol
development.
A
I
think
between
the
work
that
we're
doing
in
web3
and
the
web
platform
today,
which
is,
maybe
you
know,
a
little
bit
narrower
view
on
one
single
type
of
common
denominator
for
for
brave,
as
you
said,
as
an
internet
company,
not
just
a
browser
company.
How
do
you
think
about
that
generally
you're
developing
a
wallet
you're,
developing
a
search
engine,
you're
supporting
different
chains
and
and
different
tokens?
How
important
it
is!
Is
that
for
you
and
how
much
does
that
come
into
your
thinking
right
when
you
think
about
interoperability
or
standardization.
B
B
You
can
think
of
privacy
as
kind
of
achieving
something
like
that
where
you
try
to
provide
the
user
with
a
safe
browsing
experience,
if
you
think
about
it
like
not
been
using
browser
since
a
very
long
time,
but
not
long
not
long
back
ago.
You
just
imagine
that
you
can
browse
the
internet
without
ads.
It
was
something
unimaginable,
at
least
for
me.
Okay,
I
didn't
know
about
efficient
ad
trackers
out
there.
B
B
If
you
don't
care
about
privacy,
whether
you
go
for
something
that's
like
chrome,
I
don't
know,
but
now
that's
that's
really
important,
because
we
have
reflected
the
same
thing
with
search
and
with
all
the
other
products
that
we
have
even
with
brave
talk.
It
is
into
an
encrypted
from
day
one
unlike
zoom,
which
was
not
for
a
long
time.
So
I
think
at
least
for
brave.
B
I
can
speak
for
brave
that,
whatever
we
do,
the
products
we
build,
they
have
to
send
a
coherent
message
to
the
user,
that
okay,
if
you
care
about
privacy,
if
you
care
about
open
access
to
protocols,
then
our
platf,
we
have
a
suite
of
products
that
can
allow
you
to
do
that.
Even
integration
with
things
like
ipfs,
it's
achieving
the
same
goal
to
a
large
extent.
A
Yeah,
I
think
I
for
you
know
for
for
me
a
lot
of
it
comes
down
to
choice
as
a
as
you
know.
If
I
put
my,
I
don't
make
web
technologies,
but
I'm
a
user
of
what
technologies
have
on.
I
want
to
be
able
to
have
a
choice,
and
it
and
and
they're
not
really
a
lot
of
products
that
give
me
that
ability
to
have
that
choice.
A
Even
I
tend
to
scratch
my
own
itch
a
lot
with
browser,
extensions
and
I've
done
a
lot
of
work
with
browser
extension
apis,
even
developing
some
of
the
some
of
the
apis
and
that
surface
area
of
what
I
can
do
as
a
developer
is
increasingly
constrained.
One
of
the
big
changes
that
we're
going
to
have
this
year,
that's
affecting
our
our
development
priorities,
is
the
advent
of
manifest
v3
in
the
browser,
extension
architecture
and
infrastructure.
A
There's
now
a
a
browser,
extensions
community
group
of
the
w3c,
which
is,
I
think,
a
really
good
move
in
terms
of
standardization
and
interoperability
and
community
direction
of
the
features
and
surface
area,
but
the
really
the
the
big
architectural
change.
That
kind
of
made
made
that
happen
was
manifest
383,
which
is
a
reduction
in
what
I
can
do
as
a
developer.
A
That
runs
the
ipfs
steven
itself
until,
of
course,
we
get
native
support
for
that
across
more
browsers,
and
I
think
this
is
this
is
one
of
the
challenges
that,
as
a
user,
I
have
less
choice
in
most
of
the
browsers
and
even
as
a
developer
kind
of
the
ability
that
I
have
to
be
able
to
change
what
a
browser
experience
can
be
to
give
more
capabilities
to
end
users
to
put
more
choice
in
their
hands.
Even
that
that
api,
you
know
and
feature
and
capability
surface
areas,
is
being
more
constrained
over
time.
A
So
it's
exciting
to
see
an
approach
that
does
have
you
know
you
know
that
that
choice
or
or
openness
at
the
very
least
at
the
basis
of
how
you're
thinking
about
feature
prioritization
and
standardization.
I
I
agree
too.
I
did
a
talk
well,
how
long
ago,
so
long
ago,
now
it
feels
like
at
a
deweb
camp
a
couple
of
years
ago,
you're
like
oh,
it
was
pretty
pre-covered.
It
was
a
different
time.
A
People
were
gathering
together
together
in
in
person,
and
I
didn't
talk
about
how
whether
the
the
one
the
one
size
fits
all
browser
era
is
at
an
end,
because
there
are
all
these
ambient
pressures
pushing
on
what
the
internet
users
needs
are
that
aren't
met
by
a
one-size-fits-all
security
modeling
one
five
size
fits
all
privacy
model.
You
know
we
can.
A
We
can
rhapsodize
about
the
web,
that
we
know
you
know
no,
no
today,
but
one
of
the
largest
problems
that
is
on
the
web
today,
that
even
companies
like
google
spend
really
a
large
amount
of
money
on
this
is
things
like
malware
and
safety
production.
You
know
the
dns
is
not
dna.
The
intersection
of
dns
and
ssl
is
not
a
panacea
for
for
safety
online,
and
that's
been
one
of
the
one
of
the
major
challenges
in
in
web
2..
A
What
do
you
think
is
one
of
the.
What
do
you
think
are
the
challenges
that
face
web
3
developers
today.
You
know
we're
seeing
an
explosion
and
adopt
development,
we're
seeing
an
explosion
and
nft
platforms,
nft
development.
What
what
do
you
think
the
major
pain
points
that
they
hit
are
in
browsers
from
what
you're
saying.
B
It's
a
great
question
because
so
first
of
all,
we
have
come
a
long
way.
If
you
see
the
first
browser
that
was
ever
built,
it
was
absurd.
It
was
by
the
way
you
can
still
try
it
out.
I
think
it's
archived
somewhere
in
cern's
website,
I
kind
of
I
I
gave
you
the
shot,
so
it
seems
like
it's
1000
years
old,
like
it
seems
to
be
an
error
that
I'm
just
not.
I
cannot
digest
that,
but
there
could
be
a
browser.
B
That's
like
that,
but
even
at
the
time
to
achieve
such
a
feat
was
really.
It
was
a
big
deal
and
so,
first
of
all,
we
have
to
acknowledge
that
we
have
come
a
long
way,
but
you
have
a
long
way
to
go
as
well.
So
I
would
like
to
categorize
these
challenges
into
several
buckets,
the
first
being
ux
challenges.
B
So
there
are
a
lot
of
quirks
with
browsers,
not
just
with
browsers,
but
with
these
new
age
protocols
that
we're
integrating
the
thing
is:
we've
been
lucky
so
far,
because
all
these
users,
we
have
had
so
far,
they
have
been
early
adopters
and
they
can
work
their
way
around.
These
quirks
they
can.
They
know
how
to
figure
things
out.
B
The
basic
user
experience
around
is
around
the
tcp,
so
you
can
visit
websites
and
everything.
Now
you
have
integration
with
ipfs.
Now
you
have
a
crypto
wallet.
All
these
are
like
you're
building
on
top
of
ethereum
protocol,
ipfs
tcp,
so
on.
So
we
have
to
figure
out
how
we
can
make
it
so
intuitive
that
the
user
wouldn't
know
if
they
are
visiting
a
ipfs
website,
which
is
already
pretty
much
the
case
that
you
can
use
these
various
gateways.
There
are
a
lot
of
things
happening
behind
the
scenes.
B
A
A
So
it's
a
but,
but
even
that
said,
there
are
really
huge
challenges
ahead
in
the
design
of
the
the
security
ui,
the
the
ux
of
privacy
and
security
models
that
are
new
and
different
than
what
we're
used
to
and
how
you
bring
these
types
of
technologies
to
people
in
a
way
where
they
understand
the
trade-offs
that
they're,
making
and
and
getting
some
superpowers
in
exchange
for
for
for
different
things
that
have
to
trade
away.
They
need
to
be
able
to
understand
what
that
means.