►
Description
Kubo (go-ipfs) - presented by @adin at IPFS bing 2022 - IPFS Implementations - https://2022.ipfs-thing.io
A
All
right,
hey
everybody,
my
name
is
eden,
as
I
mentioned
before.
I
am
one
of
the
maintainers
of
kubo,
formerly
known
as
golipfs,
the
the
oldest
ipfs
implementation
and
one
you
are
probably
aware
of
so
one
of
the
prompts
was
like
what
is
this
and
who
is
it
for,
and
this
is
really
hard
because,
as
has
been
alluded
to
earlier,
it's
sort
of
been
like
everyone
wants
to
use
it
for
everything.
A
A
We
have
some
tools
which
you're
familiar
with,
like
http
gateway
apis
to
help
with
existing
with
compatibility
with
existing
systems,
and
we
have
some
cli
and
http
apis
to
help
people.
You
know
use
that
tooling
internally.
Kubo
has
this.
This
client
daemon
architecture
right,
there's
a
long
running
process,
and
then
you
issue
commands
that
are
effectively
http
commands
against
that
process.
To
do
your
work
has
trade-offs,
so
this
long-running
daemon
that
does
this
has
to
it
gets
to.
A
You
know,
cache
and
keep
all
of
your
your
network
connections,
your
database
connections
and
all
of
that
around
at
the
cost
of
you
got
to
keep
this
thing
running
and
then,
in
order
to
help
with
configurability
we
we
give
people
knobs
to
turn
in
a
config
file,
and
we
have
some
plug-in
things
that
people
can
use
to
modify,
go
ipfs
without
needing
to
or
kubo
I'm
sorry.
I
should
put
it
in
a
swear
jar
without
without
needing
to
worry
about
all
the
concerns
that
come
with
forking.
A
A
A
There's
this
ips
thing,
which
also
exists
that
deals
with
mutable
data
right
and
public
key
name
spaces
which
is
sort
of
very
obviously
glued
on
when
you
compare
it
to
the
immutable
space
right
sort
of
interesting,
it's
like
how
people,
whether
people
even
think,
is
ips
part
of
the
ipf
spec
or
the
fpps
concept,
or
is
it
something
that
lives
near?
It
is
a
friend.
A
Right
yeah:
where
are
we
in
a
lot
of
places
and
and
in
most
of
the
places
that
you
will
find
ipfs
things
there?
There
is
a
kubo
thing,
sort
of
nearby
http,
the
http
gateways
that
most
of
you
have
used
have
you
know,
are
backed
by
are
backed
by
kubo.
There
are
new
implementations
that
are
coming
that
have
or
exists
already
that
have
other
sorts
of
backing
nodes,
but
for
the
most
part
this
is
kubo.
A
There
are
others
that
embed
kubo
in
some
way
which
which
one
alluded
to
earlier
today,
including
you
know
brave,
ipvs,
cluster
desktop
and
companion.
There
are
some
like
common
infrastructure
nodes.
I
have
no
specific
reason
to
run
kubo
other
than
they
help.
They
help
us
stress
test
it
and
they
run
there
like
public
dht,
bootstrapper
nodes
and
preload
nodes
hard
to
find
stats
on
how
many
users
have
installed
kubo,
because
most
of
the
places
that
we
host
that
make
it
available,
we
don't
track
stats.
A
We
want
to
let
people
just
fetch
it.
You
can
fetch
it
over
ipfs
itself,
which
makes
which
makes
tracking
those
sorts
of
numbers
hard.
If
we
look
at
the
public
dht,
it's
almost
exclusively
the
server
side.
If
you
are
an
ipfs
node,
that
is
also
an
ipfs
public
dht
server
node
your
kubo
it'd
be
nice.
If
we
can
get
more
of
that,
there's
been
some
progress
in
both
rust
and
js
loop
p2p
to
make
that
possible
kubo's
been
around
for
a
long
time.
A
A
lot
of
people
have
contributed
to
the
project
found
over
300
or
some
looking
through
github
a
set
of
maintainers
who
are
responsible
for
helping
triage
all
the
commits
that
come
in
and
prs
for
many
people
and
moving
some
of
the
stuff
along
are
up
there.
There's
me
lytle
gus,
antonio
and
hugo,
who
you
will
you'll
see
around
we're
here.
Come
chat
with
us,
we're
pretty
friendly
yeah.
So
you
know
if
you,
if
you
want
to
contribute,
contribute
to
kubo
or
if
you
want
to
be
a
maintainer,
please
there's
there.
A
A
A
Interesting
things,
so
a
lot
of
the
maintainers
of
the
kubo
project
are,
for
some
historical
reasons.
Also
just
we
do
a
lot
of
things,
the
ipfs
community
in
general-
and
we
are
also
maintainers
for
some
of
the
the
many
ipfs
libraries
written
in,
go
that
kubo
and
other
projects
rely
on,
and
so
we
sort
of
try
and
balance
balance
our
work
there
between
making
kubo
better
and
also
making
the
tooling
better
for
the
rest
of
the
community
and
the
rest
of
the
implementations.
A
We
are
fairly
confident
that
kubo
is
not
for
everyone,
but
we
hope
ivfs
can
be.
We
got
a
bunch
of
things
coming
up
for
our
roadmap.
Most
important
things
to
consider
here
are
that
we
are
going
to
have
an
unconf
session
this
week,
where
we
can
talk
about
more
of
these.
Some
of
these
are
maybe
things
we
want
to
do.
Maybe
there's
things
here
that
we
missed.
We
have
a
huge
laundry
list
of
things
with
that.
You
know
many
many
issues
but
yeah
if
you're
interested
come,
join
us.
A
A
All
right,
so,
where
are
we
at
the
oldest
iphone
implementation?
It's
written
in
go
supported
in
some
common
operating
systems
has
a
lot
of
traction
in
wide
use
cases
not
not
for
everywhere,
though,
and
there
are
a
lot
of
community
members
in
the
public
idfs
channels
who
contribute
to
kubo
so
come,
say,
hi
and
hang
out
with
us.