►
From YouTube: 🖧 IPLD Every-two-weeks Sync 🙌🏽 2022-02-28
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
the
ipld
sync
meeting:
it's
february,
the
28th
and
as
every
two
weeks
we
go
over
the
stuff
that
we've
worked
on
and
then
discuss
any
open
agenda
items
we
might
have
and
also
good
to
know
it.
So
if
you
join
the
meeting
so
first
we
have
the
livestream
meeting.
A
Then
if
you
have
anything
you
might
want
to
say
more
in
a
private
site
and
not
really
publicly
live
streamed,
then
we
do
this
afterwards
and
then
afterwards
we
have
another
private
meeting
for
the
apocalypse
people,
because
it's
also
the
one
time
of
the
week
where
that
he
can
meet
yeah.
A
A
Well
briefly,
I
still
work
on
service,
stuff
and
rust,
but
there's
nothing
to
really
talk
about.
Hopefully
in
two
weeks
so
then
I
will
go
on
with
the
list
of
people
still
typing
feel
free
to
just
say
it
and
then
type
it
later
on.
While
I'm
reading
okay,
I.
B
Can
I
can
quickly
go,
I
mean
yeah,
not
a
lot
to
me.
I've
mostly
been
out,
obviously
have
been
involved
in
like
getting
pl
moving
out
of
pl
internal
slack.
If
there
has
been
fallout.
You
know
I
in
over
the
last
six
days
of
that
I'll,
look
forward
to
seeing
it
and
engaging,
but
I
haven't
been
able
to
engage
yet,
but
if
there's
anything
there,
particularly
as
it's
been
affecting
ipld,
we'll
definitely
look
at
it
this
week.
B
So
that's
one
and
then
the
other
you
know
involved
with
getting
mauve
here
to
join
us
welcome.
I
was
great
to
have
you
here
and
thanks
for
your
patience
through
all
the
you
know,
contract
that's
working
through
that
that
system,
but
it's
great
that
we
that
we
finally
have
you
here
and
yeah
again
welcome
and
that's
the
only
things
I've
been
involved
in.
So
that's
me.
C
So
I
move
or
I
go
by
range,
remove
on
github,
my
pronouns:
are
they
them
and
I've
been
doing
like
peer-to-peer
consulting
for
a
while,
and
I've
been
kind
of
like
doing
the
odd
ipfs
dev
grant
or
like
consulting
for
other
projects
that
use
it,
and
so
I'm
going
to
be
working
on
the
ipld
team
for
a
while
kind
of
mostly
improving
documentation
and
resources,
and
maybe
some
community
work.
C
So
if
folks,
you
know
wanna
ping
me
about
stuff
feel
free
I'll,
probably
be
in
the
chat.
I'm
gonna
be
like
ramping
up,
because
I
also
started
some
other
protocol.
Labs
related
work
this
week,
so
you'll
probably
see
more
of
me
over
the
weeks
as
my
schedule,
stabilizes
yeah.
So
my
main
task
right
now
is
this
ipld
checklist
and
the
idea
is
to
make
it
easier
for
implementers
to
kind
of
know
whether
they
are
actually
conforming
to
ipld
or
whether
their
structure
is
going
to
be.
C
C
C
A
Thanks
yeah,
I'm
I'm
like
b
plus
trees
are
interesting,
like
I
haven't
thought
about
it,
but
yeah
it
could
be.
It
could
be
interesting
because
then
then
next
step
would
be
our
trees,
which
I'm
interested
in
so
we'll.
C
See
yeah,
if
I
could
ramble
one
more
second
about
it,
coming
from
other
peer-to-peer
ecosystems
search
indexes
are
like
a
really
big
deal
so,
for
instance,
in
bittorrents
a
lot
of
people
use
sqlite
databases
sent
over
torrents
so
that
they
can
have.
You
know
the
indexes
for
large
data
sets
and
query
data,
while
sparsely
loading
from
the
index
hypercore
protocol.
C
They
have
a
b
plus
tree,
and
I
think
some
other
people
do
too,
but
there's
just
like,
I
think,
a
lot
of
potential
for
having
really
complex
data
sets
that
can
be
sparsely
queried
without
having
to
generate
indexes
on
your
local
machines.
So
right
now,
if
you
have
a
large
ipld
data
set-
and
you
want
to
query
it-
you
either
need
to
just
query
the
whole
thing
or
you
need
to
index
it
locally,
which
is
not
as
ideal
so
yeah,
that's
kind
of
where
my
motivation
is
coming
from
just
to
make
it
more
powerful.
A
Cool,
I
quickly
have
to
add,
because
it
might
be
interesting.
So
before
I
joined
protocol
labs,
I
was
working
on
a
search
index,
so
am
I
certainly
also
interested
in
making?
So
when
I
joined
protocol
labs
in
the
ipld
team,
I
was
always
interested
in
somehow
making
it
indexable
and
then
searchable
and
so
on
so
yeah.
So
I
guess
at
one
point
we
should
have
a
chat,
I
guess
and
then
yeah
because
like
we,
I
also
saw
your
overlap
with
the
geospatial
world,
where
I
then,
before
the
search
index
came
from
so
yeah.
A
This
and
we've
also
briefly
talked
a
thing
in
berlin,
a
bit
the
data
so
yeah.
I
guess
we
should
talk
again,
cool
all
right,
so
who's
next
on
the
list.
What's
in
this
on
the
list.
D
Yeah,
thank
you,
nice
to
meet
you
mom.
I
think
I've
met
almost
everybody
else.
I
work
with
the
three
box
labs
team
that
is
building
the
ceramic
network
and
we
use
ipfs
and
ipld
heavily,
and
I've
been
chatting
on
and
off
with
with
eric
about
working
on
the
ipld
update
api,
and
I
have
finally
captured
some
notes
and
have
been
chatting
with
them
further,
so
I'm
gonna
keep
chugging
along
on
that.
D
The
last
couple
weeks
I've
been
super
busy,
funnily
enough,
trying
to
switch
from
jsipfs
to
go
ipfs,
so
I
haven't
made
as
much
progress
as
I
wanted,
but
I
have
a
good
start.
I
think,
and
we'll
continue
to
work
on
that.
B
Cool
thanks,
quick
question
motion
can
is:
is
it
totally
fine
is?
Would
it
be
inappropriate
to
link
your
hackmd
document
to
the
github
issue?
I
can
do
that.
Yeah.
D
A
All
right,
I
don't
see
any
other
updates
in
the
notes.
Does
anyone
have
any
updates
or
wants
to
share
something
or
just
have
questions,
or
I
don't
know?
A
All
right,
I
don't
see
anything,
then
it
was
a
pretty
quick
meeting
which
some
of
us
enjoy,
because
it's
late
for
some
people
so
yeah.
So
thanks
everyone
for
attending
and
talk
to
you
all
in
two
weeks,
so
for
those
who
have
something
private
to
share,
please
stay
on
and
then
yeah.
So
I
now
stop
the
live
streaming.
Goodbye.