►
A
Okay,
hello,
everyone
welcome,
welcome,
welcome
all
it
is
October
the
14th,
that's
right.
It's
like
the
ipfs
core
implementations,
weekly,
sync
and
I-
am
Allen.
I'm
gonna
run
the
meeting
to
some
extent
as
best
I
can
and
yeah.
So
if
you're
here,
please
put
your
name
on
the
attendees
list
in
the
notes
document.
I
am
just
gonna
paste
that
into
their
chat,
so
you
can
see
it
and
if
you
haven't
already,
then
please
I
think
most
you
already
have,
which
is
great.
A
Please
add
your
weekly
update
for
async
review
to
the
bottom
of
the
document
is
the
last
last
heading
basically
and
that's
for
people
to
take
a
look
outside
of
the
meeting
at
what
you've
been
up
to
what
you've
done
last
week,
what
you
blocked
on
and
what
your
plan
is
for
this
week
and
we'll
do
that
a
synchronously.
So
we
won't
go
through
that
in
this
meeting.
A
But
now
what
we
do
usually
is
go
through
our
initiatives
and
get
an
update
from
people
on
what's
going
on,
I
have
I've
been
off
for
about
a
month,
so
I
have
very
little
to
contribute
so
I'm
hoping
you're
all
gonna
step
up,
but
yeah
all
right
cool
we've
got
a
note-taker
where
we
started
the
recording
and
yeah
we're
good.
Let's
go
no
so
initiatives
the
upgrading
the
release
process,
so
Steven
is
out
this
week,
I
believe
but
Alex
as
you've
been
running
the
JSI
BFS
stuff
for
releasing
and
making
it
better.
B
Sure
so
we
published
our
c0
38
that
super
good.
All
the
stuff
that
we
wanted
to
get
in
is
in.
We
also
added
automated
testing
for
all
of
the
examples,
because
testing
them
manually
is
super
tedious
and
and
who
likes
to
do
that
literally
no
one.
So
now
they'll
run
in
CI
every
time
you
push
anything
to
a
release
punch,
we
can
actually
make
them
run
on
Pio's
as
well
like
there's,
no
reason
not
to
because
the
machines
do
all
the
hard
work
and-
and
they
don't
complain.
So
you
know
maybe
we'll
do
that.
B
Next,
there
is
in
those
a
little
bit
of
weirdness
around
block
om,
which
is
going
to
be
fixed
off
by
APR,
that
is
costing
NCI
now,
but
awaiting
a
change
to
pull
ND
Jason
from
David
sticker
thing
and
then
notes
about
that.
But
yeah
super
good.
So
the
next
for
that
is
to
add
the
testing
of
the
external
repo.
B
So
we've
had
the
code
in
as
year
to
do
that
for
a
while
and
we've
been
testing
our
internal
external
repos,
but
now
we're
going
to
start
doing
third-party
things
as
well,
so
running
the
test
for
ipfs
log,
all
the
DB
and
anyone
who
signs
up
for
the
early
tester
program,
which
is
great.
So
the
only
the
only
requirement
that
it
has
is
the
the
repos
that
we
test
have
to
have
a
dependency
on
either
jsrf
s
or
the
IPS.
B
B
So
one
of
the
are
the
things
like
if
you,
if
you
discover
that
you've
broken
someone's
tests
and
you
you
write,
you
know,
you'll
be
a
good
citizen
in
your
IPR
because
he's
like
you've
done
something
you've
reached
a
breaking
change
and
they
need
to
do
some
of
your
factoring.
And
you
know
you
decide
to
be
a
good
citizen
and
you
write
a
PR
that
change.
It
does
the
refactor,
but
it
hasn't
been
merged
yet,
but
we
can't
have
that
then
hold
up
our
releases.
B
So
you
know
you
can
then
say
to
as
you
Haven
run
this
branch
instead
of
running
master,
so
we
can
run
them
against
PRS
until
they've
merged,
but
like
with
the
proviso
they've.
Obviously,
once
those
those
pr's
and
merge,
those
branches
typically
get
deleted.
So
it's
kind
of
a
time-limited
thing,
but
it
does
unblock
our
release
process
and
that's
the
stuff
that
we
do.
A
B
A
B
A
B
I
I
took
the
list
of
projects
from
the
release,
template
which
has,
like
you
know,
pea
pod
and
buy
in
gamma,
not
reverse,
and
all
that
kind
of
stuff,
and
then
we
had
and
that
as
well
as
already
being
IPO,
that's
log
and
then
had
a
bit
of
a
call
for
contributors
and
contributors
are
called
for.
Early
access
testers
and
we've
got
one
other
one.
Other
group
who've
who've
joined
in,
which
is
cool.
A
B
If
we
break
like,
if
we,
if
we
break
these
people's
builds
than
you
know,
we're
kind
of
saying
we're
not
going
to
do
that
in
future,
which
is
why
it
goes
into
CI.
But
then,
if
we,
if
we
resubmit
a
fix
and
they
haven't
merged
here,
then
we
can
run
our
CI
against
the
branch
with
a
fix
rather
than
running
against
the
broken
stop.
So
there
were
no
longer
block.
B
One
thing
in
particular,
like
pier
pad,
is
in
pretty
bad
shape
at
the
moment,
like
the
test
own
run
at
all.
Really
so
the
test
run
and
then
the
test
runner
fails,
offer
all
the
tests
of
pass,
which
is
really
tedious
and
I
spent
like
a
day
trying
to
put
her
back
into
shape,
but
yeah
all
the
no
tests
pass.
But
then
the
browser
tests
don't
run
very
well
and
Connor
is
doing
it's
lovely
job
of
obscuring
all
useful
messages.
A
Okay
and
then
young
ever
thing
I
wanted
to
raise
was
there
was
an
issue
I
think
David
opened
for
saying
that
he
might
think
the
release
process
is
too
long.
Perhaps
we
should
take
that
conversation
to
a
parking
lot
if
we,
if
we
have
time
at
the
end,
that
yeah,
if
you're
interested
in
that
then
and
you
have
feels
then
go
and
comment
on
that
issue-
maybe
I'll
add
it
to
the
notes
at
some
point
anyway.
Sorry
does
anyone
know
anything
so
moving
on?
Has
anyone
know
about
the
Go
ipfs
release?
A
C
A
Okay,
all
right
all
right,
in
which
case,
let's
move
on
upgrade
testing,
infra
and
or
process
is
assistants.
Not
here
Jim's,
not
here,
I
am
here,
but
not
a
no
stay
up
the
beat.
So,
let's
skip
over
that
one
for
today,
because
I
can't
speak
to
it.
A
litel,
subdomain
gateway,
stuff
IPS
in
base
32
I
saw
last
week
that
the
spec
got
merged
and
there
is
an
issue
tracking
its
implementation
and
I
was
just
wondering
if
they're
like,
if
you
had
any
updates
on
that
and
like
is
anyone
assigned
to
it.
A
D
D
It's
like
basically
we've.
We
need
to
switch
the
p2p
from
when
they
parse
multi
others,
the
PID
switch
it
from
being
just
a
CID,
v-0,
multi
harsh
right
now
we
use
multi
harsh
library
directly.
So
the
change
is
to
switch
multi
harsh
to
see
I
it
to
see
IDs
library
in
a
backward.
It
should
be
mostly
backward
compatible.
Cuz
like
CID
v-0,
is
effectively
multi
harsh,
that's
that's
about
it.
A
A
Then
IP
and
Ness
is
Aidan
or
Hugo
is
here
so
the
what
is
it?
The
last
week
we
had
a
some
information
about
a
pub
sub
pubs
of
discovery
being
improved.
Does
anyone
know
about
that?
We'll
have
a
link
to
APR
that
they
can
put
on
there.
Cuz
I'd
like
to
see
it
and
then
the
other
thing
was
Hugo.
I
guess
you
might
know
I
cleaner,
so
a
DNS
spec.
Is
there
a
update
on
that.
A
You
guys
alright
I
will
attempt
to
fish
them
out
or
ask
I
didn't
for
them
for
a
PR
to
look
at
so
then
upgrade
what
this
next
one.
So
migration,
tube,
multi
hash
keys
in
the
block
store
that
is
I,
don't
know
that
there's
a
big
up
there
I
think
the
actual
migration
tool
that
could
do
a
repo
migration
is
almost
merged.
I.
Think
Alex
told
me
today:
I
guess
the
the
discussion
point
on
that
is.
If
we
were
to
change
the
block
store
to
using
multi
hash
for
keys,
we
lose
the
IP
OD
codec.
A
So
when
we
use
commands
like
refs,
we
end
up
printing
out
just
multi
hashes,
not
not
see
IDs
with
peyote
codecs
in
them,
and
we
kind
of
need
a
solution
to
that
before
we
can
move
forwards
because
I,
don't
I'm,
not
sure
I
have
I'm,
not
sure
I
have
one
off
the
top
of
my
head.
But
if
anyone
has
any
thoughts
on
that,
then
we
you
should
check
out
I,
think
that's
a
pull
request
or
a
issue.
A
A
B
A
G
So,
by
the
way,
it's
a
holiday
today
in
America,
so
I
think
that's.
Why
there's
no
updates
on
some
of
this
stuff
with
respective
bit
swap
I've,
been
working
on
so
I
have
a
concept
that
I've
been
working
on
for
a
while
and
I've
got
a
running
fast
now,
meaning
it
doesn't
take
very
long
to
transfer
stuff
and
it's
consistent
across.
G
A
A
A
E
E
We
could
potentially
do
that,
but
a
lot
of
people
are
still
using
WebSockets
all
right.
So
if
we
release
the
refactor,
then
it
just
won't
work
with
it.
Ideally,
we
want
a
sunset.
Websockets
are
but
I
think
if
it
gets
to
a
point
where
it's
too
much
work
to
redo.
That
then
maybe
we'll
find
another
path.
One
of
the
things
that
we
talked
about
was
or
I
thought
about
doing,
was
just
changing
the
WebSocket
star
server
to
actually
just
be
a
circuit
relay
node.
A
So
I
noticed
that
there's
now
like
a
Trello
for
the
async/await
stuff
for
Libby
to
be
all
of
that
stuff.
Getting
done
and
that's
I
think
that's
a
really
good
idea.
Do
you
mind
linking
it
here
so
other
people
can
follow
gee.
H
H
F
This
boilerplate
boilerplate
was
refactored,
it
was
moved
into
IP,
FST
CTL
is
always
sync
awake
now
and
you
can
see
there.
The
requests
with
all
those
changes
and
also
pedro,
is
working
on
moving
the
interrupt
repo
to
a
sync
weights.
Right
now
we
are
basically
focusing
on
the
first
fully
quest,
which
is
moving
to
the
new
version
of
a
brief
sec
TL,
which
is
already
async
await.
We
had
some
troubles
even
today
we
were
here.
We
had
a
debugging
session
and
we
found
some
bugs
and
hopefully
everything
is
figured
out.
F
I
B
Following
a
pattern
we
establish
with
with
files
dot
had,
which
is
gonna,
be
super
good
when
it
goes
in,
and
that's
just
kind
of
like
waiting
for
like
fixes
to
the
block.
Rm
I
wanted
to
put
enter
master
and
then
and
then
put
the
new
stuff
in
after
that
good,
to
simplify
cherry-picking
stuff.
To
pull
over
to
the
release
branch
for
three.
A
Nice,
thank
you.
Everyone
also
hi,
bedroo
I,
didn't
know
you
started
working
whilst
I
was
away,
so
it's
nice
to
nice
to
see
your
face
can
for
the
I
feel.
That's
HTTP
response
can
I
get
a
link
for
the
pull
request.
Please
method
to
the
notes.
Brad,
thank
you
and
keep
up
the
good
work.
We
should
chat
sometime,
but
not
now
all
right.
So
this
week,
design
review
proposals.
Vidal
has
a
a
review
proposal
to
it's.
D
A
D
A
A
All
right
very
talkative
this
does
anyone
want
to
talk
about
the
release,
Paris,
that's
being
too
long,
I.
C
B
A
Okay,
I'd,
like
I,
am
yeah
I
would
at
least
like
to
go
through
this
myself,
one
iteration
before
we
decide
on
it.
I
guess
I
can't
really
speak
to
it,
but
if
you
think
it's
just
right,
Goldilocks
then
we're
good.
We
can
continue
on
the
assumption,
I
guess
all
right
and
then,
let's
finish
I
guess
are
we
all
done?
A
I'll
put
it
in
the
notes
as
well,
if
you're
interested
but
other
than
that,
I'll
see
you
on
the
chat
thing
because
it
could
be
fun
and
I'll
see
you
next
week.
Thank
you
very
much
for
updates
and
it
was
really
nice
seeing
your
faces
and
hopefully
we'll
have
more
more
go.
Ivfs
team
information
next
week
do
we
know.