►
From YouTube: IPFS All Hands Call - Q4 Planning
Description
This was the October 10th IPFS All Hands call that delved into Q4 Planning. See https://github.com/ipfs/pm/issues/217.
A
Unfortunately,
as
you
can
have
noticed,
we
cannot
stream
this
and
so
I'm.
So
sorry
who
the
people
who
like
to
beat
me
if
you're
seeing
this
in
the
future,
that's
because
we've
uploaded
the
YouTube,
which
is
the
plan
so
welcome
from
the
future.
You
have
any
questions,
we're
always
on
IRC
and
sprint
issues.
If
you
want
to
raise
them,
please
do
our
goals
for
days
a
bit
different
than
on
normal
calls,
I'm
going
to
be
going
over
q4
in
the
future
and
how
things
go
and
I'll.
A
Let
Matt
talk
about
that
in
a
minute
after
this
call,
which
should
take
around
an
hour
which
would
end
it
around
one
o'clock
eastern
time,
which
I
believe
is
1700
UTC.
We
will
have
four
calls
today.
Go
I,
PFS,
lib
PTP
know
have
a
pest
orbit.
Jsf
you've
had
some
live
p2p.
Those
are
going
to
be.
The
four
calls
in
that
order,
as
you
can
see,
on
the
sprint
issue,
which
is
in
github
com,
/I,
PFS,
/
p.m.
/
issues,
/,
217,
I-
think
that
ends
the
airplane
like
recording
of
my
announcements
today.
A
B
Hello,
so
today
we're
going
to
be
focused
on
road
map
for
q4
I,
since
we
are
not
able
to
stream.
That
means
that
anyone
on
IRC
is
not
able
to
watch
so
if
everyone
can
help
by
watching
IRC
and
if
anyone
appears
there
encourage
them
to
join
the
zoom
call
help
them
get
on
the
zoom
call,
so
that
people
can
at
least
follow
along
and
ask
questions
I
just
ask
them
to
mute
and
turn
off
their
their
video.
B
That
would
be
great
because
we
do
want
people
to
be
able
to
participate,
and
so,
let's
start
with
a
roll
call
and
then
we'll
talk
about
today's
structure.
So
let's
do,
since
there
are
a
lot
of
people
converged
at
protocol
labs
in
Toronto.
Let's
go
geographic,
but
if
you're
in
Toronto
right
now
do
Geographic
based
on
where
you
usually
are
so
starting
with
with
kuba
or
yeah,
we
should
do
roll
call,
because
it's
it's
a
road
map
called
so
start
with
Cuba
hello.
D
B
G
H
I
B
A
J
L
B
B
The
priority
is
to
identify
what
are
the,
what
are
the
things
that
we
should
be
discussing,
that
we
should
be
considering
for
priorities
for
q4
and
in
general,
we
will
be
going
in
depth
project
by
project
with
this
stuff
during
the
normal
project.
Specific
spring
calls
so
wanting
to
emphasize
is
that
if
we
want
to
identify
anything
that
would
be
great
to
work
on
that's
overarching
efforts,
things
that
cut
across
multiple
projects
now
is
a
good
time
to
discuss
those
other
than
that.
B
B
Okay,
all
right,
so
then
the
this
All
Hands
call
might
be
kind
of
short
and
we'll
get
a
little
bit
of
a
break
before
we
go
into
the
go.
I
PFS
call
I
but
I
so
then,
beginning
with,
is
there
anything
that
people
would
like
to
flag?
That
would
be
great
to
work
on
in
q4.
That
does
not
basically
as
not
go
I
PFS,
JSI,
PFS,
lib,
p2p
or
orbit.
B
For
example,
do
people
have
things
to
discuss
around
multi
formats?
Two
people,
two
people
out
what
were
some
of
the
other
things
that
people
had
flagged
on
now
would
be
a
good
time
to
talk
about
cluster
clustering
or
private
networks.
These
sort
of
cross-cutting
topics
does
anyone
want
to.
I
want
to
just
provide
this
opportunity
for
people
to
call
those
things
out.
A
B
A
B
B
B
Should
be
like
Roger,
you
I,
so
project
repose,
it
seems
like
a
really
great
place
for
us
to
start
building
up
metrics
for
our
projects
it
as
a
whole.
So
it
already
is
a
really
great
dashboard.
It's
better
than
a
lot
of
open
source
dashboards
that
I've
seen
out
there
I'm.
We
could
add
in
more
things
for
Whitby's
to
give
metrics
of
how
healthy
are
these
projects?
How
much
I've
takes
you,
they
have.
A
It's
been
great,
this
quarter,
so
I've
been
going
through
and
making
sure
a
lot
of
them
are
green,
so
likely
to
be
multi.
Formats
have
been
really
doing
a
lot
of
effort
trying
to
ensure
that,
like
everything
works
there,
what
I
would
really
like
would
be
to
actually
have
stats
for
that
as
well
and
be
able
to
log
differences
over
time.
So
I
can
sort
of
see
how
much
green
have
take
made
things.
A
Nobody
contribute
dogs
everywhere
licenses
everywhere,
like
how
what
what
our
progress
is,
because
I
feel
like
a
lot
of
that
stuff
is
a
big,
mod,
very
well
and
that's
sort
of
salt
building
the
entire
dashboard
up
a
bit
further
from
what
it
currently
is,
which
is
kind
of
just
an
overall
matrix
into
like
a
nice
more
than
a
table.
You
know
moving
on
to
a
full
dashboard
I
think
that
would
be
super
super
cool.
I
D
B
B
K
One
thing
I
would
say
about
a
project:
repose
is
that
I
think
metrics
are
super.
Important,
is
they're
starting
to
become
like
really
valuable
thing
to
to
use
in
terms
of
figuring
out
what
it
is.
Are
there
what
we
need
to
spend
time
on
PRS
and
improvements,
and
so
on
sitting
and
doing
standing
outside
some
time
to
focus
on
that
during
this
corner
would
be
pretty
valuable.
B
E
B
K
A
The
website
hasn't
been
finish.
It
would
be
great
to
get
that
up
as
well
as
the
documentation
right
now.
It's
basically
just
a
clone
of
the
readme
which
works
in
some
ways
and
like
we're
waiting
for
content
like
rows
back
and
stuff,
but
it'd
be
sweet
if
we
could
have
sabe
I'd
lay
down
to
the
bare
bones
are
like
what's
possible,
but
have
a
really
good
planning
session
about
who's.
This,
for
how
can
we
solve
this?
You
know
what's
the
website
for
who
are
its
users?
B
Emily,
could
you
flag
multi-format
says
something
that
is
going
to
need
it
discussion
at
some
point,
even
if
it
doesn't
happen
this
week,
all
right
and
then
related
with
that
is
in
my
notes.
They
said
org
set
up,
but
this
was
Richard.
You
had
said
something
about
setting
up
org
around
multi
formats
and
I
PLT,
and
all
these
other
things.
What
did
you
mean
by
that?
So
with.
A
All
of
I
PFS
is
sort
of
branched
and
all
the
sudden
we
now
have
different
organizations.
We
have
multi
formats,
I,
pld
and
just
going
to
send
orbit,
and
we
have
Libby
to
pee
right.
So
each
of
these
different
organizations
to
set
up
in
a
certain
way
there's
like
us,
a
noble
repo,
a
website,
repo,
a
community
repo
and
all
the
readings
like
currently
trying
to
use
standard
greeting
me
up
and
trying
to
make
that
consistent
across.
A
So
it
doesn't
you
end
up
with
like
random,
preemies
or
random
repos,
and
no
one
knows
what
they're
doing
it'd
be
good
to
have
a
better
sort
of
process
written
down
of
all
the
work
I'm
doing
there
and
how
other
people
could
do
that.
So
it's
not
just
a
depending
on
me
and
B.
That's
totally
get
lost
and
see.
A
We
all
decide
how
things
should
look,
and
now
we
should
talk
about
our
github
organizations,
for
instance,
should
I
open
up
a
new
repo
in
which
organization,
and
should
I
move
all
my
private
repose
to
this
organization?
What
do
they
do
with
external
collaborators
want
to
move
repositories
into
one
organization?
A
B
And
I
wonder
it:
would
it
be
overreaching
to
try
to
combine
that
conversation
with
the
conversation
about
project
repose?
That
project
repo
seems
like
a
good
way
to
track
whether
we
are
actually
setting
up
our
organizations
in
ways
that
match
with
our
sort
of
we
have
to
design
decide
how
we
want
to
be
doing
this
and
then
project
repost
becomes
the
way
that
we
check
whether
we're
actually
following
through
so
it
could
be
one
in
my
head.
It
seems
like
one
continuous
conversation.
Is
that
unreasonable
or
does
that
sound
I.
K
K
A
Think
it's
also
true
on
the
sub
organization
level,
like
the
j
s
repos,
how
do
you
figure
out
where
the
test
star
and
stuff
we've
had
a
lot
of
friction
there
and
that
would
be
super
sweet
to
overhaul
I've
go
is
also
having
the
same
thing.
That's
kind
of
part
of
the
tutorial
overhaul
there
and
those
will
also
break
down
into
the
different
calls
later,
but
I'm.
The
organizational
level
totally
applies.
B
I'm
going
to
rearrange
list
because
that
segue
is
straight
into
the
question
of
documentation,
especially
developer
documentation.
I
recently
reread
the
producing
open
source
software
book
and
it
spends
a
lot
of
time
talking
about
the
things
that
you
can
do
in
terms
of
structuring
your
project,
to
encourage
contribution
and
to
like
make
it
clear
how
people
can
contribute
and
we'll
do
a
huge
amount
of
work
on
I
mean
we
make
it
as
a
whole.
B
All
of
these
I
PFS
repos
are
exemplary
in
making
the
effort
to
do
a
lot
of
that
stuff,
but
I
think
we
can
do
even
better
and
there
are
good
guidelines,
for
example
in
that
book.
So
that's
does
anyone
have
particular
observations
around
that
of
stuff?
We
could
work
on
over
the
next
quarter,
documentation
in
general,
so
when
you
say
documentation
gave
me
an
API
documentation,
or
do
you
mean
a
better
read
me
or
so.
D
What
I
so
there's
kind
of
two
different
target
audiences
for
the
documentation
in
general
and
I'm,
looking
at
this
from
the
JSI
PFS
perspective,
but
we
have
documentation
for
people
who
want
to
contribute
that's
one
type
of
documentation,
but
there's
a
I
and
personally
I
think
this
is
the
more
important
part
which
is
the
consumers
of
that
that
particular
module.
So
people
who
don't
necessarily
want
to
contribute,
but
they
want
to
start
using
the
IP
of
its
modules
and
we're
currently
completely
lacking
that
documentation
or
like
we're
not
completely
lacking
it.
D
It's
just
really
really
hard
to
find
the
right
documentation,
and
so
that's
basically
what
I'm
looking
at
in
terms
of
Bob,
jayus
related
things
and-
and
this
mainly
concerns
the
main
module
so
JS
I
have
xavia
and
JS
I
Bevis
in
itself
like
how
do
I
use
this
module?
This
is
a
question
that
people
can
get
answered
at
the
moment,
and
this
is
a
feedback
that
gets
in
in
the
in
the
issues
quite
often
as
well
as
IRC.
D
So
that's
I,
I
personally
think
that
should
be
the
highest
priority
at
the
moment
to
get
the
user
documentation
on
up
to
a
level
where
people
can
actually
jump
in
and
start
using
it
developer.
Documentation
goes
deeper
into
all
of
that
and
includes
all
the
sub
modules
that
you
know
like
Jays
idea
this
use,
but
currently
yet
we
just
need
to
be
able
to
get
people
to
use
the
modules
past.
I
Freedom,
so
is
it
as
limited
2jsi,
PFS
I
definitely
agree.
This
is
a
problem
in
jest
IP
address,
but
I'm
wondering
if
this
is
not
a
product
problem.
So,
for
example,
who
is
this
problem
it
does
is
probably
exists.
Also
in
the
multi
format
modules.
Does
this
probably
exists
for
go
I
give
s?
If
so,
how
strongly?
Because
it
exists
there,
how
important
is
it.
H
I,
don't
think
it's
important
to
separate
the
the
kind
of
documentation
that
we're
talking
about
in
the
three
different
categories.
Basically,
first,
you
would
have
my
a
tutorial
like
a
quick
start
kind
of
like
how
go
IP.
Offense
is
doing
it
at
the
moment
with
the
examples
super
good
to
get
started
on
like
get
a
feel
for
how
the
tool
is
working,
but
then
also
have
like
diets
like
how
do
you
actually
build
things
by
using
this
tool
like?
H
Where
does
it
help
you
and
then,
of
course,
in
the
end,
you
would
have
like
a
reference
guide
for
people
who
already
know
what
they
are
trying
to
do,
so
they
can
just
jump
in
get
right,
information
on
and
continue
working
so,
and
I
feel
that
guy
is
missing
in
basically
every
single
project.
There
are
good
contributing
guidelines
like
what
somebody
calls
the
developer
guide,
but
for
the
people
that
is
actually
going
to
use
these
kind
of
things.
There
is
not
much
except
the
tests
we
have
in
the
source
code
currently.
B
B
Most
engineers
are
not
necessarily
deeply
familiar
with
all
these
topics,
there's
sort
of
a
baseline
of
reference
material
that
we
I
would
like
to
create
that
establishes
basic
language
around
things
like
Merkel
tags,
things
like
the
way
we
approach
networking
the
way
we'd
like
what
we
mean
by
pub
sub,
because
then
that,
then
you
don't
have
to
re-explain
those
things
in
all
the
other
documentation
with
like
if
we
come
up
with
a
baseline
of
it.
Good
explanations
for
these
things
are
good
link
links
to
good
explanations
of
those
things.
B
B
H
E
I
Thing
to
note
on
this
is
there
a
lot
of
product
like
services
out
there,
for
example,
have
api's
in
different
languages,
and
there
is
like
this
theme
where
you
have
the
general
explanation
of
this
is
what
this
method
does.
This
is
how
it
works,
and
then
you
have
like
a
small
pouch
that
is
language
specific,
and
you
have
like
a
selector
which
you
should
choose
like
I'm
interested
in
je
s,
I'm
interested
in
go
I'm
interested
in
PHP
right.
I
Then
you
get
examples
and
exact
call
definitions
for
that
language,
in
line
with
the
rest
of
the
gerund
documentation,
which
is
language,
agnostic
and
I,
can
see
that
happening
for
I
PFS
as
well
as
Matt
mentioned,
there's
a
lot
of
things
that
need
to
be
explained
which
are
independent
of
the
language.
It
also
gives
a
good
way
to
make
sure
people
know
what
is
there
in
some
languages,
for
example,
that
one
fee
you
can
pull
one
feature.
You
click
on,
go.
H
I
B
A
D
I
would
like
to
add
that
I
think
getting
some
documentation
to
get
started
and
again
I'm
talking
about
mainly
the
JavaScript
side
of
things,
but
we're
losing
people
because
they
can't
use
it.
They
can't
figure
out
how
to
use
the
stuff
even
looking
at
the
tests.
They
have
a
fine
hard
time
to
find
what
they
need.
So
I
think
there
needs
to
be
a
sense
of
urgency
here,
arm
and
separate
that
from
like
how
we
do
it.
D
Ideally,
because
that's
going
to
take
a
lot
of
time,
I
would
like
to
see
something
next
week
to
fix
this
or
address
this
issue.
We
can
always
improve
on
that,
but
like
if
the
starting
point
is
that
bad,
that's
that's
something
we
should
put
on
a
very
high
priority
in
the
whole
process
of
doing
this.
So.
B
Then
so,
then,
with
that,
let's,
let's
actually
ship
to
look
at
just
process,
it
was
web,
isn't
I,
have
hearing
the
agenda
community
process
or
on
documentation,
but
let's
talk
about
just
the
overall
process
around
documentation,
so
one
thing
I
would
throw
in
at
the
at.
The
top
of
that
conversation
is
creating.
Documentation
is
one
of
those
things
where
some
of
the
documentation
has
to
be
written
by
people
who
are
deeply
knowledgeable,
but
also
a
lot
of
the
like
the
grunt
work
of
documentation
is
a
great
thing
for
newbies
to
do
so
figuring.
B
Something
out
and
writing
down.
Here
are
the
things
I
had
to
do
in
order
to
make
it
work
and
then
I,
especially
if,
for
example,
you
do
that
in
more
of
a
partnered
way
right.
So
whenever,
whenever
someone
appears
asking
questions
on
any
of
these
repos
or
on
on
IRC,
to
respond,
saying
hey,
we
want
to
make
better
documentation.
Are
you
interested
in
helping
and
and
if
they,
if
they
take,
that
on,
to
follow
up
with
them
and
help
them
create
the
documentation,
Lars
I've.
E
Brought
this
up
a
couple
of
times
already
there's
a
kind
of
a
social
contract
around
community
documentation
called
wwtf,
em
read
the
manual
and
it's
basically
what
you're
describing
whenever
somebody
comes
on
and
asked
a
question,
a
question
and
somebody
steps
up
willing
to
help
out.
Then
you
and
kind
of
a
agreement
that
one
of
one
of
the
two
provides
knowledge.
Well,
the
other
documents
it
and
rides
it
up
somewhere.
Yes,
I.
B
B
I
think,
in
addition
to
that
approach,
you
also
need
a
commitment
from
the
maintainer
that
sometimes
you
do
have
to
actually
write
documentation
and
on
top
of
asking
asking
country
like
outside,
like
newbies
and
people,
to
write
documentation,
but
I
have
to
reread
it
to
remember
what
my
other
feedback
was
good.
One.
I
I
Like
if
I
want
a
social
contract,
saying
people
like
please
I'm
explaining
something
to
you,
please
document
that
man
there.
It
needs
to
be
very
clear,
very
simple:
to
write
the
documentation
toward
somewhere,
get
it
reviewed
from
someone
who's
knowledgeable
and
then
merge
it.
And
ideally,
the
merge
will
be
a
deployment
to
a
website
it
without
any
more
changes
because
that's
like,
if
you
don't
make
it
easy,
there
are
so
many
barriers
that
it
doesn't
have
so.
A
That
case,
it
might
be
good
to
overhaul
IP
/
/
examples,
because
right
now,
it's
kind
of
confusing
whether
it
goes
to
the
website
or
not,
and
how
we
do
that
and
how
we
pin
it
Lars.
Maybe
you
guys
should
sit
down
and
just
figure
out
if
we
can
make
a
really
simple
easy
guide
in
the
roomies
and
make
it
very
clear
to
everyone
going
back
like
this
works.
This
way,
that's
just
one
thing:
I
had
something
else:
Oh
Matt,
it
might
be
good
to
for
wtfm.
A
E
B
K
B
Okay,
I
I
would
in
it
in
response
to
the
technical
point.
Yes,
I've
been
watching
the
time
based
on
conversations
before
this
call.
I
know
that
pretty
much
everyone
feels
pretty
strongly.
The
documentation
should
be
a
big
priority
and
developer
experience
should
be
a
big
priority
for
the
for
q4.
That's
why
I
let
it
have
more
breathing
room
on
this
call
I
and
having
this
record,
that
we
are
all
clearly
caring
about
it
and
thinking
about
it,
I
think,
is
really
valuable
to
be
putting
out
there.
So
so
yes,
but
you're
right,
we
should.
K
Was
my
comment
just
let's
probably
use
the
word
overhaul
when
we
really
mean
dramatically
change
and
like
rethink
from
scratch,
because
I
think
you
may
mean
improvements,
and
at
least
in
my
mind
you
it's
it's
a
very
different
amount
of
effort
to
try
it
overhaul.
Something
completely
just
want
to
be
clear
in
that,
because
that
something
is
doing
it
overhauling
and
some
other
things
down.
Thank
you.
B
Poor
all
right
so
then,
the
other,
the
other
things
we
have
on
this
list
at
which
we
can
maybe
drop
some
a
community
process
in
general
I
want
a
couple
things
I
wanted
to
say
to
that
I
PFS
blog,
an
IP
of
his
pages,
might
women
feel
to
push
I
PFS.
Cluster
of
private
networks
are
both
very
important
for
us
to
discuss
on
this
call
I
and
then
generally
p
is
a
minute.
Winco,
an
IP
of
esberg
go
a
JavaScript
that
is
definitely
going
to
be
covered
in
the
other
in
the
project
specific
calls.
B
So
we
might
not
need
to
cover
it
here
so
about
community
process
in
general.
I
simply
wanted
to
give
voice
to
the
fact
that
we're
giving
a
lot
of
thought
to
community
process
and
we're
definitely
aware
of
we
want
to
have
more
people
participating
in
these
calls
for
this.
For
these
calls,
we
we
tried
to
put
out
a
call
for
people
to
participate
in
these
roadmap
calls,
but
those
invitations
sort
of
went
out
pretty
late.
B
The
main
thing
I
would
want
to
personally
want
to
communicate
to
the
community
of
contributors
and
adopters
is
that
this
is
a
we're
making.
This
shift
to
being
even
more
consistent
about
openness
and
inviting
people
to
participate,
and
in
the
future
we
will
be
putting
out
those
invitations
more
clearly
and
further
in
advance
and
we're
still
sort
of
learning.
For
example,
we
didn't
realize
that
this
call
what's
going
to
require
everyone
to
join
zoom
to
even
watch
the
call
I.
C
B
You
kuba
I,
so
does
anyone
have
anything
to
say
on
this
topic
of
community
process?
I
know
that
the
people
protocol
labs
people
are
going
to
be
discussing
this
amongst
ourselves
in
the
coming
week
about
how
we're,
however,
engaging
and
what
we
can
do
to
improve
community
process.
It's
there
anything
we
want
to
discuss
now
on
this
call.
I
I
B
Anything
else
on
that
that
topic
that
people
wanted
to
flag
alright.
So
if
people
won't
have
ideas
or
comments
or
questions
on
that
added
to
the
ticket,
the
fritos
going
to
link
to
from
the
sprint
page,
can
we
skip
the
IPF
s
blog
and
I
PFS
pages
stuff
on
this
all
right,
I,
so
I,
PFS
cluster
is
something
that
is
important.
I
have
a
sense
that
it's
on
on
developers
radar.
It
could
people
speak
to
that
since
I
think
it
won't
get
much
discussion
in
the
project
specific
calls
today.
K
One
yes,
I
think
a
Ivanov
cluster,
it's
one
of
the
most
important
things
for
anyone
who
wants
to
do
large-scale
archiving
of
data
so
as
soon
as
you
cross,
the
maybe
even
five
gigabytes
out,
they
may
even
smaller,
and
certainly
you
wanted
from
replication,
so
I
think
the
service
in
a
super
important
tool
for
a
ton
of
groups.
Anyone
who
wants
a
serious
that
use
had
requested
backup
stuff,
and
so
we
have
some
initial
design
of
it
going,
and
we
have
some
bunch
of
thoughts
and
a
certain
amount
of
energy.
K
We
did
some
amount
of
working
in
into
this
last
quarter,
but
it
was
a
lot
very
preliminary
and
it
was
mostly
getting
like
the
harnessing
around
the
project
getting
started,
so
the
design
is
roughly
there.
The
harness
is
roughly
there.
We
actually
need
to
like
build
the
thing
like
the
bulk
of
or
the
comido
building.
Epicness
Buster
still
needs
to
be
done.
There's
a
certain
amount
of
designs
to
left
around
the
interface
so
like
the
porcelain
to
ipss
cluster,
the
plumbing
is,
is
figured
out
to
some
degree.
K
The
implementation
of
plumbing
is
not
yet
figured
out,
and
so
it
really
is
like
the
core
data
structures
or
the
core
a
way
that
it
will
work,
which
is
a
really
hard
part,
is
figured
out,
but
it
needs
a
lot
of
work.
This
is
something
that
we
could
invest
into
this
quarter,
but
realistically
it
is
a
lot.
K
K
Also
interesting
this
from
other
groups,
there
is
a
couple
people
at
consensus
and
other
organizations
who
want
to
dedicate
a
bunch
of
time
until
it's,
and
so
like
one
person
is,
can
be
dedicated
to
work
on
the
six
just
a
matter
of
us
spending
up
working
on
that
very
regularly,
and
so
that's
kind
of
where
it's
at,
but
it
is
increasing
importance
and
yellin,
along
with
private
networks.
Both
are
critical
for
this
beast
in
organizations.
K
Private
networks
is
the
point
of
being
able
to
set
a
set
of
ibanez
nodes
that
only
talk
to
each
other
or,
in
some
cases
talk
to
the
rest
of
the
network
as
well,
but
have
a
clear
distinction
of
content
that
could
only
be
distributed
in
depth
I
the
network.
So
this
is
something
analogous
to
be
pms
in
the
now
in
the
straight
transport
world,
but
this
is
about,
like
think
of
it,
like
a
VPN
put
content,
and
so
you
can
either
be
in
a
completely
private
network
and
you
don't
have
to
dress
the
world.
K
This
is
something
that
a
lot
of
our
bigger
biggest
users
really
want
to
be
able
to
run
their
application,
a
couple
of
their
own
networks
and
not
have
to
worry
about
the
rest
of
the
network
over
time.
Those
networks
could
be
like
what
BP
answered
today,
which
is
mostly
separated,
but
not
completely
air
lot,
so
that
you
can
have
some
amount
of
content
going
through
that
is
meant
to.
There
is
one
really
easy
way
to
set
up
the
simplest
version
of
private
networks,
which
is
just
giving
you
the
ability
to
separate
into
your
own
network.
K
K
We
need
to
think
a
lot
more
carefully
about
how
that
would
work.
What
how
people
would
you
say,
pki?
How
authentication
would
work,
how
the
revocation
story
works
and
all
this
kind
of
stuff
I
think
that's
stuff.
That
is
definitely
in
a
road
map.
It
just
not
doesn't
really
have
a
date.
Yet
so
it's
it's
stuff
that
we
know
we
want
to
do.
But
it's
not
stuff.
It's
is
directly
and
like
slated.
Does
that
make
sense,
I
think.
F
K
Yeah
you're
right:
there's
there
isn't
a
good
spot,
I
think
there's
one
issue
somewhere,
but
there's
not
there's
not
it's
not
very
good.
This
one
I
should
go
out
the
fs,
and
what
this
really
should
be
to
be
a
note
and
make
sure
enough.
If
that's
not,
so
we
should
create
some
space
for
it
that
it
can
go
out
to
sense
that
I,
remember
and
I
can
pull
it
up
and
link
to
link
to
it.
K
Has
the
description
of
bespoke
approaches
these
two
approaches,
like
the
simple
private
network
that
allows
you
to
build
your
own
network
and
it's
not
super
security
kiss
and
in
one
node
rose.
There's
no
replication
story
you,
but
have
to
like
change
the
key
for
everyone
and
then
the
more
advanced
version
of
private
networks
that
allow
you
to
you
know,
have
a
proper,
revocation
sorry
and
also
have
the
ability
to
like
the
part
of
local
networks
simultaneously.
That
is
a
much
more
complicated
thing
that
you
know.
K
It
was
also
described
there,
but
I
would
I,
don't
know
how
what
we
need
to
do.
One
question
remains
to
be
figured
out,
which
is
how
much
does
a
simple
case
buy
into
this
direction
like
how
much
how
many
users
absolutely
require
the
more
complicated
version
and
kind
of
went
right.
So
a
lot
of
users
could
get
by
with
a
simpler
version
for
now,
if
they
know
that
the
more
complicated
version
is
coming
in
a
certain
amount
of
of
times.