►
From YouTube: 🖧 IPLD Every-two-weeks Sync 🙌🏽 2021-11-08
Description
An every two weeks 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
Welcome
everyone
to
this
week's
ipld
sync
meeting
it's
the
8th
of
november
2021
and
as
every
two
weeks
we
talk
about
the
stuff
that
happened
in
the
ipelt
world
and
then
discuss
any
open
agenda
items
there
might
be
or
if
there
are
any
questions,
as
always,
you're
also
happy
to
join
a
call.
If
you
like
to
so
first
on
my
list
for
the
update
is
dania.
B
B
B
So
load
schema
seems
fine,
so
it
comes
in
three
forms,
the
basic
one
that
takes
a
reader
and
there's
a
bytes
one
and
there's
a
file
one,
and
I
think
those
are
like
the
most
common
things
people
will
want
and
if
anybody
has
thoughts
on
those
two
apis,
please
speak
over
the
next
few
days
because
I
believe
we
haven't
done
a
release
with
them
yet,
but
I
imagine
that
will
happen
soon.
B
So
I
would
rather
not
break
them
and
also
a
couple
of
small
bind
note
fixes
for
bugs
that
massey
and
adding
spotted
over
the
last
couple
weeks.
That's
pretty
much
it
and
reviews.
C
So
I
had
only
a
couple
of
minor
things:
I'm
currently
actually
working
on
another
iteration
of
the
intro
to
ipld
material.
So
we
did
a
deck
last
year
and
it's
been
iterated
a
couple
of
times.
I'm
doing
it
again
because
we're
running
a
boot
camp
thing
for
the
protocol
lab
stack.
So
that's
that's
interesting
again
to
address
that
and
to
look
at
how
to
I'm
trying
to
pull
in
more
of
the
concepts
of
content
addressing
into
the
ipld
stuff.
C
So
it
covers
all
of
those
basics
and
trying
to
do
that
in
a
way
that
it
is
not
confusing.
Like
doesn't
just
hit
you
with
confusion.
It's
it's
a
bit
tricky,
but
it's
it's
there.
So
it's
a
bit
of
fun
and
the
other
only
notable
thing
that
in
the
last
couple
weeks
was,
did
some
debugging
on
a
persistent,
bundling
failure
that
we
have
in
our
javascript
stack.
C
That
has
been
reported
by
multiple
people,
but
it's
been
really
hard
to
actually
pin
it
down
and
say
exactly
what
combination
of
things
require
that
you
require
to
get
the
error.
We
live
in
this
really
messy
world
right
now
with
bundling
and
loading
in
javascript,
where
we're
going
through
a
huge
change
in
the
in
the
ecosystem
and
it's
taking
multiple
years
to
get
through
this
change,
because
there's
so
many
custom,
loaders
and
bundlers
and
and
things
and
they're
all
trying
to
they're
all
trying
to
implement
a
standard.
C
That's
not
really
well
defined,
and
so
we
end
up
with
all
these
edge
cases,
and
so
this
one
is
an
edge
case
that
you
need
to
have
a
particular
combination
of
tooling
to
encounter
and
and
what's
more
it's
actually,
it
turns
out
to
be
a
bug
in
one
of
the
bits
of
tools
which
is
not
a
surprise,
and
it's
not
just
that.
C
You
need
a
particular
combination
of
tools,
but
you
need
your
packages
to
be
ordered
in
a
particular
way
to
encounter
the
problem
so
just
a
mess,
but
the
bug
has
been
fixed
upstream.
It's
been,
we've
identified
exactly
what
the
bug
is
thanks
to
alex
but
cities
who
did
the
bulk
of
the
debugging
on
that
and
we're
just
waiting
for
the
ecosystem
to
catch
up,
but
the
the
the
the
package
that
has
the
bug
is
not
doing
back
ports
so
there.
Basically,
you
have
to
use
the
tool.
C
That's
got
the
newer
version
of
it
bundle
which
is
yeah
anyway.
At
least
we
know
what
it
is
and
we
can
say
to
people
you
need
to
either
upgrade
or
put
pressure
on
the
tooling
people
to
get
the
new
version
of
the
thing
included
in
your
version,
so
mess
absolute
mess
and
yeah
browsers,
bundling
garbage.
Okay,
eric.
D
That
sounds
like
fun
that
you've
been
having.
I
don't
know
if
I
have
a
ton
of
cool
stuff
to
report.
I've
been
working
a
little
bit
on
a
documentation
scatter
around
here
and
there.
So
soon
you
might
see
some
pr's
appearing
for
more
adl
reference
material,
because
someone
was
asking
questions
about
that
and
I
wanted
to
get
it
written
down,
but
it's
not
quite
there.
Yet
there's
a
pr
just
opened
in
guaypld,
prime
finally
introducing
a
migration
guide.
D
That's
probably
like
really
long
overdue.
So
I'm
kind
of
excited
about
that.
Even
if
it's
a
bit
small,
it
lists
some
of
the
old
going
libraries
and
like
specific
names
of
apis,
that
you
might
be
querying
search
engines
for
how
the
heck
do
I
get
from
a
to
b
names,
those
and
names
what
the
new
stuff
is.
So
it's
not
exhaustive
and
it's
not
like
said
refactor
scale
instructions,
because
the
change
in
apis
is
often
somewhat
bigger
than
that,
but
at
least
gives
you
some
like
critical
pointers
of
old
and
new.
D
A
Cool,
I
don't
have
any
update
this
time,
but
probably
soon,
and
then
we
have
one
argentine
item
which
is
about
the
future
planning,
because
there
was
the
library
where
protocollabs
and
other
people
met
last
week
and
there
was
a
bit
of
planning
and
does
anyone
from
you
talk
about
this
perhaps
or
just
explain
what
it
is
about
and.
C
We'll
put
together
this
this
write-up
of
the
discussion
that
we
had
it's
linked
in
the
doc.
It's
a
it's
a
hack
pad
a
hack
md
for
anyone
to
look
at,
and
it's
just
a
bunch
of
ideas
about
things
that
we
could
consider
doing
in
the
next
six
months
in
the
prioritization
and
how
important
they
are
so
very
initial
discussions.
C
But
anyone
that
tuning
in
to
this
is
welcome
to
have
a
look
at
that
and
and
weigh
in
with
your
opinions
about
what
is
important
for
us
to
be
doing
and
focusing
on
in
the
next
six
months
or
so.
A
All
right,
thank
you.
Is
there
anything
else.