►
Description
Meeting description here:
https://github.com/ipfs/team-mgmt/issues/992#issuecomment-596614509
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
Okay:
okay,
okay,
okay,
okay,
we
are
in
the
ipfs
quorum,
implementations,
weekly
sync,
it
is
the
life
of
March.
It
is
2020
still
for
a
while.
Yet
welcome
welcome
everyone.
If
you're
here,
please
add
your
name
to
the
attendees
list
on
the
hackpad
I
will
paste
it
one
more
time
in
the
chat.
Just
in
case
you
missed
it.
A
If
you
have
any
a
sync
updates
that
you
would
like
people
to
hear
then
add
them
to
the
or
hear
or
read
and
then
add
them
to
the
bottom
of
the
dock.
We
won't
go
through
them,
but
people
will
be
able
to
look
at
them
later
when
the
notes
get
caught.
I
said
to
the
the
team
management
repo
and
some
people
can
review
on
those
whenever
they
please
and
other
people
who
weren't
able
to
be
here,
can
look
at
them
too.
So
that
still
be
useful.
A
B
C
C
Some
like
interesting
things,
because
we
need
to
do
a
repo
migration
and
we
have
numbers
for
things
and
the
next
one
was
a
place
to
be
the
migrations
of
storing
Brooks's
by
a
multi
hash
instead
of
IC
ID.
So
I
don't
know
if
we
want
to
pin
the
next
version
number
on
that
feature.
So
finished
that
and
then
get
the
pen
migration
in
need
to
have
a
conversation
about
this
prioritization
in
the
week
with
other
than
that,
like
bug
smashing
party.
C
Mono
repo
style
so
there's
a
whole
bunch
of
like
outstanding
PRS,
so
I've
been
I've,
been
triaging
the
issues
and
moving
the
ones
across
they're
still
valid,
but
there's
a
whole
bunch
of
PRS
they're
lower
than
quite
simple,
like
just
small
things,
adding
arguments
or
things,
and
so
gonna
have
like
a
bug,
smashing
party,
they
should
know
we
go.
We
bang
through
all
these
PR.
So
I
say
we
we
at
the
moment
as
me.
So
if
anyone
wants
to
join
the
party
cool,
Wednesday,
Thursday
I'll
be
fun.
A
A
B
A
A
Okay,
so
next
up
we
have
content.
Routing
I,
have
an
update
on
that
or
like
Debbie
and
I
have
an
update
on
that.
We
did
this
like
soul,
and
course,
and
the
last
day
the
vide
was
like
we
could.
We
could
kickstart
this
hydro
booster
thing,
and
so
we
spent
our
last
day
of
of
these
systems
distributed
systems.
A
Learnings
kick-starting
this,
this
hydro
project
and
forking,
the
the
old
go,
was
the
IPS
DHT
repo
and
fixing
it
up
and
separating
the
concerns
and
adding
tests
and
creating
plans,
and-
and
so
it
sort
of
became
a
thing
and
I
just
spent
today,
just
fixing
up
some
of
the
refactorings
that
I
was
kind
of
in
the
middle
of
and
adding
some
tests
and
things
and
we've
got
it
running
on
CI
and
but
devide.
Would
you
like
to
explain
what
a
Hydra
booster
is
to
everyone.
D
So
the
booster
was
our
like
wow
and
say
like
last
day
of
this
project,
but
it
doesn't
like
something
that
has
been
like
being
pawed
through
and
spiked
out
over
the
course
of
multiple
weeks
prior
to
that
and
it's
essentially
a
DHT
index.
And
now
it's
a
node
that
exists
not
to
be
just
one
more
node.
But
I
can
note
to
augment
the
quality
of
the
service
of
the
network.
D
I'm
not
really
playing
about
too
much
time
to
explain
it
in
detail.
But
I'll
just
say
that
you
know
that
benefits
from
the
lack
of
civil
resistance
in
the
network
to
see
cigarette
packet
to
place
multiple
heads
and
the
Hydra
in
multiple
occasions.
So
that
like
when
someone
asks
for
a
record,
the
Hat
can
go
to
its
belly,
which
is
shared.
D
I
got
have
so
many
heads
and
give
the
record
out,
and
the
reason
why
I
saw
the
hydro
booster
is
because
it
also
takes
ideas
from
another
proposal
that
was
like
the
HD
boosters
v2
to
not
only
index
out
the
VT
records
but
out
so
keep
kind
of
like
a
yellow
pages
of
all
the
dressed
of
all
the
peers.
So
that
you
can
equip
peers
with
boosters,
they
can
jump
directly
into
the
like
the
right
location
rather
than
having
to
traverse
the
Academy
HT
over
and
over.
D
You
know
it's
like
perhaps
link
here,
the
RFC
and
the
link
to
the
mic
working
progress
implementation.
There
is
a
multi
stage,
implementation,
which
Alan
already
translated
to
a
Zeb
Gantt
chart.
So
much
yeah
I
do
the
short
version.
Yuxuan
more
details
come
on
Ian,
Allen
and
Stephen,
and
Raul
wannabe,
like
a
lot
of
people,
could
get
me
into
this
I.
A
E
E
F
A
G
Including
the
inner
strength,
which
is
not
that
easy
to
test
it
without
DNS,
so
PR
is
ready
for
review
I'm
pretty
happy
with
it,
because
it
does
what
I
wanted
to
do.
I
link
to
the
configuration
recommendation.
So
if
anyone
is
interested,
how
that
thing
would
be
set
up
now
is
the
last
call
to
back
that,
but
I'd
feel
it's
like
pretty
easy,
pretty
pretty
small
configuration
surface,
just
minimal
set
of
new
keys
solely
to
set
up
subdomain
feature
which
paths
are
mounted
per
hostname
and
do
we
support
DNS
link
resolution
for
that
specific
hostname?
G
A
Nice
thank
you
later,
if
you're
interested
in
configuring
subdomain
gateways,
so
not
the
slash,
ipfs,
slash,
cid
the
ipfs
dot
your
domain
then,
and
you
want
to
know
how.
How
would
you
configure
that
in
the
future
and
are
interested
in
how
you
would
configure
it
in
the
future,
then
go
and
check
out
load
was
PRS.
H
Yeah
so
last
week,
I
was
basically
doing
some
fine-tuning
on
this
one
so
heading
into
the
to
the
releases
upcoming,
so
just
sort
of
cleaned
up
a
couple
of
POS
there
and
some
tests
and
stuff
like
that.
And
then
this
week
I've
won
outstanding
PR,
that's
pretty
close
to
me
image
and
so
that
I'm
just
gonna
focus
on
post
testing
performance
testing.
I
We
spoke
with.
He
would,
this
morning
and
isolated
all
the
gorgeous
mismatches
that
I
found
there
not
yet
in
there
not
yet
in
the
interrupt
test,
but
it
is
Darius
a
good
like
CSV,
with
with
all
the
extra
details
that
human
is
for
that,
and
we
have
a
blocker
listed
towards
the
end
that
we
need
to
talk
about
today.
We
have
time
and
the
guaipe
EFS
car
support
is
almost
there.
I
I
C
I
J
J
So
basically,
we
are
now
with
to
be
ours
for
review,
which
are
configuration
and
examples
both
for
just
Liberty
engines
are
FS
and
after
they
got
reviewed,
will
ship
the
final
release.
For
starters
and
after
that,
the
final
step
will
be
to
basically
sync
with
the
infra
team
to
deploy
fuel
started,
signalling
servers
so
that
people
can
make
experiments
and
demos
without
needing
to
run
their
own,
and
that's
it
for
now.
A
Nice,
thank
you.
You've
asked
just
for
anyone
listening
who's
curious,
the
start,
us
it's
a
it's
a
replacement
that
was
a
while
ago
and
it's
basically
a
better
WebSocket
star,
and
it
was
originally
I'm
not
sure
why
I
originally
came
about,
but
I
know
that
WebSockets,
though,
had
they
big
security,
vulnerability
that
didn't
meant
that
we
weren't
happy
with
taking
it
forward,
and
ideally,
we
kind
of
want
to
shut
down
these
that
star
star
servers
and
things
in
the
future
anyway.
A
A
All
right,
no
questions.
That
means
our
initiatives
will
quickly
go.
Will
quickly
go
for
you,
so
these
are
the
backlog
stuffs.
If
there's
anything
I'm
just
going
to
read
the
titles,
if
it's
anything
to
say
on
them,
just
shout
out,
so
we've
got
UNICEF
s
version
1.5,
that's
just
nice
to
be
on
and
go
add
performance
distributed,
signalling
migration
to
multi,
hash
keys
and
blog
store
introduced.
Wait
a
minute
introducing
rust
ipfs
initiative.
C
C
K
You
miss
how's,
it
going
I'll,
be
really
quick,
I
just
linked
to
the
the
grant
proposal
and
the
current
status,
which
is
just
the
github
projects
for
everything
and
I
guess:
I
have
a
small
request.
If
somebody
on
the
JSF
BFS
team
can
do
an
NPM
publish
of
the
interface
ipfs
core
tests
to
the
latest
version,
that's
in
the
mono
repo,
instead
of
in
the
singular
github
repo.
That
would
be
really
helpful,
but.
A
K
So
1.0
was
project
set
up
and
giving
the
conformance
testing,
Interop
and
interface
testing
running
and
now
we're
working
on
a
block
store
for
rust,
ipfs
and
we're
going
kind
of
a
endpoint
by
endpoint
to
get
the
Interop
and
conformance
testing
passing
so
we're
implementing
pub/sub,
swarm,
ID
inversion
now
and
then
we're
moving
on
to
object
or
and
dad
get
beg
put
and
a
couple
other
ones
in
the
next
phase.
After
that.
K
So
we're
really
aiming
for
specific
use
cases
this
time
around
and
then
we'll
be
putting
the
Help
Wanted
call
for
contributors
out
for
the
rest
of
the
endpoints
and
things
like
that.
So
it's
looking
pretty
good.
So
far,
fingers
crossed
and
I'll
be
the
main
sort
of
point
of
contact
for
the
rust
ipfs
team,
but
also
Jonas
from
the
team
might
be
joining.
These
calls
as
well.
A
C
C
L
A
One
one
last
thing:
I
just
have
to
show
you
this
look
at
the
suite
logo.
Oh
yeah,
that's
really!
Helen!
Thanks
to
Alan.
We
have
this
awesome
logo.
It's
not
often
that
I
get
to
show
off
two
logos
on
one
call,
but
this
this
day
has
arrived.
Alright
and
so
cool
Thank,
You
Marc,
look
forward
to
hearing
from
you
and
and
others
on
the
rust
implementation
in
the
future.
Any
quick
questions
for
mark.
C
Yeah,
this
is
just
for
the
the
storing
pins
in
the
data
store.
So
if
anyone's
interesting
coming
just
take
your
name
down
and
I
will
find
a
convenient
spot
for
us
about
it.
A
B
My
point
here
is
basically
like
was
already
basically
Rabin's
from
experimental.
It
already
has
pretty
terrible
performance
and
we
can
go
and
we're
planning
on
swappi
offer
something
else.
They
wouldn't
spend
too
much
time.
Trying
to
like
me,
go
in
like
disagreed
on
this
and
said
to
say:
okay,
whatever
like,
if
it's
really
fast,
do
it,
if
it,
if
it's
not
just
like
we're
going
to
replace,
is
something
else
anyways
so.
I
B
Don't
think
anyone
is
using
it
in
practice
and
if
they
are
like
changing
it
with
but
says
like
we
change
we're
gonna
change
it
anyways
like
if
we
change
it
then,
like
that's
gonna,
break
Park
settings
for
someone
somewhere
so
like
they
might
as
well
just
switch
to
the
new
fancy
thing
we
end
up
making
and
like
the
current
labs
and
libraries
are
using,
is
unattainable,
so
yeah
I
mean
I.
Think
it's
I
think
this
might
just
like
it's
not
worth
it
even
future
with
that.
A
Very
real
crashes,
yeah
personally
I'd,
probably
get
those
fixed
and
then
well
I,
probably
just
take
to
take
a
cursory
look
at
why
they
we
might
have
differences
and
if
there's
something
that
there's
broken
on
Jess,
that
we
need
to
fix-
and
it's
super
easy
then
I'd
get
it
done,
but
otherwise
yeah.
Maybe
maybe
it's
a
good
idea
not
to
invest
significant
amounts
of
time
on
this.
A
M
M
Sure
Anton
is
on
holiday,
it's
so
we're
kind
of
a
little
bit
short-staffed.
Hugo
is
kind
of
spinning
up.
We
will
have
a
status
meeting
thing
tomorrow.
We
have
revamped
the
entire
test
round
project
board
into
a
new
agile
methodology.
So
it's
very
easy
to
read.
You
can
tell
what's
being
worked
on
this
sprint.
What's
the
goals,
what
will
she'll
be
delivered
by
next
sprint,
and
you
know
how
we
can
forecast
that
work
so.