►
From YouTube: 🖧 IPLD weekly Sync 🙌🏽 2019-11-25
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
B
A
What
interview
ending
talked
about
any
open
discussions
that
we
might
have
so
I
stopped
myself?
So
I
actually
can't
recall
what
I
did
since
the
last
meetings.
This
was
a
while
ago,
but
the
important
thing
is
that
I'm
now
working
100%
on
FICO
until
the
test
at
launch.
But
while
doing
this,
they
saw
some
IP
related
stuff
that
I
will
work
on
and
the
background
kind
of
so
I
was
taught
him.
Those
meetings
and
also
he
had
do
code
reviews
and
so
on.
B
So
I've
got
more
done
as
you
guys
last
week.
I
don't
have
as
much
to
show
for
it,
but
I
will
do
in
the
next
style
too.
I
just
mainly
been
focusing
on
this
browser
testing
thing
and
made
really
good
headway.
I
have
a
tool
that
I'm
trubbish
that
just
makes
the
whole
process
of
he
I've
got.
I've
got
a
JavaScript
library.
I
want
to
know
that
it
works
in
the
browser.
That
process
makes
it
easier.
B
So
I'll,
try
and
publish
that
today
or
tomorrow
and
and
it's
it'll
be
something
to
eat
a
rate
on
as
well
to
bridge
and
explore
ESM
and
other
things.
But
it's
a
it's
a
it's
a
basic
focused
use
case
tool
that
isn't
dependency
heavy
yeah
anyway.
That's
that's
mainly
what
I've
been
doing.
I've
done
a
little
bit
of
sea
ball,
pausing
stuff,
but
it's
mainly
been
focused
on
browser
testing,
which
has
been
very
educational.
C
So
I
don't
have
time
to
a
report
from
engineering
stuff
this
week
because
it
was
a
lot
of
humans
things
in
the
last
week.
But
one
piece
of
good
news
is
I
got
to
roam
the
the
ideas
that
I'm
calling
the
rocker
pattern
of
design
from
memory
allocation
avoidance
in
the
builders
in
the
cogent
past
Hanna
and,
for
example,
among
a
couple
other
people,
but
we
didn't
find
any
obvious
showstoppers
and
running
over
that
design
for
a
while
and
I
think
that's
like
kind
of
the
best
feedback
that
I
can
possibly
get.
C
Is
that
there's
nothing
obviously
wrong
convinced
and
we
didn't
come
up
with
any
obvious
improvements.
I
did
that
had
fewer
drawbacks,
so
I
think
some
of
those
ideas
and
I
talked
about
the
last
time.
We
were
all
together,
probably
going
to
move
forward
into
implementation.
Now,
and
hopefully
we
continue
if
I
know
showstoppers
from
the
phone
and
talking
to
a
bunch,
yeah
I.
B
C
And
I
think
it
is
the
case
that
the
design
is
actually
going
to
manage
to
cling
to
the
exactly
current
note
builder
interface,
it's
just
that
many
of
the
implementations
will
have
these
kind
of
nasty
conditionals
on
them
like.
If
you
call
this
set
of
functions
in
this
order,
then
it's
going
to
say
know
is
sort
of
working.
B
C
We
just
yeah,
we
failed
to
find
any
better
idea
than
that,
and
it
turns
out
to
generally
be
the
case
that
you
call
the
limit
order
anyway.
So
really,
the
rules
I'm
just
gonna-
have
to
come
up
with
some
really
good
documentation
around
high
level
rules
that
interface
and
what
you
are
definitely
allowed
to
do
and
then
make
sure
that
those
rules
are
both.
C
Documents
at
end,
like
that
code
is
generally
written
to
those
rules
and
and
I
think
also
make
sure
that
neither
pathway
gets
loosey-goosey
about
the
minimum
rules
like
I
wanted,
for
example,
one
thing
that
could
be
done
is
when
we're
doing
this
from
memory
sharing
interface.
It
could
be
the
case
that
it
would
actually
make
things
visible.
Even
if
you
never
called
the
set
method,
because
you
had
gotten
it
derived
no
build
a
relationship
which
is
already
initializing
the
same
memory
but
I'm
just
going
to
add
enough.
C
It's
not
the
worst,
but
it's
a
bit
like
so
some
of
the
methods
that
are
currently
on
there
for
like
set
at
arbitrary
index
I'm
thinking.
It
might
actually
make
more
sense
to
just
drop
support
for
those,
because,
if
that's
going
to
end
up
being
conditional
and
twist
even
you
might
as
well
just
not
have
them.
D
D
C
D
B
C
D
C
Think
at
this
point
we've
got
the
documentation
on
schema,
stuff,
really
solid
and
the
authoring
guys
they're
super
good,
but
now
we're
actually
like
relatively
sparse
on
basic
data
model
stuff
and
making
sure
that
those
have
examples
and,
and
then
just
generally
the
entry
point
like
I,
don't
know
if
you
guys
saw
the
emails
coming
in
from
github,
but
some
people
in
the
wider
community
of
jumped
in
and
said
like
what
good?
What's
what
is
this
homepage
for
us
and
I?
Think
we
knew
that,
but
maybe
it's
time
to
do
something
about
it
at.
B
Some
point
we
need
to
take
ownership
of
the
the
website
and
yeah.
Do
something
sensible
with
it
yeah
but
yeah
I
did
I
did
think
that
the
next
task
to
tackle
would
be
what
is
I
feel
t.
What
are
we
trying
to
solve
talk
about
the
data
model
and
and
that
and
that
that
would
open
up
like
if
we
could
do
that?
B
Well
enough,
it
would
open
up
some
of
the
discussions
that
we
keep
on
having
about
the
data
model
in
its
restrictions
I,
you
know,
even
that
you
know
fix
UNIX,
fsv,
51.5
thing
and
the
int
maps
came
up
and
it's
like.
Oh
okay,
you
know
we're
trying
to
constrain
the
data
model
of
it,
but
what
do
I
link
to
well
it'd
be
good
to
have
some
something
explaining
at
least
more
of
the
philosophy
you
know
in
a
digestible
way.
D
D
A
Cool
things
and
I
forgot
I,
remember
that
last
week,
I
also
talked
with
Eric
about
how
things
work
in
go
IPL
D
and
that
basically
helped
me
because
already
for
the
replica
headed
here
that
probably
a
we
might
not
even
need
sir
day
or
yeah
would
work
without
it
or
basically
I
come
to
the
realization
that
so
there
would
be
just
assuming
more
of
another
layer
of
indirection.
So
it
isn't
too
bad
to
use
it.
D
A
quick
top
of
Stephen
about
that
and
we
kind
of
realized
it
like
it's,
actually
really
easy
for
all
the
stuff
to
support
third,
a
to
one
direction.
Only
right,
like
you
can
add
the
sir
date
rates
to
all
the
itlp
stuff,
so
it
works
like,
as
goodness
are
they
can
support.
Even
if
we
didn't
use
survey
as
like
the
core
thing.
A
D
A
But
this
might
also
be
clear
that
basically
people
could
use
any
format
that
is
implement
cycle
D
could
use
service
utilization
would
also
be
nice
in
this
rupiah
SS
please
fit
for
more
cool
and
that's
all
I
have
and
I
see.
We
have
someone
you
join
this
meeting
and
to
you
might
to
introduce
yourself
really
quickly.
A
B
C
So
I'm
gonna
take
a
couple
days
off
this
week,
lest
I
burn
out
after
that.
So
the
whether
or
not
this
design
with
Rackers
on
how
to
handle
this
shared
memory
stuff
will
work,
has
been
a
question
that
had
been
bugging
me
and
was
kind
of
a
blocker
for
like
quite
some
time
now,
I
I
think
the
answer
is
like
confidently.
Yes,
this
design
works
now
so
I'm
going
to
get
back
to
banging
out
in
the
next
week
and
I.
C
Don't
know
if
I
have
a
super
high
res
expectation
of
when
of
how
that's
going
to
go.
I've
ended
up
kind
of
deferring
that
whole
set
of
problems
and
questions
around
the
maybe
stuff
as
well,
because
that
turned
out
to
be
entangled
with
all
this.
So
that's
gonna
come
back
after
that,
but
a
lot
of
the
other
questions
about
native
typed
go
builder
patterns.
The
answer
has
also
turned
out
to
be
forced
by
this
memory.
Layout
stuff,
basically
trying
to
use
helper
strokes
is
non-viable
entirely.
C
C
D
C
C
For
like
the
next
person
to
start
depending
critically
on
the
go,
cogent,
yeah
I,
don't
think
there's
any
super.
Strict
deadlines
like
I
personally
want
it
to
be
done,
so
I
can
go,
do
something
more
fun!
That's
about
it!
That's
the
only
forcing
function,
I'm,
hoping
that
a
lot
of
gets
done
throughout
December.
There
will
probably
be
left
over
in
January
I.
Don't
know
how
much,
hopefully
not
much
more
than
that.
C
A
It
doesn't
look
like
it
then
I
closed
this
meeting
for
this
week
and
hope
to
see
you
all
next
week,
goodbye
everyone,
ciao.