►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2020-03-30
Description
Learn more about the work of the IPFS Docs & Developer UX Working Group and how to join our weekly syncs: https://github.com/ipfs/docs
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
A
A
A
B
A
Mentioned
this
a
couple
weeks
ago,
so
this
release
is
coming
out,
there's
a
load
of
new
features
and
fixes
they're
going
into
it's
really
exciting.
It's
like
they're
one
of
the
biggest
go
releases
that
we've
done
since
the
last
release
the
combined
May
last
year
ago.
So
there's
just
some
changes.
The
documentation
was
going
into
that
there's
an
issue
with
users
behind
an
nad.
That's
an
existing
issue
that
goes
out
through
all
ipfs
nodes.
A
If
you're
sat
behind
an
nad,
so
a
network
address
translator,
your
your
IPS
node
will
often
not
be
able
to
communicate
with
the
rest
of
the
network.
So
there's
essentially
a
lot
of
work
going
into
making
guides
and
telling
people
how
to
get
around
that
thing
without
taking
down
the
NA
T,
because
the
na
T
is
like
a
a
big
super,
useful
thing
and
taking
it
down
as
a
huge
issue.
A
So
that's
getting
that's
getting
finalized
this
week,
updating
the
branch
ready
for
release
and
merge
into
masters,
so
the
rest
of
the
documentation
for
guaca
past
no
point.
Five
is
pretty
much
done,
it's
just
being
sort
of
tweaked
now
so
that
when
the
time
does
come
for
the
release
to
go
live,
you
can
just
mirja
straight
into
master
without
any
any
faffing
around
or
anything
like
that.
I
just
got
an
email
this
morning
saying
that
the
release
has
been
pushed
back
further
into
April,
but
that
really
shouldn't
have
found
this
group.
A
Since
most
the
documentation
is
already
done
unless
there
are
major
changes
that
come
out
as
a
result
of
testing
the
release
candidate,
which
is
my
next
point
on
the
list
we
need
to
test,
or
at
least
Canada
know,
that's
been
finalized
to
actually
make
sure
that
all
the
stuff
I've
written
is
correct.
So
the.
A
Right,
TBD,
yeah
and
removing
stuff
isn't
I,
don't
mind.
Removing
stuff
is
easier
than
throwing
and
stuff
earlier
date,
which
Jessica's
laughing
so
I
feel
like
she's
had
to
do
that
before
so
yeah.
So
that's
been
I
spent
a
lot
of
the
focus
of
my
time
for
the
last
couple
of
weeks,
just
sort
of
rushing
around
dealing
with
various
developers,
making
sure
that
why
I'm
writing
is
in
fact
the
truth
and
I'm
not
making
setup
so
yeah
any
questions
about
that
specific
point.
There.
B
A
A
B
A
A
B
A
From
what
are
you
doing
that
I'll
just
jump
over
the
issues
that
we
decided
on
so
deprecated
that
legacy
so,
as
you
just
saw
that
this
would
be
super
exciting?
A
lot
of
the
feedback
we've
had
the
vast
majority
feedback
we've
had
over
the
the
new
Darkseid
has
been
positive.
Everyone
prefers
and
way
prefers
over
the
current
exists.
Things
like
you
go
based
so
view.
Press
is
just
generally
by
it's
easy.
It's
a
work
where
it's
easier
for
us
to
write
with,
and
it
looked
prettier.
A
So
that's
great
so
we'll
get
that
done,
probably
within
April.
At
some
point,
that's
like
a
big
p0
I
want
to
get
sorted
the
next
one,
so
a
web
developers
introduction.
So
this
has
been
bribed
quite
a
lot
recently
within
the
community
and
also
internally
within
PL,
that
we
don't
have
a
series,
writers
and
like
web,
develops
to
kind
of
hit
the
ground
running.
We've
got
loads
of
stuff,
that's
very
conceptual,
so
people
can
kind
of
come
along
and
be
like.
Okay,
cool!
That's
what
that's!
What
this
offers?
Okay,
cool!
A
That's
how
you
know
this
loop,
each
piece
that
works,
but
there's
nothing.
There's!
No
real
meat
that
people
can
get
their
hands
on.
Thank
you
for
that
type
of
there,
Jessica
so
yeah.
So
creating
this
series
would
be
just
incredible
sort
of
boost
to
drive,
really
sort
of
helping
developers
actually
get
get
building
something.
So
the
initial
tutorial
of
this
is
Oh
doing
written.
So
the
basic
this
for
us
that's
exciting.
Are
you
posting
stuff,
like
that?
A
First
side
of
things
so
be
interesting
to
get
his
his
point
of
view
on
sort
of
single
source
of
my
firms
are
gonna
second
source
documentation
on
static
site
generators
and
things
like
that
on
how
they
can
be
implemented
in
our
next
one
single
source,
documentation.
This
is
this
is
likely
going
to
be
an
ongoing
thing
throughout
the
year
and
it's
probably
just
gonna,
be
an
ongoing
thing,
as
repos
develop
their
own
documentation.
But
the
main
point
of
this
is
that
we've
got
ipfs
documentation
all
over
the
place.
A
So
it's
in
loads
of
different
repos
and
haxor
has
been
doing
an
incredible
job
recently
of
finding
these
mysterious
repos
and
then
kind
of
closing
them
or
archiving
them,
while
bringing
them
around
and
then
marking
issues
in
the
docs
repo
to
say,
hey,
we
probably
need
this
documentation
for
living
dogs,
so
the
idea
of
single
source
documentation
is
to
bring
every
all
of
that
documentation
into
one
place,
so
it
lives
in
one
place
locally.
This
is
going
to
involve
a
lot
of
managing
and
dealing
with
the
owners
of
those
repos
to
be
like.
A
A
The
best
solution
is
probably
just
going
to
depend
on
the
particular
repo
owners.
I'm
gonna
have
to
be
we're.
Gonna
have
to
be
pretty
flexible
when
it
comes
to
this,
we
can't
we're
not
gonna,
be
able
to
say
you
have
to
write
in
our
repo
just
because
I
love
a
lot
of
the
tools
and
workflows
the
repo
owners
use
are
probably
going
to
be
very
sort
of
unique
and
tied
to
that
particular
repo.
So
we're
gonna
have
to
be
flexible
in
terms
of
how
to
get
the
documentation
out
so.
B
Just
just
for
a
context
in
the
past,
the
reason
why
we
have
just
Docs
scattered
all
over
Rico's
has
just
been
because
this
thing
that's
like
evolved
organically.
It
hasn't
too
much
didn't
because,
like
people
are
super
attached
to
the
idea
of
having
like
their
stuff
in
their
repo
and
I,
think
right
before
right
before
you
joined
on
Johnny
I,
think
I
was
having
I
was
having
sort
of
like
big
conversations
with
everybody
about
like
hey
it's
there.
Any
reason
why,
particularly
for
guess,
go
those
materials?
B
Is
there
any
reason
that
you
don't
that
you
wouldn't
want
us
to
pull
those
out
of
your
rebound
and
put
that
in
mid
Docs?
And
the
answer
was
inevitably
no,
with
the
possible
exception
of
API
and
say
line
documentation,
which
is
its
own
kettle
of
fish,
which
we
can
kind
of
ignore
for
the
purposes
of
this
discussion,
so
I'm,
not
I,
don't
think
you're
gonna
be
running
into
a
whole
lot
of
like
like
objection
to
this
is
a
practice.
I
think.
A
C
A
B
We
can
take
offline
the
next
time
you
and
I
just
some
sort
of
strategic
things
that
I
floated
in
the
past,
but
I
think
I.
Think
it's
just
like
I
I,
don't
know,
I,
don't
know
about
the
both
of
you,
but
I
would
be
I'm,
leaning
a
lot
more
towards
doing
this
slowly
and
intentionally
in
the
case
of
API
in
CLI
Docs,
then
building
something
quickly,
that's
only
moderately
less
awful.
We.
A
B
B
That's
in
the
IBM
s,
/
IPs
repo
into
more
frequently
edited
location,
so
ipfs
ipfs
was
basically
just
there
to
point
us
to
other
locations
which
I
think
was
a
sort
of
been
the
intention
for
that
repo
for
a
while
and
we're
closed,
and
hopefully
that
should
be
done
by
the
end
of
this
week.
So,
thanks
for
looking
over
that
kind
of
it
cool.
A
B
And
fortunately,
as
a
result
of
a
lot
of
things,
hopefully
the
ecosystem
out
of
being
among
them
Hector's
like
the
repo
vendor
right
now,
and
it
just
hasn't,
been
as
long
about
tidying
things
up
and
and
I'm
excited
to
make
them
for
as
long
as
yeah.
A
Tony
he's
got
the
unique
about
the
skills
of
you
know,
he's
passionate
about
it,
and
he
also
has
the
rights
access
to
be
able
to
change
these
kind
of
things,
which
is
always
handy.
Ok,
cool
Donna,
quickly,
jump
onto
the
last
one.
This
is
a
p2
I,
think
I
said
it
us,
so
it's
not
as
important
as
the
other
three
but
I'd
like
to
get
it
done.
So
it's
automated
docks.
A
This
is
an
automation
in
terms
of
a
permutation
automation,
automation,
automation
or
things
like
automatic
grammar
testing
automatic
spell
checking
automatic,
broken
links,
checking
checking
the
images
on
broken
things
like
that.
Three
of
these
things
are
fairly
easy
to
do
so
spell
testing,
broken
links
and
broken
image.
A
B
There
are
probably
some
very,
very
common
first
for
grammar
things
that
we
can
automate
without
having
to
write
in
giant
grammar
checker
things
that
are
just
sort
of
idiosyncratically
common
to
us,
like
we
have
a
bunch
of
writers
who,
whose
native
language
is
a
language
that
doesn't
use
like
definite
articles,
can
be
super
easily
checked
for
just
stuff,
like
that.
I
think
that
there's
probably
a
small
handful
of
stuff
that
could
be
fairly
simply
hand
coded
and
get
us
a
long
way.
B
A
B
A
Not
no
I
just
remembered
that
this
morning,
so
just
well,
my
coffee
was
brewing.
I
threw
that
in
there,
but
so
on
to
Darwin
yeah,
so
there's
a
new
meantime
sauce
in
the
last
Monday
of
every
month.
This
is
an
effort
to
number
one
kind
of
consolidate
everything
and
save
people
time
a
lot
there
and
also
to
keep
it
a
bit
more
asynchronous.
This
meeting
is
useful
but
kind
of
the
ecosystem,
team
and
Deitrick,
and
particularly
China
for
more
good,
more
of
a
synchronous
workflow,
especially
while,
all
day
yesterday,
my
my
internet
was
just
non-existent.
A
So
I
was
very
easy.
It
was
a
Sunday,
but
you
know
could
happen
any
day
the
week
so
yeah.
So
that's
that's!
What's
going
on
out,
there
is
also
going
to
be
a
place
for
Docs
discussion,
so
it's
gonna
be
a
static
place
either
in
the
Disco's
forum.
So
just
ghost
all
built
in
within
hubs,
discussion,
platform,
I'm
gonna,
get
on
that
today.
I
was
hoping
together,
I'd
done
by
today,
but
other
things
kind
of
cropped
up.
B
B
A
B
B
A
B
Also
I'm
also
envisioning,
like
a
bunch
of
scenarios
where
somebody's
like
I
want
thing
X
in
the
docks,
because
I'm
working
on
project
Y,
that
does
things
ed
and
then
that's
really
easy
to
branch
people,
often
to
like
hey
all
these
other
things.
All
these
other
folks
are
talking
about
things
that
over
here.
So
in
terms
of
like
interconnection
of
the
discussion,
that's
cool
but
yeah
at
some
point
once
it
manifests
it's
something
like
actual
issues
in
the
docks
repo,
then
in
your
branch,
McMuffins
also,
that
I
said
is
part
of
the
overall
site.
A
B
B
C
The
only
thing
I
wanted
to
comment
on
was
I
think
our
privatization
is
mostly
right.
I
think
that
my
deprecating
the
legacy
site
and
wanting
the
B
to
say
it's
a
release
is
p0
and
if
everything
else
there
drops
fine
like
so
in
I
would
encourage
a
harsh
prioritization
there
with
what
little
time
we're
gonna
have
this
quarter.
C
C
forward,
but
Toyota
is
that
that
one
that
one
bit
more
than
anything
I
think
that'll
give
us
the
most
that'll
give
us
the
most
flexible
space
moving
forward,
because
the
old
another
thing
that
that's
worried
about
yeah,
no
good
point
and
a
big
wind
filling
for
the
community
and
new
developers
coming
to
the
project
as
well.
Yeah
and.