►
A
Hi
everyone
welcome
to
the
ipvs
core
implementations
weekly
sync
for
monday,
the
14th
of
december.
I
am
aching
brain.
I
will
be
your
host
we're
going
to
go
through
all
the
usual
good
things:
the
high
priority
initiatives,
the
upcoming
ship
releases,
pinning
services
low
priority
initiative;
no
other
initiatives,
nothing's
low
priority,
we're
all
friends
here:
q,
a
parking
lot,
fun,
fun,
fun
all
right.
A
B
C
Yeah
and
in
the
lipid2p
front,
and
just
a
bit
of
30
last
week,
we
shipped
the
rc
0
and
then
rc1
with
some
fixes
that
we
got
while
trying
to
integrate
with
ibfs.
So
we
are
basically
now
finishing
this
integration
with
ipfs
before
shipping.
The
final
release,
it's
basically
almo.
Almost
then
the
type
check,
ci
jobs
are
finally
green
and
I
am
just
missing
a
test
in
http
client,
which
is
currently
failing,
and
there
is
also
an
issue
with
the
bundle
size
that
somehow
it
is
way
bigger
than
it
should
be.
C
I
I
was
looking
into
it
with
google
just
some
minutes
ago,
and
I
think
we
found
the
solution,
but
I
will
check
after
the
meeting
just
for
the
record.
Libitpio.30
will
ship,
with
the
authorly
support
type
devs
in
liberty,
core
customize
filter
in
the
custom,
dialer
address
sorter
and
also
discover
and
connect
to
closest
peers,
and
hopefully
this
week
it
will
ship.
B
D
E
That's
it
yeah,
just
like
to
finish
this
up
on
the
iphone's
web
ui
front.
Rafael
is
back
and
we'll
be
switching
to
the
http
client.
With
those
new
commands
added
by
iraqi,
we
will
probably
tag
a
new
web
ui
release
where
support
for
remote
pinning
is
not
enabled
yet,
but
all
the
unrelated
improvements
are
present
and
include
that
in
0.8.
E
And
if
we
are
lucky,
we
may
switch
that
pull
request
to
the
version
with
pinning
services.
If
not,
we
will
probably
not
include
it
in
a
version
of
web
ui.
That's
like
hard
coded
with
go
ipfs
and
include
it
in
the
next
version,
or
maybe
we'll
do
a
patch
version,
depending
how
long
it
takes
for
us
to
fix
all
the
bugs.
B
See
yeah,
I
suspect
whether
you
know
we
may
end
up
with
more
rc's.
Just
if
we're,
if
we
end
up
finishing
certain,
you
know
certain
things
ahead
of
other
ones
like
we
finish
mfs
stuff
before
web
ui
is
ready,
and
things
like
that,
yes,
next
up
is
local
pinning,
which
is
which
is
is
done,
is
in
or
at
least
storing
pins
in
the
data
store
and
go
ipfs
is
done,
it
is
in
0.8,
rc1
seems
to
be
working,
fine
download,
try
it
out
see
if
it
does
anything
weird
for
you.
B
B
This
issue
may
be,
you
know,
maybe
closed
for
now,
or
we
may
reopen
it
when
we
are
ready
to
implement
the
a
local
pinning
equivalent
to
the
remote
pinning
commands
in
go
ipfs
with
things
like
named
pins
and
stuff,
like
that
that
people
have
been
looking
for
still
figuring
out
where,
on
the
priority
list,
that's
going
to
come.
For
you
know
the
next
quarter.
A
G
C
Yeah,
so
I
started
the
nutrition
last
week
on
the
renewable.
Basically,
I
started
refactoring
the
client
api.
Now
we
are
we.
Basically,
the
client
will
receive
the
renewable
server
multi-others
from
liberty
config,
instead
of
what
I
was
doing
before,
which
basically
was
trying
the
renewable
protocol
in
each
node
that
would
connect
to
us
and
it
would
be
more
in
a
way
of
each
node
could
be
a
rendezvous
server,
but
we
don't
want
to
go
in
that
way.
A
Awesome
I'm
on
next
bi-directional
streaming
and
streaming
errors
in
the
browser.
So
if
there
are
no
more
objections,
I
think
I'm
gonna
ship
this
kind
of
experimental,
but
it's
gonna
be
really
good.
It's
been
on
the
cards
for
a
long
time
been
talking
about
it
for
ages
and
I'm
just
gonna
ship
it.
That's
that
I
mean
ship,
it
see
what
happens.
A
It's
gonna
hopefully
unlock
a
bit
of
the
dht
stuff
as
well,
because
a
lot
of
that
is
streaming
and
the
thing
that,
like
first
actually
put
me
onto
these
errors,
not
working,
was
trying
to
make
a
dht
query
with
a
timeout
and
just
being
like
oh
cool.
It
just
returns
the
number
of
like
results
it
got
in
that
time
period
and
they
did
it
on
the
command
line.
It
was
like.
Oh,
why
did
I
exit
with
a
non-zero
error
code?
A
D
A
A
A
C
H
Right
so
there's
a
couple
more
prs
on
the
data
source
for
data
store,
fs
data
store
level.
The
test
ground
sdkjs,
is
also
adding
types
and
I'm
currently
working
on
the
on
the
ipfs
repo.
Since
I
already
did
all
the
data
stores
that
repo
depends
on
so
yeah
check
the
the
issue
where
everything
is
tracked.
A
Great,
that's
it
for
the
other
initiatives,
so
moving
on
to
the
other
items,
so
design
review
proposals
if
you've
got
something
to
propose
a
design
review
for,
if
you'd
like
to
propose
something
that
needs
a
review
of
the
designer.
Stick
it
on
the
list,
just
tying
myself
in
nuts
anyway.
Yes,
stick
a
thing
in
that
section
of
the
notes:
boxes,
lots
of
pr's.
A
D
Yeah,
so
am
I
on
unit
yeah,
so
last
friday,
I
think
we
had.
I
don't
know
a
little
bit
of
dumpster
fire
with
something
changing
and
then
breaking
other
things,
and
I'm
not
sure
it
is
worse,
doing
those
kind
of
updates
to
cids
that
don't
really
change
anything
but
like
implementation,
wise,
but
then
can
cause
the
issues.
Given
that
I
think
we'll
migrate
to
multi
format,
cid,
and
I
think
it's
not
just
the
ids,
like
generally,
the
things
that
are
will
be
replaced
by
multiformats.
D
A
So
so
in
the
parking
lot,
there's
that
issue
that
you
opened
on
jsippfest.
So
I
did
reply
to
that
issue
this
afternoon.
Basically
saying
like
breakage
is
gonna
happen
when
we
change
things
without
releasing
them
with
the
right
version
numbers
all
right.
That's
just
that's
going
to
happen.
We
should
move
to
the
new
multi
formats
now
that
we're
kind
of
doing
our
q1
planning
for
next
year.
It's
a
good
opportunity
to
block
off
some
time
to
actually
do
that
work.
H
A
G
H
D
A
D
D
Maybe
I
can
talk
a
little
bit
about
the
next
item,
which
is
you
kind
of
mentioned
already,
which
is
so
I
wrote
a
kind
of
proposal
and
I
think
alex
you
said
you
responded
to.
I
have
not
seen
it
yet
in
terms
of
how
we
can
approach
to
adopting
new
cid,
and
specifically,
I
don't
think
we
can.
We
can
just
dump
the
existing
cid
and
say,
like
don't
use
it
anymore.
D
A
A
D
Sure
I
I'm
not
saying
it's
gonna
save
there,
but,
like
I
think
we
will,
as
we
will
be
migrating
two
new
cids,
we'll
have
to
think
how
do
we
duplicate
old
one
with
a
new
multi-formats
proposal?
There's
the
same
thing
like
doing
some
renaming,
even
if
we
just
bump
the
version.
I
don't
think
that's
enough.
D
I
think
we
need
a
transition
phase
where
we
can
guide
how
to
do
the
transition
and
allow
some
name,
like
specifically,
I
proposed
in
that
issue,
but
you
can
have
old
names
and
new
names
at
the
same
time
and
all
names
can
say:
hey
we're
deprecated,
so
they
show
up
in
editors.
They
dump
warnings.
They
tell
what
to
rename
to
and
tell
you
when
it
will
go
into
effect
and
be
removed.
D
D
So
if
that
sounds
good,
I
can
write
a.
I
don't
know
document
like
a
markdown
and
maybe
we
can
stick
it
into
somewhere
and
whenever
we
are
doing
breaking
change,
we
can
point
in
the
pr
like.
Can
you
follow
this
guide
or
something
along
those
lines?
So
we
have
the
contributing
guidelines.
Maybe
it
should
go
in
there
cool
like
how
about.
I
write
it
and
submit
it
for
the
review
and
you
can
all
provide
the
feedback.
That
sounds
good.
A
D
I
You
so
note,
like
some
of
those
deprecation
paths
are
going
to
need
to
be
different
depending
on
the
scale
of
the
breaking
change
like
we
may
do.
You
know
longer
period
of
time
for
deprecation
support,
but,
like
a
lot
of
that,
depending
on
the
feature
set,
that's
needed
to
change,
should
we
should
clarify
what
the
path
the
update
path
is
and
the
deprecation
items
in
whatever
issue?
That
is
so,
for
example,
if
we're
transitioning
to
multi-formats-
and
this
is.
I
Be
a
huge
breaking
change
to
the
code
api,
then
clarifying.
What
that
timeline
and
path
looks
like
for
support
in
this
specific
issue
and
then
making
sure
we're
doing
appropriate
blog
and
forum
announcements
that
that's
that's
coming
and
people
need
you
have
three
months
or
six
months
or
whatever
time
frame
to.
I
A
F
Andrews
go
yes,
there
is
one
more
update,
it's
more
of
an
internal
concern
than
an
external
one,
but
it's
sort
of
exciting
news.
At
least
for
me,
the
migrations
have
been
completely
refactored
and
I'm
finishing
up
the
last
prs
that
consolidate
all
the
code
between
the
ipfs
update
ip
go,
ipfs
the
automatic
updater
inside
of
that
and
what
was
fs
repo
migration.