►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 January 28, 2019
A
A
Cool
welcome,
if
you
are
here,
please
put
your
name
in
the
attendees
list
in
the
notes.
Can
we
have
a?
We
have
a
note-taker
who's
volunteered
himself
this
week
and
it
is
Jacob,
Thank,
You
Jacob,
then
what
happens
next?
Okay,
so
now
what
we
do
is
we
do
a
weekly
update,
where
we
all
tell
each
other
what
we
did
last
week,
what
we're
blocked
on
and
what
we're
planning
to
do
this
week,
I'm
going
to
start
from
the
top
and
the
first
person
on
the
list
today
is
Jacob.
B
Love
to
yes,
so
last
week
focused
mainly
on
finishing
up
the
daemon
work
and
that
took
a
break
from
that
because
I
was
being
my
head
on
the
wall
and
fixed
some
old
stuff
for
the
s3
data
store.
So
there's
an
example
lock
that
improves
some
of
that
and
then
fixed
in
a
multiple
call
back
issue
with
the
AWS
library,
because
it
is
inconsistent.
B
I'm
also
now
leave
maintainer
on
J's,
multi,
adder
I
think
I'm
watching
that.
But
if
not
feel
free
to
add
mention
me,
if
you
have
any
PR,
is
there
lots
reviewing?
Last
week
this
week
we
have
a
couple:
issues
have
come
up
around
transport,
listening,
improving
that
so
I've
gone
ahead
and
created
a
issue
in
a
slow
p2p,
I'm
gonna
work
on
finalizing
this
week
that
talks
about
that
whole
structure
of
adding
retry
logic
to
transports
and
better
error,
messaging
and
state
messaging
on
whether
we're
listening
or
we
need
to
retry
or
whatever.
B
So
if
you
are
interested
in
that,
please
check
out
that
issue
in
comment.
So
we
can
get
that
rolling
and
hopefully
get
that
up.
They
did
soon
then
yeah
finished
the
daemon
and
then
I
will
also
work
finalizing
the
rendezvous
timeline
for
getting
the
rendezvous
servers
rolled
out
the
next
couple
of
quarters.
Any
questions
for
me.
B
B
Websockets
when
they
try
to
listen
to
like
the
WebSocket,
our
servers
that,
if
we
have
the
connections
down
or
the
WebSocket
star,
is
down
when
your
node
goes
to
initially
connect
and
listen
on
via
those
servers
right,
we'll
just
end
up
like
failing
hard
and
crashing
the
node.
Until,
ultimately,
what
we
want
to
be
able
to
do
is:
do
you
like
a
back
off
free
trial
odjick
so
that,
whenever
you
know
just
offline
or
the
servers
go
offline
that
we
have
retry
built
in,
so
we're
not
crashing
those?
And
then
we
can
just
automatically
reconnect.
A
A
C
So
I
hope
to
get
this
finish
this
week
and
next
week
or
this
week
it
won't
work
on
the
graph
sync
selectors
stuff.
Finally,
and
then
there's
also
so
this
was
only
part
of
the
chase.
I
fell
deep
things,
so
the
other
part
is
the
IP,
so
called
IP
only
formats,
which
is
the
lower-level
minutes
about
protocol
buffers
in
sea,
bore
and
keep
and
so
on
and
those
formats.
These
needs
an
update,
but
once
this
other
changes
merged
I
would
then
call
out
for
help
and
for
moving
those
formats
also
over
to
a
new
API.
A
C
D
C
C
A
Sorry,
ok
and
you
have
a
question
for
ooh,
okay
moving
on
next
person
on
the
list
of
me.
Okay,
so
this
week,
I
did
moving
the
private
private
lipid
to
be
nodes.
The
thing
to
do
a
property
called
lib
p2p
and
it's
essentially
exposing
the
p2p
or
the
p2p
node
in
ipfs
other
than
by
every
other
method,
other
than
just
start
and
stop
which
of
the
current,
which
was
what
it
was
previously
I,
looked
at
and
solved
the
issue
with
IP
HTTP
client.
It
wasn't
being
bundled
in
meteor.
A
It
had
a
yeah,
it
had
a
thing
in
its
package
JSON
and
the
browser
section
to
say:
don't
bundle
my
PFS
HTTP
client.
So
what
meteor
was
doing
wisdom
was
just
removing
it
from
the
bundle
entirely,
so
that
was
no
good,
and
so
that
is
fixed
in
released.
That's
good
I
started
the
migration
to
see
id
v1
basic
value
2
by
default.
I
sent
a
PR
to
jess
the
ID.
A
A
So
this
is
kind
of
in
a
kind
of
relevant
to
the
async/await
endeavor
and
yeah.
Eventually,
we're
gonna
have
to
upgrade
anyway,
so
I
thought
it
would
be
fun
to
take
it.
Get
on
that
I
fixed.
An
issue
with
IPS
had
I
noticed
that
the
response
for
all
of
your
files
was
being
buffered
into
memory
before
it
was
being
sent
down
to
the
client.
So
that's
that
was
super
easy
to
fix,
so
I
just
did
it.
A
At
the
same
time,
I've
been
removed
nearly
800
lines
of
code
so
far,
which
is
kind
of
fun
and
yeah.
Today,
I
was
looking
at
Jess
that
I
professed
that
IO
is
it's
currently
using
the
old
files
API
in
that
is
present
in
0.33,
and
some
of
the
examples
are
broken.
So
I
sent
a
pull
request
to
that
and
actually
earlier
in
the
week
I
so
we've
got,
we
had
a
new
contributor
rad
and
he
has
sent
sent
a
PR,
which
adds
support
for
underscored.
Dns
link
has
a
subdomain
for
your
DNS
links.
A
So,
instead
of
just
having
a
text
record
on
your
domain,
you
can
have
a
txt
record
on
your
a
subdomain
called
underscore
DNS
link
to
achieve
the
same
sound
drink.
So
that
adds
add
support
for
that.
It's
just
a
basic
and
if
it
doesn't
exist
on
your
domain
on
the
domain,
you
asked
for
then
check.
That's
up
to
me
so
yeah,
that's
what
I
was
doing.
I'm,
not
locked
on
anything
I'm
gonna
finish
off
that
upgrade
to
have
18
minutes.
A
I've
got
like
maybe
four
endpoints
to
do
now,
so
that
PR
is
fun
times
big,
but
yeah.
You
know
sorry
and
yes,
I'm
going
to
continue
with
the
CEO
DB
one
base
a
two
and
on
Friday
I'll
do
some
violin
work,
which
would
be
fun
because
it's
file
going
Friday
nice
alliteration.
That's
me:
does
anyone
have
any
questions?
A
E
A
A
E
A
A
F
Echo
Islands
comments
and
also
say
that,
like
again,
the
PBS
demon
ingest
just
exists
for
sake
of
testing
and
like
providing
like
full
functionality.
More
than
actually
being
the
reason
why
the
religion
exists,
and
so
it
might
be
a
useful
thing
to
do
in
the
future.
But
I
saw
so
many
other
bottlenecks.
F
They've
I've
been
identified
on
the
core
that
should
be
tackled
first,
even
though,
if
the
happy
transition
to
some
other
framework
might
some
more
appealing
or
more
isolated,
and
so
yeah
I'll
make
sure
to
create
an
issue
and
I
could
describe
water
is
a
problem
and
a
proposal,
but
I
definitely
did
not
like
prioritize
at
all.
Just
because,
like
there
is
like
something
so
much
more
work
to
do
in
the
core
itself,.
G
Bruins
so
last
week,
I
worked
in
the
continuous
integration
in
Jessica
fest.
Now,
basically,
the
current
state
I
have
the
CIA
grin
right
now,
I've
been
trying
to
run
it
several
times.
It
is
not
really
stable.
Yet
it
feels
like
it
should
three
four
times
it
fails
at
least
one
but
I
think
it's
one.
The
good
way,
besides
that
I
I,
fixed
IP,
v6
connection
that
was
failing
using
WebSockets.
G
That
was
a
problem
that
reached
in
seei
with
the
HD
and
I'm,
not
working,
also
in
the
index,
adding
the
connection
manager
limits,
which
I
think
will
also
help
in
the
CI
not
bring
that
style
in
the
DHT.
But
I
would
like
Alan.
If
you
have
time
this
week
to
have
a
review
for
the
HTTP
are,
while
I
finished
connection
manager
stuff
to
see.
If
we
can
finish
it
this
way.
Other
things,
then
the
HT
I
created
a
web
server
based
protocol
module
because
now
we'll
be
collaborating
with
my
Kira
from
the
change
safe
systems.
G
We
had
a
meeting
last
week,
the
Liberty
B
team
and
I
will
be
helping
with
gossip
serve
in
Jesslyn
and
so
I
created
this
vice
protocol.
That
was
extracted
from
the
flood
step
in
order
to
allow
them
to
start
implementing
the
gossip
step.
With
the
same
we
base
as
we
are
using
in
the
flood.
So
right
now
and
finally,
I
also
created
the
the
first
benchmark
for
web
site,
which
is
a
simple
simple
test
for
benchmarking:
message
being
subscribed
and
published
Authority,
and
so
for
this
week,
I
will
I
want.
G
G
G
D
H
D
H
E
Last
week,
I
was
sick
at
the
end
of
the
week
and
the
rest
of
it's
fixed,
some
stuff
about
the
bootstraps
not
connecting
release
a
new
version
of
the
ISO
URL
package.
I
also
had
added
support,
for
course,
on
the
payloads
Mach
server,
so
we
don't
actually
disable
security
on
Firefox
and
Chrome
or
whatever,
when
running,
testing
a
browser
device.
Some
error
about
the
URLs
not
being
correctly
parse
or
outputted.
E
This
was
related
to
I
P
v6
IP
is
not
using
brackets
and
then
do
the
URL
package.
Throwing
an
error.
I
think
that
should
be
fixed
already
and
I
know
I'm,
not
actually
sure,
but
Fusco
will
probably
know
more
about
it
and
also
added
support
for
coverage
in
karma.
This
is
related
to
the
CI
prototypes
I'm,
still
blocked
on
the
M
flex
package.
E
If
Jacob
finds
some
time
this
week
to
help
me
out
with
this
I'm
trying
to
make
the
full
stream
to
stream
package
out
kind
of
output,
readable
stream
3,
but
there
is
so
much
overriding
and
over
rolling
overloading
in
there
that's
stuff
keeps
breaking
and
I
skip,
keep
breaking.
Even
the
tests
on
the
full
stream.
2
stream
are
really
strange
because
they
they
assume,
like
the
the
really
old
way
of
dreams
working
in
node.
E
That's
like
three
iterations
on
top
of
it.
So
it's
kind
of
weird
to
make
everything
work,
so
I'm
kind
of
kind
of
blocked
on
that
this
week,
I'll
be
having
a
day
off
tomorrow,
and
then
we
will
have
a
foursome
conference.
I'll,
try
to
fix
finish
the
pool
streams,
to
streams
and
also
an
issue
with
the
proper
locks.
Well,
I
think
it
was
Allen
that
reported
it
as
we
now
kind
of
check
the
staleness
of
the
log
file.
E
If
you,
if
you
like
close
your
laptop
or
make
it
sleep
for
a
while
and
then
you're
woken
it
open
up
again,
the
the
demon
will
probably
throw
with
narrow,
saying
that's.
It
couldn't
update
the
stealth
check
or
the
style
timer
and
then
just
breaks
the
the
demon
I'll
try
to
fix
that
this
week.
That's
it.
Anyone
has
any
questions.
I
Hello,
so
I've
been
working
on
on
trying
to
integrate
ipfs
with
NPM,
so
there's
a
client,
yes,
there's
a
package
called
good
day
and
which
talks
to
something
called
NPM
registry
client,
which
is
the
interface
for
the
ipfs
registry,
so
ever
interment
in
a
module
that
implements
the
same
API
is
that
there
talk
to
ipfs.
Instead,
it's
not
done
yet
because
you
know
it's
a
pretty
leaky
abstraction
for
those
HTTP
stuff.
All
over
the
place
is
just
super
tedious,
be
hopefully
all
together
done.
I
The
beginning
of
next
week,
I've
been
looking
at
all
of
Volkers
I
Tod
API
changes.
It's
really
cool
really
get
all
that
merged.
It
would
be
great
so
when
yeah,
when
the
main
jet
IPO,
the
change
goes
in
and
the
new
versions
releasing,
we
can
merge
all
the
units
of
Vesta
when
that's
done,
I'm
going
to
start
combining
them
all
to
be
async
and
it
erases
and
a
lot
of
kind
of
fun
stuff
and
that's
going
to
me.
I'm
gonna,
be
I,
thought
that
next
week
so
hope
to
see
some
of
you
there.
Any
questions.
J
A
K
K
So
Matteo
has
enough
information
on
that
with
the
with
the
clinic
output
is
on
the
issue,
so
I
think
he's
gonna
be
looking
at
that
more
this
week
too,
so
yeah
so
added
those
tests
added
the
TC
0
using
TCP
or
WebSocket
connection
on
those
tests.
So
the
web
Mitch
we've
just
been
adding
more
to
the
web,
make
that
make
sure
it's
the
test
matrix
was
filling
in
some
of
those
things
also
on
the
transport.
So
I
had
some
questions
about
the
transporter.
K
Ellen
didn't
answer
those
questions,
so
thank
you
so
much
a
lot
of
detail
and
I
so
and
just
looking
over
that
last
guy
I'm
gonna
need
to
make
some
changes
on
our
runner.
That
was
also
kind
of
brought
in
and
the
pub/sub
tests
were
shown
so
we're
going
so,
instead
of
passing
in
just
the
options
when
I'm
passing
all
the
options
that
are
possible
to
create
ipfs
Accutron,
so
you
can
customize
it
make
it
behave,
how
you
need
it
to
and
I'll
need
that
also
for
the
different
transports.
Yeah.
K
A
L
Like
just
a
very
quick,
quick
update,
really
relevant
to
JSF
EFS,
we
were
able
to
whitelist
IP
first
companion,
extension
ID
in
experimental
branch
in
brave,
and
that
way
we
have
the
stable
ID
that
across
multiple
machines
so
having
that
I
was
able
to
access
Chrome
sockets
api's
from
I
from
ipfs
companions
background
page.
It's
the
same
page
that
embedded
JS
activists
runs
right
now,
if
you
switch
them
by
the
Hulk
and
I
was
able
to
start
HTTP
server
from
that
context.
L
A
Cool
okay,
any
questions
for
light:
oh
okay,
cool,
in
which
case
we
are
on
time
completely
on
time.
Does
anyone
have
any
super
quick
things
to
say
before
we
leave
all
right,
in
which
case
big
hearts?
Yes,
we're
always
welcome,
always
and
rad
vehicle.
Thank
you
for
thank
you
for
joining
us
for
this
exciting
edition
of
what
we
did
last
week.
What
we
are
gonna
do
this
week
or
what,
until
next
time,.