►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 April 8, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
hello
and
welcome
to
the
jazz
core
dev
team
weekly
sync:
it
is
April
the
8th,
Fizz
2019
and
I'm
ill,
so
there
yeah
this
will
be
fun.
I'll
probably
burst
out
coughing
any
minute,
but-
and
if
you're
here
please
add
your
name
to
the
attendees
list
on
the
hackpad,
the
link
is
for
the
link
in
the
chat
for
everyone.
A
Cool
and
if
you
haven't
already,
then
please
add
your
weekly
update
in
the
relevant
section
and
what
happens
next
is
we
usually
do
the
round
of
our
weekly
updates,
where
we
tell
each
other
what
we
did
last
week,
what
we
upload
fun
and
what
we're
going
to
do
next,
so
Jacob
is
first,
but
he
is
not
him,
so
we
will
skip
over
him
temporarily
and
I
guess
he'll
make
me
join
us
someone
later
vodka.
Oh
wait,
wait!
A
Thank
you
very
much
if
the
ball
goes
fast,
so
you're
they
again
vodka.
If
you
will
go
first
to
give
us
your
update,
please
let
us
know
what
you
were
doing
last
week,
you're
blocked
on
and
what
are
you
doing
next.
B
Sure,
hey
guys
so
last
week,
I've
been
I've
had
like
cold
days
meeting
with
near
firm
guys
regarding
the
visualization
tool,
which
was
like
an
intricate
process
of
providing
feedback
and
answering
doubts
about
the
old
early
p2p
data
that
they
need.
Other
other
and
kind
of
related
with
that
I've
been
working
in
the
elliptic
to
be
introspection.
I
have
currently
rough
ER
with
the
switch
data
for
of
the
data
model.
I
I
need
to
still
to
clean
up
some
code
and
it
will
hopefully
be
ready
this
week
for
a
review.
B
Also
I
need
to
review
the
streams.
Terrible
requests
for
from
mentis
and
I
will
also
start
doing
some
work
in
the
sink
it's
Reiter's
IO,
so
I
will
start
by
defining
the
what
the
interface
transport
interface
connection
would
look
like
and
other
than
that
I
will
review
again.
The
JavaScript
point:
I
should
not
gossip.
So,
as
my
career
reached
me
today
and
said
that
I
could
give
you
a
new
best,
so
I
will
do
it
any
questions
or
comments
for
me.
A
C
C
C
So
if
you're
interested
in
that
feel
free
to
pop
in
there
and
comment
in
the
Oakland
PD
are
there's
a
proof
of
concept
in
there
without
working,
but
it
need
some
updates
to
other
things
in
order
to
ship
it
other
than
that.
I
will
continue
to
work
on
the
JSI
BFS
network
performance
with
the
DHT
this
week.
Yeah
any
questions
for
me.
A
D
So
I've
worked
on
the
IP
ID
formats,
stuff
I'm,
sure
I
have
done
something
else
as
well,
but
I
can't
recall
that's
my
only
item
and
but
I
still
keep
working
on
it
and
so
parallel.
We
still
do
discussions
on
the
next
iteration
of
the
API
there's.
Clearly
lots
of
discussions
going
on,
but
we'll
see
how
this
goes
and
next
week
here.
I
will
also
look
at
it,
but
so
the
format
for
IP
LD
protocol
buffers
is
basically
done,
which
probably
will
make
Alex
happy.
D
E
A
Cool
okay.
Moving
on
this
should
be
fun:
okay,
okay,
so
I
made
a
pull
request
to
allow
the
IP
necessary
publisher
to
shut
down
a
bit
quicker
that
was
got
reviewed
emerged.
We
had
a
contribution
from
our
open
source.
Apprenticeship,
with
this
I
think,
is
that
the
placements
company
pest
pest
Oh
anyway.
This
is
a
guy
who's,
been
doing,
went,
request
really
useful
stuff
for
us,
and
one
of
them
was
getting
recursive
recursive
DNS
link
on
the
cups,
which
is
cigarette.
A
So
then
I
reviewed
that
and
washed
it
and
I
spent
some
time
we
have
the
lipids
P
guys
last
week,
testing
out
the
DHT
in
0:35.
We
found
that
it
wasn't
really
working
at
all
and
we
don't
really
know
why
and
we're
sort
of
in.
We
need
to
figure
out
why
there's
a
possible
issue
might
be
the
bit
swap
when,
when
you
ask
this,
what
for
something
it
doesn't
and
it
finds
it
finds
something
I
think
it
does
a
cold
call
and
because
of
the
queuing
things
we've
added
to
the
p2p.
A
Those
concur
comes,
get
put
on
the
back
of
the
queue
and
possibly
might
not
even
be
called
at
all
so
bit
swap
it
might
never
actually
dial
the
note
that
it
that
it
needs
style
to
get
the
content.
So
that's
just
a
potential
issue
that
I
was
debugging
last
week.
Yeah
that
needs
more
more
work,
so
it
means
that
there
is
some
still
way.
Some
still
some
problems.
0:35
release
and
I
opened
a
PR
for
ya
against
interrupts
for
0:35,
and
that
was
also
not
incredibly
successful.
A
The
performance
of
exchanging
files
has
Dramastic
drastically
changed
for
the
worse,
so
that
needs
to
be
figured
out
as
well
and
I.
Think
that's
what
was
talking
about
earlier
as
well
and
and
then
today,
I
submitted
a
pull
request
for
mdns
discovery
interrupts.
This
is
just
kind
of
a
quick
pull
request,
slippy
to
be
mdns
on
the
test
side,
which
allows
it
to
discover,
go
lippy
TV
and
the
go-go
idea
past
nodes,
and
vice
versa.
It's
basically
compatible
with
what
go
does
and
does
pretty
much
the
same
thing.
A
I
thought
it
would
be
really
simple:
just
change
a
few
like
service
tags
and
things,
but
then
I
realized
that
the
go
mdns
implementation
is
is
pretty
fun
times
and
it
was
difficult
to
debug,
but
anyway,
the
sort
of
darn
it
needs
tests
adding
to
it.
But
in
lieu
of
the
newer
implementation,
I
thought
it
best
to
spend
a
little
bit
of
time
just
getting
the
current
implementation
to
work
together,
because
because
you
know
we
don't
know
when
it's
gonna
and
it's
gonna
change.
A
So
that's
what
I've
been
doing
like
I
said
on
block
times
everybody
five
release
because
of
the
DHT
and
the
performance
problems
that
I
saw
in
Interop,
and
so
my
toy
list
right
now
is
to
get
sorted.
The
okay
ours
for
q2
I
mean
not
q1
because
they
are
not
finalized
yet
and
yeah
I've
been
else
I
haven't
been
able
to,
but
might
might
do
this
and
then
I
want
to
figure
out
what
to
do.
Move.
0:35,
release
and
I
would
appreciate
your
input
they're
like
should
we
shouldn't?
A
E
So
last
week
about
NPM,
stuffed
Lua,
which
was
you
know
quite
sad
to
watch
from
from
the
exterior
and
some
people
on
Twitter
started.
Talking
about.
Oh
and
it'd
be
great.
If
we
had
a
distributed
version
of
NPM
and
I
kind
of
like
they
start
saying.
Well,
actually
all
the
D
web
stuff
is
super
slow.
So
it's
not
gonna
solving
our
problems
and
I
was
like
I.
Actually
I
saw
some
other
interesting
problems,
kind
of
go
involved
in
our
conversation
and
what
what
came
out
of
it
was
oh
yeah.
E
If
you
add
transports
here,
then
we'll
think
about
merging
them
into
NPM
cool,
so
I
implemented
ipfs
and
IP,
and
s
transports
for
MDM
and
opened
a
PR
that
took
most
of
last
week
and
it
should
be
super
exciting
if,
if
he
gets
merged
so
also
I
do
PR
for
that
problem
with
pulling
ham
shards
down
by
the
gateway
which
resonators
there
have
been
some
comments
on
so
in
the
next
bit.
Will
we
hear
fixing
that
up?
E
I
am
might
be
unblocked
now
on
the
async/await
stuff,
unix
averse,
maybe
depending
on
what
folker
has
done
to
the
api.
But
if
it's
shipped
then
that's
great
and
we
can
fix
it,
that
will
be
cool
yeah,
so
I
am
going
to
continue.
I
started
looking
at
some
problems,
MP
on
ofs,
some
really
weird
slow,
behavior
I,
don't
if
it's
related
to
how
it
how
it
was
there
were
some
problems
with
I'm.
Sorry,
it
might
be
related.
I've
just
started
looking
into.
E
A
F
F
We
will
be
talking
about
it,
so
we
don't
duplicate,
work
and
find
us
good
solution
before
I'd
be
nice.
I
also
finished
the
last
bundle
size,
pull
requests,
removing
the
IP
le
formats
for
the
browser,
I
added
a
bunch
of
documentation
explaining
out
app
developed
in
the
browser,
can
add,
support
back
and
stuff
like
that.
I
also
fixed.
F
F
Old
Eli,
and
also
that
with
that
person,
instead
of
like
using
the
daemon
to
to
do
all
the
tests
and
basically
the
MF
s,
commands
words
in
the
parser,
were
only
in
the
CLI
file,
so
I
fixed
that
and
also
added
a
safer
way
to
exits
the
CLI
basically
instead
of
using.
Finally,
we
are
with
this
full
request.
G
Now
in
past,
I
was
only
able,
through
these
directories
now,
like
loading
images,
videos,
work
and
while
I
was
doing
that
I
also
fixed
streaming
in
Jessica
TFS,
which
did
not
flash
before
entire
payload
was
received.
Cause
like
I
think
by
default.
Happy
is
responding
with
gzipped
dialogue,
so
the
compressor
used
by
happy,
which
is
our
HTTP
server,
intersective
s,
that
compressor
did
the
flash
only
with
each
received
entire
payload
from
ideas
and
I
fixed
that
so
after
receiving
each
chunk
from
ipfs
there's
a
small
flash
to
compressor.
G
So
streaming
works
with
gzip
compression
over
HTTP,
which
is
cool.
So
my
that's
more
or
less
what
I've
been
up
to
and
my
turn
for
this
week
is
basically
clean
up
a
lot
of
code
and
submit
a
lot
of
upstream
patches.
There's
this
one
draft
of
HTTP
API
pri,
already
open
I
need
to
like
update
that,
because
there
there
are
some
small
stuff
on
top
of
that.
But
yeah,
that's
my
a
bit.
A
That's
really
cool
news:
I
can't
wait
for
your
upstream
pr's
to
come
along
cool
okay.
Now
we
are
done
with
the
regular
weekly
update
sections
and
normally
we
now
move
on
to
the
cross
team
update
section,
an
array.
So
this
is
a
new
section
where
the,
where
people
from
other
teams
that
are
not
there
possibly
outside
of
chance
call,
can
share
their
wins
we've
with
us
if
they
so
wish.
A
H
H
H
We
can
decide
where
to
have
the
conversations
next
so
see,
I've
been
playing
around
with
the
magic
wormhole
to
sort
of
a
fun
utility
which
probably
a
lot
of
people
don't
know
about
which
you
can
is
for
sharing
secrets
between
generally,
like
it's
a
Python
app,
then
you
can
see
put
a
secret
in
a
file
and
share
it
with
somebody,
and
then
they
have
to
connect
at
the
same
time.
And
then
you
just
give
them
three
three
words
and
they
type
it
in,
and
then
they
get
the
secret
on
their
in
and
I
figured.
H
That
would
be
a
really
clever
way
to
hook
together
a
lot
of
these
pure
base
web
apps
I'm
building
where
you
need
to
get
a
secret
from
one
machine
to
another,
so
I
built
a
little
HTTP
API
around
that
didn't
have
one
and
I'm
integrating
that
into
the
peer
test,
app
that
Juan
wrote.
So
that
should
be
hopefully
done
today.
I
want
to
get
that
launched
and
then
the
main
thing
you're
gonna
do
this
week
is
dig
into
test
labs.
H
So
you
know
we
have
our
nice
integration
test,
but
be
nice
to
be
able
to
random
on
large
numbers
of
servers
and
the
validity
to
be
team.
Cole's
working
on
this
thing
called
test
labs,
so
I
try
to
earlier
version
of
it,
but
he's
got
it's
a
much
more
usable
state
now,
so
we're
gonna
dig
into
it
this
week
and
also
pure
base
is
sort
of
legging
behind
on
the
GSI
PFS
version.
H
I
Yeah
I
am
really
excited
to
announce
that
I
am
NOT
just
totally
stuck
in
actually
making
progress
now
and
it's
iron
files
tutorial.
So
that
does
mean
it's
been
a
scoped,
which
is
part
of
me
feeling
like
I,
can
just
move
forward.
So
you
can
see
we're
now,
focusing
just
on
MF
s,
and
there
are
two
main
reasons
for
that.
It
used
to
be
that
the
plan
wants
to
make
one
tutorial
about
the
non
MF
s
commands
like
learn.
I
How
do
you
say
learn
how
to
do
the
same
stuff
like
add
the
files
and
then
learn
how
to
use
m
FS
with
this
layer
of
abstraction?
On
top
of
it
and
the
two
reasons
I'm
just
focusing
on
immutable
file
system
now,
one
is
that
people
have
suggested
that
the
order
is
wrong.
Mf
s
is
the
beginner-friendly
thing,
even
though
it's
this
weird
like
not
really
what
ipfs
doing
thing
and
then
diag
and
other
file
stuff.
I
It's
like
more
advanced
and
requires
more
understanding,
but
the
other
more
practical
reason
is
that
I
discovered
that
blobs
aren't
supported
directly
by
the
non
MF
s,
methods,
which
makes
it
really
hard
to
teach
a
lesson
on
just
adding
a
file.
Because
then
you
also
have
to
teach
a
lesson
on
how
to
turn
a
blob
into
something
that
is
actually
accepted
and
I'd
rather
not
be
teaching
that
infertile
school.
I
So
Hugo
mentioned
to
me
that
he
has
an
OK
R
to
make
blob
supported
by
the
non
m
FS
commands,
which
I
think
it's
fabulous
so
I'm,
postponing
that
and
for
now,
just
focusing
on
this
that
I
can
push
through
on.
So
the
first
couple
of
lessons
here
are
more
just
basics:
how
to
interact
with
the
system,
but
we
have
a
commit,
a
lesson
on
right
and
we
have
one
on
LS
for
right
now
and
I'm
still
working
through
that,
so
the
basic
plan
for
what's
inside
of
them.
My
first
tutorial
hasn't
changed.
I
It's
just
that
I'm
focusing
narrowing
and
I'm
specifically
doing
that
one
and
then
I
know
Allen
yeah,
oh,
and
you
were
thinking
about
how
this
might
get
used
to
ipfs
camp
and
hoping
that
this
the
file
thing
would
be
done
before
then
I'm
hoping
you
were
on
the
other
piece
of
it.
Also
I,
don't
know
what
you
know.
What
Hugo's
timeline
is
on
that
change,
but
this
current
plan
so
I'm
very
open
to
feedback
as
always,
but
this
is
this.
A
A
E
Think,
as
a
point
of
order,
the
head
of
masters
should
be
releasable
at
all
times,
but
we
shouldn't,
have
you
know
code,
that's
in
there
that
stops
releases
from
happening
like
we
can
have
experimental,
okay,
you
know,
but
it
should
be
turned
off
by
default
and
then,
when
it's
ready
it
can
be
turned
on.
So
we
can
have
regular
releases
without
backing
lots
of
stuff
up,
as
has
happened
in
this
case,
so
I
think
yeah
disabling
it.
Keeping
the
code
in
and
releasing
you're
disabled
is
is
completely
the
right
thing
to
do.
A
A
It
was
actually
failing
it
unless
you
actually
you
properly
run
it
and
to
be
fair
to
us
Seifer.
We
should
have
run
that
and
figured
that
out
before
before,
where
it
got
merged,
and
that
didn't
happen.
So
that's
just
a
learning
for
the
next
time,
but
yeah
in
general
I
totally
agree
and
we
want
master
to
be
yes,
beliefs
of
all
anyone
given
any
given
point.
Basically
so
yeah.
A
The
DHT
is
moving
into
0:36,
potentially
right.
Well,
okay,
get
on
the
get
on
the
bike
with
that.
Then
this
week,
all
right,
okay,
wherever
by
the
word
of
time,
thanks
for
spending
all
of
your
time
with
us
and
it's
been-
it's
been
fun
and
I
hope
to
be
a
little
bit
better
next
week
and
less
cranky,
but
until
then
have
a
lovely
week
and
do
some
awesome,
investing
and
we'll
see
you
next
all
right,
bye.