►
A
Hi,
everyone
welcome
to
the
ipfs
core
representations,
weekly
sync
for
monday,
the
26th
of
october
2020.
I
am
a
king
brain.
I
will
be
your
host
we're
going
to
play
the
game
of
what
we've
done,
what
we're
brought
by
what
we're
doing
next
we're
going
to
go
through
our
high
priority
initiatives,
our
slightly
lower
priority
initiatives
and
then
design
review
parking
lot.
Q,
a
all
that
we're
going
to
have
a
great
time,
it's
going
to
be
amazing,
probably
the
best
one
ever
without
further
ado.
A
A
So
that's
a
thing
that
people
should
be
aware
of,
and
also
like
lots
of
small
fixes
trying
to
like
bring
so
that's
kind
of
fallen
out
of
the
of
the
types
work
is
the
a
lot
of
the
apis
aren't
aligned
between
the
http
client
and
the
core
and
they're
supposed
to
be
so.
Some
of
those
apis
are
now
more
aligned
than
they
were
before,
which
hopefully
will
reduce
confusion.
They
may
trip
some
people
up.
Please
do
read
the
release,
notes
it's
going
to
be
very
important
anyway.
That's
it.
B
There
will
probably
be
an
ipget
release
this
week.
Yeah
go
ip5.8
still
some
things
that
need
to
get
done.
We
last
last
week.
Not
a
lot
happened
on
that
front,
between
people
being
people
being
out
of
town
and
and
just
other
things
coming
up,
but
we
are,
we
are
post
most
of
our
ci
hell
and
so
should
be,
should
be
getting
a
move
on.
D
A
C
B
Yeah,
we
also
relates-
I
don't
remember
if
I
post
it
in
here
or
not
last
last
week,
but
yeah
we
had
some
really
productive
discussions,
trying
to
align
the
what
we
want.
The
new
sort
of
local
pinning
api
to
look
like
with
the
remote
pinning
api
and
so
they'll
be
basically
the
same
and
lytle
linked
in
there.
Some
small
changes
to
the
remote
api.
Yes,
yes,
one
thing
that
came
out
of
that
was
the
defaults.
The
default
search
by
name
was
case.
B
B
There
will
be
some
examples
out
there
for
if
people
want
to
test
their
client
against
a
remote
service,
they
can
sort
of
see
what
is
that
we're
doing,
which
is
just
sort
of
spin
up
a
docker
container
with
andrew's
pinning
service
server
and
then
just
like
run
some
queries
again
run
some
http
queries
against
it
and
like
see
how
everything
goes,
do
we
actually
have
any
published
benchmarks
already
that
we
can
present
it
against
for
the
local
stuff
alex?
Are
there
scripts
that
you
used
when
you
collected
your
benchmarks.
A
A
B
E
C
A
E
F
Okay,
so
in
the
improve
discoverability
and
discovery
and
connectivity
in
js,
I
was
out
last
week,
so
there
was
not
that
much
progress,
but
in
the
outer
relay
front
I
have
only
one
pr
pending,
which
is
the
custom,
announce
filter
to
filter
out
the
to
provide
the
users.
The
ability
to
filter
out
addresses
that
they
don't
want
to
announce
it's
mostly,
then
I
just
need
to
add
tests,
so
it
should
be
done
probably
today
in
the
rendezvous
part,
I'm
mostly
blocked
now
on
the
discovery.
A
G
Not
much
update
on
there
it's
being
kind
of
behind
the
types
and
typescript
stuff,
so
hopefully
this
week,
but
pr's
are
there.
Next
one
is
also
mine,
but
alex
already
talked
about
it.
Typescript
stuff,
it's
landed
yeah
thanks,
alex
for
tag
teaming.
This
through
we'll
probably
be
adding
more
stuff
over
time,
because
it
doesn't
quite
cover
everything,
but
it
was
good
to
actually
learn
something
and
then
improve
things
in
the
tree.
B
B
B
C
F
Yeah,
the
the
three
pr's
for
multi
others
may
have
empty,
and
liquids
b
are
ready
for
review.
I
just
addressed
the
review
of
the
mifmt
earlier
today
and
I
just
need
to
test
the
michael's
pr
that
updates
the
examples
to
use
the
new
dns
other
multi-others
and
check
if
everything
is
now
working
as
expected.
So
I
hope
that
we
will
get
this
done
this
week.
D
F
The
rendezvous,
it's
a
it's,
the
pr
with
implementation
in
the
lipitp
rendezvous
module.
The
discovery
api
is
an
issue
where
there
is
a
proposal
where,
basically,
the
goal
is
to
use
the
rendezvous
and
the
content,
routing
and
eventually
other
modules
in
the
future.
For
this
discovery
of
services,
and
so
it's
basically
an
issue,
I
can
send
the
link
to
you.
Where
is
it
my
proposal?
And
now
we
should
do
it.
D
D
G
I
just
put
items
there,
so
we
do
have
a
bunch
of
places
in
js
ipfs,
where
we
say
there's
the
interface
for
say
repo
and
you
can
provide
implementation
but
pretty
much.
There's
a
js
ipfs,
repo
implementation
and
similar
stuff
for
bitswap,
and
there
are
some
interface
definitions
and
markdown
files
that
potentially
others
could
implement.
G
A
I
think,
like
a
good
place
to
start,
for
that
might
be
something
like
the
data
store,
because
we
have
headline
interface.
Data
storage
defines
a
suite
of
acceptance
tests
fundamentally
that
verifies
that
the
implementation
is
a
data
store
and
adding
types
to
that
would
be
like
a
logical
extension
because
then,
if
that's
a
like,
if
that
pans
out
and
that
works,
then
we
can
totally
replicate
that
pan.
G
A
All
right,
I
guess
that's
it!
That's
the
end
of
the
parking
lot.
Please
fill
in
your
weekly
updates,
it's
lovely
to
know
what
everyone's
been
doing.
This
has
been
the
core
foundations
weekly
sync
from
monday,
the
26th
of
october.
It's
been
amazing,
I
told
you
it's
gonna
be
really
good.
Thank
you
very
much,
see
you
all
next
week
bye.