►
From YouTube: IPFS in Web Browsers - July 2018
Description
Recorded during the Berlin Developers Meetings from July 9-13, 2018.
For up to date status visit https://github.com/ipfs/in-web-browsers
A
A
What
we
mean
by
that
is
to
make
sure
I
PFS
as
a
technology
as
a
set
of
libraries
and
solutions
tools,
are
a
part
of
the
web
stack
that
web
developers
can
use
to
make
it
at
one
of
default
choices
to
build
a
great
in
web
apps,
and
we
do
that
by
creating
custom
browser
integrations
such
as
browser
extensions.
We
work
with
browser
vendors
directly
to
integrate
ipfs
technologies
and
to
extend
existing
kpi's,
create
new
api,
solve
performance
issues,
and
generally
we
try
to
understand
the
existing
challenges
of
ipfs
in
web
browser
context.
A
A
Most
of
you
may
be
familiar:
if
not,
this
is
our
browser
extension
called
ipfs
companion.
It's
a
browser,
browser
companion,
extension
to
your
local
IP
FS
note,
if
you
do
not
have
it
go
to
Firefox,
Store
or
chrome,
store
and
install
it
from
a
real
Channel
there's
also
like
a
better
channel,
we
make
monthly,
stable
releases.
Weekly
Bettis
feel
free
to
try
it
there's
a
lot
of
GUI
that
exposed
internal
IP
FS
features,
but
that
will
be
in
the
next
talk
in
this
talk.
A
I
want
to
focus
on
things
that
developers
from
this
developer
meeting
may
appreciate
and
that's
like
something:
I
called
ipfs
path,
uplift,
which
is
a
fancy
way
to
say
redirect
just
start
using
content
addressing
today.
If
you
have
building
websites
make
sure
your
paths
are
valid,
ipfs
paths,
our
browser
extension
will
detect
that
validate
content
ID
and
make
use
of
local
IP
FS
note,
instead
of
sending
request
over
HTTP
transport
and
it's
how
we
do
it
now.
In
future,
there
will
be
other
solutions
to
uplift.
A
A
Most
of
api's
can
be
safely
scoped
per
application,
so
no
dialogue
is
displayed
to
user.
For
example,
multiple
file
system
is
scoped
per
application
in
a
fashion
similar
to
service
workers.
Generally,
it's
a
living
prototype
feedback
is
welcome,
go
to
ipfs
companions,
repository
there's
like
a
dog
subdirectory,
and
there
are
notes
on
this
new
interface.
Q&Amp;A
called
samples
and
stuff
like
that,
you
may
ask
is
browser
extension
all
ipfs
in
web
browsers
group
is
doing
now.
A
We
are
generally
tackling
a
lot
of
open
problems
that
J's
ipfs
and
generally
ipfs,
as
a
protocol
and
ecosystem
is
facing
in
the
web
browser
context.
Those
are
some
of
them
there's
more
one.
That
I,
want
to
extremely
highlight
today
is
to
move
to
the
base
virtual
CD
version
one
encoding,
and
we
need
that
if
we
want
to
be
to
have
a
presence
in
browsers,
we
need
to
have
a
proper
way
to
represent
the
authority
components
so
that
origin
based
security
parameter
is
respected
by
the
browser's
and
our
Content
ID
the
root
content
hash.
A
Will
the
authority
component
so
I
hope
we'll
move
this
forward.
This
week
we
plan
to
ship
new
web
UI
with
companion.
What's
web,
you
are
you
ask
you
will
know
about
that
after
next
lightning
talk,
there
are
multiple,
like
performance
issues,
strange
bugs
across
different
vendors
related
to
pushing
a
lot
of
data.
A
That's
what
I
give
us
is
doing,
so
we
are
tracking
those
down.
We
try
to
move
the
ceiling
on
the
file
size
limit
it
up
and
we
want
to
embed
jeaious
ipfs
with
the
browser
extension.
It's
actually
possible
right
now.
You
can
go
to
the
Preferences
and
switch
to
the
embedded
node,
but
it's
not
that
magical
experience
we
all
want-
and
hopefully,
like
David
mentioned
this
quarter,
we'll
try
to
address
that.
Why
I
mentioned
it
here
is
that
in
the
browser
extension
context,
we
can
add
additional.
We
can
additional
powers
to
the
JS
ipfs.
A
Those
might
be
new
api
is
like
dns
lookups
like
raw
socket.
Api
is
multicast
dns
native
protocol
handlers
and
so
on
and
so
forth,
and
we
hope
that
will
make
the
experience
of
having
one
node
that
is
exposed
to
all
pages
even
better,
and
if
you
are
interested
in
those
challenges
or
have
an
idea
or
your
own
challenges
in
the
browser
context.
Please
join
us
on
the
github
there's
a
metal
repository
for
like
high-level
planning
and
overview
and
there's
like
IRC
channel.
Also
we
are
part
of
ipfs
GUI
working
group.
B
On
the
soy
sobbing
issue,
as
far
as
the
privacy
concerns
in
correlation,
given
your
unique
window,
ID
or
generally
I'd,
give
us
note
and
so
I
think
yeah.
It
could
be
a
solution
for
using
and
using
an
accommodation
with
a
nonce
or
HD
wallet
we're
actually
you
have
a
derivative,
ID
and
so
I
think
so
every
time
you
have
a
new
session
for
a
website
or
you
have
a
pair
wise
association
for
each
ID
for
each
website.
You
go
to
like
where
one
domain
and
it's
I
think
interesting.
So.
A
Generally,
we
are
exposing
a
subset
of
like
ipfs
api's,
and
one
of
those
api's
is
like
the
ID,
so
you
actually
have
provide
a
unique
identifier
of
your
note.
We
may
provide
kind
of
sandboxing
solutions
that
you
mentioned
like
for
file
systems.
We
do
that
we
currently
for
more
sensitive
api's.
We
provide
a
dialogue
to
the
user.
That
user
needs
to
explicitly
approve
this
like
website
to
have
access
to
API
and
in
future
we
will
switch
like
move
to
the
direction
of
sandboxing,
instead
of
like
nagging
user,
with
additional
questions.
I
just.