►
From YouTube: 🖧 IPLD weekly Sync 🙌🏽 2020-06-01
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
Tags:
A
B
C
Our
engineering
I
guess
maybe
I'll
shout
out.
That's
something.
I
would
like
to
think
about
doing
in
the
next
week.
It
is
maybe
try
pairing
with
someone
to
write
some
draft
specifications
that
I
want
a
cold
brain
for
something
that
I've
had
on
kind
of
the
back
burner.
Is
this
need
that
we
probably
have
four?
So
what
I'm
going
to
call
it?
Placeholder
name
power
passing
like
when
we
have
paths-
and
we
want
to
start
talking
about-
isn't
this
past
segment
going
to
go
in
and
use
a
hampt
or
something
versus?
C
Is
it
not
strength,
be
able
to
toggle
modes?
Do
I
need
to
be
able
to
I,
don't
know
anything
else
that
you
can
imagine
being
touched
on
in
that
so
I've
got
some
like
super
skeletal
thoughts
about
that
that
I
want
to
explore,
but
they're,
not
even
in
a
publish
relaxed
Laurasia
report.
Yet
so
yeah
I,
don't
know
when
but
I'd
love
to
borrow
some
his
brain
and
tried
drafting
together
and
maybe
that'll
get
out
faster.
C
C
B
C
A
It's
not
yeah,
it's
it's
not
the
end
of
the
world,
but
it's
not
pleasant
because
block
time
doesn't
exist
in
the
place
where
you
need
it.
So
you
need
it's
one
of
these
pieces
of
context.
You
need
to
carry
with
you
as
you're
doing
this
navigation,
which
is
not
terrible.
It's
not
if,
if
you,
if
you
had
a
problem
taking
context
with
you,
while
you're
waiting
a
vagator,
this
is
a
case
where
that
and
and
where
you
and
then
you
couldn't
differentiate.
This
is
one
of
those
cases
where
it
wouldn't
matter
so
much
it
matters.
A
A
That's
where
it
matters?
And
that's
you
know,
for
this
kind
of
data.
That
use
case
is
not
really
that
that
alive.
So
it's
not
the
end
of
the
world.
It's
just
very
unfortunate
that
a
block
train
hype
has
to
come
into
the
equation
and,
as
Peter
was
saying
earlier
yesterday,
I
think
this
is
going
to
come
into
play
without
the
blockchain,
so
we're
height
is
used
as
a
flag
for
a
number
of
different
switches
of
protocols
and
formats
and
things,
and
they
just
because
you
just
don't
store
the
height
on
these
things.
A
The
height
is
external
context.
Time
is
a
proxy
for
height
and
in
bitcoins
case
it's
not
a
terrible
proxy,
because
there
are
some
validation
guaranteeing
is
about
time
being
within
a
certain
window.
I
was
trying
to
figure
out
exactly
what
that
algorithm
was,
and
it's
it's
pretty
tight,
but
anyway,
that's
unfortunate.
I
started
writing
a
big
spec
doc
for
this
to
describe
Bitcoin
from
a
IPL.
The
content
addressing
perspective
it'll
eventually
be
a
pull
request
against
the
specs
repo
I
cleaned
up.
All
the
codes
ready
to
push
in
most
cases,
Doc's
are
ready.
A
You
know
in
the
different
code
bases
I
just
need
to
give
Michael
a
this
itemized
list
of
things
to
be
done.
That
are
dependencies
for
this
work,
because
this
is.
This
is
also
in
the
middle
of
the
JavaScript
multi
formats
work
that
it's
not
quite
resolved
yet,
so
that's
not
super
critical
work.
It's
just
sort
of
Ling
lingering
at
the
moment
and
I'll
get
that
done.
Maybe
this
week,
that's
me,
I
think
I
have
I've
got
a
different
week
coming
up,
but
I've
still
got
it.
A
D
One
to
ask
last
to
add
one
thing
to
what
rod
said
for
those
who
didn't
see
my
message:
it's
not
only
that
the
block
height
is
something
historic,
it's
something
that
will
keep
reappearing
in
the
future,
because
core
distributed
soft
forking
relevant
by
consensus,
dis,
essentially
Don
the
way
to
agree
on
something
to
say
somewhere
in
the
future,
that
height
such-and-such.
If
the
rest
of
the
network
agrees,
who
will
start
doing
X
instead,
so
this
will
keep
coming
up
even
after
we're
done
with
the
with
the
work
right
now,.
B
I'll
also
say
that,
like
something
that
I
see
fairly
often
is
like
a
blockchain
transaction
used
as
like
a
cheap
timestamp
on
something
and
like
a
verifiable
timestamp
on
something.
So
this
is
probably
something
that's
gonna
come
up
again
and
again
and
that
we
should
just
think
like
there's
some
sort
of
higher
level
library
here.
That
would
do
a
nice
job
of
surfacing
this
that
we,
we
don't
really
have
at
that
codec
layer
right
now.
But
it's
just
me
keep
in
mind.
D
A
Which
would
be
unfortunate
for
Falcone,
because
I
think
they've
got
a
very
heavy
blockchain,
it's
very
dense
and
a
lot
of
data
being
generated
in
a
short
amount
of
time.
So
it
would
be
a
shame
to
need
all
of
that
to
be
able
to
discern
some
of
these
things,
but
it'll
be
interesting
to
see
their
response.