►
Description
Notes: https://github.com/ipfs/pm/issues/358#issuecomment-290755009
A
Oh,
finally,
for
the
first
time,
I
managed
to
click
the
record
button,
and
actually
it
was
really
proud:
okay,
so
hi
everyone.
This
is
like
the
last
stand
up
for
this
quarter,
which
happens
to
be
this
print
that
was
converted
to
a
sprint
II
know
of
using
HT
and
rely
to
access
stuff
on
the
browser
we
kind
of
like
try
to
cram
everything
in
one
week
but
see
what
we
got.
A
B
C
D
I'm,
getting
really
close
to
having
the
really
working
so
I
have
the
I
have
the
basic
case
working
with
the
dial
in,
and
the
relating
I'm
working
on
listening
right
now
on,
listen
turn
on
relay
endpoint
or
a
relay
address
and
implement
in
the
I
think
it's
called
onion
dialing,
which
is
probably
the
most
involved
with
the
to
close.
You
know
the
onion
I
think
I
get
the
integration
points
kind
of
figured
out,
I
implemented
it
as
a
transport
itself
as
a
lower
low
transport.
So
it's
it's!
You
know
it.
D
C
I'm
on
that
gsfs
site
does
the
does
the
transport?
When
you
do
a
lot
of
transport,
you
give
it
the
purity
that
you're
dialing
yeah,
okay,
we
on
the
go
side.
We
strict
that
out
because,
like
the
transport
is
agnostic
of
like
what
Pierre
you're
actually
diamond,
like
that
information
doesn't
go
to
that
layer,
so
I'm
trying
to
figure
out
how
to
plug
this.
In
so
what.
D
A
D
C
A
Since
it's
ghost
clarification,
our
transports
do
not
know
what
the
pure
idea
is
in
terms
of
I.
Think
up
like
the
abstraction
of
transport.
It
doesn't
know
swarm,
there's
no
like
swap
when
swaras
calling
the
transport
it
has.
The
pure
info,
like
this
container
of
the
information
of
the
pier
and
that's
like
like
it,
doesn't
go.
It
doesn't
bleed
into
the
transport
abstraction
right,
but
but
yeah
like
in
the
beginning,
like
swarm
as
like.
A
When
was
calling
for
a
sport
with
us
or
not
to
have
access
to
the
pure
info
now
it
s,
because
we
also
want
to
then
register,
which
was
the
multi
other
used
to
dial
at
Pierre.
So
that's
when
we
look
if
it's
connected
or
not,
we
know
which
what
the
other
is
being
used
from
all
the
available
ones,
so
yeah
just
to
clarify
the
transport
obstruction
still
doesn't
have
right
idea.
What.
D
Could
be
ID
yeah,
so
all
the
the
transport
does
is
basically
kind
of
parse.
The
multi
address
expect
all
the
the
circuit
endpoints
and
then
has
that
onto
this
form,
and
this
form
takes
care
of
the
diving
from
there,
so
basically
kind
of
it
wraps
around
for
us
form.
But
yet
what
W
said
basically
I'm.
C
D
A
D
A
D
D
A
C
Be
cool
because
there's
another
person
who's
really
wanting
a
similar
feature,
and
so,
if
we
can
figure
out
a
like
a
good
way,
you
know
privacy
conscious
way
of
doing
this,
then
that'd
be
good
to
make
a
lot
of
people
happy.
So
so
definitely
something
we
want
to
figure
out.
But
it's
kind
of
hard
great.
A
One
of
the
things
that
I
can
be
like
a
first
step.
If
we
have
that
feature
enabled
behind
the
flag,
then
we
can
have
a
bootstrapper
now
that
the
editor
and
like,
if
you
are
dialing
to
the
bootstrapper
nodes,
you
are
already
revealing
yourself
to
the
network.
So
it
might
be
good
for
some
before
a
browser
node
or
for
it.
A
No,
that's
like
really
down
the
hall
behind
a
lot
of
Nats
to
thigh
out
to
a
bootstrapper
and
then
like
to
be
able
to
see
which
nodes
of
wood
strawberries
aisle
two,
so
that
they
can
rely
to
these
other
nodes
that
are
one
up
away,
but
just
the
bootstrappers,
not
the
entire
network.
But
we
can
it's
a
setting
in
the
herbs
issue
as
wide
suggested
on
my
scene.
G
F
C
B
B
B
F
Yeah,
what
the
HD
thing
is
most
things
they're
working
because
they're
pretty
much
for
every
single
thing.
It
just
might
not
be
working
so
I'm,
currently
going
through
writing
more
tests
and
testing
various
things
and
making
sure
things
doing
what
they're
supposed
to
do
and
then
it's
currently
in
isolation,
it's
just
in
the
DHT
module.
So
the
next
step
will
then
be
integrated
into
swarm,
integrated
to
the
PTP
integrated
to
JSI
PFS
and
implement
the
the
high
level
trapping
commands
and
and
all-day
integration
start
and
then
do
interrupt.
F
C
F
A
F
F
F
F
B
F
G
H
A
Okay,
my
update,
if
someone
can
help
me,
take
that
one
I've
been
like
working
on
all
the
like.
So
like
freedom
as
prepare,
this
issue
that
I
a
week
on
the
notes.
It
is
like
a
comprehensive
list
of
all
the
things.
I
don't
need
to
happen
for
tht
freedom
has
been
doing
all
the
hard
work
inside
the
core,
mojo
and
I,
can't
drop
tests,
and
so
on.
A
Well,
I've
been
like
kind
of
like
cleaning
the
rest
of
the
pads
for
the
integration
on
swarm
on
pearbook
on
theory
flow
and
so
on
kind
of,
like
we
took
the
opportunity
to
the
redesign.
Some
of
API
is
make
them
simpler,
with
the
result
of
like
having
like
removing
so
much
code
from
so
many
modules,
because
we
repeated
the
number
of
operations,
and
now
we
have
I
just
cleaner
API
is
that
are
more
convenient
for
the
typical
things
that
we
do
everywhere
so
that
led
to
a
lot
of
refactoring
I
started.
A
B
A
Now
you
can
like
start
integrating
digital
I
will
update
now
the
browser
version
and
then
like
foots
a
bit
swap
and
then
just
a
DFS
to
use
these
new
AP
eyes
and
also
to
start
consuming
the
connected
addresses
from
the
ones
that
are
active
on
people.
So
the
thing
that
was
saying
before
in
the
beginning
of
the
call
we
now
register,
which
multi
other
we
are
using
when
we
dial
to
someone.
A
So
we
will
start
printing
the
writings,
the
others
when
we
like
swarm
peers
and
not
like
all
the
others
that
we
know
so
that
will
be
nice
and
also
for
users
and
yeah.
So
that's
what
I'm
focused
after
I
do
this
I
still
I'm,
not
sure
what
is
more
important
if
I
should
like
as
the
way
to
see
recording
to
pearbook
like
if
that's
cool,
be
very
quick.
It's
like
doing
things
like
recording
the
effort
so.
F
F
Okay,
it's
like
so
what
is
important,
though,
what
you
eat
is
connection
closing
we
need
to
close
on
interface
connection
I,
need
that,
because
I
need
to
open,
specifically
diappears
to
check
if
they
actually
can
speak,
DHT
yeah
and
then
need
to
close
that
connection
again
and
that's
going
to
be
a
multiplex
connection.
So
we
really,
we
have
connection
closing.
A
We,
the
only
thing
that
like
doesn't
happen
right
now,
he's
like
when
you
dial
to
like
a
peer,
and
you
have
like
ten
different
multi
others.
If
you
happen
to
like
nail
on
like
two
or
more
sockets,
you
are
going
to
not
close
graciously
one
of
them,
you're
just
going
to
use
one
of
them
and
the
other
ones
will
be
like
lingering
there.
But
connection
closing
happens
like
you
can
angle
your
and
you
can
like
yeah,
but.
F
B
F
F
B
I
A
For
how
you
use
yeah,
if
there's
a
connection
already
open
so
just
like
in
bit,
swap
I
never
like
if
I
open
a
bit
swap
stream
to
you,
a
stream
out
the
connection
like
you
are
not
going
to
send
me
blocks
on
that
one.
You
are
going
I'm
just
going
to
send
you
stuff
and
I
know.
If
you
want
to
send
to
me,
you
open
a
bit
from
swim
to
me
and
what
I'm
asking
is
like
when
I
open,
a
DT
stream
to
you.
A
F
F
A
A
So
yeah,
so
that's!
What's
that's
like
the
idea
I'm?
Having
is
so
you
can
by
default
as
soon
as
a
connection
open
write
a
pawlenty
like
if
you
open
a
connection
to
me,
you
can
write
pool
empty.
So
if
I
want
to
test
you
I
can
like
open
a
connection
and
then
do
PO
empty
and
that
connection
is
wearing
it.
Sorry
that
stream
is
going
to
get
closed,
graciously
always
yeah.
So
we
can.
F
F
A
I
think
is
like
the
clothes.
The
other
thing
is
we
talking
about.
The
clothes
is
more
closing
all
the
sockets
that
were
open
till
them
till
the
socket
level.
So,
like
we
have
this
connection
obstruction,
we
need
to
have
a
closed,
that
propagates
to
the
sockets
that,
like
causes
destroying
on
the
circuit
or
whatever
method,
is
called
on
that
transport.
We
basically
need
to
provide
to
the
interface
transport
to
have
that
method
defined
so
that
every
transport
implements
it,
and
so
on
that
that
it
was
perceived
very
much
so
so,
let's
take
this
one.
A
F
A
F
A
F
It
cannot
be
stopped,
I
I
didn't
make
it
so
that
it
doesn't
throw
up
when
the
p2p
gets
stopped.
So
in
theory
you
should
it
should
be
enough
to
just
stop
the
p2p
and
the
deal.
She
will
not
be
able
to
do
anything
with
network
anymore,
which
is
sad,
but
it
should
what
cannot
eat
ever
stop.
It
could
have
a
stop.
I
just
didn't
do
one.
Can
we
have
one
because
I
also
didn't
start,
do
a
start
one.
We
actually
need
one.
A
A
Fs
level,
where
you
you
need
to
call
provide
explicitly
if
you
had
something
what
I
mean
is
like,
should
there
should
be
an
options
that
gets
passed
through
peer-to-peer
to
activate
or
deactivate
the
routing
and
I?
There
should
be
also
something
that
gets
exposed
like
to
to
enable
and
disable
that
and
like
why
not
like
Davichi
is
chatty
enough
and
like
like.
F
A
F
I
F
A
F
A
Is
there
any
outstanding
questions
that
people
would
like
to
see
answered,
or
is
there
any
information
it?
Okay?
Does
everyone
feel
that
their
time
was
well
spent
in
this
call?
Was
it
useful
so
awesome,
okay,
so
I
have
a
great
rest
of
your
day
or
a
great
day
if
you
are
starting
your
day
and
enjoy
your
weekend
and
let's
get
this
ship
so
close.
D
H
A
Okay,
so
trying
to
not
get
distracted,
be
trying
you
feel
free
to
continue
play
so
yeah
next
week.
As
you
know,
we
have
like
this
lively
thing
where
we
spend
a
lot
of
time
talking
and
preparing
a
discussing,
and
so
I
cannot
promise
me
or
Friedel
or
Jaime
or
whomever
to
like
review
extensively
all
the
code
I
like
if
relay
and
each
TRT,
where
we
have
like
tests
and
tests
and
tests
and
like
we,
we
try
it.
We
we
check
out
the
latest
the
wrenches
and
every
good
thing
works.
Super
fine.
A
B
F
B
B
B
A
F
Super
cool,
yeah
super
cool.
One
more
thing:
do
we,
you
asked
what
you
could
like,
where
you
could
do
stuff
the
public
facing
API
of
the
DIA
she's
pretty,
and
if
you
look
at
it
yeah
it
should
be
its
tribute
all
documented.
So
what
you
couldn't
do,
starting
it
work
on,
is
the
correct
the
methods
in
Jason
cthis,
so
the
CLI
and
the
core
methods
yeah.
F
A
F
A
I
was
like
I,
don't
know
like,
for
example,
I,
don't
know
how
much
of
the
sharpness
has
changed
in
go
ipfs,
because
we
don't
have
them
in
a
separate
repo.
It's
like
do
I
need
to
keep
like
pulling
them
down.
Another
thing
like
if
my
PFS
keeps
realizing
this
way
like
we
need
to
automate
the
process
of
like
updating,
ipfs
diamond
controller
and
like
pushing
just
ipfs
api
with
a
new
version,
because
I
ain't
nobody
got
time
to
like
be
doing
that
manually
every
two
weeks.