►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 October 29, 2018
Description
A
A
Allowing
large
file
uploads
allows
web
UI
to
detect
and
connect
to
origin
without
the
user
having
to
configure
API
I
attempted
to
release
ODOT
33,
but
there
is
some
delay
due
to
a
myriad
of
things
that
have
popped
up,
so
I
think
he'll
be
working
on
that
this
week,
he'll
also
be
working
on
the
CID
base
option
and
then
reviewing
many
a
PRS
there's
also
a
PR
open
for
easier
pre-release
support.
I
think
that
one
should
be
good
to
go.
A
B
So
last
week
I
created
the
interrupt
PR
for
the
DHD.
It
is
grains
and
it
is
ready
for
being
reviewed
and
I
also
created
a
couple
of
beers
for
City
l2f.
The
DHT
interrupts
working
I
have
just
minor
problem
with
the
DHT
in
the
really
awesome
endeavor
that
I
take.
Do
the
pits
to
check
it
out
when
you
have
time
with
schechter,
because
it's
just
minor
detail,
there
is
missing
for
the
interface
the
idea,
fest
interface
car
test.
B
Then
I
agreed
that
the
interface
that
the
story-
new
lots
of
modules
for
the
service
worker
gay
aah,
a
great
example
that
I
previously
had
to
use
webpack
for
because
gsm
FSIA
was
having
problems
with
the
web
part
4
and
the
service
worker
gateway
and
I
created
an
example
with
a
pack
for
to
track
down.
If
it
was
the
service
worker
gateway,
probe
or
not,
and
then
the
IP
NS
over
pub,
so
I
created
the
danger
of
PR
as
well,
but
it's
not
green.
B
C
D
C
E
C
F
A
Other
questions
for
rush
Propst
all
right
next
up
is
me
alright.
So
the
major
things
last
week
was
working
on
the
lid
p2p
release
I
found
a
bug
in
switch
while
doing
the
tests
against
Jay
s
ipfs,
so
that
is
fixed
and
then
I'm.
Trusting
the
release
candidate
to
that
should
be
good
to
go
today
or
tomorrow.
A
I
just
need
to
go
test
against
the
Jaya
GSI
PFS,
one
more
time,
while
that
is
stable-ish
now,
hopefully,
there
was
a
lot
of
issues
last
week
just
going
through
the
tests
and
then
having
the
key
data
store,
updates,
breaking
that
called
the
master,
builds
and
causing
a
big
nightmare,
and
then
the
length
of
time
for
running
that
GSI
PFS
tests
made
me
go
crazy
again.
Last
week,
so
I
started
looking
at
all
of
the
test,
Suites
to
figure
out
how
we
can
just
get
rid
of
demons
across
the
board.
A
H
Last
week,
I
still
worked
a
little
bit
on
the
on
the
pipeline.
I
did
a
couple
calls
with
the
guys
from
the
infra
team,
explained
everything
with
about
my
prototypes.
They
are
still
working
on
a
surgical,
CI
prototype
based
on
the
things
I
did
forget
laughs,
but
I
basically
finished
the
the
like
at
least
a
basic
configuration
with
to
use
case
we
already
talked
about
this
is
all
on
on
working
on
a
fork
of
the
GSI
BFS
repo
on
my
github
account.
You
can
check
there.
H
I
also
activated
the
renovate
on
that
repo,
because
I
can't
really
activate
it
on
on
the
other,
repos
and
I
will
make
issue
talking
about
it.
I
also
did
the
couple
of
stuff
on
DL,
basically
improving
the
purposes,
improving
the
speed
and
basically,
that's
like
adding
an
option
to
send
the
configuration
when
you
in
it's
a
demon,
so
we
don't
have
like
to
do
like
four
different
style
processes
and
stuff.
H
Also,
these
couple
of
pull
requests
about
missing
in
and
use
dependencies
on
it
on
the
API
and
on
the
ipfs
repo,
the
other
stuff
was
fixing
CTL,
not
actually
starting.
When
you
passed
start
to
true
and
also
fix
up
a
lot
of
the
options
handling,
it
was
kind
of
crazy.
I
will
continue
with
this
work
on
the
files
on
CTL,
because
the
options
handling
is
kind
of
crazy
in
there
too.
H
These
also
work
on
just
some
excellent
stuff
that
came
up
when
we
start
removing
and
necessarily
the
balances,
and
for
this
week
I'll
push
the
the
PR
the
guys
from
the
14
deed
I'll
try
to
make
to
help
them
finish
up
the
circle
CI
prototype,
so
we
can
compare
the
two
or
circle
see
I
would
eat
lab
and
figure
out.
What's
best
for
us,
I
also
will
do
an
issue
explaining
everything
about
to
renovate
service
and,
with
my
fork
as
an
example
and
I'll
try
to
push
Asia
experimental
builds
to
be
the
default
one.
H
C
No
question
yeah
like
true
the
weekend:
I
got
to
see
a
bunch
of
things
that
got
stuck
I.
Think
right
now
we
are
paying
huge
costs
for
not
spending
time
on.
I
can
prove
you
already
have
to
link
and
yet
I
see
a
lot
of
PRS
that
I
just
don't
merge
for
weeks
to
months.
It
are
super
simple.
They
are
there,
but
like
there
was
like
some
CIE
cap.
C
The
thing
got
red,
no
one
paying
attention
again,
and
so
we
really
need
like
to
speak,
like
I
fear
that
we
might
like
be
losing
like
30
or
more
or
40
percent
of
our
time,
just
having
to
fight
with
the
CI
right.
Now
it's
very
troubling
like
to
the
point
where
thank
you
so
much
for
liking
the
weed
and
like
checking
out
things
with
the
table
like
yeah.
C
H
Yeah
last
week
and
through
the
weekend,
I
got
really
frustrated
about
the
second
situation,
because
everything
was
not
getting
green
at
any
cost
and
especially
as
I
actually
implemented
a
pipeline
that
works
faster
and
more
reliable,
I
even
get
more
foresight
about
it
and
things
that
that
we
are
being
that
we
are
discussing
on
a
issue
like
pretty
releases
and
stuff.
Like
that,
that's
there's
all
that
stuff
is
already
in
my
prototype
and
working
perfectly.
So
we
need
to
really
double
down
or,
as
you
said,
and
we
will
be
really
really
helpful.
H
In
my
opinion,
it's
not
like
the
best
choice
because
we'll
eat.
We
will
go
through
the
problems
we
had
in
the
past
about
queuing
up
with
others,
other
clients
and
stuff
like
that,
but
we
need
to
discuss
it,
but
we
need
to
also
discuss
it
fast
because
we
need
to
solve
this.
The
our
CI
problems
should
be
able
to
work
faster.
C
J
H
From
what
I
was
able
to
learn,
we
can
pay
them
for
something
like
adding
up
bigger
containers
or
something
like
that,
but
I'm
not
really
sure
that
we
they
can
solve
the
queuing
problem
like
for
more
money.
Ok,
yes,
so
you
usually
have
a
better
idea
than
I
have
so.
Ok,
thanks
I'm,
not
like
a
hundred
percent
on
it,
but
from
from
the
talks
I've
been
listening
from
Gaddafi's
shoes
and
stuff.
H
C
C
Can
I
ask
everyone
to
put
as
an
action
item
of
their
like
I'm
there
to
do
this
this
week
to
review
this
proposal?
Remember
like
this
will
affect
the
way
you
work.
It
will
affect
the
way
that
you
like
communicate
with
the
community,
and
so
it's
very
important
for
everyone
to
really
like
pay
attention
and
understand,
and
I
can
also
ask
questions.
Make
sure
like
these
questions
like
capture
so
like
there
is
a
proper
proposal
like
taking
into
example.
C
The
the
proposal
is
created
to
adopt
discuss
where
there
like
the
study
of
multiple
options
and
like
the
things
that
were
brought
on
early
on
and
the
things
that
caught
answered
and
like
the
reason
why
we
finally
made
the
decision
to
really
discuss.
Let's
make
sure
that
we
do
the
same
for
for
these,
with
everyone
on
board
can
I
can
I
get
a
thumbs
up
from
everyone
like
all
right,
always
way
to
do
it
two
times?
Let.
C
Em
FS
to
these
first,
like
these
top
level
comments
and
basically
make
everything
of
these
files.
A
top-level
comment
given
the
his
ipfs
and
so
I
worked
on
that
I
got
the
test
done
on
a
deficit
that
score
documentation.
I
got
just
a
TFS
API
to
work.
I
almost
did
all
of
the
GOP
best
I
have
to
do
it
on
the
plane,
but
apparently
just
a
few
fast
and
just
have
you
can
say
my
first
ever
circle
circle
or
dependency,
which
makes
it
very
hard
to
like
just
get
out
of
it
like.
C
We
need
to
get
very
good
at
like
stopping
with
a
circle,
but
this
is
we
at
least
probably
in
the
past,
where
I
can
order
to
fix
them
or
joke.
It's
really
the
one.
But
you
got
to
realize
another
one.
You
were
to
like
really
the
first
one
and
so
in,
and
so
basically
you
have
to
really
the
module
we
are
passing
at
a
time
is
the
other
one
very
fast:
it's
just
a
mess.
C
Let's
when
there
is
such
kind
of
thing,
where
let's
make
an
interface
and
just
like
MIT's,
let's
get
them
in
fast
to
use
like
that
and
have
cats
get
interface.
That
then
Jessica's
can,
just
like
add
those
commands,
rather
than
adding
the
whole
ipfs
object.
But
but
I
can
take
care
of
that.
It's
just
like
a.
It
was
impossible
for
me
on
a
plane,
and
so
then
I
also
found
an
issue
on
a
PSD
CTL,
a
bunch
of
audits.
C
Actually
there
there
is
like,
just
by
my
question
of
hey
Ike.
Why
are
things
taking
so
much
time
to
merge
and
so
I
found
a
bunch
of
PR
that
were
perfect
and
they
would
like
remove
time
from
realizing
staff
or
simplified
code,
and
so
I
just
like
took
on
the
the
responsibilities
of
like
reviewing
doing
a
lot
of
releases
from
master
like
checking.
They
were
passing
the
tests
and
merging
and
releasing
them
so
like.
You
might
actually
know
a
lot
of
releases
during
that
weekend.
C
It
was
due
to
that
and
I
want
to
use
that
as
hey
I
there's
a
lot
of
things
that
people
have
been
producing.
That
is
super
useful
for
some
projects
that
are
not
getting
intentional,
so
I
think
we
need
to
get
better
at
like
waffle.
Boarding
I
did
some
waffle,
grooming
and
so
I
went
through
a
bunch
of
issues
that
the
labels
basically
like
check
like
what
was
still
valid.
What
was
fix,
what
was
not
fixed
and
then
was
super
helpful
for
me.
I'm
not
sure,
I
keep
waffle.
C
It's
still
super
helpful
to
everyone,
but
but
a
twist
like
for
me,
I
have
a
great
good
experience
or
just
opening
up
like
setting
up
a
timer
saying,
I
thirty
minutes,
45
minutes
open
a
bunch
of
issues,
label
them
like
answer
to
them
merge
and
if
they
are
poor
request,
cle-cle
are
done
a
and
feel
very
good
about
myself
in
the
project
is
like
so
much
work
gets
done
like
so
fast,
because
I
can
work
is
already
there.
I
just
have
to
like
realize
things
and
version
it's
great
like
you
should
try
it
as
well.
C
It's
great
try
it
so
yeah
what
I
did
do
and
now
I
created
a
new
ipfs
architecture.
Diagram.
Go
there
post
comments.
So
far,
people
seem
pretty
happy,
but
again
you
just
like
representing:
what's
there
so
I
guess
like
there's
not
too
much
to
bike-share
other
than
the
diagram
itself,
but
to
go
there
and
comment
and
and
also
I
opened
an
issue
which
I
think
seems
irrelevant
some
of
these
conversation,
which
is,
should
we
try
get
up
for
our
art?
We
talked
about
it
in
past.
C
It
seems
like
we
kind
of
like
keep
patching
our
coordination
book.
It
we
more
Google
Docs,
more
github
issues,
more
templates
for
poor
requests
and
whatnot
and
more
see.
Is
that
break
and
like
when
I
look
at
the
other
web?
It's
like
they're,
like
issues
that
can
be
multiple
repos.
They
can
have
like
epics
and
they
have
my
Kanban
boards
and
they
have
Mike
Riley's
life
cycle.
They
have
monitoring
he's
like
wow.
C
Hey,
like
I,
think
we
have
all
the
to
link.
We
just
haven't,
polished
it
yet
and
so
I
took
on
the
task
of
like
upgrading
a
tool
and
I
do
it
on
the
past
that
was
kind
of
fun
in
the
time
and
got
a
lot
of
attention,
but
then
I
stopped
having
time
to
pay
attention
to
it.
If
so,
it's
all
broken.
So
if
you
like,
refactoring
it
and
polishing
it
and
I
creating
a
roadmap
for
it,
so
you
check
it
out
and
now
comments
and
feedback
and
ideas,
but
yeah.
C
J
So
it's
pretty
quick,
so
I
did
a
bit
of
a
graph
seeing
stuff,
but
mostly
I,
spend
time
getting
my
IPL
d
by
breaking
I
don
t
change
in
five
FS,
because
it
also
breaks
the
ipfs
api
and
yeah.
So
we
spent
the
half
week
on
basically
getting
this
release
kind
of
our
trying,
yeah
and
then
I
want
to
think
of
it
when
I
go.
J
Would
those
all
issues
that
he
was
inventing
it
merging
them,
because
there
was
plenty
of
stuff
that
I
did
and
and
things
yeah
and
next
week,
I
will
also
like
hopefully
does
iPod
a
change
will
go
in
forgiveness.
We
had
will
have
a
release
and
again
grousing
stuff
and
then
just
like
catching
up
with
the
things
that
I
couldn't
get
done
because
of
the
iPod
II
stuff
and
circular
dependencies
in
CIS.
Oh
yeah
awesome
right
and
that's
all
any.
A
E
Hi
so
I
did
a
new
release
of
ipfs
NPM,
which
is
pretty
cool.
It's
now
like
a
standalone
that
kind
of
wraps
either
NPM
or
yon,
and
uses
our
ipfs
registry
to
pull
down
your
dependencies
and,
and
it
will
just
proxy
everything
else
to
those
commands.
So
if
you're
doing
something
that
isn't
pulling
down
dependencies,
it
will
go
off
and
it
will
do
the
right
thing.
E
In
theory,
I
would
do
a
demo,
but
it's
really
slow,
so
I'm
not
going
to
do
a
demo
because
I'm
going
to
spend
the
rest
of
them
of
the
week
making
it
fast.
So
at
the
moment,
we're
syncing
all
of
em
p.m.
which
you
know
will
make
it
easier,
because
we
won't
have
to
go
off
to
itself
to
get
stuff
which
will
make
it
a
little
bit
faster.
E
C
E
C
By
the
way,
like
I
opened
a
bunch
of
issues,
there's
a
lot
of
like
room
for
creativity
here,
like
I,
actually
already
got
my
my
Raspberry
Pi
in
my
external
hard
drive,
because
I
want
to
have
like
a
box
which
is
my
local
NPM
cash
in
my
network
and
I
want
to
be
able
to
say,
hey
and
pee.
My
guess
is,
for
the
future.
I
want
to
be
able
to
say,
hey
my
local
NPM
registry,
cache
to
my
PFS.
C
Could
you
sink
to
my
laptop
all
the
modules
I
keep
using
that
I
can
go
on
this
like
very,
like
three
long
flight
and
like
have
all
my
dependencies
with
me
that
I
keep
using
it'd
be
great
and
so
yeah
like
you
could
be
you.
You
can
have
like
your
portable
version
of
NPM
with
you.
While
you
have
like
your
pee-pee,
like
complete
version
of
NPM
on
your
local
cache,
just
get.
A
D
C
True,
but
but
like
any
kind
of
like
feedback,
if
you
have
for
our-
and
you
know
like
anything
that
you
need
from
a
jazz
team-
is
absolutely
a
good
time
to
open
it
up.
I
keep
you
up
blocks
on
something
so
that
we
know
diction
another
thing
that
I
would
love
and
like
if
Alan
was
here,
you
would
probably
bring
his
self
I
will
have
like
the
community.
I
want
you
to
tag
along
with
us.
Is
this
awesome
and
ever
sink
iterators?
C
C
C
So
I
think
it
would
be
super
cool
if
the
community,
given
that
I
gave
you
any
to
JavaScript
air,
to
help
us
on
this
endeavor,
because
it
will
give
you
like
firsthand,
first-time
experience
on
like
all
these
modules.
There
really
is
it
just
the
tests
like
what
they
do,
what
they
do
not
do
and
I
like
you,
you
will
have
an
opportunity
to
impact
our
api's,
that's
that
will
be
exposed
to
all
the
developers
so
don't
feel
like
it.