►
From YouTube: 🖧 IPLD weekly Sync 🙌🏽 2019-07-29
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
I'm
the
first
one
on
the
list,
so
I
start
with
the
stuff
that
I've
done
or
I
can
also
paste.
The
group
head
into
the
chat
room
where
we
put
in
the
notes.
Oh
and
I
forgot.
Do
we
have
a
note-taker
for
the
two
days?
Probably
ok,
thanks
yeah,
so
I
guess
there
won't
be
that
much
to
to
write
down,
but
I
will
see.
Ok,
so
I
start
with
my
stuff,
so
I've
mostly
done
work
on
the
JavaScript
side
of
things.
A
Codebase
I've
also
done
the
changes
there
and
I
haven't
pushed
PRC
yet,
but
they
are
on
the
machine
in
they
work
and
during
this
I
ran
into
issues
with
NPM
link
and
everyone
who's
familiar
with
NPM.
There
are
sometimes
problem
with
making
stuff
and
I
ran
into
one
of
those
issues,
and
I
will
write
a
post
about
it
because
it
was
quite
interesting
to
me
and
although
they
may
block
us
out
there,
but
I
think
this
is
kind
of
a
special
case.
A
So
I
put
a
blog
post,
it's
not
published
yet
and
but
will
be
soon
and
the
finalists
the
to
fix
this
issue.
One
solution
is
to
use
a
project
from
Google
called
connect,
apps,
and
the
short
version
is
what
it
does.
Is
it
instead
of
linking
it,
it
does
an
NPM
peg,
which
makes
terrible
of
the
of
the
dependency
and
then
installs
that
hard
wall,
so
in
the
end,
is
like
a
normal
and
pyramid
store
from
the
repository,
and
this
way
you
make
sure
that
all
the
dependency
deduplication
really
works.
A
The
way
it
would
normally
do
through
an
NPM
install
it's
pretty
great.
It
works
well
yeah
and
this
fixed
my
problem
with
failing
tests
on
the
one
side
of
things,
I
feel
I
put
a
bit
of
thought
into
how
we
actually
bridge
data
between
the
host
language,
which
clearly
most
most
of
the
time,
is
JavaScript
and
Rossum
itself,
and
because,
at
the
moment
you
can
only
pass
on
pointers.
A
I
guess
I
will
start
with
passing
on
Seabourn
with
which
seems
to
be
a
sensible
way
as
most
of
the
ipod
II
stuff
is
based
on
snip
or
anyway,
and
then
on
that
JavaScript
side
you
would
just
see
I
need
to
decode
it
again.
On
my
okay
hours,
there
is
one
item
saying
that
I
work
on
a
rust
sea
bore
em
tag
and
see
boring
current
decoder,
and
the
goal
is
truly
see
how
it
has
the
basic
data
moment.
A
I
thought
it
looked
like
in
rust,
I'm
sorry
we'll
work
on
this,
and
then
this
should
be
been
compiled
to
blossom
as
well,
and
then
you
should
be
able
to
even
use
the
Seabourn
current
decoder
that
was
immersion
in
JavaScript.
Although
I
found
out,
this
probably
doesn't
really
make
sense
and
it
won't
be
faster
because
you
have
this
burden
off
again.
Bridging
the
bridge,
bridging
between
the
bridging
between
the
was
and
the
javascript
is
and
passing
on.
A
Data
is
quite
difficult
because
you
need
to
create
a
javascript
object
out
of
it
and
that's
quite
expensive,
so
it
probably
won't
be
faster
than
what
we
currently
have.
But
it's
not
for
proof
of
concept
to
see
if
you
can
really
pass
on
the
full
equality
model
from
and
click
between,
JavaScript
or
wasn't
alright
yeah.
A
B
Need
to
sorry
my
links
in
my
document,
I
would
did
some
work
on
I.
Think
I
called
bit
sequence,
which
was
it's
a
repo
in
my
github
that
just
takes
a
laboratory
suit,
string
of
just
a
byte
array,
and
then
you
can
slice
out
an
arbitrary
set
of
bits
from
it
and
turn
that
into
an
integer.
It's
fun
have
been
indexing
at
different
widths
and
so
I
just
wrote
it
as
a
generic
tool.
Where
you
can
say
here's
a
binary.
B
He
is
a
bit
start
and
and
a
bit
length
and
I
want
to
snip
out
those
bits
and
give
me
an
integer
based
on
it
and
it
it
can
do
even
an
arbitrary
length
in
JavaScript
which
can
get
kind
of
dangerous
when
you
go
big,
but
we
only
need
really
up
to
about
16
byte
bits
anyway.
So
it's
it's,
it's
not
a
big
deal.
B
So
that's
working
and
the
whole
lot
of
tests
in
there
to
verify
that
it's
doing
the
right
thing
and
then
I
did
a
go
version
of
it
and
use
the
same
fixtures.
So
I
wrote
the
JavaScript
tests
and
output.
It
a
fixture
file
that
that
had
what
it
was
testing
and
then
I
imported
that
in
to
go
and
then
test
it.
So
I
was
getting
the
same
thing,
so
I
should
be
able
to
use
this
as
a
reference
point
for
the
hashmap
spec
to
say
this
is
how
you
do
indexing.
B
Npm
package
data
still
I'm
playing
with
this
in
an
ongoing
basis,
have
just
got
stuff
churning
away
in
the
background,
processing
and
building
data
structures
and
seeing
what
they
do
and
I
write
up.
Some
performance
notes
in
the
peel
slack
I
want
to
try
and
formalize
how
I'm
doing
that
or
they'll
semi
formalize
it
anyway.
So
I
can
come
up
with
some
useful
numbers
about
how
these
things
perform
and
figure
out
best
practice,
or
at
least
best
practice
for
this
data
set
anyway.