►
Description
See the meeting notes at https://github.com/ipfs/team-mgmt/issues/992#issuecomment-679190715
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
Hi
everyone
welcome
to
the
ipfs
core
implementations
weekly
sync
for
monday,
the
24th
of
august
2020..
I
am
a
king
brain.
I
will
be
your
host.
We
are
going
to
go
through
our
high
priority
initiatives
and
our
other
initiatives
and
then
questions
and
design
reviews
and
all
that
fun
stuff.
So
the
first
thing
to
talk
about
is
upcoming
and
shipped
releases.
B
That
yeah,
so
agaves
0.7,
is
almost
there.
All
of
the
features
are
basically
in
there's
just
one
or
two
bugs
that
we
are
running
up
against
before
we
put
together
the
rc
so
hopefully
early
this
week,
meaning
the
next
couple
of
days.
C
Yeah
and
then
jslippydp0.29
we're
working
on
the
final
bits
for
that,
so
that
will
include
un8
array,
support
across
the
board
and
then
we'll
also
include
gossip
sub
1v1
along
with
signed,
appear
records.
So
hopefully
we
should
have
that
I'd.
Imagine
maybe
maybe
midweek.
A
A
Benefit
yeah,
so
next
up
is
pinning
services.
C
The
client
work
for
go
is
still
pending
the
rc
finishing
up
and
we
can
move
over
to
working
on
that.
C
C
There
is
a
as
part
of
that
we
found
there
was
an
issue
last
week
and
jsipfest
that
we
found
with
inline
keys,
like
ips,
was
not
handling
that
properly.
That
has
subsequently
been
fixed,
but
it's
currently
in
master
and
jsipfess
in
an
0.49.1
rc.
So
I
imagine
that
will
just
land
in
0.50,
probably
later
this
week,
yeah.
B
A
Is
it?
Is
it
worth
doing
a
patch
release
of
js
ipfs
with
the
ips
key
validation.
C
A
Yeah,
the
like
the
only
time
you
see
pub
sub
break
is,
if
you
built
your
own
version
of
the
browser
node
from
source,
because
the
the
the
change
went
in
after
we've
done
the
last
release.
So
the
minified
version
doesn't
have
the
broken
utils
enough,
but
yeah.
C
Yeah
I
mean
if
cutting
that
release
is
quick.
I
would
just
go
for
it
just
because,
like
ips
was
also
doing
some
nasty
things
when
trying
to
do
resolve
which
make
things
slow.
So
this
will
also
help
speed
that
up.
It's
like
the
same
patch
that
go
made
to
remove
trying
to
fetch
the
public
key
before
you
actually
fetch
the
record.
C
A
C
Yes
and
I
believe,
like
there's
work,
so
we're
updating
the
daemons,
because
we
run
a
few
of
the
relays
that
ipfs
uses
we'll
also
be
updating
those
to
remove
secio
as
well.
C
B
C
Just
do
that
because
yeah,
I
think
it
might
already
been
merged.
Actually,
okay,
all
right.
If
not
then
yeah
it
should
be
mergeable,
and
then
we
can
do
a
minor
release.
So
that's
already
been
notified.
People
have
been
notified
on
discuss,
so
you
can
still
re-enable
it
and
bring
your
own
config
if
you
need
to,
but
by
default
we
will
not
ship
with
it.
B
I
guess
related
to
the
elliptic
curve
keys,
one
more
thing
or
not
quite
but
go
multi-outer
has
support
for
cids
in
peer,
ids
or
pid
is
represented
as
cids.
So
that
means
that
if
you
get
a
multi-adder
that
has
like
you
know,
slash
p2p,
slash
baffy,
something
in
it
that
will
work.
B
We
will
eventually
try
to
move
all
of
the
p2p
multi-outer
resolution
this
way,
but
not
everyone
has
the
cid
code
yet
in
all
of
the
different
implementations.
So
this
will
take
longer.
D
Yeah
thanks:
we
are
working
towards
pinning
we're
hoping
to
get
that
in
within
the
next
week,
maybe
next
two
weeks,
so
that
just
involved
a
lot
of
refactoring
but
also
getting
a
dht
working
as
well.
So
that's
a
lot
of
nice
conformance
tests
that
are
passing
and
dht
content.
Discovery
works
really
well,
but
publishing
is
tricky
because
there's
no
autonat
stuff
in
the
rustling
p2p
implementation.
D
I
noticed
there's
a
couple,
pull
requests
that
are
in
there.
So
maybe
those
need
to
get
reviewed.
I
don't
know
if
anybody
has
any
inroads
to
parody
nudge
them
on
that
stuff
and
we'll
be
able
to
publish
content
on
the
dht.
D
Otherwise
things
are.
Things
are
moving
along.
A
Cool
next
up
is
live,
p2p
sign
peer
records
and
gossip
sub
v,
1.1.
E
F
Pub
sub
interface
is
basically
ready.
It
was
mostly
finished
last
week
and
jacob
did
enormous
review
last
week
and
a
second
pass
today.
So
I
think
we
are
mostly
ready
for
merging
it.
The
flat
sub
pr
is
also
updating
the
implementation
to
use
this
interface,
steam's
also
ready
and
reviewed,
and
exactly
the
same
for
gossip.
So
so
we
have
basically
one
thing
to
finish
in
gossip
1.1.
F
Basically,
we
have
a
flaky
test
regarding
opportunistic
crafting
and
I
will
be
looking
into
it
later
today
and
hopefully,
if
I
get
it
fixed,
I
think
it's
the
only
blocker
left
so
that
we
can
start
merging
and
releasing
everything
unless
any
last-minute
review
stuff
happens
and
yeah.
Also,
I
tested
it
in
both
suggested
php
and
js
ipfs
in
the
jslip
hp.
You
are
basically
running
the
interrupt
tests
with
an
older
version
of
globally,
while
we
don't
have
the
demand
updated.
F
So
we
are
basically
running
the
jsp
with
gossip
sub
1.1
and
goalie
php
with
the
gossip
sub
1.0,
and
everything
is
good,
which
is
also
a
good
sign,
but
it
would
be
cool
to
test
with
the
gospel
one,
not
one,
but
then
I
tested
in
jsrpfs,
which
currently
tests
with
the
latest
go
ipfs,
and
this
one
is
already
using
gossip
1.1
and
interrupt
tests
are
working
as
well
so
yeah.
I
think
we
are
pretty
confident
that
everything
is
cool
in
interrupt
part
of
things
going
to
the
next
item:
the
jsimpler
discoverability
and
connectivity.
F
C
I
think
that
got
merged
into
wwe,
but
we'll
need
the
latest
changes,
but
I
think
that
that
will
at
least
get
us
the
the
gossip
sub.
So
if
there
is
further
delay,
then
we
can.
We
can
do
that,
but
I
think
we
can
probably
wait
until
the
next
little
pdp
version
is,
is
done.
A
Okay,
that
is
it
for
the
high
priority
initiatives.
Moving
on
to
the
other
initiatives,
sub
domain
gateway.
I
have
no
lydle,
no
reba.
B
There's
no
merge
the
pr
and
go
ipfs
for
wildcard
gateways
so
that
there's
a
quest
request
for
people
to
be
able
to
have.
You
know,
gateways
that
are
named.
Like
you
know
my
my
thing:
dot,
username
dot,
you
know
the
tld,
and
so
now
we
have.
We
have
support
for
that.
A
So
the
unix
of
s,
v
1.5
and
guy
pfs
not
update.
As
far
as
I'm
aware
pinning
system
revamp,
I'm
gonna
merge
it
like
tomorrow
morning.
After
doing
this
point
release
of
js
ipfs
and
then
it
needs
it's
like
all.
The
all
the
pr's
that
are
required
to
be
merged
have
been
merged.
The
last
thing
is
just
the
js,
the
p2p
release,
which
we've
gone
over
already
dag
service.
G
It's
me:
I
didn't
really
have
time
for
it
last
week,
so
nothing
happened
there.
The
next
one
is
improving
web
ui
file
stuffs
that
pr
got
merged.
G
I'm
still
working
through
the
progress
bar
reports
turns
out
web
ui
had
it
at
some
point,
but
it
was
ripped
out
so
there's
a
lot
of
things
that
need
to
happen
to
get
it
to
work.
It
was
also
semi-blocked
on
the
progress
events
that
were
rejected
and
I
think
now
we're
gonna
put
them
back
in
into
the
http
client,
so
they
do
that's
what
they
it
will
use.
If
not
then
we'll
fake
it.
I
mean
the.
G
Progress
yeah:
this
is
it.
A
Cool
so
moving
on
design
review
proposals.
Does
anybody
have
a
proposal
for
a
bike
shared
contest.
A
Come
on
that's
so
much
fun:
okay,
fine
blockers
and
asks.
G
Anybody
blocked
alex
if
you'll
get
a
chance
to
review
some
of
the
non-js
ipf
as,
like
the
other
libraries
that
we
pull
in.
There
are
a.
A
B
Fun
one
which
is
once
once
this
releases
out
for
0.7.
B
B
So
if
you
would
like
to
lobby
me
for
your
favorite
feature,
now
would
be
the
time
now
not
meeting
this
meeting,
but
over
the
next
week.
A
Okay,
good,
if
there
are
no
more
parking
lot
items,
then
we
can
draw
this
meeting
to
a
close.
Please
fill
in
your
async
updates.
Let
people
know
what
you're
going
to
be
working
on.
Thank
you
very
much
everyone.
This
has
been
the
ips
core
representations.
Wiki
sync.
For
monday,
the
25th
of
august
2020.