►
From YouTube: js-ipfs discussion
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
B
Run
cool,
so
we
don't
have
a
note-taker
sign.
Would
someone
like
to
volunteer
to
take
notes
for
this
hall
Emily?
Thank
you.
They're,
awesome,
all
right!
So,
if
you
haven't
done
the
things
you
want
to
talk
about
in
this
meeting,
please
do
add
them
to
the
agenda.
The
first
item
was
not
tell
by
me,
but
definitely
important
to
go
true,
not
true.
Whoever
but
I
can
do
the
review.
So
the
first
item
is
review
to
confer
prosperous
and
why
we
are
to
two
weeks
behind
the
schedule
at
we
at
point
four.
B
So
if
you,
if
you
have
a
look
at
the
the
mouse
down
the
road
map
or
just
a
chief
s,
we
are
like
workin
all
them
also
to
getting
a
lot
of
tests
getting
things
like
work,
we're
very
well.
It
is
really
like
we
plan
initially
to
like
have
that
done
by
the
third
week
of
august
with
weak
sauce
with
august.
B
There's
like
definitely
things
that
we've
been
talking
about
that,
like
always
steals
a
bunch
of
5
from
the
government,
because
if
people
that
are
doing
Jessica
fest
are
doing
all
the
jazz
stuff
on
the
IP
15
things
that
back
each
time
we
go
into
just
agree,
50
pies,
and
we
the
problem
with
the
CVP
I,
and
then
what
we
spend
like
one
day,
trying
to
figure
out
why
there
is
something
weird
happening
with
the
CBP
I.
Now
we
are
losing
a
bunch
of
time
at
each
time.
C
Yeah
Richard,
obviously
yeah
go
ahead,
feel
okay,
cool
right,
so
I
was
the
one
who
wrote
it
sorry
that
I
forgot
Chapman
mine
in
there.
Thank
you
for
addressing
for
addressing
most
of
it.
The
main
reason
I
want
to
put
I
just
wanted
to
call
mainly
attention
to
this,
simply
as
just
for
us
and
when
we
do
planning
just
to
be
aware
of
a
lot
of
things.
That
happened,
we're
somewhat
known,
whether
with
the
planning
arm
and
we
kind
of
we,
we
underestimated
them.
C
At
least
I
did
some
of
them
and
I
think
we
just
can
learn
from
this.
In
terms
of
how
we,
we
estimate
some
things
and
just
know
that
things
often
take
longer
yeah,
which.
D
B
Think
that's
more
like
a
project
management
issue,
then
I,
specifically
just
a
PFS
or
what
they
are
doing.
We
just
have
BFS.
We
do
try
to
keep
like
like
we
do,
try
to
always
have
a
list
of
items
that
each
girl
is
composed
of,
and
we
always
I
try
to
see
and
I
picture
that
the
ball
is
rolling
in
every
direction
so
that,
like
we
don't
lose
track
of
anything.
There
is
always
like
hospitals
at
you
will
face
that
we
cannot
predict.
B
There
is
always
like
things
that
consume
our
time:
the
poor,
not
in
the
plans.
I,
do
think,
though
again.
But
this
is
more
of
purchasing
management
thing.
I,
don't
think
they
like
being
optimistic
and
I.
Think
dishes
and
I
try
to
push
as
much
harder
as
we
can
in
the
short
amount
of
time
even
like
if
we
have
to
do
a
little
bit
but
like
if
we
like
a
nest
and
why
we
do.
B
The
world
is
more
important
than
just
like
having
a
lot
of
space
to
do
less
work
and
then
and
then
I
be
more
comfortable,
because
we
would
have
liked
more
space
than
more
time
than
we
actually
needed.
I,
don't
know,
I
didn't
want
to
or
I
don't
think
like
its
proper
protective
to
use
this
time
to
like
go
through
those
things.
B
We
definitely
it's
something
that
we
touched
in
the
last
gathering,
p,
I,
don't
know
or
I,
don't
know
what
I
do
like
best
and
I
dunno
I
work
best
and
make
something
that
everyone
who
feels
that,
like
you,
should
change
that.
We
should
like
have
smaller
milestones
and
like
I've,
always
time
to
like
the
time
that
we
expect
to
develop
and
the
time
that
week
we
add
as
a
buffer,
always
on
the
road
map.
It
seems
like
something
that
I
can
go
like
to
ask.
B
C
Yeah
I'd,
make
makes
sense,
I
think
to
add
some
proper
time.
I,
don't
see
that
we
will
run
into
the
problem
of
oh.
We
have
all
this
much
time
and
we're
like
going
and
relaxing
I,
don't
think
that's
going
to
be
any
issue,
but
I'd
rather
have
a
more
realistic
approach
to
the
estimates
like
we're.
Doing
them
then
to
make
them
as
squeezable
as
possible.
Given
that
we
all
know,
things
often
take
longer,
and
things
come
up
because
it
does
create.
Like
being
you
know,
two
days
behind
schedule
is
nothing
we
sweat.
C
E
Are
all
really
great
comments
and
I
think
that
some
of
this
will
be
resolved,
especially
as
mad
and
I
finish,
ironing
out
the
PM
process?
But
why
don't
you
spend
the
rest
of
this
call
going
over
the
rest
of
the
q2
goals?
It
looks
like
there's
a
lot
left
under
the
testing
infrastructure
as
well
as
some
of
the
dependencies.
Do
you
want
to
start
going
over
that
to
read
yeah
sure,
happy.
B
To
so,
I
just
have
one
of
the
things
I'm
on
Mike
the
goal
of
the
milestone
like
the
quality
and
the
correctness
of
the
documentation.
The.
What
are
the
problems
that
we
had
in
the
past
was
because
of
like
the
lack
of
good
error
handling
in
terms
of
like
no
gestures
worked
and
that's.
Why
we'd
like
to
see
huge
discussion
about
migrating,
triple
streams
or
react
reactive,
but
we
decided
to
go
with
the
full
stream
the
now
like.
B
C
B
C
C
B
Ok
definitely
add
that
to
the
notes.
I
need
to
check
that
again
than
triples
seems
like
an
end,
this
sorry
yeah,
cool
and
I
to
merge
all
of
those
both
dream
PRS.
They
just
need
to
add
a
documentation
of
what's
going
on
there
and
like
explain
people
while
we
are
using
for
streams
as
we
agree
in
the
past.
F
I
just
wanted
to
say
that
this
is
a
really
good
morning.
Well,
because
what
the
proposal
to
pull
strings
was
coming
up.
Oh,
it's
like
this
is
going
to
take
a
million
years
and.
B
F
Going
to
be
very
slow,
changing
a
technology
throughout
Echo
Base,
it's
never
easy.
It's
full
of
questions,
it's
full
of
things
that
you
didn't
know
we're
going
to
happen,
and
so
yeah,
it's
like
a
really
hard
thing
to
do.
Even
in
the
evenin,
the
change
seems
small,
even
if,
like
though
oh
it
should
just
be
like
stopping
one
library
out,
always
the
students
going
to
take
a
lot
longer.
F
Always
a
service
gonna
like
a
bunch
of
problems,
so
in
general
I
would-
and
this
is
like
a
different
public
forum
inefficient,
but
it
would
be
great
to
I'm
not
like
that.
It
seems
to
me
and
like
maybe
this
is
just
my
expiration
outside,
but
it
seems
to
me
like
JJ,
said
because,
like
it
jumps
through
a
bunch
of
different
technologies
like
a
lot
into
that's
a
bunch
of
time
dealing.
F
The
option
of
adopting
a
bunch
of
different
tank
and
then
to
being
like
not
actually
useful
work
because
it's
like
there
was
one
way
of
doing
it.
One
like
this.
This
thing
in
like
now
we're
everyone
getting
a
car
like
guys
with
this
other
plates
rate
and
like
then
we
take
a
long
time
to
get
in
there
and
they
go
somewhere
else.
F
C
One
very
important
thing
I
wanted
to
mention
here
is
yes
this.
We
have
that
issue
in
the
JavaScript
world,
I
want
to
say-
or
at
least
there's
a
lot
of
part
of
the
community
likes
shiny,
new
things.
I
also
liked
Jenny
things
I'm
not
going
to
deny
that
I
do
want
to
point
out,
though,
that
the
pool
stream
change
was
done
due
to
the
simple
fact
that
we
were
running
against
issues
and
node
streams
that
we
were
not.
C
We
didn't
effectively
know
how
to
fix,
with
act
without
actually
like
rewriting
the
whole
library,
because
basic
things
like
error
and
and
propagation
are
simply
not
there,
and
we
were
just
seeing
that.
C
Didn't
see
a
way
out
fixing
yes,.
D
B
F
I'll
totally
write
it
there
and
still
thinking
through
the
phone
I
got
some
ideas
of
how
you
could
have
come
at
a
text
in
JavaScript
rah,
it's
more
about
it
to
how
the
call
X
work.
There
is
a
fun
of
a
problem
that
you
can't
you
don't
have
switch
in
JavaScript
like
you,
can't
wait
for
two
things
at
once.
It
by
definition
of
callbacks
right
is
that
it's
not
code
routine.
F
This
it's
called
X
so
because
of
that
you're
always
going
to
end
up
with
a
problem
that
you
will
have
something
hanging
with
a
call
back
and
it
has
to
be
fired,
and
the
first
thing
that
caught
likes
does
is
check
its
context
and
the
context
says:
hey
you're
done,
then
it
just
returns.
Even
if
you
just
got
the
data
that,
like
you,
need
it
or
something
like
no,
it's
a
constant,
and
so
that's
I
think
the
only
way
to
look
like
sanely
and
birthing
context
in
JavaScript
as
its
without
changing
like
it's
ken.
F
B
Definitely
it'll
be
very
hard
like
to
reach
a
conclusion
here.
Do
not,
though,
from
like
one
thing
that
has
this
notion
of
context
and
like
a
boring,
the
request
is
the
heb
module.
In
note,
the
thing
is
like
we
should
be
module,
which
is
like
this
black
box
that
you
would
like
to
make
a
request
and,
like
you,
call
abort
on
that
request.
B
The
way
that
the
nature
of
like
oh
I
PFS
works
like
we
would
have
a
board
like
a
files
up
get,
for
example,
and
the
files
get
to
get
to
get
to
board
the
beat
swap
call
step.
He
calls
to
get
the
blocks
and
then
the
be
top
will
have
to
call
aboard
the
book
service
or
the
thing
that
he
is
like
asking
from
the
network.
So
it
has
to
be
something
I'd
like
chains
very
well,
and
that's
like
one
thing
about
the
others,
but
not
yeah.
F
Go
ahead,
that's
what
context
does
it
go?
Yeah
I
saw
ideas
from
therapist
would
look
like
other
shows,
an
addition.
C
Know
it
just
one
quick
note
on
that:
there
is
another
discussion
going
on
it
on
exactly
this
theme,
which
is
on
the
standards
bodies
around
cancellable
promises
and
the
run
promises,
which
is
the
current
discussion
around
how
to
handle
things
like
cancel
actions,
especially
things
like
fetch
that
introduced
promise
api's
for
HTTP
requests
in
the
browser
need
a
standard
way
to
be
able
to
be
cancelled.
There's
already,
that's
already
been
a
lot
of
work
around
this
and
there
are
there
in
couple
of
presentations
and
and
suggestions.
So
we
definitely
should
look
at
that.
B
Yeah,
definitely
if
you
couldn't
bring
all
that
to
that
issue,
and
even
if
we
know
the
people
that
are
involved
on
that
draft
spec,
probably
we
can
invite
them
to
like
chat
on
that
trail
as
oh
and
bring
their
what
they
have
one
that
we
are
pretty
great
cool.
So
definitely
pity
that
we
have
10
minutes
left.
Why
talk
about
what
you're
going
to
do
this
week
this
week
is
going
to
be
about
like
merging
the
post
stream?
B
The
other
thing
that
we
need
to
complete
is
I.
Don't
know
what
of
work
on
getting
interface,
FS
Corps,
more
complete,
like
adding
the
rest
of
the
API
specs,
getting
a
lot
of
tests
there,
that
I
run
on
Jessie,
PFS,
API
and
Jessa
PFS
and
I
leave
one
extra
thing
than
I
didn't
plan
in
the
beginning,
but
reality
to
the
roadmap.
B
B
Accepted
back
so
it
is
raining
I,
so
like
running
the
interface
Africa's
core
tests
over
IP
FS
API,
the
client
library
against
the
implementation
of
HTTP
API,
a
spare
on
Jessie
PFS.
So
basically
we
are
running
the
same
tests
through
core
and
through
the
CBP
I,
and
this
way
we
are
fixing
the
HTTP
I
making
sure
because
I
we
don't
have
a
batch
of
test
from
HTTPS
back
to
run
against
it.
So
we
are
wearing
the
same
test,
but
truth,
our
client
library,
which
we
know
it
works
against
you
I
PFS.
B
So
it
looks
like
we
get
like
some
level
of
confidence
assurance
that
the
HTTP
I
implemented
stuff
correctly,
because
jessica
ASAP.
I
can
talk
with
it
and
with
that
we
actually
found
like
a
bunch
of
bucks,
so
it
was
very
productive.
I
already
did
it
for
a
bunch
of
api's.
We
are
just
missing
files
and
swarm
swarm
requires
me
to
change
a
little
bit
of
whip
you
to
appear
to
be
able
to
dial
two
nodes
that
we
don't
know
the
ID
beforehand
it
just
like
physically
some
little
changes.
B
We
just
assume
that
we
already,
we
would
always
knew
the
the
IPF
SI
d
beforehand,
leather.
I
could
make
it
easier
because
we
could
then
I
check,
if
area
connection
etc.
Now
we
just
have
to
change
that
to
the
packet
gets
the
ID
from
the
identify
or
second
you
know
first
and
then
like
it
then
understands
it.
You
know
it
does
appear
that
song
too
yeah
so
like
need
to
change
yet
in
order
to
be
able
to
pass
the
same
tests
and
then
ditch
the
files.
B
The
files
there
is
a
PR
to
get
the
app
DF
command
working
through
a
cheap,
EP
a--,
which
box
a
lot.
I
was
working
on
it
couple
months
ago,
I
believe
he's
pretty
busy
right
now,
I'd
like
to
check
with
them,
but
we
might
have
to
continue
and
finish
up
and
clean
up
that
work.
It
needs
a
rebase
and
it
needs
to
be
completed
once
we
have
that
add
HTTP
API
endpoint
of
min
just
ffs.
B
B
Then
there
is
the
network
testing,
which
is
something
that
I
started
working
before
the
internet
archive.
But
it's
it's
on
a
PR
right
now
it
is
like
spawning
nodes,
just
I
professed
nodes
and
like
destroying
them
by
creating
tests
that,
like
really
test
jetta
TFS
in
the
epoxidation,
so
that
we
know
that,
like
if
some
node
fails
in
the
network
or
like
if
something
goes
wrong,
that
the
other
nails
don't
crash,
because
I
know
a
socket
closed
or
something
especially
now
that
we
have
there
or
propagation
than
bright
with
four
strips.
B
So
this
will
be
like
the
treating
of
like
bigger
focus
for
this
week.
Oh
yeah
yeah
pretty
girl.
F
B
So
what
I
hope
to
have
is
like
some
time
with
you
and
Jeremy
like
an
hour,
maybe
two
hours
just
to
go
to
all
the
things
I
need
to
change
in
order
to
get
to
the
new
see
ids
and
then,
when
I
figure
out
the
list
of
like
the
action
items
that
needs
to
be
done
in
order
to
get
IPL
beyond
jessica,
fest
and
working
over
the
top.
B
I'm
sure
there
will
be
some
things
that,
like
we
will
need
to
change
specifically
on
beat
swap
to
work
on,
go
I,
PFS
that
it
might
be
more
clear
for
go
I
PFS,
and
then
we
can
just
like
porch
those
ideas
to
just
give
us
and
the
like.
As
soon
as
we
get
together,
it
would
be
like
yeah
as
soon
as
we
get
together,
it'd
be
pretty
cool.
B
B
C
I
can
I
can
do
it
in
three
minutes,
I
made
an
effort
to
porch
jsap
FS
API
to
use
fetch
directly,
which
is
the
replacement
and
browsers
or
xhr
in
modern
browsers,
come
to
reduce
the
file
size
of
chase.
A
PFS
API
is
well
successful
and
so
far
then
I
have
test
passing
in
modern
browsers,
IE,
chrome
and
yeah,
and
Crow
and
and
most
tests
are
pressing
and
other
browsers.
The
problem
is
that
chrome
is
the
only
eight
browser
that
actually
implements
proper
streaming
for
fetch
requests.
C
All
the
other
browsers
are
just
saying
like
now
like
we
can
fetch
stuff,
but
we
don't
do
streaming
are
witches
makes
one
particular
request
impossible
for
us,
which
is
I
PFS
logs
long
tail
is
an
HTP
request
which
just
hangs
it
stays
open
and
it
will
just
send
data
until
you
cancel
it.
You
can't
actually
cancel
requests
and
some
other
browsers
on
fetch
API.
So
we
can't
even
like
say:
okay,
we
wait
too
it's
and
we
cancel
it
and
that
we
take
the
result.
F
C
B
Is
a
mess,
can
we
that's
pretty
cool
like
definitely,
especially
because
again,
it's
just
like
removing
a
bunch
of
the
crypt
of
dependencies
that
we're
adding
a
lot
of
ways
now?
Can
we
have
that
in
separate
pr's?
Can
we
have
like
the
crypto
dependencies
scheming
on
one
PR
and
the
migration
to
fetch
in
another
PR,
because
it
seems
like
it's.
C
C
Otherwise
you
can't
drop
them
in
jsf,
FS
API,
because
what
we
currently
use
is
wreck
and
wreck
is
was
written,
your
original
library,
so
it
requires
HTTP
and
HTTPS
and
those
pull
and
all
the
crypto
dependencies,
because
our
modular-
and
so
it
just
pulled
in
all
the
crypto
stuff.
Yeah
H
users
for
HTTPS
requests
the
crypto
stuff
in
the
browser.
So
it
doesn't
ship
anything
crypto,
stuff,
cook
your
things
or
doing
these
requests,
but.