►
From YouTube: IPFS Weekly Call 🙌🏽📞December 17, 2018
Description
IPFS Newsletter: https://tinyletter.com/ipfsnewsletter
DHT Stress Test: https://github.com/vasco-santos/iptb-dht-test
IPFS Roadmap: https://github.com/ipfs/roadmap
A
Excellent
hello,
everyone
and
welcome
to
the
ipfs
weekly
meeting.
This
is
a
place
where
we
learned
what's
happening
in
our
community
and
the
cool
stuff,
that's
being
built
on
top
of
IP
FS,
so
our
format
is
going
to
be
a
little
different.
Today
we
are
going
to
do
announcements
last
and
we're
going
to
start
with
our
two
presentations.
It's
nothing!
That's
changing
of!
We
have
two
presentations
today.
Our
first
presentation
is
from
VDS
and
he'll
talk
about
the
okrs
and
the
second
one
is
from
Vaako
santos
and
he's
going
to
talk
about
DHT
stress
test.
B
Right,
Thank,
You,
Portia
cool,
so
let
me
share
my
screen
so
that
I
can
show
you
some
nice.
Can
you
see
my
keynote
app
yeah
by
the
way
I'm
trying
this
like
multi
screen
setup?
So
if
you
see
my
face
just
like
looking
at
multiple
places,
it's
very
destructive
I'm,
just
looking
at
multiple
screens
cool,
so
hi,
everyone
welcome
to
the
ipfs
project.
Where
map
soft
launch.
B
We
everyone
really
appreciates
each
other's
contributions
to
it.
So
I'll
try
to
be
very
brief
so
that
we
can
have
the
other
presentation
on
this
call
without
eating
on
others,
callsign.
So
agenda
is
particular
map.
What
is
the
way
to
happen
after
the
soft
lounge
in
Oh?
Everyone
can
contribute
to
planning
cool
so
without
further
ado,
I
introduce
you
to
the
fantastic
first
of
its
kind.
Beyond
interplanetary
the
ipfs
project,
chrome,
app
version
zero
4.0.
B
This
segment
is
now
live
on
the
roadmap
repo,
so
you
can
go
to
get
out
of
comm,
slash,
ipfs,
slash,
chrome,
app,
and
you
can
see
all
this
stuff,
but
there
and
this
Huffman
packs
many
many
great
amazing
things.
First
off
the
ipfs
mission
statement,
it's
the
first
time
we
as
a
project
go
at
least
written
down
and
something
that
the
working
groups
got
the
chance
to
peer
review
and
stand
behind
so
I'll
just
give
ten
seconds
for
everyone
to
I
got
a
chance
to
quench
through
the
mission
statement
here,
just
let
that
sink
in.
B
All
right,
I
see
some
smiley
faces,
some
people
nodding.
Yes,
so
as
I
the
first
project,
we
believe
that
all
of
information
on
the
Internet
should
be
uniquely
and
permanently
content
addressed
on
a
disputed
peer
web.
But
what
does
it
mean
like
it's,
a
pretty
bold
statement,
and
so
we
to
make
that
more
tangible?
We
impact
that
mission
segment
into
goals.
B
Some
people
call
them
visionary
goals
and
you
can
see
the
list
here
from
package
managers
wash
files.
So
as
we
look
at
the
web
and
the
list
goes
on,
you
can
find
a
description
for
each
of
these
very,
very
ambitious
goals
on
the
ipfs
project
roadmap,
but
after
much
thought
and
consideration,
and
because,
like
again,
this
is
like
each
of
these
goals
by
itself
is
very
large
and
very
ambitious.
We
had
to
create
a
sorting
function
to
help
us
identify
what
would
be
the
ones
that
we
should
be
focusing
on.
B
First,
to
give
the
whole
org
a
sense
of
direction,
a
sense
of
unified
direction,
rather
than
everyone
trying
to
do
all
the
things.
At
the
same
time,
until
after
the
design
of
the
third
function,
we
come
up
to
what
we
call
the
2019
priorities,
so
these
top
five
priorities
basically
are
going
to
be
the
things
that
we
are
going
to
focus
really
hard
on
top
19.
So
you
will
see
other
working
groups
were
maps
reflecting
much
of
what
is
described
here.
The
everything
else
that
you
see
here,
the
remaining
goals
are
20
20
plus
priorities.
B
So
we
are
not
discarding
them,
we're
not
dropping
them,
but
actually,
by
focusing
on
these
priorities
really
hard
and
getting
them
done,
we
will
be
building
the
foundation
like
leveling
up
the
baseline,
that
the
bar
that
then
will
enable
us
into
the
future
the
following
years
to
nail
down
the
remaining
goals.
So
what
are
these
priorities?
Sir
first
starts
with
supporting
package
managers.
Package
managers
are
one
of
the
top
use
cases
for
ipfs.
It
is
one
multiple
package
management
communities
have
been
part
of
the
project
since
the
beginning
and
being
part
of
our
channels.
B
B
One
of
the
reasons
why
it's
so
interesting
to
prospective
energies
is
because
package
managers
have
to
move
a
lot
of
code
around
until
IP
passed
by
itself
gives
a
lot
of
like
interesting
properties
from
like
just
other,
together
the
codes
being
able
to
fetch
the
call
from
close
machines
and
make
it
work
offline
and
also
attracts
a
whole
set
of
developers
from
multiple
language
communities
that
will
make
the
project
even
more
interesting.
The
next
priority
is
transferring
large
file
data
sets
a
DFS
designer
phone
data
file
system.
B
So
it
is
a
file
system,
and
so
we
want
to
focus
and
make
sure
that
we
build
the
the
tool
change
the
the
libraries,
the
the
examples
that
we
nail.
The
stories
that
like
will
enable
users
to
transfer
files
in
a
very
simple
way.
Next
up,
we
have
building
the
decentralized
web,
something
that
we
have
been
putting
a
lot
of
energy
into
and
we
want
to
even
put
more
in
1219,
basically
create
the
framework,
the
library
that
will
enable
an
explosion
of
the
civilian
applications
to
appear
in
2010
and
Beyond.
B
And
of
course
last,
but
not
the
least.
The
two
other
objectives
are
supporting
party
growth.
So
there
is
a
lot
of
builders
on
top
of
a
TFS
today,
and
so
we
have
been
asking
getting
feedback
trying
to
understand
better
their
needs
and
priorities
and
how
IPS
is
part
of
the
critical
path
and
we
are
trying
to
make
sure
we
hear
all
about
those
requests
and
we
prioritize
them
accordingly
to
what
is
our
capacity
so
that
we
can
empower
and
enable
all
of
those
users
and
then
building
foundation
for
future
goals.
B
So
this
takes
me
back
to
what
I
said
in
the
beginning,
which
is
by
really
focusing
really
hard
on
these
tough
travel
priorities
and
some
things
extra.
We
actually
prepare
a
way
better
foundation
for
all
of
the
other
future
goals
that
we
have
for
the
project.
So
this
top
five
labelled
priorities
are
reflected
on
the
working
group.
Ro
Maps
each
working
group
got
their
own
roadmap,
and
so
you
can
directly
check
in
with
working
group
on
like
what
they
are
planning
to
do.
B
What
is
their
progress
and
and
like
talk
with
them
to
see
if
there
is
something
that
you
believe
should
be
present,
that
there
or
represented
there,
and
it's
not
or
yeah,
just
learn
what
is
the
direction
overall,
but
like
kind
of
like
reading?
All
of
these
working
real
world
maps
is
hard
like
those
are
like
also
long
documents.
B
The
first
one
is
that
we
want
to
get
the
reference
implementations
to
become
production
ready,
and
this
basically
means
that,
like
the
implementations,
will
become
reliable
for
businesses
to
trust
running
it
them
in
production
and
like
relying
on
it
to
to
run
their
businesses
to
run
their
projects
to
run
their
products.
The
reality
is
actually.
B
This
is
already
happening,
like
there's
already
applications
out
there
that
I
use
like
a
festival
every
day
and
they
rely
on
it,
although
we
have
only
really
savvy
first
alpha,
but
we
want
those
19
to
be
the
year
where
we
invested
in
the
more
energy
so
that
the
tooling
the
debugging,
the
support,
is
there,
the
API
completion,
etc.
So
that,
like
those
users,
can
feel
even
more
empowered
and
a
whole
new
wave
of
users,
can
I
jump
into
the
project
and
start
relying
on
it
as
well.
B
Second
related
to
the
top
priority,
we
want
to
support
package
managers
to
enter
into
the
web.
We
want
to
kick
off
a
working
group
to
like
own
this
set
of
tasks,
and
we
want
to
make
sure
that
the
implementations
meet
the
needs.
The
scalability
and
performance
needs
for
these
use
cases
to
like
be
efficient
to
exist
except
skilled,
a
Beaver's
network
as
we
get
more
and
more
use
cases
kneel
down
and
as
we
get
more
users
in,
we
need
to
make
sure
that
IP
%
work
is
capable
of
scaling.
B
We
with
that
demand,
and
so
not
only.
We
want
to
make
sure
that
that
because
network
skills,
but
also
we
want
to
make
it
proven
by
tests
by
test
best,
that
we
can
indeed
scale
the
network
and
we
can
deal
with
flash
crowds
and
so
on,
creating
the
platform
to
that
entangles,
the
mysteries
of
developing
adapt.
Again,
a
lot
of
work
has
been
put
into
this
already,
but
we
want
to
put
even
more.
B
We
want
to
be
or
to
create
the
toolkit
that
answers
many
of
the
questions
from
our
community
on
how
to
build
these
real
applications,
and
it
we
have
answers
to
too
many
of
those
questions
like
how
to
transfer
state
between
clients
how
to
identify
a
user,
how
to
give
some
permission
to
some
piece
of
content
or
to
edit
a
piece
of
content,
etc.
So
why
not
work
they're?
B
B
Then
everyone
gets
a
simple
way
to
have.
F
share
retrieve
persist
files
on
the
websites
on
a
TV
network.
Again,
this
is
like
really
basically
like
understanding
what
are
what
is
blocking
the
users
from
like
jumping
WS
network
and
using
a
day-to-day
tool
to
share
that
files
to
share
in
Evan,
share
files,
and
so
there's
a
lot
of
work
here
as
well.
Seven,
we
got
a
lot
of
feedback
from
users
and
in
which,
like
they
want
to
see
more
testing
more
benchmarks,
more
performance,
optimizations
like
they
will
have
ipfs.
B
They
want
to
rely
on
it
but
like
they
want
to
be
sure
that,
like
IP
fest
will
be
able
to
deal
with
their
requirements
with
the
amount
of
data
that
they
are
transferring
every
day
and
so
will
also
put
a
big
focus
on
that
and
last,
but
not
the
least.
We
want
to
support
the
IP
address
the
growing
ipfs
community.
Today
we
are
more
than
3700
contributors,
or
at
least
like
3700
people
that
contributed
at
least
once
to
the
project
in
some
form,
either
by
poor
request,
review
or
research
contribution
or
killed
commit.
B
This
doesn't
count
all
the
builders
of
about
capacity
just
like
people
that
touch
directly
our
repos.
So
if
you
can't,
with
the
whole
our
Jericho
system,
it's
actually
a
large,
so
we
want
to
improve
documentation.
A
big
thing
that
is
coming
2019
is
proto
school,
so
I
can
online
Academy
to
learn
web,
so
yeah
stay
tuned.
For
that,
so
yeah
there
was
the
Rome
app.
The
document
is
live.
You
can
go
again
to
IP
fast
sorry,
get
out
comm
such
a
PFS
washroom
app
and
read
it
out
there
like
it's
to
give
up
repo.
B
You
can
open
issues
with
questions.
You
can
submit
pull
requests
to
fix,
typos
or
like
to
make
suggestions
just
go
a
while
review.
It
give
us
feedback
what
is
happening
after
now
that
we
have
opened
IVFs
project
roadmap
for
the
first
time.
Well,
we
are
doing
self
launch
right
back,
so
it's
happening
here.
We
are
sharing
with
you
all
presented
on
this
weekly,
ok
check,
then!
Yes,
we
not
only
push
that
because
project
map
to
the
repo.
We
also
pushed
each
working
group
map
to
the
repo.
B
So
you
can
also
give
feedback
to
the
working
groups
directly,
so
check
check
there
as
well,
and
now
we
are
looking
forward
to
hear
from
everyone
in
the
community
to
give
us
feedback
to
review
it,
to
see.
What's
missing,
to
like
ask
us
stuff
that
we
like
check
our
assumptions
and
and
help
us
like
drive
the
papers,
project
or
map
for
impression,
0.42,
actually
version
1,
so
that
we
can
do
a
big
launch
early
in
January.
So
that's
it
like.
B
We
now
want
how
your
help
like
we
want
your
reviews,
one
to
your
feedback,
so
that
we
can
prepare
a
big
launch
and
tell
the
whole
world
that
the
first
project,
the
biggest
project
as
a
road
map,
and
that
people
cannot
use
it
as
a
reference
point
for
their
own
planning.
So
yeah
version
1.0,
the
my
map
happening
launching
early
in
January,
we'll
do
like
a
blog
post
and
I
call
the
fence
fair.
So
that's
like
we
are
doing
this
announcement
here.
It
is
actually
a
talk.
B
B
It's
really
really
welcome
the
same
thing
for
like
our
icky
arts
planning
for
next
quarter.
So
as
it
is
tradition,
we
always
do
open.
Okay,
our
planning.
That
means
that,
like
the
working
groups
are
now
using
the
room
map
to
kind
of
like
set
direction
for
next
quarter,
set
goals
for
next
quarter
and
they
have
these
open
threads
where
they're
members
of
the
working
group
and
anyone
else
that
as
feedback
suggestions,
requests,
can
go
to
that
trap
and
propose
suggestions
for
goals
on
next
quarter.
B
Of
course,
like
it's,
not
just
because
proposing
a
goal
that,
like
that,
gets
like
injected
into
the
the
goal,
though,
the
list
of
goals
for
next
quarter,
but
but
like
they
it
will.
There
are
multiple
iterations
up
and
over
those
four
requests
in
which
then
people
try
to
call
s,
and
they
defy
one
of
the
things
that
are
most
important
and
actually
a
to
one
exporter
and
then
there's
a
last
pass.
B
I
could
review
that
everyone
can
check
in
and
see
if
they
agree
with
the
the
objectives
and
key
results
that
are
set
for
next
quarter
and
and
that,
basically,
that
last
pass,
as
the
last
review
is
happening,
this
Wednesday
so
I
actually
super
close
right
back.
So
we
have
this
open
call
that
is
happening.
Wednesday
starts
at
5:00
p.m.
OTC.
B
It's
going
to
be
very
long
call,
but,
like
you,
don't
need
to
watch
all
of
it
or
you
can
always
like
just
participate
on
the
the
sections
that
you
are
most
interested
in
and
you
can
listening
to
the
room
to
the
okay
arts
presentation
by
so
yeah.
This
was
like
my
super
quick
presentation
of
my
PFS
project
on
maps
just
like
to
get
it
out
there,
I
really
looking
forward
to
hear
all
your
thoughts
and
I
can
receive
all
your
questions.
Thank
you
for
your
attention.
B
Thank
you
for
being
a
really
awesome
community
and
for
contributing
to
the
project.
It
is
really
amazing
to
work
with
you
all
and
be
part
of
like
this
is
super
important
project.
So
yeah
I'll
finish
up
here
and
perhaps
I'll
stop
my
screen
share
and
I'm,
not
sure.
If
we
have
time
for
questions
here,
maybe
you
can
take
one
for
you.
You
know.
A
C
D
D
Okay,
so
sorry,
first,
during
this
quarter,
two
of
their
main
goals
of
the
GSA
PHP
team
was
to
ever
get
you
enabled
in
jessup
FS,
as
well
as
to
start
working
on
a
test
bed
that
enabled
us
to
simulate
large
scale
tests.
So
in
one
side,
we
wanted
to
guarantee
that
the
HT
was
good
enough
to
be
enabled
in
Jessica
fest
and
in
the
other
point
of
view,
for
the
test
bed.
D
We
wanted
to
have
a
proof
of
concept
of
how
we
would
test
DHD
before
going
into
and
technical
aspects,
myself
Jacob
and
Cole,
we
host
testbed
weekly,
sync
every
Tuesday
at
6
p.m.
Lisbon
time.
If
you
have
some
ideas
or
you
want
to
contribute
or
know
what
we
are
doing
just
to
welcome.
You
are
welcome
to
a
period
okay,
so
starting
in
the
news,
IPTV
HD
chest.
D
So
the
main
goals
of
the
simulations
is
to
test
two
different
workloads
through
the
use
of
seven
different
parameters.
First,
we
we
can
test
the
challenges
to
look
at
workload.
That
time
is
to
test
the
HT,
with
frequent
beers
being
connected
and
disconnected
through
the
network,
while
the
lookup
intensive
workloads
aims
to
test
the
network
while
putting
and
carrying
a
lot
of
data,
so
requirements
are
produced,
it's
just
to
have
installed
IP
to
be
as
well
as
yes
ffs
and
go
at
the
fest
CLR.
D
Just
when
fing
important
Jessup
FS
has
not
yet
DHT,
we
are
merged.
So
if
you
want
to
test
with
just
a
ref
s,
you
should
use
this
PR
in
here.
Okay,
so
we
have
two
two
different
comments
with
the
first
one
new
simulation,
while
the
second
one
is
statistics,
the
simulation
creates
a
JSON
file
with
the
results
that
we
can
observe
with
the
statistics.
However,
the
simulation
also
ends
the
statistics
in
yen,
so
we
basically
just
want
to
use
the
simulation.
Okay,
so
I
will
Jam
you
now
to
this.
D
I'll
put
this
one
running
because
it
will
take
a
while,
while
I
explain
the
other
end.
So,
okay
in
the
simulation
commands,
we
basically
pass
the
parameter
simulation
to
to
the
tool
and
we
can
basically
decide
what
implementation
we
want
to
use
if
we
want
to
use
at
the
first
go
implementation,
or
just
at
the
first,
the
number
of
notes
that
we
want
to
start
the
network,
the
number
of
iterations
that
we
want
to
put
and
get
data
into
the
DHT,
the
lookup
factor,
which
basically
consists
on
the
key
replications
for
the
number
of
nodes.
D
There
is
if
we
have
five
nodes
and
look
lookup
factor
of
two
we'll
have
ten
different
cues
available
and
basically
we
generate
a
random
key
for
it
for
each
into
iteration
and
we
will
use
it
to
put
a
random
value
in
the
DHT
and
we'll
use
it
afterwards
as
well
to
get
that
data
from
the
HT.
And
finally
you
we
can
also
use
the
churn
factor,
which
is
the
number
of
nodes
that
we
will
disconnect
and
connect
from
the
network
per
second.
D
D
D
We
really
aim
to
give
a
step
forward
and
we
want
to
get
this
work
in
the
testbed
effort
that
we
have
also
been
making,
and
we
aim
to
fo
a
to
analyze
the
data
that
we
obtained
from
these
tests,
which
we
currently
do
not,
and
when
we
have
these
results,
we
also
want
to
F
plans
on
out.
We
should
improve
the
DHT
in
order
to
improve
the
these
results,
so
I
have
here
the
results.
D
Now,
as
you
can
see,
this
is
the
final
analysis
and
it
also
was
created
a
JSON
file
with
this
for
further
analysis.
So
we
basically
ran
two
hundred
iterations
with
five
notes.
We
no
caption
factor
of
two
in
the
shown
factor
of
one.
So
for
the
put
comments
in
the
DHT.
We
got
a
round-trip
time
of
278
milliseconds
on
average,
and
we
have
just
six
file
lots
of
line
boots,
which
basically
were
due
to
we
selected
a
random
pair
to
put
data,
but
that
random
beer
will
gotta
fine
in
the
process.
D
While
in
the
get
part
of
this
we
add
the
round-trip
time
of
270
milliseconds
on
average
failed
off
line
seven
and
this
one,
which
is
like
probably
one
of
the
most
important
metrics
right.
Now
we
and
we
expected
that
we
would
get
the
most
recent
value
that
we
put
in
the
DHT,
but
in
28
of
our
cases
we
got
a
previous
value
instead
of
the
most
recent
one.
D
So
our
goals
with
this
tool
is
also
to
have
more
parameters
that
we
we
can
add,
as
well
as
get
more
metrics
from
these
simulations.
We
we
have
been
also
discussing
with
John.
Yes,
I
always
should
add
more
things.
What
we
should
have
and
also
what
are
the
results
that
we
will
aim
to
get
I've
been
reading
some
some
papers
that
he
recommended
me
and
for
now
tits.
This
is
what
we
thought.
That
would
be
the
most
important
factors,
so
wrapping
up
your
feedback
would
be
awesome.
Please
reach
me
out.
D
A
E
D
Now
there
is
no,
there
is
no
option
for
that,
but
as
we
improved
our
tool,
at
least
for
the
testbed
one
of
the
things
that
we
want
to
get
is
to
have
with
the
different
configurations
of
the
lipid
to
be
in
each
demon
and
afterwards
we
can
have
different
tests
with
different
configurations
for
the
cattle
HT.
We
currently
support
it
in
the
laboratory
site,
but
as
we
are
not
using
yet
lipid
freedom
and
we
are
using
yes
ffs
one
or
the
guide,
the
first
one.
We
don't
have
from
that
perspective.
A
B
The
remember
like
really
contemplates,
like
the
plans
of
the
apes'
project,
the
goals
and
equities
project
is
trying
to
achieve,
and
now
so
we
try
to
acknowledge
it
that
build
that
isn't
about
PFS.
Some
of
them
might
run
in
businesses
on
top
of
like
the
protocol,
and
so
we
want
to
make
sure
that,
like
a
DFS
deploys
like
the
features
that
those
partners
need
to
in
order
for
them
to
be
successful.
Of
course,
we
if
it
falls
within
the
scope,
what
we
even
the
the
objectives,
are
ipfs.
B
It
is
the
thing
that
we
have
opened
as
a
channel
like
we
are
still
like
getting
more
feedback
like
we
welcome
like
any
partner
to
reach
out
to
us
and
tell
us
what
they
need
like
what
are
the
challenges?
What
what
are
the
bottlenecks?
What
are
the
issues
that
they
are
seeing
and
and
like
work
with
us
to
make
sure
like
we
can
meet
those
needs
like
that
we
can
like
ship,
those
like
see
those
features
and
so
like
we.
We
are
super
interested
in
that
information.
B
As
for
I,
don't
know
if
there
was
like
an
another
question
in
your
question
about
us:
if
ipfs
is
going
ffs,
the
project
is
going
to
develop
any
commercial
product
instead
of
19
like
that,
because
the
project
itself,
there
is
no
plan
internally
to
do
that,
like
we
will
continue
focusing
on
the
infrastructure
on
the
protocol
and
making
sure
that
we
work
closely
with
our
users
to
to
get
the
things
out
there
like
really
enable
them.
The
users
build
those
products,
build
those
applications.