►
Description
IPFS Companion, IPFS Desktop, and Brave - presented by @lidel at IPFS þing 2022 - IPFS Implementations - https://2022.ipfs-thing.io
A
How
does
the
ipfs
implementation
targeted
to
and
your
end
users
look
like?
Suddenly,
you
don't
need
to
worry
about
a
lot
of
technical
things,
so
this
talk
will
be
kind
of
like
an
evolution.
It's
I
I'm
omitting
a
lot
of
historical
context,
but
just
giving
you
a
taste
of
the
arc
we
are
on
and
maybe
some
things
that
we
could
discuss
this
week,
some
food
for
thoughts
around
user
interfaces.
A
So
a
firefox
extension
happened
on
march
2015.
I
know
because
I
looked
at
the
first
comment
and
it
was
only
firefox
extension
and
over
time
it
added
support
for
chrome
and
chromium-based
browsers,
and
it
got
renamed
to
ipvs
companion
and
now
it's
a
browser
extension
which
has
over
60
000
users
in
chrome,
web
store
alone.
A
It
does
not
have
to
be
brave
specifically
if
it's
not
brave,
you
want
companion
and
it
gives
you
this
icon
in
the
address
bar
with
additional
interface
related
to
ipfs.
So
what
companion
does
it
automatically
detects
ipfs
resources
and
by
ipfs
resources?
I
mean
anything,
that's
content
address
on
the
web.
It
could
be
url,
it
could
be
the
nes
link
website,
which
has
the
valid
txt
records
and
by
default,
if
you
have
locally
running
http
gateway
or
if
you
set
up
some
remote
gateway,
it
will.
A
A
It
provides
user
interface
for
frequently
used
ipfs
actions.
You
can
copy
shareable
link
to
something
that's
already
on
ipfs
or
you
could
mirror
assets
from
websites
import
them
to
your
own.
Node
node
will
start
providing
that
to
the
network.
You
could
copy
c
ids
or
you
could
even
import
a
file
from
a
local
file
system.
A
A
You
install
it
and
you
are
presented
with
a
user
interface
with
the
state
of
your
node.
If
you
are
connected
to
the
network,
how
many
peers
are
you
connected
to?
It
gives
you
a
user
interface
which
replaces
the
command
line,
and
that
brings
makes
ipfs
more
approachable
to
people
the
application
itself.
A
Aside
from
providing
the
user
interface,
it
orchestrates
kubo
daemon.
So
if
you,
when
you
install
ipfs
desktop
it
automatically,
will
install
the
daemon
and
it
will
orchestrate
it
for
you.
It
will
auto
update
when
the
simulation.
It
will
start
stop
when
you
start
or
exit
the
desktop
application
and
you
are
able
to
go
to
the
user
interface
directly
from
your
menu
bar
or
tray,
and
the
interface
itself
is
our
exploration
of
converting
low-level
concepts
like
mfs
or
maybe
local
or
remote,
pinning.
A
A
You
are
able
to
context
click
on
an
item
and
explore
a
specific
dag.
If
it's
a
big
file,
you
are
able
to
explore
all
the
blocks
inside
of
it.
You
can
see
what
peers
you
are
connected
to
what
are
prevalent
connections
when
we
introduce
quick.
It
was
really
fun
to
see
like
months
months
later,
seeing
more
and
more
appears
supporting
quick.
A
A
A
What
we
mean
by
that
is
that
when
you
use
ipfs
resource
for
a
first
time,
brave
will
prompt
you
and
ask
you
hey:
do
you
want
to
enable
local
ipfs
daemon
should
brave,
take
care
of
it
and
run
it
for
you?
And
if
you
enable
it
you,
you
essentially
are
done,
because
you
are
able
to
paste
the
address
and
it
magically
resolves
to
the
gateway
provided
by
kubo,
because
brave
internally,
at
least
right
now,
because
there's
nothing
better
wink
wink,
it
runs
kobo
gateway.
A
It
will
automatically
update
it
for
you,
just
like
ipfs
desktop
does,
but
it's
just
a
component
there's
for
sure
a
better
implementation
with
lower
performance
impact
or
lower
cpu
usage
and
so
on.
But
the
coolest
thing
in
brave
is
that
the
protocol
stays
in
the
address
bar
and
if
the
protocol
stays
in
the
address
bar,
that's
the
clear
indicator
that
you're
like
using
ipfs
natively
you
you
are
able
to
delegate
resolution
to
a
public
gateway,
but
you
don't
you?
A
Don't
need
to
you
can
run
your
own
node,
and
this
is
like
a
very
powerful
story
because
now,
instead
of
asking
people,
hey,
install
ipvs
companion
on
this
browser
extension-
and
you
start
this
desktop
application,
you
need
to
run
like
both.
You
just
say:
hey,
install
brave
open
this
ipn
ips
address
or
ipfs
cid
address,
and
that's
it
you,
the
user
onboarding,
suddenly
got
collapsed
into
two
lines
and
it's
it
may
not
sound
like
much,
but
it
is
really
really
a
lot
because
brave
is
more
than
doubling
their
you.
A
They
monthly
you
active
user
base
year
to
year
2021
it
was
over
50
million.
We
are
in
the
middle
of
2022
just
saying,
and
that
means
our
the
content
address
data.
The
addresses
that
don't
have
location
can
now
resolve
out
of
the
box
for
more
than
50
million
of
users,
so
it
I
I'd
argue:
that's
like
pretty
popular
ipfs
implementation
in
running
in
the
production,
so
browser
extension
desktop
application
brave.
A
What's
next
in
this
space,
I'm
not
sure
if
I'm
over
time
so
I'll,
just
briefly
signal.
What's
on
our
short,
mid
and
short
roadmap,
and
what
I'm
happy
to
discuss
and
workshop
this
week,
brave
mobile,
like
no,
the
mobile
browsers,
have
challenges,
and
now
that
we
have
trustless
gateways
and
trustless
gateway,
retrieval
is
possible.
The
mobile
web
browsers
are
able
to
support
content
as
well
as
data
natively.
A
Without
running
for
peer-to-peer
stack.
They
could
still
use
it
as
a
fallback
mechanism,
but
the
default
which
does
not
drain
battery
could
be
now
gateways
or
a
pool
of
gateways.
Ipvs
companion
rewrite.
We
have
to
rewrite
it
because
of
reasons,
but
it's
a
good
opportunity,
because
now,
oh
maybe
if
we
have
the
service
worker,
which
is
a
part
of
manifest
v3,
maybe
we
could
also
leverage
this
trustless
retrieval
inside
of
companion,
and
that
means
that,
even
if
you
don't
have
desktop
you
don't
have
brave,
you
prefer
a
different
browser.
A
Maybe
you
still
can
have
trustless
retrieval
in
just
extension,
writable
protocol
handlers
based
on
the
writable
gateways.
It's
a
discussion
we're
having
later
this
week.
I
mentioned
that
before
agrigore
is
taking
the
path
for
that,
hopefully
we'll
establish
something
that
other
browsers
like
brave,
can
implement
and
then
like
mounting
immutable
assets,
mutable
local
file
systems
in
a
way
that's
native
to
the
system.
A
A
Similarly,
if
you
we
are
able
to
like
expose
ipf
content
address
resources
using
the
abstractions
right
there
in
operating
systems
in
like
a
windows
explorer
or
mac
os
finder,
without
any
special
interface
like
web
ui.
That
would
be
great
and
having
multiple
ipfs
node
on
your
machine
may
become
the
problem
so
figuring
a
way
for
good
applications
to
like
share
or
delegate
routing
networking.