►
From YouTube: go-ipfs 0.6 and beyond... - Adin Schmahmann
Description
go-ipfs maintainer Adin Schmahmann talks about the progress made since the major 0.5 release this spring, as well as shares what’s in store for upcoming 0.6 and 0.7 releases.
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
Producting
connections,
ipfs
404
and
base
36,
so
I'll
sort
of
go
through
these
one
by
one
see
see
how
we're
done
so,
quick.
It's
now
enabled
by
default.
It's
it's
been
around
as
an
experimental
feature
for
a
while.
Now
we're
using
quick
draft
28
as
it's
going
to
be
sort
of
the
least
stable
one
within
ipfs.
A
For
those
of
you
who
are
unfamiliar
quick
is
a
udp-based
streaming
transport
that
is
sort
of
bundled
with
all
of
the
goodies
that
you
might
want
in
a
streaming
transport,
including
encryption
and
streaming
and
stream
multiplexing.
So
allowing
multiple
streams
of
data
over
a
single
connection
quick
will
allow
us
to
have
lower
connection
times
between
peers,
like
you
know,
much
lower
1/3
as
many
round
trips,
which
is
fantastic
for
things
like
DHT
queries
where
you're
gonna
be
querying
many
new
peers.
A
Additionally,
going
forward,
we
can
add
the
ability
for
sort
of
know
round
trips
required
resuming
of
connections
which
means
like
you
could
store
information.
What
peers
you'd
encountered
in
the
past
and
as
long
as
they're
still
at
the
same
IP
address,
so
you
can
still
find
them.
You
could
send
them
new
messages.
A
Next
up
is
noise.
We
have
experimental
support
for
the
noise
security
transport
noise
is
going
to
be
easier
for
most
likely
fest
implementations
to
work
with
than
TLS,
which
is
why
a
number
of
other
look
EDP
implementation,
other
than
gallupi
to
p,
have
been
brilliant
to
using
noise
as
their
secure
as
their
default
security.
Transport
noise
is
more
widely
used,
embedded
in
Sakaya,
which
is
the
kuraki
FS
default,
and
we're
in
the
future
planning
to
use
noise
to
replace
sec
is
the
defaults
cross
implementation
security
transports.
A
This
is
like
a
really
really
good
step
forward
on.
I
could
on
IG
festive
ecosystem
growth
and
and
security
staying
connected
I
professed
as
a
peer-to-peer
system
you
connect
appears
you
need
to
stay
connected
to
the
information
from
them
that
you
that
you
need
to
deal
with
the
fact
that
we
have
so
many
peers
that
we're
talking
that
we
might
talk
to
you
know
over
the
course
of
running
and
IPS
node.
A
We
have
to
decide
which
connections
are
the
most
valuable
and
keep
them
around
and
get
rid
of
the
connections
that
we
don't
need
right
now.
It
currently
works
by
basically
figuring
out
the
score
of
usefulness.
Of
each
peer
and
then
saying,
oh,
which
ones
aren't
useful
and
getting
rid
of
them,
but
there
are
some
peers
that
are
sort
of
extremely
important
to
stay
connected
to
whether
a
short-term
or
long-term,
and
so
we'd
like
to
be.
We
now
protect
those
connections
and
say
they're,
not
even
under
consideration
from
being
terminated.
A
A
In
addition,
we
now
have
a
caring
configuration
where,
if
there's
a
particular
node
that
you
want
to
stay
connected
to,
you
know,
you
run
a
bunch
of
infrastructure
nodes
and
you
want
to
make
sure
they're
all
well
connected
to
each
other.
Your
Gateway
is
connected
to
your
cluster
or
or
any
number
of
other
notes
that
you
want
to
be
insured
are
always
able
to
quickly
do
things
like
that
swap
with
each
other.
You
can
now
add
those
into
the
peering
configuration
and
it'll
get
taken
care
of
for
you,
so
I'd
be
best
404.
A
A
B
A
I
go
to
a
if
I
use,
you
know,
I
can
S
or
DNS
link
to
resolve
some
path.
You
know
could
have
been
here.
It
could
have
been
there
and
maybe
was
there
a
week
ago,
but
now
is
not
there,
because
the
data
underneath
it
has
changed
right.
This
is
the
the
nature
of
mutable
things.
Instead
of
immutable
things,
and
so
having
you
know,
a
more
convenient
error
message
or
nicer.
A
A
Elliptic
curve
keys
by
default
is,
is
great.
You
should
you
should
be
very
excited
about
lipstick
curve,
keys,
I,
know
I
am
because
their
small
size
lets
us
save
on
bandwidth
and
storage
and
memory,
but
and
also
allows
us
to
finally
have
signed
provider
records.
When
you
tell
people
about
content
right
now,
they're
served
on
in
an
ad
hoc
way
to
make
sure
that
you
know
you
are
the
peer
that
tells
people
you
have
data,
but
if
you
have
sign
provider
records,
then
all
of
a
sudden
you
can
ask
people
to
talk
to
the
DHD.
A
On
your
behalf
and
say:
oh
hey,
you
have
I
have
data.
Please
tell
the
DHD
that
I
have
data.
It
also
add
us
to
add
more
context
to
provider,
records
and
add
more
add,
more
field.
Saying
like
I,
have
not
just
this
this
C
ID,
but
the
entire
dag
underneath
the
CID
and
going
forward.
We
have
some
DHT
resilience
things
that
we'd
like
to
do,
in
particular
routing
tables
which
tell
you
which
peers
you
should
interact
with
and
help.
You
guide
your
way
as
you
crawl,
through
this
DHT
network,
to
find
information.
A
Currently,
we
just
look
for
peers
that
seem
useful
and
we
talk
to
them,
but
we
like
to
find
other
ways
to
keep
the
peers
that
we're
interested
in
talking
to
you
know,
have
a
better
set
of
those
tiers
have
ones
that
have
been
historically
useful,
have
ones
that
are
currently
online
and
have
been
stable.
For
you
know
the
last
a
couple
hours
and
have
diverse
characteristics
so
that
we
sort
of
are
not
affected
by
one
area
of
the
network.
Having
trouble.
B
Awesome
Thank
You
Dean.
We
do
have
a
couple
of
questions
very
excited
for
the
network.
Upgrading
that's
gonna,
be
huge
for
the
future
and
being
able
to
continue
to
roll
out
awesome
stuff.
So
take
your
first
one
from
Stefan.
What's
the
best
way
to
figure
out,
what's
going
on
in
my
node
like
trying
to
get
an
idea
why
I
cannot
route
to
another
node
that
serves
a
certain
content,
debug,
peers,
historically,
etc.
Visually
Prometheus,
kevanna,
best
practices,
yeah.
A
A
There
are
sort
of
events
that
you
can
print
out
and
sort
of
like
a
nice
JSON
format
to
get
to
you
know,
make
it
a
little
easier
to
parse
to
figure
out
what's
happening,
one
of
the
difficult
things
it's
sort
of
like
step,
one
to
check
as
always
are
these
peer
is
actually
diable
right
now,
like
that's
something
we
should
definitely
add
in
CYFS
is
the
way
to
tell
you
like
you
are
dot,
you
know,
hey,
you
are
diable
or
you're,
not
dial
of
all.
Did
you
think
you
were
supposed
to
be
so
that's.
A
A
Advantage
was
that
it
is,
it
can
be
represented
in
either
lowercase
or
uppercase
and,
in
particular
the
reason
for
using
base
36
is
to
get
the
key,
get
the
IP
and
s
keys
for
elliptic
curve
keys
to
fit
into
the
subdomain.
So,
like
you
know,
KABC
dot,
ip-ah
ip-ah
nice
thought
the
web
dot
link,
and
basically
it
won't
do
that
because
it
has
both
uppercase
and
lowercase
characters.
And
so
DNS
is
like
nope
bad
news.