►
From YouTube: libp2p weekly sync - December 16, 2019
Description
A
Alright,
hello,
everybody
welcome
to
the
last
lippy
d2p
sink
of
the
year.
Dropping
the
iPad
notes
once
again
in
the
chat.
Although
I
think
everybody's
here
we'll
have
a
short
meeting
today,
most
people
are
out
or
busy
working
on
test
ground
and
things
like
that.
So
we
can
go
ahead
and
kick
it
off
if
you
have
any
agenda
items
other
than
that
Libby
to
be
the
weekly
updates
feel
free
to
add
that
now
and
we
can
come
back
to
it,
this
will
get
started
first
up
is
me.
A
So
last
week
worked
on
the
async
refactor.
We
got
a
pre-release
of
that
out
for
Jas
worked
on
integrating
that
into
GSI
PFS
bit
swap
as
part
of
the
integration
phase
found
a
few
bugs
fixed
to
those
also
added
coalescing
dial
support
for
that,
and
we
push
out
another
pre-release
yesterday
this
week
we're
working
on
integrating,
in
a
JSI
p
of
s,
part
of
that
we're
working
on
building
out
a
migration
guide,
because
some
of
the
API
has
changed
and
then
working
with
Josh
go
to
flesh
out
the
rest
of
the
Docs
and
examples.
B
Everyone
so
last
week,
I
worked
mostly
in
Docs,
and
some
minor
fixes
for
the
new
material
is
so
wide.
Legally
I
got
the
API
config
Docs
merged,
as
well
as
the
registration,
organic
started
document,
which
Jake
have
already
provided
a
first
review.
Then
I
also
did
the
effector
for
ping,
which
was
pretty
simple
and
those
time
release
fixes
there.
It's
not
relevant
to
talk
about
then
I
continued
with
the
repair
of
some
examples.
Some
of
them
now
depend
on
the
ipfs,
so
basically
we
Jacob
I
will
switch
switch.
B
Basically,
she
wanted
to
create
an
example
on
view,
I
think
for
J's
lab
HP
and
basically
I
made
a
proposal
that
we
should
make
kind
of
a
catalog
where
the
community
could
could
post
their
examples
and
we
could
review
them
and
accept
them
and
everyone
else
could
check
them
without
like
going
in
so
many
Rufus,
but
basically
I
really
tried
on
that
proposal.
During
maybe
next
week,
not
this
week
because
checkable
way
out
and
I
will
maybe
leverage
that
time
to
have
other
type
of
work
that
doesn't
need
is
initial
review.
B
A
Awesome
and
I'm
posting
a
link
in
the
chat,
so
one
of
the
things
we
looked
at
for
that
rush
was
talking
about
so
ipfs
has
like
the
awesome,
ipfs
Taiyo,
which
is
like
that
catalog
it
links
out
to
bunches
up.
So
this
is
kind
of
what
we're
discussing
doing
for
all
of
the
pdb,
not
just
Jaso,
to
be
on
next
up.
Dean.
C
Yeah
I'm
blocked
I'm,
a
bunch
of
p2p
things.
Someone
need
someone
blocked
me
or
tell
me
that
they
don't
care.
One
of
them
is
multi
hashes
use
provider
records
using
multi
hashes
instead
of
CI
DS,
we
have
like
the
PR
is
there.
There
are
like
three
or
four
different
options
for
what
we
can
have
the
server.
What
types
of
provider
record
keys
we
can
allow
the
server
to
accept.
C
We
don't
necessarily
care
about
breaking
the
CID,
be
ones
so
just
multi
hashes,
it's
probably
fun,
but
you
know,
but
we
can
do
it
for
now.
If
it's
easy
enough,
the
other
is.
Allow
me
to
review
arches
PR
on
persisting
the
DHT
persisting,
the
DHT
routing
tables
and
loading
them.
It's
looking
pretty
good.
Now,
there's
a
couple
of
questions
that
were
sort
of
left
unanswered
from
when
he
originally
reviewed
the
PR
yeah
either.
Do
we
need
to
be
empowered
to
just
merge
it
or
instr?
You
know
we
need
to
review,
and
the
next
up.
C
D
I
mean
one
point
about
the
CATV
one,
the
bench
of
break-ins,
which
we
don't
care.
One
thing
we
care
about
this
one
day
before
pops
out
with
the
using
CA
BB
1,
so
this
is
going
to
create
a
rift
in
the
network
because
they
want
to
be
able
to
find
each
other.
The
Pierce
all
P
is
going
to
be
able
to
find
new
beers.
You
know
like,
in
vice
versa,.
D
C
D
B
D
Okay,
it
looks
great
Adam,
so
the
concerning
eclipse
attacks
and
no
like
general
civil
litigation,
so
there's
several
parameters
and
knowing
at
abuses
can
affect
your
score.
The
most
important
is
like
we
raise.
How
old
is
this?
You
can
be
so
we're
not
accessible
to
plot
attack.
Don't
show
ignore,
like
rate
by
which
they're
sending
us
good
messages.
Also,
what
are
the
attendances
well
message
and
all
that
so
I
need
the
filter,
pretty
rowdy
good.
A
C
A
D
C
C
B
D
B
C
D
C
D
C
D
So,
there's
you
don't
get
been
thinking
a
lot
about.
We
discussed
this
with
roll
quite
a
bit
for
you,
because
we
want
to
do
something
about
when
dropping
events
to
make
use
more
intelligent.
So
one
thing
we
want
to
do
is
we
want
to
make
the
queues
adapt
instead
of
giving
a
fixed
size
so
basically
yeah
the
second
component,
the
second
few
there
behind
the
telchines
always
laid
out
and
can
absorb
parts
and
transcend
collective
cages.
D
The
second
thing
we
want
to
do
is
we're
going
to
notify
the
upper
layers
not
to
communicate
on
their
phones
up
at
the
router
itself,
so
the
different
periods
persistently
is
dropping
messages
or
if
we
are
or
dropping
messages,
all
over
the
place
means
two
things
either
or
clearly
slower
or
we're
slow.
So
if
we're
pretty
slow,
we
should
remove
them
from
the
rest,
probably
if
we're
slow,
which
is
downscale
or
rest,
because
we
can't
keep
up
with
the
network
the
flow
of
messages.
D
C
D
That's
true,
but
during
the
problem
with
that
again,
is
that
the
reason
why
we're
dropping
two
messages,
because
I
said
it
might
be
a
slope
here
or
it
might
be,
we're
slow,
so
different
actions
need
to
be
taken
for
the
two
different
options,
and
this
is
something
the
router
to
do
so.
I
think,
whatever
higher
level
event,
your
tears,
hey,
I'm,
dropping
published
messages.
Perhaps
for
this
we
could
have
an
event,
but
on
the
other
hand,
if
you
published
message
leaves
leaves
home
now
then
go
through
a
couple
of
beers.
D
C
Yeah,
that's
there
I
mean
basically
the
the
awkward
thing.
Is
that,
because
we
rely
on
streams
in
the
underlying
like
because
the
pub/sub
is
stream
oriented
and
on
message
oriented,
it
means
we
can
guarantee
that.
As
long
as
this,
with
the
exception
of
dropping
messages
because
of
cue
overflow,
we
can
guarantee
that
a
message
is
sent
to
all
of
our
peers
and.
D
Probably
have
a
higher
level
event
and
hey:
maybe
it
doesn't
matter
they
would
dr.
IPC,
because
they're
busy
actually
made
it
to
enough
peers
to
propagate
into
the
mess
right,
and
also
it's
a
very
internal
thing
to
do,
and
very
in
dental
detail
how
the
pops
up
its
wired
internally,
while
its
operating
I,
don't
know
whether
we
should
actually
lick
these
to
the
applications.
Don't
think
recently.
You
know
it
must
value
attitude,
application
we're
doing
that.