►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 February 25, 2019
Description
A
Thank
you,
Jim
all
right
sheet
is
in
the
chat,
go
ahead
and
add
your
name
to
the
attendees
list
and
we
will
get
started.
Welcome
everybody
to
February
the
25th
dev
core
J
s,
all
our
weekly
sync
we're
gonna
go
over
what
we
did
last
week
or
blocked
on,
and
what
we've
got
going
on
this
week
and
I
will
get
started
since
I
am
first
I've
got
a
work
in
progress
for
the
pool
in
Plex
going
into
JSI.
A
Pfs
I
do
need
to
do
some
ipfs
interrupt
tests,
some
more
of
those
I
fixed
an
issue
last
week
where
I
was
having
issues
with
high
throughput.
So
like
file
exchanges,
there
was
some
memory
issues
there
fixed
that
and
then
looked
at
benchmarks
between
it
and
Lippi.
2:00
p.m.
Plex
and
pull
in
Plex
is
performing
better
now.
A
So
gonna
do
some
more
interrupt
testing
this
week
before
releasing
that
to
JSI
PFS
added
unix
protocol
support
for
a
J's
multi
adder
I
also
updated
the
protocol
table
there
because
it
was
a
bit
out
of
date,
so
that
should
be
in
a
better
spot.
That's
released
as
605
there's
a
small
update
for
the
Jas
loopy
to
be
config
to
make
it
less
restrictive.
It
was
a
bit
too
restrictive
on
transports
and
then
a
slew
of
updates
for
the
jlpt
b-daman
to
help
with
the
testbed
and
Lippi
to
be
interrupt
tests.
A
There's
currently
an
issue
with
highlight,
guess
that's
blocking
some
of
the
builds
so
we're
just
working
around
that.
In
the
meantime,
that's
from
that's
an
8-year
dependency
through
documentation
Jas
this
week
going
to
work
on
the
Paul,
M,
plex,
interrupt
testing
and
then
work
on
better
support
for
listen,
announced
and
no
announced
addresses
for
J
asleep
p2p.
Does
anybody
have
any
questions
for
me.
C
And
so
I
was
working
on
I
blow,
deflectors
him
and
I
kind
of
implemented
it.
What
is
a
draft
spec
if
for
anyone,
who's
interested
in
the
staff
can
clean
it
out
and
then
also
we
had
in
the
graph
sink?
We
had
discussions
about
the
wire
protocol
and
we
ended
up
with
a
protocol
that
was
proposed,
but
I
did
have
write
up.
C
How
I
would
do
things
with
lead,
p2p
and
just
also
like,
if
interested
in
those
kind
of
things
check
it
out
as
well,
and
then
I
worked
a
bit
on
the
J's
I
put
the
api's
Allen
gave
feedback,
and
now
it's
really
way
better
code.
So
he,
this
big
ask,
was
to
change
from
mixing
promises
and
call
thanks
to
justice
in
chrome,
missy,
fine
for
the
callback
stuff,
and
this
really
makes
the
code
way
cleaner
and
way
easier.
C
So
if
anyone
supporting
something
from
for
the
issue
away-
and
ever
I
really
proposed
it
instead
of
mixing
promises
and
colleagues
just
using
from
pc
fire
for
the
old
stuff,
this
basically
is
in
clean
and
I'm
not
blocked
and
mixed.
So
this
week
I
already
hope
that
it
finally
get
the
IPL,
dapi
think
merged,
and
yet
just
do
some
work
on
me,
selector
stuff.
D
B
Guys
so,
basically,
a
last
week
between
terrible
requests
for
the
test,
setup
and
identified
was
connects
and
it
was
merged,
and
I
also
start
the
DHT
terrible
test.
Basically,
we
have
the
way
obsessed
in
ipfs
for
gets
inputs,
where
I
will
this
time
make
sense
for
all
the
available
functions
that
we
have
like.
The
vine
providers
find
peer
among
others.
B
Then
I
also
moved
a
bunch
of
ripples
to
Travis
and
I,
also
added
the
word
West,
where
I
think
a
horse
for
a
pub
7hd
in
lipids
be
in
order
to
afterwards
verify
them
in
jessup,
FS
blocked
like
Jacob
I
liked.
The
problem
for
now
I
would
recommend
that
people
that
went
or
needs
to
do
endtime
install
that,
basically,
you
can
do
NPM
install
first
of
I,
like
yes
master
branch
and
from
there
you
you
are
able
to
at
least
for
now
work
and
install
your
dependencies,
and
so
for
this
week.
I
will.
B
Finally,
hopefully,
tomorrow
debug
the
superiors
at
John
sky
in
is
yes
ffs,
which
is
also
triggering
a
lot
of
locking
in
the
river.
Then
I
also
want
to
migrate.
The
last
repose
that
I
asked
to
the
travesty
I
didn't
finish
them,
because
some
of
them
are
with
really
old
dependencies
and
I
wanted
to
also
create
dependencies,
but,
as
some
of
them
are
Breton
changes,
I
have
to
also
fix
tests
and
other
another
stuff.
That's
why
I
didn't
finish
all
the.
B
E
B
F
F
Still
on
the
Travis
topic,
we
we
need
to
be
like
careful.
What
with
what
we,
how
much
time
we
spent
on
it,
because
some
news
got
out
that
the
company
that
bought
drivers
is
kind
of
as
a
reputation
of
not
kind
of
keeping
talent
in
the
company,
and
some
of
them
are
already.
We
like
fires
and
stuff
like
that,
so
the
probability
of
we
getting
a
good,
stable,
Windows
environments
on
travel
is
getting
lower
and
lower.
F
F
Also,
almost
an
just
training
for
the
PTP
release
created
a
new
module
to
convert,
pull
strings
to
strings
just
to
reduce
the
number
of
readable
streams
versions
on
the
bundle
sizes.
If
anyone
is
still
interested
in
that
stuff,
you
can
check
it
out
in
the
on
the
link.
I
put
there
I'm
blocked
on
the
particular
release
and
on
the
I
yjs
issue
and
for
the
rest
of
the
week.
F
I
want
to
finish
the
GSI
BFS
bundle
requests
finally
get
to
the
benchmark
integration
and
mo
th
and
multi-action
async
async
await
public
quests
that
we
probably
gonna
conversation
tomorrow,
see
if
we
start
to
merge
some
stuff
or
not
yeah
for
the
rest
of
it.
That
should
be
it.
Anyone
has
any
questions.
G
So,
just
very
briefly,
I've
been
looking
through
a
lot
of
the
sort
of
proposed
IPs
improvements
that
I've
come
up
over
time
and
I'd
like
to
actually
make
some
of
them
happen.
I'm
trying
to
categorize
like
the
relative
importance
of
the
improvements.
So
not
generic
things
like
I
want
faster,
please,
but
instead,
like
you
know,
let's
have
pub/sub
do
this
in
order
to
make
it
go
faster.
So
those
are
there
if
you
have
any
interest
like
please.
Please
comment
Thanks
and
if
you
have
any
questions
I'm
here
to
awesome
any
questions.
H
I
Just
just
started
a
quick
check
to
his
ipfs
library.
It's
a
library
used
in
various
projects
for
detecting
high
PFS
resources
and
a
simple
check
for
telling
keep
festering
or
buffer
is
some
of
the
other
was
requested
by
multiple
people,
so
I
just
added
that,
but
in
the
process,
I
also
fixed
a
small
problem
with
multi
other
format.
The
readme
said
that
it
supports
buffer,
but
it
actually
did
not
so
there's
like
an
open,
PR
I
created
to
to
fix
that
and
I
need
that
to
to
merge
the
multi
other
check.
I
Support
to
his
ipfs
I
think
this.
It
was
probably
already
mentioned:
I
had
a
like
a
connectivity
issue
and
joint
the
late
I'm,
also
sort
of
blocked
with
on
this
highlight
J's
thinking
yeah.
So
that's
a
J's
correlated
stuff
for
me.
My
plan,
if
anything
goes
well,
is
to
revisit
Chrome
socket
API
sin
brave
after,
like
to
recheck.
F
I
There
already
exists
polyfills
for
to
expose
net
and
HTTP
modules
from
node
using
chrome,
sockets
api's
as
a
back-end,
but
those
were
created
around
node
6,
so
I
expect
some
stuff
to
be
missing
and
the
goal
is
just
to
identify.
What's
missing,
we
probably
I
expect
we'll
probably
end
up
with
forking
existing
polyfills
or
creating
our
own,
but
it's
like
exploratory
work
to
tell
what's
like
what
what's
work
remains
to
be
done.
Okay,.
F
That
is
on
my
on
my
github,
and
actually
we
can
talk
about
this
later,
but
I
have
a
branch
that
is
already
a
dependency
of
HTTP
clients
DFS
to
be
client.
That
I
will
probably
just
like,
create
another
or
another
package
for
it,
so
we
can
iterate
on
the
stuff
you
need
in
that
specific
module
regarding
tonight
is
gonna,
be
way
harder
with
yeah
yeah
yeah.
Listen
thanks.
A
A
J
What's
up,
I'm
derek
ma'am
today,
I'm
just
kind
of
liking,
but
yeah
this
week
I've
been
working
on
doing
some
async
awaits
like
converting
some
libraries
from
coal
bags
to
async/await,
so
I'm,
working
on
JSI,
p,
NS
record
store
and
working
on
the
the
DHT
is
all.
D
Yeah
malala's
technical,
that
a
lot
of
people
on
this
call
from
the
IRC
in
this
court
I've
been
working
on
on
this
on
this
app
of
ours.
That,
essentially,
is
aiming
to
make
it
easier
for
journalists
to
to
write
and
not
be
censor
that
we're
doing
that
by
using
JSF
DFS.
We
want
you
to
write
your
stuff
put
your
article
swing
around
without
trying
to
figure
out
they
make
their
anything
work.
D
K
K
Filter
thing
on
top
of
lambda
so
basically
looks
at
github
archive
tarballs,
which
is
every
it's
all
the
metadata
for
everything
that
happened
globally
and
github,
and
so
we
we
run
through
all
of
that
in
parallel
and
basically
filter
and
pluck
the
data
out
that
we
need-
and
you
can
give
it
like-
essentially
a
list
of
thousands
of
repositories.
So
we
can
go
and
pull
all
the
dependencies
for
get
ipfs,
for
instance,
and
then
give
that
repository.
K
Listen
then
we
end
up
with
a
subset
of
all,
but
all
that
ever
happened
to
github
about
all
of
those
repositories,
so
that
works.
You
can
pull
a
month
of
data
in
about
five
or
seven
seconds.
Roughly,
you
eventually
you'll
be
able
to
pull
a
year
in
that
amount
of
time.
Once
I
get
the
AWS
thing.
My
lambda
limit
there's
there's
a
limit
of
a
thousand
concurrent
processes
right
now.
K
K
E
I'm,
sorry,
there
we
go
hey
everyone,
I
am
working
on
and
refactoring
a
promise
and
making
it
in
a
wait.
I
have
to
like
create
a
test
for
it,
and
some
Doc's
I
already
have
a
PR
for
it.
Once
again,
I
need
to
put
Doc's
hit
a
test
out,
and
then
people
can
look
at
it
again.
So
that's
what
I've
been
working
on.
A
G
Hi
Dean
yeah,
I
guess
I
had
a
question
given
that
if
any
of
the
the
IP
and
I
stuff
is
going
to
involve
modifications
to
how
you
know
hub
stub
or
gossiping
works,
what
the
status
is
of
I
know,
there's
like
a
group
working
on
gossip
sub
for
JSI,
PFS
now
or
Jess.
Let
p2p
now.
What's
the
process
of
that
or
migrating
that
into
core
of
getting
Jess.
B
Yeah
I
can
talk.
Basically,
my
cure
I
did
the
initial
implementations
without
to
test
it,
where
I
I
got
her
a
review
for
initial
feedback.
So
now
she
sheds
like
last
week
for
working
on
it
again.
I
will
try
to
look
this
week
to
shake
it,
but
I
think
the
plan
is
for
them.
They
want
to
have
the
gossiper
implementations
by
the
end
of
March,
and
this
will
include
interrupts
test
as
well
with
Golic
HP.
So
I
would
like
to
have
by
the
end
of
March
hopes
of
implementation
of
gossip
so
available
for
Jessa
business.
A
F
Yeah
I
agree
basically
I
really
liked
suggestion
you
made
about
like
doing
the
nightly
wheeled
or
ever
like
validates
that
we
don't
like
break
stuff
for
the
upstream
users
regarding,
like
start
to
shrink
wrapping
a
here.
I'm,
not
sure
that
would
be
like
I
go
to
a
good
spot
to
start
because,
basically
H
it
is
like
tooling,
it's
not
really
something
that
we
care
much
about
like
some
a
developer
using
it
and
braking
there's
their
app.
A
I
think
that
it
would
be
beneficial
to
use
to
do
shrink
wrap
on
Asia
is
that
we
just
had
like
all
of
our
J
s.
Developers
have
issues
running
like
JSI,
p,
FS
and
J
slipper
to
be
in
new
builds
because
we
have
some
tertiary
dependency
of
Asia.
That's
breaking
a
build,
so
adding
shrink
wrap
would
prevent
us
from
getting
in
the
situation
where
our
development
is
being
halted.
Yeah.