►
From YouTube: libp2p weekly sync - January 20, 2020
Description
A
B
Yeah,
hello,
everyone
just
a
quick
item
to
mainly
get
roles
opinion
on
the
desk
v5
a
node
discovery
protocol
from
a
theorem,
so
I
had
call
with
Felix.
Last
week,
last
Friday
and
they're
looking
to
do
some
protocol
optimizations
for
what
they
have.
They
are
stuck
with
a
couple
of
problems
and
they
would
kind
of
welcome
any
help
with
us,
both
drafting
down
things
as
a
more
like
format,
but
also
help
with
any
performance
for
you,
Asia
and
optimizations
things
like
that.
So
my
question,
please.
B
C
C
I
just
speak
to
Phoenix
as
well,
and
he
told
me
that
he
then
I
was
in
CCD
on
the
meeting
and
asked
me
like
impromptu.
Can
you
join
now
because
the
meeting
is
taking
place
now?
I
was
like
no
sorry
but
but
yeah.
Definitely
we
should.
We
should
catch
up
on
that
and
find
like
whatever
ventures
for
collaboration
or
some
elements
of
their
initial
proposal,
like
the
ones
that
we
discussed
in
in
the
workshops
in
in
am
stem,
particularly
the
way
that
you
know
they
conduct
amasian
of
the
popularity
of
a
particular
topic.
C
They
do
acknowledge
that
there
are
some
some
flaws
behind
them
in
the
way
that
you
know
they
propose
to
conduct
these
calculations
based
on
like
base.
What
we
detected
on
site
I
was
like
hey
Dex.
This
doesn't
seem
to
work
and
he
was
like
yeah
awesome,
some
gaps
in
some
polls
here.
So
definitely
we
should.
We
should
wait
together
too,
because
these
are
like
we
have.
We
have
very
similar
powers,
as
they
you
know,
are
projecting
to
solve
with
this
solution.
So,
okay,.
B
A
C
A
All
right
yeah,
so
all
the
final
stretches
of
the
a
slip
DB
refactor
of
working
through
some
bugs
in
the
browser
example
we're
having
some
issues
connecting
to
the
ipfs
bootstrap
nodes
due
to
some
certificate
issues.
There
were
intermedius
shirts
missing
in
that
chain,
but
those
should
be
updated
now,
so
that's
resolved
that
issue
and
then
fix
some
bugs
with
the
WebRTC
star
not
working
properly.
A
So
that
should
be
good,
a
good
to
go
just
finishing
up
some
PRS
there
and
then
I'll
finalize
some
Docs
and
then
there's
one
outstanding
bug:
I
need
to
fix
with
the
pub/sub
Interop,
but
once
that's
done,
we
should
be
good
to
launch
and
the
ipfs
Interop
tests
are
looking
pretty
good
as
well,
so
hopefully
we'll
be
able
to
release
that
this
week
and
then
I
think
ipfs
will
do
a
release
candidate
once
we've
done
that
on
the
homestretch.
Any
questions
for
me
yep
all
right
next
up,
Yousef.
G
Yeah
I
guess
most
of
what
I
actually
did
last
week
was
refactoring
gear
records,
PR
that
mostly
in
the
the
core
PR
based
on
roles,
feedback
and
I.
Think
it's
really
improved.
Quite
a
bit
and
I
think
I'll
be
done.
Changing
the
core
stuff
by
end
of
today
or
tomorrow
and
I'm
gonna
update
that
Peters
to
forego
the
p2p
branches
and
then
send
up
a
little
signal
to
roll
visa
that
hey.
G
Maybe
we
could
maybe
like
all
three
of
these
things
are
most
ready
to
go,
but
now
that
there's
no
break
Guinea
API
I
change
with
urgency
around
merging
them
at
the
exact
same
time,
isn't
really
there
anymore.
So
we
could
potentially
merge
core
and
before
the
pierced
or
change
was
ready.
If
work
happy
about
the
API,
it
shouldn't
take
long
to
fix
up,
though,
and
then
the
rest
is
just
stuff
that
I
didn't
do
or
didn't
complete.
G
C
G
H
F
A
quick
question
for
you,
sir
I
just
want
to
ask
so
I
think
I
may
have
sent
out
an
update
to
a
video
update,
a
gale
investors
absolutely
and
I
think
I
said
pure
assign
P
records
were
done.
Do
you
know
roughly
like
give
it
a
like
timeline?
What
do
you
think
it'll
be
completely?
They
don't
know
we're
good
I.
Think
I.
G
Think
that
we
can
complete
the
the
main
work
of
it
this
week,
I
don't
know
how
long
it
will
take
to
integrate
into
all
of
it
like
into
a
new
release
of
whippy-tippy,
but
hopefully
not
very
long.
There's
not
like
component
of
breaking
stuff
that
we're
anything
to
to
merge.
This
change
set
is
weak.
No.
C
G
F
Oh
yeah,
so
I'm
in
all
of
my
time
in
this
week
next
week,
another
following
week
basically
is
going
into
this
performance
review
stuff
I'm
actually
going
to
stop
putting
this
into
the
career
pad,
because
this
call
is
really
supposed
to
be
about
the
loop
EDP
project
and
that's
a
thing
that
only
is
effects
protocol
the
labs
employees
so
but
I
just
just
to
give
you
a
sense
of
what
I'm
working
on
and
it's
just
collecting
feedback
from
a
lot
of
different
people
aggregating
it
and
please
don't
be
anxious
or
nervous
about
the
process.
F
I
Hey
guys
I
joined
on
Wednesday
nice
to
meet
all
of
you
and
yeah
look
forward
to
doing
some
great
work.
So
this
is
my
first
week
so
I've
been
working
on
onboarding
tasks
for
week,
one
I
finished,
all
of
them
went
to
the
onboarding
dock
and
I've
also
started
setting
up
one-on-ones
with
the
team
members.
Some
of
you
might
like
I've
already
sent
invites
to
some
of
you
in
addition
to
that,
Raul
asked
me
to
come
up
with
a
script
too.
I
So,
as
you
might
know,
we
are
working
on
introducing
better
project
management
for
the
p2p,
and
one
of
the
goals
is
that
we
want
to
have
all
these
shoes
in
the
gold
p2p
rapport,
which
will
act
like
the
umbrella
wrap
up.
So
we
can
easily
track
and
search
and
discuss
about
issues
so
I'm
working
on
a
script
to
transfer
I
finished
a
script
to
transfer
issues
from
all
the
lipid
lip
p2p
repose
to
the
gold,
p2p
rebel
and
label
them.
Accordingly,
Raul
is
going
to
take
a
look
at
the
PR
when
he
gets
time.
I
C
So
yeah
I
worked
a
little
bit
of
setting
up
the
labels
declaratively
we
using
github
that
keeps
everything
in
saying
where
the
colors,
the
descriptions
and
so
on,
and
it
kinda
it's
pretty
cool
because
it's
self-contained.
So
if
you
want
to
go
this
house
with
my
JSF
each
of
the
years,
where
else
we
can
just
take
this
configuration
and
just
put
it
in
and
that's
the
end
of
it
and
only
labels
will
immediately
get
it
right.
C
There
is
a
test
ground
meeting
tomorrow
and
we
are
merging
the
test
ground
team
or
the
content
routing
team
for
now,
and
this
meeting
is
going
to
host
both
both
both
both
teens
and
Steph
and
I
would
probably
would
probably
walk
through
the
content
routing
plan
in
this
meeting,
because
we
hope
to
have
it
finalized
by
then.
So,
if
you
want
to
join
you're
welcome,
most
of
you
I
think
I
joining
anyway.
So
yeah,
that's
that's
great
and
I.
C
C
Be
able
to
stitch
a
test,
a
test
plan,
a
test
case,
a
test
run
of
like
say,
1,000
nodes,
where
different
proportions
of
nodes
are
running
against
different
upstream
dependencies,
so
create
a
essentially
in
network
with
an
ensemble
of
1000
notes
where
300
nodes
are
writing.
The
new
version
of
the
DHT
200
nodes
are
running
the
old
version.
The
another
set
of
nodes
is
running
a
may,
be
a
candidate
change
set
and
for
us
to
allow
us
to
like
actually
understand
and
quantify
what's
going
so
this
is.
C
This
is
gonna,
be
a
key
feature
and
I'm
gonna
be
prototyping
that
so
so
that's
mostly
some
of
the
things
that
I'm
a
pipeline
for
for
this
week.
Yeah
and
if
you
need
me
to
look
at
something
I
know
that
visa
has
the
peer
exchange
PR,
which
is
now
waiting
on
some
of
the
changes
that
you
have
made
recently.
You
surface
is
actually
going
to
be
updating
your
branch
visa
two,
because
we
did
introduce
some
changes
to
like
names
and
methods.
J
So
give
it
a
rough
draft
for
first
recording
thanks
for
design.
So
this
is
the
function
that
we
want
to
introduce
in
gossip
shop
in
order
to
score
peers
and
mitigates,
give
you
an
overview.
I
have
come
up
with
five
initial
parameters:
one
is
the
application,
specific
parameter
and
the
other
sorry
six
parameters,
one
is
the
location,
specific
parameter
and
the
other
five
are
internal
to
observe.
So
in
him,
wait
for
them.
So
the
parameters
I
want
to
use
this
one's
the
lifetime
parameter,
which
is
going
to
be
the
total
time
connected
to
the
node.
J
So
this
is
the
lifetime
of
an
outer
same
buyer
over
here.
It's
going
to
give
it
tiny
weight.
So
it's
going
to
be
measured
in
days
when
I,
give
it
any
weight
and
like
every
calf
of
what
so,
basically
gives
a
small
boost
to
all
the
nodes
model
absence
any
other
information.
So
the
second
parameter
is
a
number
of
good
messages
delivered
by
the
note
in
the
last
night.
So
this
is
the
message
that
the
know
delivered
first,
so
this
is,
you
know
like
we
first
got
dispensed
by
this
node.
J
It
has
a
larger
weight
rather
medium.
Then
we
have
the
number
of
good
duplicate
weights
where
the
node
is
the
last
day
so
which
is
a
small
weight.
Then
we
have
two
negative
parameters.
One
is
the
number
of
invalid
messages
with
a
big
weight
and
the
other
one
is
the
absence
of
messages
in
the
topic
in
the
last
day.
So,
basically,
if
a
node
hasn't
delivered
well,
it
couldn't
be
less.
C
J
J
D
A
B
I,
don't
have
anything
to
update,
basically
have
been
working
on
the
ipfs
things
this
week.
Trying
to
finalize
the
America
et
paper,
which
is
used
to
be
submitted,
morrow
have
started
looking
into
the
outcomes
of
the
work,
show
mean
Amsterdam
and
I
will
be
compiling
together.
First
drafts
of
the
work
packages
and
work
items
in
some
formal
leap
of
Lists,
with
criteria
that
I
have
in
mind,
and
hopefully,
I
will
be
able
to
send
the
first
draft
of
that
out
to
Raul
and
Molly
or
the
wider
group
by
the
Bible
yeah.
Ideally
before
Friday.
B
And
related
to
that,
to
whoever
was
in
the
workshop
basically
and
row
in
particular:
do
you
have
something
in
mind
or
a
structure
in
mind
that
or
something
in
mind
that
you
would
like
to
see
as
outcome
of
this,
so
that
I
mean
I've
got
a
plan
of
what
I
want
to
do?
But
if
I
get
input
from
others
that
it
would
be
great
if
we
could
have
that
or
anything.
That
would
help
me
to
include
each
as
I
go
as
I
go
yeah,
so
I
would.
C
You
know
compliance
so
like
this
dynamic,
switching
between
toilet
server.
If
a
client
is
not
convicted,
if
it
is
d,
if
it
HD
no,
that
is
because
it
turns
out
to
be
implying.
How
do
you
make
sure
that
it
still
remains
discoverable
the
routing
table
conversation
like
some
of
these
things.
We
have
a
pretty
clear
idea
on
so
I.
Don't
think.
That's
like
much
is
much
useful
for
you
to
create
a
void
package
around
those
it's
more
about
like
what
do
we
want
to
do.
C
Ngm
has
already
covered
the
first
three
months
of
work.
It
would
be
an
ideal
for
you
to
be
able
to
structure
in
work
packages
the
items
that
were
more
related
to
rethinking.
You
know
certain
ways
versus
fixing
what's
broken,
what
we
know
is
broke
yeah,
yeah,
okay,
yeah
things
like
coral
multi-layer.
Dht
is
like
all
these:
they
provide
a
records,
you
know
the
fashion
while
providing
records
and
like
these
things
those
would
be
ideal.
C
A
C
Where
we
are
right
now,
the
labels,
so
we
had
this
definition
of
labels
that
we
already
merged
in
and
the
ability
to
people
and
I've
taken
those
labels.
I
have
created
them
and
I'll
show
you
how.
But
this
is
what
it's
looking
like
most
labels.
Most
categories
actually
have
a
fixed
color.
So,
for
example,
the
area
coded
it
blue
components
has
got
a
bit
yellow
for
easy
identification
of
which
categories
are
actually
a
given
you,
a
given
issue
is
labeled
with
in
which
are
knocking.
C
Others
are
hints
which
are
bright,
blue
and
we've
got
impact,
which
is
kind
of
like
a
whitish
color,
and
all
these
things
right
so
I've
tried
to
make
sure
that
visually
they
are
different
from
from
one
another,
so
that
it's
very
easy
to
spot.
What's
been
added
to
an
issue
and
what
flat
now
some
labels
do?
Have
a
color
legend
like,
for
example,
priorities?
C
It's
you
know
very
usual
to
like
label
priorities
in
red
and
and
green
depending
on
the
severity
of
the
priority,
so
I've
gone
ahead
and
done
that
and
then
for
those
for
those
dimensions
or
categories
that
are
actually
a
they're.
Actually,
a
spectrum
like,
for
example,
an
effort
of
a
private
greedy,
so
we've
got
effort
you
can
see
this
is
Nona.
This
is
not
ordered
by
my
quantity.
C
So
that's
why
it
doesn't
like
it
doesn't
form
a
gradient,
but
that's
just
the
way
that
get
home
borders
labels
but
alphabetically,
but
yeah
you
see
here
and
then
the
same
for
difficulty
and
the
way
that
this
is
a
red.
No
of
my
own
creation.
This
is
my
own.
It's
a
red
one
that
I
created
to
to
like
do
buy
it
my
plane
here
and
I.
C
Think
this
is
looking
pretty
good
so
far,
and
the
way
that
this
is
set
up
is
super
simple:
it's
women,
github
dog,
github
folder,
we've
gone
a
workflow
which
uses
an
action
that
is
publicly
available
or
labeled
sinker
and
on
every
commit
to
master.
It
just
goes
ahead
and
declaratively
applies
these
tables
and
the
labels
on
to
fine
here.
It's
a
Yammer
file,
for
example,
take
content
routing
as
an
area
which
is
very
impressed
these
days.
So
it's
a
Content
routing
as
an
area.
C
You
provide
the
color
and
you
provide
the
description
and
every
time
that
this
one
changes,
the
action
goes
to
github
and
it
just
updates
enables
there.
So
it's
very
easy
to
like
take
this
there's
this
particular
file
and
cherry-picked
it
trying
to
get
into
any
any
other
purple
out
there.
If
you
want
to
vote
out
exactly
the
effect
that
this
has
on
a
tune.
Example
is
that
you
have
the
same
labels
applied
everywhere,
so
you
can
now
start
thinking
about.
C
For
example,
when
we've
got
the
noise
bank
and
we
want
to
implement
it
in
five
different
implementations,
we
can
very
easily
track
the
progress
across
five
different
rebels
each
of
of
a
language
if
they
all
are
using
the
same
so
so
yeah.
That's
that's
what
I
wanted
to
show
you
any
questions,
comments,
feedback.