►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 April 1, 2019
A
Okay,
welcome
everybody:
it's
April
of
1st
2019.
This
is
the
Jay
s
core
dev
team,
weekly,
sync
I'm,
your
host
Alan
sure,
if
you're
here,
click
on
the
crib
pad
link
and
add
your
name
to
the
attendees
list
so
that
we
know
who's
here
for
for
the
future,
people
who
look
at
these
notes,
I
guess
anyway,
attendees
we've
got
a
note-taker
Jacob
again.
Thank
you
very
much.
A
Let's
do
what
we
do
always
and
we
go
through
a
round
of
updates
where
we
all
tell
each
other
what
we
did
last
week
and
what
we're
gonna
do
this
week
and
what
we're
currently
blocked
on,
so
that
we
can
unblock
each
other
and
make
some
progress
cool.
So
I
will
start
at
the
top
of
the
list.
If
you
haven't
already
put
your
weekly
update
in
please
at
it
now
and
we'll
get
to
you
and
at
the
bottom,
then
you
might
have
more
time
to
add
it
cook.
So
first
up
is
Vasco.
B
B
C
B
Unique
socket
taps
to
multi
others
instead
and
I
needed
to
the
interface
so
this
week,
I
want
to
get
the
streams
interrupt
tests.
We
are
reviewed
judgment
as
he's
working
on.
Yes,
some
problems
with
that
I've
been
talking
with
him
and
maybe
I
will
have
to
help
them
as
well.
To
finish
it
then
I
need
to
continue
the
CHP
introspection
reporter
I'm,
still
working
on
and
hopefully
future
planning
for
shares
of
it.
That's
everything
from
me
any
questions
or
comments,
or
others.
A
B
Basically,
it
is
like
an
aggregated
state
of
fold
them
the
state
in
metrics
that
we
went
to
get
out
of
lipid
speed
to
expose
for
the
in
this
case,
for
the
nationalization.
But
we
are
also
working
with
the
desperate
people
and
we
are
like
converging
pull
the
data
that
we
need
for
all
those
cases
and
basically
that
module
is
possible
or
holding
that
data.
A
Okay,
cool:
if
there's
no
questions
and
let's
move
on,
it's
me
next,
so
whatever
done
okay,
yeah,
okay,
so
I
helped
debug
and
I
can
appear
for
there's
a
there
was
a
duplicate
variable.
There
was
a
duplicate
function,
declaration
actually
in
stream
to
call
stream.
It's
just
basically
the
same
function
defined
twice,
but
the
only
the
second
one
wins
I
think
so
so
I
just
removed
it.
But
that
was
problematic
because
it
meant
the
well.
What
was
happening
is
babel
released.
A
new
version.
B
A
Of
itself,
with
a
change
that
meant
that
if
you
had
duplicate
variable
declarations,
they
would
throw
and
not
build
your
thing,
which
meant
that
all
our
browser
builds
in
CI
were
they
were
breaking
just
because
this
had
been
updated
and
it
was
an
arranged
version,
update
and
so
yeah.
It's
tracked
that
down
and
fix
that.
So
that's
down
and
dusted
and,
secondly,
bundle
size.
They
pr's
got
merge
into
Jeff's
like
FS.
A
The
BTB
has
never
had
that
many
peers
to
dial
before
so
there's
been
a
kind
of
per
peer
dark.
You
implemented
in
the
b2b
switch
and
yeah.
So
I
was
reviewing
that
and
and
that
that's
largely
solved
the
problem
and
we've
got
a
new
problem,
which
means
we've
got
too
few
peers
now,
which
is
kind
of
we've
gone
too
far.
The
other
way,
so,
hopefully
that
will
be
resolved
very
soon
as
well
and
I
was,
at
the
Lisbon
hacking
plan,
events
doing
retrofitting
and
defining
okay
ours.
A
It
was
super
useful
to
me,
because
I
was
working
on
a
pull
request
to
switch
to
a
b2b
WebSockets
to
async.
It
arose
and
I
forked
called
WS,
which
is
a
kind
of
wrapper
around
the
module
WS,
but
for
pull
streams
and
made
it
async
iterable
a
bowl
and
yeah
just
thinking
about
like
what
a
duplex
is
into
in
these
terms,
yeah
just
ivory,
and
then
that
allowed
me
to
kind
of
add
sync
and
duplex
support
to
the
module.
A
The
ASIC
iterated,
the
pull-string
modules
that
we
can
convert
async
iterators
to
portions,
because
we've
now
defined
what
what
a
sink
is
in
terms
of
it
only
taken
to
iterator
and
what
duplex
is,
which
is
to
be
honest,
similar
to
what
pull-string
thinks
they
are.
Basically.
So
it's
all
good,
so
yeah,
like
I,
said
zero.
85
was
blocked
again
temporarily
and
but
Jacob
has
been
working
really
hard
to
get
another
fix
in.
A
Why
sure
it'll
read
it
in
a
bit,
but
but
yeah,
that's
cool.
So
my
next
ask
about
top
priority
right
now
is
to
finalize
okay
ours
for
the
next
quarter,
which
is
started
now.
I
need
to
review
that
fix
that
I
just
mentioned,
and
people
have
been
submitting
poor
requests
to
Jaso
BFS
and
the
HTTP
API,
client
and
I.
Haven't
had
a
chance
to
review
them
yet
so
I
need
to
get
on
with
that
and
then,
if
all
goes,
it
all
goes
to
plan
a
0:35
release.
A
A
D
Yeah
there's
not
really
an
outcome
yet,
but
just
like
ongoing
discussions
and
yeah
just
and
it's
like
it's
so
many.
So
if
you're
interested
just
go
on
the
iPad
e
repositories
and
then
you
will
probably
find
some
issues
in
discussions
there
and
I'm
not
blocked,
and
next
week,
I
vote
or
this
week,
I
will
work
on
the
IP
on
the
format's
part.
D
This
is
kind
of
part
of
the
pacing
iterators
endeavor,
because
yeah
it's
a
DVD
festival
basic
await
and
we
kind
of
like
stripped
it
down
a
bit
from
the
Digital
proposal
to
make
make
it
easy
easy
to
agree
on
and
move
forward
and
there's
already
a
proposal
on
for
the
next
API
refactoring
and
we'll
see
how
this
goes
and
then
I,
hopefully
the
as
the
IPL
dapi
have
got
merged.
Hopefully
this
new
API
will
then
in
union
service
and
an
activist
the
pro
requests
are
done.
E
D
A
G
As
Alan
mentioned,
I've
been
mostly
working
on
performance,
4G,
asleep
PDP
for
the
upcoming
RPF
s,
release
big
issue
that
we're
having
there
is
the
DHT
is
effective
and
we're
discovering
a
lot
of
peers.
We
were
hitting
issues
where
we'd
discover
like
30,000
peers,
with
the
node
running
for
like
30
seconds.
The
problem
with
that
is
JSI
PFS
will
try
to
dial
every
single
one
of
them
and
the
PTP
doesn't
like
that,
and
so
like
right
now
we
aren't,
we
weren't
doing
any
real
blocking
in
whippy-tippy.
G
There's
no
real
queue
management
for
that
like
it
would
just
try
to
spam
everything.
So,
naturally,
the
CPU
would
just
hit
a
hundred
percent,
and
things
would
crap
out.
So
we've
been
working
on
making
that
more
manageable
right
now
in
lippy
tepee,
everything
is
considered
a
dial,
even
if
you
just
want
to
like
negotiate
a
protocol
and
just
want
to
open
a
new
stream.
G
So
if
you
PRS
open
for
that
and
then
be
working
on
one
last
PR
for
those
cold
calls
and
then
hopefully
we
should
be
able
to
get
up
that
out
the
door
this
week
and
start
working
on
the
long-term
solution
for
those
also
be
looking
at
working
to
review
a
old
PR
from
machi
for
the
web
RTC
star
refactor
also
need
to
do
some
final
validation
on
pulling
prefixed
PR
that
fixes
empty
streams
and
large
sync
streams
that
can
cause
the
like
max
size
or
the
full
stack
overflow
issues,
yeah
and
I
think
that's.
It.
G
H
G
F
Know
that
actually
goes
implementation
of
the
DHT.
This
total
raw,
so
you
should,
like
you,
haven't,
read
the
Escamilla
and
thinking
up
whatever
she
should
read
them,
because,
like
one
of
the
reasons
we
had
some
of
these
just
with
dialing
is
that
we
were
basically
dialing
everyone
in
the
network,
which
also
made
contact
writing
work,
but
this
doesn't
scale
very
open.
You
never
grows
so
like
did
you
base
it
off
of
the
go
DHT
or
gave
papers.
B
G
I
There's
still
one
left
that
it's
a
little
bit
more
controversial
and
with
the
real
problem,
we
will
have
more
discussions
about
it
regarding
the
removing,
by
default,
the
IPL
D
formats,
only
in
the
browser
and
teaching
the
docs
out
to
add
them,
but
we
will
figure
that
out
later
also
I've
been
debugging.
The
vu
CLI
set
up
for
our
view,
community
and
protocol.
I
I
I
I
I
will
finish
the
first
one
and
then
try
to
figure
out
the
second
one,
but
this
one
is
more
critical,
also
well
debug,
the
stream
suppose
stream
double
declaration
issues
and
at
the
lovely
time
in
Lisbon,
with
all
you
guys
or
most
of
you
doing,
some
retro
and
some
planning
and
some
lunching
and
footing
and
stuff
like
that.
It
was
great
great
great
time
and
next
I'll
finish.
I
A
A
I
H
I
One
of
the
function
calls
that
it's
called
in
one
of
the
events,
basically
a
resume.
The
the
context
that
is
injected
in
that
function.
Call
it's
undefined.
You
know,
I
have
no
idea
why?
Because,
basically,
everything
is
like
next
week
next
week.
Next,
stick
is
really
out
to
debug,
where
the
that's
that
fireball
gets
undefined,
but
yeah
sometimes.
A
H
H
Is
we
do
that
every
week,
but
it
was
really
nice
to
really
nice
to
meet
everyone
and
then,
in
terms
of
actually
doing
work.
I
was
doing
some
DHT
fixes
last
week
and
I
was
doing
some
testing
and
trying
out
examples
for
the
release
working
on
the
awesome
endeavor.
That's
the
one
for
committing
callbacks
to
they
sink.
Oh
wait
and
next
I'm
gonna
do
the
same
thing
for
the
TCP
library
that
Alan's
been
working
on
for
the
WebSockets
too,
to
kind
of
streaming
API.
E
Hello,
so
there
was
a
PR
outstanding
on
handling
sub
shots
of
shots
to
get
created
in
one
haps
update
in
NFS
I
merge
that,
and
there
was
the
QT
planning
for
HIV
investment
for
package
managers
and
Lisbon.
You
know
everyone
who
was
at
that's
a
lot
of
fun
started
after
we're
talking
about
badger
as
a
datastore
from
go,
I
started
missing
right
with
them.
I
could
see
native
module
for
JavaScript
to
to
cool
down
to
budget
and
yeah.
E
It
looks
like
it
was
kind
of
possible
I
had
quite
happily
around
shipping
from
JavaScript
ago
and
back
again,
yeah.
So
look
at
that
a
bit
more
in
the
spare
time.
I
got
a
bunch
of
weird
errors:
I
don't
understand
that
I
did
a
lot
to
do
with
native
modules,
but
that's
just
my
lack
of
knowledge,
so
it's
gonna
be
fun
figuring
out
the
problem
areas
I
really
want
to
get
the
async/await
stuff
done
for
Emma,
fest
and
UNIX
advice.
E
E
Basically
a
pion
used
to
settle
as
well,
where
I
can
really
finish
that
off,
like
I
could
wrap
everything,
and
then
you
know
unwrap
it
later
on
when
the
API
becomes
available
by
rather
not
after
all,
the
kind
of
performance
stuff
that
we
did
around.
You
know
not
having
crazy
amounts
of
async
and
allocating
buffers
and
that
kind
of
stuff
it
seems
a
bit
iffy
like
a
backward
step
to
go
and
just
artificially
introduced
more
stuff.
That
could
be
bad
so
rather
not
do
that
at
all
possible.
E
There's
a
problem
with
reading
sharded
directories
by
the
Gateway
I
did
a
little
quick
half
to
fix
it,
like
I
suggested
fixing
in
the
upstream
librarians
I
work
everyone,
so
you
probably
fixing
the
ending
upstream
library,
which
is
great
because
removed
the
whole
bunch
of
code,
which
is
cool.
Some
people
have
been
opening
some
issues
again.
Some
peon
ipfs,
which
is
great
so
I,
need
to
do
a
barrier
against
that.
E
A
B
A
Would
be
really
nice
because
it
was
slightly
annoying
where
it
does
all
right
cool,
so
we've
got
no
minutes
left
for
across
team
updates,
but
we,
if
you
are
still
here
then
then
you
can
you're
welcome
to
leave,
but
if
lied,
vital
and
Terry
would
like
to
give
us
your
quick
cross
team
updates,
then
I
will
definitely
listen
to
you.
I
do
if
you
go
first.
Sorry,
ok,.
C
I
will
be
very
brief.
There's
a
new
release
of
our
browser
extension.
It's
a
perfect
day
for
pushing
release
to
the
stable
channel.
So
just
visual
refresh
context.
Actions
are
available
on
the
NS
linked
websites,
even
if
you
disable
the
redirect
to
local
gateway.
We
ship
new
web
UI,
which
has
very
cool
fixes
and
improvements
of
our
file
manager,
I
think
it's
some
details.
If
you
are
interested,
then
there's
like
our
website
to
redirect
opt
out,
and
there
is
also
like
a
global
with
direct
opt
out.
So
you
can.
C
C
J
K
So
I
was
really
happy
to
be
with
folks
in
Lisbon
last
week,
wherever
we
were
and
I
had
drafted
the
road
map
before
then,
but
was
able
to
make
a
couple
of
quick
adjustments
to
it.
Well,
we
were
there
so
I've
dropped
the
links
in
so
you
can
spend
some
time
on
your
own
looking
at
this,
but
proto
school,
which
is
a
community
for
learning
about
decentralized
web
concepts
in
which
the
bulk
of
the
content
right
now
is
about.
Ipfs
now
has
its
own
road
map
sort
of
guiding
principles.
K
If
I
were
gonna
direct
you
to
one
thing
here,
it
would
be
these
in
terms
of
how
we
want
to
structure
our
content
moving
forward.
What
are
the
things
that
are
gonna
make
this
stay
as
sort
of
a
cohesive
experience
that
makes
sense
as
it
grows
as
we
try
to
accept
contributions
from
all
over
and
I'm
looking
forward
to
working
with
some
of
you
on
content,
specifically
designed
for
ipfs
camp
that
happens
to
fit
into
the
proto
school
roadmap.
K
J
A
Wait:
they're,
real,
okay,
no,
no
questions
all
right,
cool,
Thank,
You
Terry!
All
right,
then
we're
three
minutes
over.
Thank
you
for
sticking
with
us.
If
you
did
and
that's
it
goodbye
thanks
for
coming,
it's
been
a
rad
time.
We'll
see
you
next
week
for
another
exciting
round
of
what
I
did
last
week.
What
I'm
gonna
do
this
week,
what
I'm
on
and
also
cross
team
updates,
which
is
fun
hi
everyone
thanks
bye,.