►
A
B
So
the
best
0.7
did
not
get
out
last
week,
but
it
is
almost
there.
I
know
I
know.
Actually
I
mean
all
of
the
all
the
release
stuff,
all
of
like
the
things
that
we
needed
to
investigate
all
sort
of
turned
out.
Fine
just
needed
to
actually
go
through
the
process
of
doing
the
release.
B
If
fans
was
on
the
call,
I
was
gonna
ask
him
to
look
at
the
orbit
db
test,
but
oh
well,
the
time
has
come
and
gone
so
off
to
the
release
we
go
and
that
should
be.
That
should
be
coming
out
quite
soon.
C
Spec
itself
and
kicked
off
supporting
js
http
client,
which
will
be
using
new
pin
remote
commands
from
work
in
progress,
pull
request
in
go
ipfs.
I
think
we
need
to
like
wire
up
config
and
figure
it
out.
The
way
a
config
will
be
up
like
updated,
like
how
we
add
and
remove
pinning
services
if
it
will
be
possible
to
like
modify
like
specific
one
in
the
way.
That's
just
like
an
array
of
objects
in
the
config.
C
B
Yeah,
I
think
so
we
have
has
anyone
reached
out
to
matt
about
regenerating
the
code
on
his
end
with
the
newest
specs.
C
B
I
think
that
the
we're
gonna
probably
need
a
dedicated
command
is
my
guess,
because,
basically
because
the
secur,
because
the
api
keys
are
effectively
as
sensitive
as
symmetric
keys,
you
need
to
guarantee
they're
not
getting
sent
to
the
wrong
place
and
so
changing
the
name
is
an
attack
vector
where
the
name
where
the
the
key
gets
sent
to
the
wrong
place.
B
D
B
Yeah,
well,
it
just
means
like
if
I
rename
you
know
your
pinning
service
from
alex,
you
know
alex's
pinning
service
and
to
alex's
pinning
service
back
up,
and
then
I
make
a
new
one
and
call
it
alex's
pinning
service
right
like
I
can
like.
I
can
like
change
the
names
around
so
that
when
you're
sending
to
me
you're,
actually
sending
me
like
a
different
key
than
you
meant
to
so
we'll
just
have
to
make
that
not
a
thing
that
you
can
do.
That's
it's.
A
B
D
Done
yeah
picking
there
that'll
all
go
out
without
seven
release
and
then
on
the
js
ipfs
side
of
thing.
I
opened
up
a
pr
today
to
remove
that
everywhere,
so
that
can
just
go
out
whenever
we
do
the
next
minor
release.
B
B
A
Definitely
she
was
no
last
update
this
week.
E
Yeah
I
so
the
after
relay
is
still
in
progress.
The
initial
implementation
got
merged
last
week
in
the
0.30
range,
which
is
a
branch
for
the
jsonptp
feature
release
the
milestones.
23
are
ready
for
reviewing
we'll
review
them
this
week.
They
include
the
network
update
to
inform
the
other
peers
using
an
identified
push
that
we
have
now
a
new
listening
address
that
people
could
use
to
reach
to
us,
and
I
also
needed
to
update
the
self-signed
peer
records
to
being
basically
recreated
with
the
new
address
and
the
thermal
sound.
E
Basically,
when
we
don't
have
in
enough
relays
to
listen
on
according
to
how
user
configured
the
liberty
we
can
try
to
find
them
on
the
on
the
network
using
by
now
only
b2b
content
routing.
So
in
ipfs
people
would
basically
use
the
delegates,
as
we
still
don't,
have
the
dhc
enabled
by
default.
But
I
plan
to
also
offer
the
next
week's
follow
up
this
with
rendezvous
integration.
E
And
with
this,
the
plan
is
to
basically
have
the
lpgp.discovery
api
and
basically
we
would
go
to
rendezvous
to
find
it
through
the
delegates
in
the
future
through
dht
and
the
goal
is
to
find
remote
relays
and
other
services
that
we
will
eventually
need
yeah
and
basically,
the
last
step
for,
for
the
auto
relay
part.
E
It's
to
don't
do
don't
announce
the
private
addresses,
which
is
a
problem
that
we
already
have,
and
usually
we
have
people
creating
issues
saying
that
we
have
warnings,
for
example,
in
the
browser
saying
that
we
are
trying
to
dial
to
local
addresses
in
the
browser
which
it's
basically
because
other
peers
are
advertising
them,
as
listening
addresses
that
people
should
be
able
to
dial,
which
is
not
the
case.
So
basically,
we
will
need
to
know
that
we
have
the
auto
relay
to
get
rid
of
this
issue
yeah
and
finally,
regarding
the
connection
manager.
E
Overall,
I
started
last
week
by
creating
a
document
with
the
baseline
for
discoverability
and
connectivity
for
each
environment
and
use
cases
not
all,
but
basically
a
start
in
the
goal
year
is
basically
to
understand
what
are
the
important
connections
for
a
peer
in
each
use
case
and
environment,
and
with
that
try
to
find
strategies
for
a
more
intelligent
connection
manager
in
js,
where,
basically,
we
need
to
understand,
for
example,
the
author
real-life
connections
that
we
are
buying
to
it's
really
important
that
we
cannot
disconnect
that
peer
and
we
need
to
find
all
these
peers,
for
example,
the
peers
that
we
share
topics
of
pub
sub
and
protect
all
these
connections
automatically
and
yeah
basically
find
this
kind
of
strategies
and
yeah.
A
I'm
going
to
want
to
improve
like
so
something
that's
not
implemented
in
json
conversion
with
sessions
in
blitzwell,
so
I
think
there
would
be.
I
guess
we
end
up
treating
it
similar
to
like
pops
up
here,
because
you
have
like
groups
of
peers
that
you
want
to
have
like.
E
Yeah,
one
of
the
things
that
I'm
considering
in
this
baseline
is
the
application
level
protocols
that
use
the
multicollect,
topology
and
bitswap
would
be
in
that
category.
E
I'm
we
are
still
aligning
like
how
involved
she
has.
The
ptp
would
be
in
the
car
side
if
it
would
basically
be
intelligent
enough
to
just
protect
everything
or
if
we
should
guide
people
on
who
build
protocols,
and
now
they
should
protect
the
peers.
That's
some
of
the
things
that
we
need
to
polish.
While
we
implement
it.
I
think.
A
B
But
I
recommend
that
if
and
when
you
do
implement
sessions
that
you
allow
there
to
be
some
sort
of
context
about
how
the
query
was
made
or
like
the
evolution
of
the
query,
one
thing
that
we
would
like
to
do
and
go
is
be
able
to
figure
out
like
more
stuff
about
the
graph
as
part
of
the
session,
so
that
you
could
stop
providing
every
single
block
and
instead
provide
you
know,
roots
or
files
and
directories
or
just
logarithmically
blocks
down
the
tree
every
so
often
right,
something
that
is
not
as
much
as
just
every
block.
B
And
in
order
to
do
that,
we
need
more
context
about
the
query
than
just
I'm
asking
for
a
block.
So
we
have
the
legacy
of
trying
to
like
figure
out
how
to
plumb
all
these
things
through.
But
if
you
guys
are
starting
from
scratch,
something
to
keep
under
advisement.
D
I
invited
several
people
here
to
it
on
friday,
but
if
you're
not
on
that,
let
me
know
and
I'll
add
you
to
like
a
beyond
bit
swap
research
discussion,
because
the
resident
lab
team
is
working
on
beyond
bit
swap
so
what
the
future
of
the
bit
swap
or
block
swapping
looks
like.
So
that's
on
friday
to
just
what's
the
state
of
that
research
where's
the
project
going
solicit
feedback,
so
this
could
be.
D
I
don't
know
if
that
will
be
a
full
replacement
or
not
for
bitswap
or
an
amendment
to
that.
But
that
could
be
something
that
we
we
look
at
in
lieu
of
going
through
the
process
of
adding
sessions
to
js.
A
Okay,
that's
the
end
of
the
high
priority
initiatives.
Moving
on
to
other
initiatives.
F
I
crossed
it
out
I'll
take
that
off
the
list,
because
I'm
not
spending
much
time
on
it
so
once
I'll
actually
start,
then
I'll
put
it
back
on
the
list.
The
next
one
is
also
mine.
Improving
web
ui
file,
let's
sing
so
a
lot
of
stuff
has
already
landed
last
remaining
piece
that
I'm
working
on
is
actually
doing
the
ui
piece.
So
it
will
let
you
know
how
it's
progressing.
F
I
also
found
out
that
maybe
the
progress
handler
was
there.
So
all
of
the
patches
that
I
wrote
for
the
update
and
download
progress
was
not
necessary,
so
I
think
I
might
close
those
pull
requests,
but
good
news
is,
we
won't
have
the
we
wanted
the
complexity.
F
The
next
one
up
is
also
mine,
which
is
typescript
integration
so
for
ipfs
there's
a
pull
request
that
is
running
on
alex's
review.
I'm
gonna
do
the
update
of
that
pull
request,
but
the
middle
of
it
will
be
the
same
mostly
to
propagate
some
changes
that
happen
in
the
meantime.
F
F
It
just
generates
types
separate
from
the
tree
and
tells
typescript
where
to
look
for
them
and
then
there's
a
older
pull
request
from
hugo.
That
does
a
doc
generation
from
the
types
and
I
forgot
exactly
what
few
other
things
so
I'll
be
splitting
up
those
into
separate
tasks
and
lend
them
one
by
one.
F
Once
we
have
a
ipfs
type
generation
working
I'll,
probably
go
on
and
try
to
add
the
similar
mechanism
to
other
recalls
as
well
and
take
the
learnings
that
we
get
from
there
so
except
expect
pull
requests
there.
Part
of
the
reason
is
also
like
for
ipfs
to
generate
meaningful
types.
It
should
be
able
to
understand
the
dependencies
pulls
in
so
if
flippy
t2p
is
not
typed
and
none
of
the
ipld
is
typed
and
it
can't
really
make
much
sense
of
it.
Yeah
so
through
that.
F
Yes,
I
think
some
of
the
same
people
did
some
minutes
original
pull
requests
to
typescript
as
well
to
ipfs
as
well
with
some
types
so
yeah.
I'm
I'm
definitely
going
to
try
to
leverage
as
much
as
I
can
on
the
community
and
I'm
aware
of
many
people
who
are
interested
in
that
too.
A
Cool,
I
wanted
to
add
a
couple
of
things
into
the
other
initiatives
so
stuff
I'm
working
on.
So
one
thing
is:
I'm
trying
to
decompose
the
icfs
module
a
little
bit,
so
I'm
spread
out
the
cli
and
the
http
api
server,
and
I
mean
what
is
kind
of
a
cool.
A
The
idea
being
that
you
can
just
require
the
core.
You
don't
have
to
like
go
through
the
installation
of
all
the
dependencies
for
the
cli
and
the
http
api,
which
you
usually
don't
need,
because
that's
kind
of
something
that
people
complain
about
quite
a
lot
and
then
so.
That's
kind
of
why
I
haven't
got
to
the
touchscript
stuff
yet
because
I've
been
moving
on
so
far
as
well.
A
But
that's
what
nearly
almost
done-
and
I
went
on
an
epic
side-
quest
to
kind
of
bring
npm
on
my
professor
today,
so
that
we
could
run
the
go
profess.
2.7.
A
Another
test
against
guy
progress,
9.7,
which
entailed
bringing
the
icfs
npn
registry,
mirror
up
to
date
because
it
shares
a
whole
bunch
of
the
code
which
has
been
interesting
and
I
was
exposed
to
the
misty
v8
still
welcome
because
it
cools
through
into
the
noses
tp
module,
which
requires
either
buffers
or
strings
to
be
sent
you're,
not
using
aos,
which
is
mega
tedious
clearance.
Unfortunately,
that's
different.
A
A
Cool
that
is
it
for
the
other
initiatives.
B
No,
I
just
there
is
there,
is
you
know,
someone
poked
at
like
one
of
the
the
old
go
ipfs
issues
for
moving
the
pins
into
the
data
store?
I
suspect
we're
going
to
taking
a
similar
approach
to
what
you
did
in
jessakifas,
but
I
think
it
might
be
worth.
B
I
don't
know
if
it's
going
to
be
this
this
week
or
next
week
would
be
better
but
discussing
how
we
want
the
pinning
to
look
in
light
of
some
of
the
changes
to
in
light
of
the
work
vital
has
done
on
the
pinning
services
api
in
particular
around,
like
you
know,
named
pins
or
having
multiple
pins
that
target
the
same
cid
and
like
what
might
be
an
appropriate
way
to
manage.
All
of
that,
I
don't
think
this
week
is
going
to
be
the
time
for
that,
but
maybe
next
week.
F
D
I
think
there's
like
there's
like
the
the
short-term
data
storage
thing
and
then
there's
like
a
long-term
just
moving
pinning
completely
over
to
threads,
but
I
think
that
is
going
to
require
a
much
much
larger
conversation.
But
is
there
something
that
we
can
do
in
that
interim?
That
gets
like
that
pinning
performance
improvement
for
the
the
pinning
services
so
that
they
can,
you
know,
just
improve
performance
on
their
systems
until
we
get
to
the
the
thread
thing
or
whatever
that
ends
up
being.
B
I
suspect
that
the
big
question
will
just
be
like
for
now
I'll
just
be
like
what
is
the
thing
to
be
the
primary
key?
What
is
the
correct
thing?
Is
it
like
a
cid
or
a
name
or
some
uuid,
and
then
once
you
have
that
figuring
out?
Okay,
what
do
you
want
to
do
in
the
cases
where
you
want
to
you
wish
the
primary
you
know
key
was
something
else.
B
F
Thanks
for
explaining,
I
have
one
section
I
want
to
mention
so
in
jazz
projects
we
used
to
or
still
use
azure
to
do
the
eslinting,
but
there
were
the
problems
that,
if
you
just
clone
a
project
and
start
it
vs
code
and
other
tools,
would
assume
other
formatting
rules
and
what
eslint
assumed,
because
they
look
for
eslint
config
and
if
it's
not
theirs,
then
if
they
just
go
with
a
generic
sync,
I
think
so
with
there's
a
pluricos
for
ipfs
that
I
don't
think
has
landed
yet
and
put
and
succinct
in
asia
landed,
which
is
we
have
now
shareable
config
for
eslint
that
azure
uses.
F
So
we
could
just
add
one
liner
to
every
repo
saying
that
extends
ipfs.
And
then
all
the
tools
would
be
aware
of
what
the
config
should
be
like
and
hopefully
create
a
better
experience,
so
I'll
be
adding
some
of
that
to
other
repos
and
would
encourage
others
to
help
me
with
that
too.
G
Yeah
right,
so
I
have
some
code
sitting
around
that
looks
through
every
repo
in
a
a
user
or
org
and
looks
for
a
file
and
then
sees
if
it
matches
the
file
that
I
have
locally
and
then
replaces
it.
If
it
doesn't
using
my
github
token,
I
use
it
to
update
all
of
the
github
action
workflows
whenever
there's
a
change,
because
I
have
like
50
repos
that
all
have
the
same
workflow.
G
So
if
you
want
to
borrow
that
code,
it
might
be
like
a
reasonable
script
to
just
go
and
change
all
of
these,
but
it
it
just
overwrites
the
file.
It
doesn't
like
open
a
pr
or
anything.
So
I
don't
know
if
you
want
to
be
that
aggressive.
F
F
Oh
another
thing
alex,
so
we
did
publish
the
fork
of
basics
based
on
your
pull
request
in
multiformat's
namespace
or
whatever
the
scope
can
we
should
we
update
the
js
ipfs.
I
think
something
was
blocked
on
basex
right.
Maybe
we
should
use
that
forks.
There.
A
Yeah
multi-base
depended
on
basics.
F
Arrive,
it's
already
done,
you
mean,
or
he
released
release.
It
doesn't
include
it.
A
Yeah,
unless
it
depends
on
it
directly
but
like
so
so,
the
next
release
will
put
it
in
to
the
browser
bundle.
It
you
know
built
the
minified
version.
A
Great
thanks
cool
questions.
D
I
shared
the
okr
sheet
so
fill
it
out
we'll
meet
on
thursday
to
verify,
but
add
all
your
thoughts,
please
we're
going
to
try
to
solidify
that
this
week.
A
That's
that,
then,
thanks
for
coming
everyone,
this
has
been
my
professional
invitations
represent
for
monday,
the
21st
of
september
2020.
Please
please,
seek
updates,
be
safe,
see
you
on
the
internet,
bye.