►
From YouTube: 🖧 IPLD weekly Sync 🙌🏽 2020-02-03
Description
A weekly meeting to sync up on all IPLD (https://ipld.io) related topics. It's open for everyone and recorded. https://github.com/ipld/team-mgmt
A
Okay,
welcome
everyone
to
this
week's
IPL.
D/Deaf
meeting
is
February
the
3rd
2020
and
as
every
week
we
go
through
the
stuff
that
we've
done
last
week
and
things
that
we
might
do
next
week
and
then
discuss
any
open
items
we
have-
or
we
also
take
the
time
to
welcome
new
people
to
this
call,
and
they
can
briefly
talk
about
like
who
they
are.
B
Hi
everybody
I'm
back
Hilton
again
this
time
on
IPL
B
and
making
selectors
a
lot
more
usable,
some
cool
stuff,
I,
don't
know
I
guess
for
those
that
don't
know
me,
I
have
a
lot
of
experience
in
note,
Jay
s
and
just
networks
and
content-addressable
stuff.
In
general,
one
of
my
fun
projects
was
porting
it
to
JavaScript.
C
Yes,
hello,
everybody,
my
name
is
Kevin
Raye
I'm,
a
member
of
the
project's
org.
We've
done
protocol
labs
and
I'm
just
here
to
be
a
fly
on
the
wall
and
just
kind
of
listen
as
I
get
up
to
speed
in
the
overall
company,
and
my
role
is
just
kind
of
like
unifying
projects,
plugging
in
where
I
can
help
and
I'm
a
project
manager
by
trade.
So
any
way
that
I
can
help
out
with
the
team,
take
how
many
action
items
and
that
kind
of
domain
is
why
I'm
here,
but
most
things
can
be
muted,
smiling.
A
A
Thanks
yeah,
so
next
we
go
over
the
stuff
that
we've
worked
on
again
paste
that
I
had
paid
to
the
chat
room
and
where
we
put
the
MIDI
notes
and
then
I
probably
start
with
myself.
So
last
week,
I've
spent
a
lot
of
time
on
rust
and
IP
LD
and
I
basically
make
sure
that
the
rust
iPod
ad
stuff
is
actually
becoming
a
thing,
and
the
big
news
is
that
the
repository
linked
also
in
the
notes,
the
rust
I
put
the
1.
A
There
was
really
an
existing
effort
by
some
community
member
and
now
my
plan
is
to
rebase
our
also
our
apology
of
rust
I
put
the
efforts
on
those
things,
because
well
it's
already
there
and
I
looked
over
it.
It
looks
pretty
good,
surely
needs
some
changes,
but
my
not
doing
them
directly.
There
and
I
also
got
already
at
my
Nexus
on
their
repository.
So
if
any
wants
to
be
edit
a
big
deal-
and
the
other
thing
is,
is
it's
more
of
news?
A
A
The
efforts
as
well
as
5
coin,
and
also
we
already
see,
pour
requests
from
the
implementers
of
the
rust
icon
stuff
on
the
multi
for
my
stuff
and
basically
I
spend
my
time
on
getting
all
those
people
are
not
one
umbrella
and
busy
making
sure
we
don't
have
doublet
efforts,
but
really
working
together
on
the
whole
thing.
That's
pretty
exciting,
so
yeah,
that's
pretty
much
what
I
did
last
week
next,
one
on
my
list
is
Eric
or
do
you
want
to
go?
Have
someone
else
go
first,
yeah.
E
E
E
I
am
pretty
much
fully
committed
to
all
of
these
things,
because
benchmark
said
it
was
good
I'm
working
on
reimplemented
the
package
called
IP
LD
free,
which
is
basically
what
users
the
library
used
when
they
don't
have
any
other
node
implementation
in
mind.
All
right
so
like
all
of
our
stuff,
has
selectors
and
well
right.
Now,
basically,
everything
until
code
run
comes
around
uses.
E
So
this
involves
a
surprisingly
large
number
of
generated
types.
This
week,
I
had
a
little
bit
of
a
sidequest.
Making.
Sure
I'm,
not
like
omitting
old,
would
be
large.
Binary
assembly
results
it's
fine,
but
it
is
something
to
keep
an
eye
on
so
I'm,
going
to
try
to
finish
up
the
new
IP
lovely
packages
or
the
new
I
feel
lead-free
implementation
packages
in
like
this
next
week
and
then
try
to
start
merging
things
into
the
core,
which
would
be
fun
at
that
point.
E
G
G
That
mines
been
pretty
simple
and
not
super
high
bandwidth,
so
just
some
spec
work
I'm
just
in
the
process
of
merging
the
car
spec,
which
represents
the
current
state
of
the
car
format,
so
that
we
can
then
start
working
on
a
version
two
which
I
think
Michaels
gonna
be
raising
a
bit
off
in
his
and
the
taxi
bore
one
is
still
I
think
the
dike
seaboard
spec
changes
are
ready
to
merge.
They
just
it
just
raises
a
lot
more
questions
than
it
solves,
because
it
introduces
suggested
constraints
that
none
of
the
current
implementations
have.
G
So
we'll
need
to
think
about
what
to
do
about
that.
But
I
think
I
think
we
should
merge
it
because
it
is.
It
is
the
status.
What
is
it?
It's
not
suggested
it's
prescriptive,
not
descriptive,
so
that
should
be
okay
and
while
I'm
working
on
the
other
thing,
I'm
working
on
is
Seaboard
new,
see
more
stuff
in
JavaScript
and
I'm
trying
to
take
this
into
account
as
well
as
performance
improvements
and
that's
an
interesting
journey.
So
how
do?
G
How
do
we
push
down
this
strictness
all
the
way
into
the
the
parser
and
encoder,
and
and
how
do
we
maintain
performance
while
doing
that?
It's
yeah
raises
lots
of
interesting
stuff,
but
I
think
the
dag
several
changes
that
the
pull
request
is
probably
ready
to
merge
as
well,
and
then
we
can
go
about
revisiting
the
implementations
and
say
well.
What
are
we
doing
about
this?
You
know:
should
we
start
rejecting
these
things,
and
can
we
even
start
rejecting
them
with
the
current
coding
we
have
anyway.
That's.
That's
me,
nothing
major
of
them.
A
H
Yeah,
sorry,
okay,
so
couple
quick
things
wish
that
we
did
resurface.
Some
more
constraints
on
car
files
in
particular
file
coin,
apparently
like
the
file
claim
kind
of
ecosystem
layer,
has
started
to
make
assumption
about
there
only
being
a
single
group
from
the
side
of
the
car
files.
So
for
this
big
data
project
we
working
on,
we
have
to
kind
of
back
up
now
rewrite
a
bunch
of
stuff
throw
away
a
lot
of
work
and
in
particular
we
it's
not
as
simple
as
just
saying.
H
Okay,
we'll
take
all
the
old
words
that
we're
adding
and
like
stick
them
in
one
see
we're
walk
together
because
some
of
the
way
the
allocated
was
written,
it
was
only
based
on
size
of
the
data
going
into
the
car
file
and
not
based
on
the
number
of
file
entries
in
the
car
file.
So
there
are
some
that
would
end
up
being
like
three
megabytes
of
Seaboard
a
block.
So
we
don't.
H
We
can't
do
that
so
anyway,
that's
all
getting
rewritten
this
week,
a
few
things
that
I
wanted
to
bring
up
one
is
we
started
to
service
more
requirements
for
a
future
version
of
the
car
spec,
so
in
particular
we
want
to
be
able
to
have
all
of
the
information
that
you
would
need
to
deterministically
reconstruct
a
car
file
accessible
in
its
header.
So
that's
all
of
the
routes,
the
ideas
and
the
selectors
that
were
to
create
those.
H
H
Probably
Eric
tends
to
be
ahead
of
me
so
then,
being
in
nicely,
more
blocks
is
probably
like
intended
that
you
can
and
and
Eric
always
has
like
this
Turtles
inside
Turtles,
all
the
way
down
mentality
about
all
this
stuff,
so
probably
thought
about
this
already
but
yeah.
We
should
spec
out
what
that
looks
like,
so
that
the
next
version
of
the
car
header
format
is
not
out
of
line
at
all
with
sliders,
and
this
is
in
fact
a
balance.
H
This
idea
that
I
have
called
a
web
repo,
which
is
basically
just
add,
an
interface
for
and
I
peeled,
the
storage
layer
that
is
designed
not
to
look
like
a
database,
but
to
look
more
like
a
get
repository,
so
you
store
blocks
in
it.
You
tag
films,
you
can
compare
those
tags,
you
can
sync
those
tags,
you
can
do
things
with
them,
so
that's
the
way
that
I've
been
thinking
about
that
and
want
to
poke
it.
H
We
want
to
start
poking
at
that
as
soon
as
I
can,
but
we'll
see,
I've
got
a
lot
of
what
I
put
into
play
right
now.
Also,
we
should
do
a
team
week.
This
year,
we've
been
sort
of
tentatively
targeting
q2
I,
don't
know
we
haven't
talked.
We
talked
a
lot
about
one
into
another
team
week
we
haven't
talked
about
what
we
want
to
cover
in
the
team
week,
though
we're
in
a
groove
we're
actually
pretty
good
at
working
remotely,
so
we
don't
have
like.
H
Like
last
time,
we
had
like
a
bunch
of
things
that
we
really
wanted
to
give
in
like
a
lined
about
and
now
I
feel
like.
We
don't
have
such
an
obvious
list,
so
maybe
we
should
start
thinking
about
maybe
in
the
meetings
once
a
week
and
just
kind
of
batting
around
ideas
or
things
that
we
would
want
to
cover
in
a
team
week
and
sync
up
about
and
really
get
on
the
same
page
well,
we're
all
together
in
the
same
room.
So
that's
that's
it
for
me.