►
A
A
So
if
you
are
here,
please
put
your
name
on
the
attendees
list
and
please
also
do
fill
out
your
async
weekly
update.
We
won't
go
through
this
in
the
meeting,
but
if
this
is
for
everyone
else
to
read
up
on
what
you've
been
up
to
in
the
past
week
and
in
their
own
time,
so
yes,
please
fill
out
that
so
people
know
what
you've
been
doing
and
we
will
begin
by
running
through
the
we
have
a
note
chicken.
A
We
will
begin
by
running
through
the
initiatives
so
initiatives.
What
are
we
doing?
What
are
we
doing?
What
have
we
been
doing?
Well,
first
of
all
upgrade
the
release
process.
I
can
talk
a
little
to
that
because
last
week,
I
sent
a
pull
request
for
updating
the
release
process
for
jeaious.
Ipfs
is
based
heavily
on
the
good
work
that
went
into
the
pull
request
for
improving
the
release
process
called
go
IGFs.
Thank
you.
A
B
A
A
So
that's
cool
moving
on
then
upgrading
the
testing
impress
match
process.
I,
don't
have
anything
new
here,
I'm
hoping
that
maybe
this
week
I
have
time
to
the
fitness
benchmarks,
poor
request,
but
I
don't
have
anything
else
to
add
so
Steven
your
gem.
Would
you
like
to
talk
to
that?
If
you
have
any
news.
B
Not
a
whole
lot
of
these
roll,
your
old
push
done
some
more
code
which
I
have
to
look
at
and
sort
of
taking
the
day
off
today,
mostly,
but
I've
been
experimenting
a
bit
with
adding
some
instrumentation
to
to
pull
out
some
more
events
you
get
somewhere
observability
into
like,
if
that's
I,
confess
itself
and
actually
has
some
interesting
demos
for
that
and
roll
some
code.
For
writing.
Some
stuff
on
about
cluster
might
understand
so
back
to
okay.
A
So
that's
all
for
updating
the
testing
in
first
process.
For
now
next
up
is
garbage
collection
and
pinning
last
was
I
wasn't
last
week,
because
I
wasn't
here
last
week,
but
it
was
a
week
before
I
think
might
have
been.
Last
week
anyway,
I
match
the
initial
implementation,
with
garbage
collection.
The
Dirk
had
done
for
JSI
PFS
and
that
will
be
available
in
the
upcoming
release
of
the
next
release
of
Chase
ipfs
0:38,
and
just
a
note
to
people
that
this
is
literally
just
the
first
pass
implementation.
A
C
A
Thank
you
for
putting
out
there
as
well
that
we
were
I.
Think
you've
done
this,
but
in
the
basis
of
kind
of
renaming
that
enable
pub/sub
experiment
flag
to
enable
pub/sub
because
of
the
fact
that
it's
being
pulled
out
of
any
experimental,
config
elsewhere
and
I
think
I
suggested
leaving
that
old,
the
old-style
one
as
a
kind
of
alias
for
now.
Yes,.
A
A
Sorry
go
for
a
second,
so
there
is
the
gossip
sub.
Implementation
is
coming
to
you,
J
sake
FS,
and
we
have
renamed
because
it's
basically
moved
out
of
experimental
in
all
of
the
other
config
we've
renamed
the
ipfs
daemon
flag,
enable
pub
sub
experiment
to
just
enable
pops
up
without
the
theremin
right.
D
D
So
we
are
looking
at
to
potentially
change
in
the
protocol
to
not
use
message
signing
to
rely
on
some
other
way
to
like
get
messages.
I
certainly
rely
on
my
sub
sentence
if
you
have
like
the
ID
and
like
some
arbitrarily
chosen
over
that,
we
use
this
to
get
messages,
but
this
is
something
it's
a
sign.
D
The
kid
so
you
can't
like
toss
people,
so
there
are
some
questions
about
whether
or
not
we
have
to
go
with.
Like
change
some
things
now
we
can
always
just
grab
the
protocol,
so
he
finds
anything
he
bets
on
an
issue
I
in
bit
like
I
guess,
on
this
specific
topic,
I
wouldn't
say
we
name
any
one
hopes
to
expect
to
observe
I
would
just
enable
by
default
if
it
becomes
no
I,
don't
see
any
reason.
Why
not
is
that
mister.
A
D
A
D
F
D
A
D
D
D
You,
unless
you
want
to
have
something
we're
like
if
you
aren't
subscribed
to
anything
you
just
don't
like,
ideally
like
if
I'm,
not
scratch
anything
I
would
just
like
shut
down
the
entire
column,
so
service
ended
if
I
subscribe.
I
would
like
a
reopen
it
I,
don't
know
how
much
extra
band
what
that
would
take
like,
but
no
that's
a
really
that's
hard
to
do.
No,
we
can't
do
that
because
we
don't
currently
have
a
good
way
like
pushing
out
no
PhD
PSA.
Okay.
We
now
support
this
thing.
A
D
A
That's
that's,
let's
talk
about
it
later
and
we
can
come
to
a
conclusion.
I
didn't
think
it
would
be
quite
some
problematic,
but
let's,
let's
do
that,
because
we
have
only
have
so
much
time
for
this
cool
but
I'm
glad
I
raised
it
at
least
alright.
Moving
on
that
subdomain
gateway
Lydell,
are
you
hate?
Give
us
a
quick
up.
G
Very
quick
updates
would
be
made
another
pass
on
the
RFC
number
one
and
apply
it's
just
changes
mainly
added
upgrade
path.
So
the
short
short
story
is,
we
will
add,
support
for
decoding
CID
v1,
like
decoding
PRDS
represented
as
CID
p12
like
first
release
the
TP
and
we'll
wait
either
three
months
or
until
the
next
release
happened
and
then
we'll
switch
the
default.
G
A
C
H
Yeah
hey
so
the
spit
work
is
ongoing.
We
call
scheduled
for
tomorrow
to
discuss
some
missing
pieces
and
it
will
be
out
this
week,
hopefully
also
ever
requests
regarding
almost
ready
to
merge.
Hopefully,
it's
running
the
test
for
the
last
time
and
now
we'll
start
to
implement
the
DNS
over
HTTP
for
the
FS
DNS
comment
to
support
penis
over
DNS,
which
will
make
the
whole
our
implementation
much
simpler.
A
No
we're
cool
thanks
for
the
update
you
go
and
this
stuff
is
regression
to
multi
hash
keys
and
block
store,
okay,
fun
times,
so
Adam
is
Adam.
No,
no!
It's
not!
Okay!
Someone
has
got
this
out
of
this
initial
analysis
in
code
base
for
parts
that
will
be
affected.
Okay,
interesting
outcome
is
in
alright,
yes,
and
so
there's
an
action
item
for
me
and
Steven.
So
have
a
look
at
that
bull
request
or
issue.
D
A
Was
the
thing
yet
Dirk's
gonna
present
his
improve
these
improvements
on
the
next
meeting
so
be
sure
to
check
that
out,
because
that
should
be
really
interesting
or
at
least
I
think
so
and
cool.
So
next
up
the
async
of
weight,
refactor,
so
I
put
some
notes
here.
So
alex
is
trying
to
land,
adding
with
an
async
iterator
and
there's
a
possibility
that
that
might
make
Jase
IVFs
be
able
to
add
things
to
it
faster
than
go
ipfs
in
certain
situations.
D
I
I
A
Right
so
aside
from
that,
the
ipfs
httpclient
has
now
has
browser
pops
up
in
the
browser,
which
is
super
good
news,
but
not
really
relevant
to
async/await,
or
is
it
because
it
actually
uses
the
fetch
API
in
the
browser,
which
is
all
kind
of
promise
based.
So
it
is
a
stepping
stone
to
async
await
in
that
particular
library
as
well.
So
there's
good
news
and
now
that
that
that
initial
step
has
been
taken,
we
can
sort
of
roll
that
out
to
the
other
API.
Is
that
are
there?
So
that's!
That's!
That's
cool!
A
A
D
A
A
D
A
A
Please
read
it
and-
and
please
read
it
and
give
me
your
review
and
I
added
a
couple
of
things
from
the
go
I
like
if
you'd
read
the
go
one,
then
it's
probably
really
familiar
you'll
be
able
to
skim
it
really
quickly,
and
there
was
a
couple
of
things
that
I
wanted
to
highlight,
which
is
that
I've
added
is
like
adding
a
shipping
date
just
so
that
we
can
give
the
night
people
an
idea
of
when's.
The
thing
might
actually
arrive.
A
We
don't
have
to
be
specific,
but
just
saying
probably
this
week
in
September
or
would
be
useful
for
July
visitors.
The
second
thing
was
opening
up
the
like
the
next
release
issue.
As
soon
as
we've
done
the
release
just
so
that
people
can
start
planning,
we
can
work,
we
can
give
them
an
idea
when
the
next
one
might
be
available
just
yeah
just
for
that
kind
of
that
process
to
start
up
quickly
rather
than
waiting
before
until
we
need
to
start
doing
the
steps.
A
A
My
second
ask
is
I'm
going
to
be
going
away
for
a
little
bit
for
like
a
month
and
the
next
year's
IVFs
release
needs
to
need
to
be
released
according
to
that
updated
shares,
I'd
be
a
first
release,
process
document
and
so
I've
linked
to
an
issue
where
I've
kind
of
described
the.
What
kind
of
needs
to
happen.
But
importantly,
we
kind
of
need
someone
to
spearhead
it
and
and
take
it
to
the
finish
line
and,
and
it
would
be
cool,
maybe
I,
don't
know,
but
maybe
having
like
a
duo
of
people
releasing.
A
D
Would
miss
I
mean
like
making
PRS
assigned
a
people,
Leslie
maintainer,
so
various
proposed?
If
you
aren't
willing
to
do
this,
please
or
think
you
might
be
willing.
Please
meet
the
mediators
document
and
make
sure
that
you
guys
want
to
take
on
because
it's
non-trivial
amount
of
work,
but
I
think
once
they
are
subdued.
This
is
really
important
so
that
we
spread
the
load
around
it.
Also,
like
other
people
like
understand
the
different
repose
yeah.
It
also
mixtures
that
things
get
through
faster.
The
main
thing
really.
E
A
D
D
G
Something
related
I
like
we
talked
a
lot
about
this,
but
I
am
Not
sure
it
might
be
related
is
that
with
added
tests
for
DNS
resolver
for
that
ETH
in
Jessica's
and
to
the
Interop,
and
they
were
migrating
to
permanent
infrastructure
and
they
shut
down
the
old
one.
So
for
a
half
a
day,
our
CI
went
down
to
two
dots,
but
I,
don't
think
it's
I
just
looked
at
the
test
and
it's
not
the
same
thing.
So
it's
not
actually.
C
A
Okay,
yeah,
that's
the
so
this
could
be
that
the
gateways
have
switched
to
using
a
new
version
of
go
ipfs
just
now,
and
not
just
now
over
there
bin.
When
did
I
see
this
failing,
maybe
you
fries
fried
Saturday,
maybe
late
Friday
or
Friday
in
the
u.s..
Maybe
is
that
ring
any
bells?
Okay,
alright!
So,
anyway,
questions
is
there
any
questions,
we're
running
out
of
time,
really
rapidly,
No,
okay,
parking
lot.
Okay!
Next
steps
for
I
don't
asks
that.
What
are
the
next
steps
for
the
HD
in
choice?
I
profess?
A
There
is
a
pull
request,
adding
the
DHT
there
is
a
list.
I
will
link
to
that
pull
request
and
put
it
in
in
this
document.
But
there
is
a
list
of
things
that
need
to
happen
for
us
to
merge
it
and
what
I'm
thinking
is
likely
right
now
is.
We
should
just
add
it
in
DHT,
client
mode
and
by
default
and
and
leave
it
at
that.
A
We
don't
have
the
ability
to
know
when
we're
behind
than
that,
so
I'm
hesitant
to
add
it
as
not
client
mode,
but
there
are
other
things
that
are
in
the
way
before
that
can
happen.
I
could
list
it
as
one
of
the
things
potentially
for
the
0:38
release
and
that's
one
of
the
things
that
I
would
like
input
on
from
people.
If
they're
interested
there
is
an
0:38
release
issue
a
link
to
it
somewhere
in
this
document
already
just
go
to
the
issues
thing
on
jesso
because
it's
pinned
at
the
top.
A
If
you
really
want
it,
then
maybe
+1
it
cool
all
right
and
then
write
the
weekly
updates
and
that's
it.
So
we
are
done.
We
are
finished
and
it
is
6
o'clock,
so
you're
right
on
time.
Thank
you.
Everyone,
brilliant
work,
any
last-minute
things
you
want
to
voiced
today,
alright
cool.
Thank
you
very
much.
Everyone
for
your
updates
and
and
interactions
I've
enjoyed,
seeing
your
faces
and
I
look
forward
to
seeing
them
again
soon
happy
Monday
and
have
a
lovely
week,
I'm
PMSing,
wherever
you
are.