►
A
Alright
I'm
recording
this
now
so
be
aware.
Look
lively!
Okay!
Let's
do
it,
hello!
Everyone
welcome
to
the
ipfs
core
implementations
weekly
sync!
It
is
December
the
9th
we
are
running
out
of
time
of
for
2019.
It's
it's
rapidly
dwindling
away,
but
at
the
end
comes
good
things.
So,
if
you're
here,
can
you
please
put
your
name
on
the
attendees
list
of
the
notes?
I
will
put
the
notes
in
the
chat
right
now.
A
You
all
right,
you
have
a
weekly
update,
then
please
at
the
bottom
of
the
document,
is
the
place
where
you
can
put
that
and
people
will
review
it
asynchronously.
We
won't
go
over
in
this
meeting,
but
what
happens
when
it's
meeting
finishes
that
we
would
send
a
pull
request
to
IVFs
/
team
management
and
that's
where
we
check
each
other's
weekly
reports.
I
still
haven't
done
mine,
but
I
would
get
it
done
after
the
meeting
as
soon
as
I
can
so
put
it
put
it
in
there.
Please.
A
If
you
have
an
update
that
we
read
and
next
up,
we
will
go
through
the
initiatives
and
see
what
progress
we
have
on
the
things
that
we
are
working
on
cool.
So
so
people
keep
messaging
me
all
right.
I've,
coming
and
shipped
really
see
things.
So.
Last
week
we
talked
about
how
jess
IVFs
340
had
shipped
next
up.
I've
made
the
issue
for
Jess
I
with
a
Serie
41,
and
if
you
look
at
the
issue,
it's
gonna
be
amazing.
A
It's
going
to
be
really
really
good.
We're
gonna
have
UNIX
FS
1.5
implemented,
so
you
can
now
put
metadata
along
with
your
imported
files.
So
that'll
be
super
cool
ipfs,
add
performance
has
increased
as
increase
it's
better
now
than
it
was
significantly
better
and
also
we
have
brand
new
api's.
Finally,
our
endeavor
to
rewrite
the
entire
code
base
in
in
promises
and
async
it
erases
and
things
has
has
bubbled
up
to
write
up
to
ipfs.
A
We
have
many
modules
that
refactor
has
been
part
of
a
70
or
treepo
refactor,
but
it's
finally
done
and
it's
going
to
yield
huge
benefits
and
I'm
hoping
to
write
a
blog
post
on
that
for
a
later
this
week.
So
keep
your
eyes
out,
not
literally
so
that's
that
does
anyone
else
have
any
questions
or
upcoming
or
shipped
things
they
want
to
talk
about
before
we
move
on.
A
C
C
Yeah,
there's
just
a
several
a
lot
of
initiatives
going
on
a
lot
of
work.
Anton's
joined
the
team
and
he's
done
a
lot
of
work
on
the
infrastructure,
so
getting
things
to
spin
up
on
Amazon
Web
Services.
So
he
took
that
over
for
me
and
that's
going
amazingly
well
and
Henriques
been
doing
a
lot
of
work
on
one
of
the
test
plans
and
that
we're
all
and
Stephen
there
there's
gonna
be
a
big
week,
because
they're
going
to
really
try
to
nail
some
of
the
DHT
issues
and
get
that
ready.
A
Nice
I
should
so
mentioned
that
this
work
that
is
being
done
on
the
test
ground,
will
hopefully
be
completed
in
time
for
a
now
scheduled,
go
ipfs
release
0.5
for
the
24th
of
December
I,
think,
which
is
it's
gonna,
be
a
really
nice
Christmas.
So
that
was
maybe
last
week
that
I
heard
that
so
that
could
have
changed,
but
that's
worth
maybe
noting
down
for
all
of
them.
Although
the
view
is
cool,
thank
you,
Jim
any.
Does
anyone
have
any
questions
for
Jim.
A
D
Yep,
quick
updates,
there's
a
relevant
discussion
in
I
prefer
dogs.
It
started
for
around
our
new
dogs
website,
but
the
problems
are
relevant
to
everyone
and
basically
our
endeavor,
to
be
great
to
see
a
DV
1
by
32
to
expose
sub
to
move
from
pass
back
gateway
to,
like
abdomen
gate
gateways
for
websites.
D
D
Central
European
Time,
it's
in
ipfs
community
calendar.
If
someone
wants
to
join,
will
be
discussing
topics
from
this
issue.
It's
mostly
about.
Are
we
able
to
make
it
easier
today
to
publish
web
site
on
my
PFS
without
worrying
about
relative
stuff
things
like
that,
and
that's
also
like
companion
mixed
into
this
discussion.
However,
going
back
to
actual
development,
we
sort
of
talked
with
Steven
last
week,
what
needs
to
happen
to
unblock
pier
IDs,
as
C
IDs
in
IDF
has
passed
like
IP
NS
passed
in
gold
land
cause.
D
It's
interesting
situation
will
need
solve
this
issue
in
jail
and
but
we
still
got
open
80
hours
on
the
go,
so
the
next
step
is
to
unblock
deja
I
linked
it's
about
basically
like
accepting
see
IDs
during
the
same
change
we
did
and
already
shipped
in
jail,
and
when
that
happens,
we
will
bubble
up
to
go
ipfs,
not
sure
if
it
will
land
it.
The
next
release,
however,
like
the
the
end
goal,
is
to
coordinate
both
go
and
Jas
to
provide
subdomain
gateway
functionality
out
of
the
box
and
that's
for
or
less
like
the
goal.
D
This
like
support
on
path
is
nice,
but
actually
does
not
solve
the
underlying
issues,
so
we
will
probably
coordinate
in
the
beginning
of
2020
shipping
subdomain
gateway
out
of
the
box
right
now.
If
you
want
to
run
subdomain
gateway,
you
need
to
run
nginx
in
front
of
go
ideas
of
JSF
device,
because
it
does
not
understand
how
the
header
yet,
but
we
will
get
that.
A
Nice
thank
you
light
or
the
just
for
anyone
who's
listening
the
TLDR
with
relative
passes
that
are
gateways.
We
have
like
type
of
SiO,
/,
IP,
fest,
less
hash,
and
then,
if
you
want
to
host
a
website
there,
all
of
your
links
have
to
be
relative
to
that
URL.
Otherwise,
you
end
up
it's
like
some
weird
place
off
the
top
of
IP
of
esta
io
and
moving
to
a
subdomain
gateway.
We
get
a
security,
wins
for
doing
that,
but
also
like
a
lot
of
tools
out
there
that
generate
static
web
sites.
A
E
E
E
A
Alrighty
next
up
we
have
migration
to
multi
hash
keys.
I
did
hear
from
Adam
actually
and
he's
looking
to
maybe
come
back
to
doing
some
work
on
this,
but
it's
still
on
hold.
Basically,
there
is
no
bandwidth
in
my
in
my
calendar
at
the
moment
to
get
us
done,
and
so
we'll
probably
as
Lida,
was
saying
and
get
this
addressed
in
2020
when
it
comes
around.
A
B
Much
more
than
that,
yeah
I'm,
just
currently
going
through
review
I,
have
a
test
plan
written
in
test
ground,
but
we
still
need
to
there's
like
a
couple
of
other
things
that
needs
to
be
finished
off
with
the
test
ground.
So
you
can
do
traffic
shaping
and
testing
different
versions
and
stuff
like
that.
I'm
also
going
to
probably
start
working
on
the
JavaScript
side,
just
to
make
sure
that
we
can
get
interrupts
from
the
gecko.
B
A
A
I'm
know
I'm
a
bit
of
a
hypocrite,
because
I
will
encouraging
people
to
do
small
pool
requests
and
then
I
go
and
land
a
massive
one,
because
anyway,
I
didn't
I
didn't
expect
it,
but
it
turned
out
to
be.
But
it's
the
HTTP
client
is
kind
of
done
and
ready
pending
reviews
and
changes.
The
slice
is
now
down
to
hhk.
A
These
new
api's,
which
includes
like
only
only
promise
based
api's
own
only
async
iterators,
know
lots
of
different
types
of
streaming
api's
in
the
next
release,
which
is
0.41
and
that's
probably
due
to
land
mid-january,
but
I'm
hoping
to
be
able
to
get
a
release
candidate
out
before
christmas
roof.
All
right,
Jacob
of
ochco,
would
like
to
update
us
on
the
b2b
side
of
things.
Yes,.
F
We
would
yeah
so
we
went
through
and
on
the
daemon
went
through
refactor
the
daemon
to
use
the
latest,
a
singlet,
p2p
and
bubbled
that
up
to
the
daemon,
client
and
Interop,
so
go
and
jaea
slippy
to
be
interrupts.
Us
are
passing
for
the
refactor,
so
we
didn't
break
everything.
So
that's
good
then
got
the
refactor
the
to
the
low
p2p
dialer
to
be
toke
based
set
EQ
based
on
that
is
pending
a
final
review,
but
should
be
good
to
go
this
week
we
are
finishing
up
things
stats
in
connection
manager.
F
Those
are
smaller
efforts,
but
they
are
the
last
of
what
we
need
to
ship.
So
once
those
and
the
token
dialer
are
reviewed,
we
should
be
good
to
do
a
pre-release.
So
we
are
targeting
a
pre-release
this
week.
We
will
do
it,
it
will
go
out
the
door
and
then
hopefully,
we'll
get
an
official
RC
out
early
early
next
week
at
the
latest,
bashko
has
been
cranking
away
on
docks,
so
we've
got
a
bunch
of
improved
docks
for
the
p2p
there's
new
API
doc.
F
There
is
a
new
configuration
dock
which
we
didn't
have
before,
which
explains
what
the
configuration
is.
That's
typically
been
a
nightmare
for
people
and
we
already
got
some
community
feedback
that
that
is
a
vast
improvement
over
what
we
had
and
then
Bosh
was
gonna,
be
working
on
a
getting
started,
docks
for
limb,
p2p
for
more
entry-level
stuff
this
week.
F
A
If
there
are
no
questions
and
then
we
will
move
on
to
there's
no
design
review
proposals
this
week,
I
left
these
two
things
from
the
week
last
week
in
the
week
before
Jo.
So
professor
Jeff
I,
because
httpclient
are
relicensing
to
a
dual
MIT
and
I
might
visit
MIT
or
just
MIT
I.
Don't
even
know
that,
plus
a
factually
and.
A
E
E
A
A
E
E
E
A
A
G
A
D
Sort
of
like
yet
another
strength
of
unspooling
that
issue
I
mentioned
in
subdomain
gateway,
section
part
of
the
fault
like
the
solution
or
yeah.
There's
a
ongoing
problem
of
IP.
First
companion,
breaking
origin
security,
sandbox
of
DNS
link
website
to
put
it
in
a
short
sentence
and
there's
a
proposal
of
solving
that
by
stopping
the
redirect
by
default
and
if
user
chooses
to
open.
But
until
we
do,
we
have
subdomain
gateway
on
localhost.
D
So
for
now
we
would
stop
the
redirect
and
we
would
open
like
if,
by
default,
the
regularize
ditch
server
that
that's
probably
a
IP
first
gateway
and
if
user
chooses
to
open
the
website
from
the
local
gateway
that
would
be
in
the
browser
browser
action
menu
as
an
view
on
a
gateway.
But
that
would
open
it
in
a
new
tab.
Excuse
me
in
a
new
tab,
because
it's
a
separate
origin.
D
D
D
Sorry,
just
like
add
additional
data
point
is
that
we
have
the
same
problem
with
like
subdomain
gateways
right
now
like
CloudFlare,
and
we
got
the
d
web
link
in
both
cases
when
you
load
CID
through
that
subdomain
gateway
you
get
this
original
ation
and
companion
does
not
redirect
that,
but
for
the
nesting
website
we
do
redirect
to.
The
idea
is
to
simply
like
unify
this
behavior
and
give
the
security
isolation
by
default,
which
we
we
do
provide
for
subdomain
gateways
with
it.
Just
for
historical
reasons.
We
can
redirect
Indian
I
think
that's
it.