►
A
Hi,
everyone
welcome
to
the
first
core
implementations
weekly
sync.
On
monday,
the
12th
of
october
2020..
I
am
aiken
brain.
I
will
be
your
host
we're
going
to
go
through
our
high
priority
initiatives,
now
other
initiatives
and
then
questions
parking
lot.
Q,
a
all
that
good
stuff,
so
to
kick
this
off
we're
going
to
talk
about
upcoming
ship
releases.
So
what
is
upcoming.
B
A
Incredible,
there's
a
there's
going
to
be
a
json
previous
release.
I'm
now
like
working
full
time
on
trying
to
get
iraqi's
typescript
stuff
over
the
line
with
him
and
as
soon
as
that's
end,
we
will
ship
a
release
which
will
include
the
deprecation,
no,
the
removal
of
secular
as
well,
so
that
should
hopefully
be
up
this
week.
B
B
We
had
a
meeting
to
discuss
local
and
remote
pinning
like
cli
and
http
api.
I
put
a
link
in
which
has
sort
of
my
summary
of
where
I
think
I
conclude
where
our
conclusions
were
jacob
and
lytle
have
already
commented,
which
is
very
helpful.
I
still
have
to
respond
all
that
to
their
very
helpful
comments.
B
B
C
B
Once
that's
out,
we
will
then
fire
a
shot
across
the
bow
by
just
like
turning
off
sekio
on
the
bootstrap
nodes
and
seeing
if
anybody
has
not
been
reading
their
their.
You
know,
github
twitter
discuss
anywhere,
we've
been
yelling
at
them
about
secure
removal
and
then
we'll
get
lots
of
floods
being
like
hey
my
nodes
stopped
working,
at
which
point
we
will
then
say
hi.
Your
note
is,
like
you
know,
over
a
year
olds,
please
update,
there's
a
good
reason.
B
I
guess
related
to
sec
oil
andrew
nesbitt
is
going
to
be.
Do
is
doing
some
analysis
on
the
dht
as
to
who
is
running
these
old
nodes
so
that
we
can
maybe
communicate
with
them
and
help
figure
out
help
them
figure
out
how
we
can
help
them
upgrade,
and
that
is
that
is
ongoing,
which
has
the
benefit
of
us,
making
better
dht
crawling
stuff.
A
E
Yes,
so
the
the
pr
that
I
had
opened
last
week
got
merged
it.
Basically,
now
we
can
find
the
remote
realize
on
the
network
using
content
routing,
and
this
is
merging
the
0.30
branch
for
the
upcoming
release
and
for
finishing
the
outer
relay
stuff.
I
will
work
this
week
on
a
custom,
announced,
filter
function
and
also
a
sorter
in
order
to
allow
us
to
order
the
dials.
E
A
D
Yeah,
so
I
don't
have
a
list
on
the
notes
yet,
but
there's
a
whole
stack
of
requests
to
get
in.
I
got
some
reviews
from
alex.
I
need
to
still
follow
up.
I
think
some
of
the
patches
need
upgrading
because
things
have
landed,
and
now
they
have
merged
conflicts,
because
that
everything
was
green
last
friday.
So
I
think
what
to
remember,
hopefully
soon
the
next
one
is
also
mine,
which
is
typescript
integration.
So
last
week
I
updated
all
the
or
I
guess,
one
pull
request.
D
I
got
another
review
from
alex
that
I
was
just
following
up
so
after
this
call
I'll
submit
the
changes
that
were
requested,
so
hopefully
we
can
land
it
very
soon.
It's
so
close,
it's
so
very
close.
It's
gonna
be
great
by
the
way
alex
if
you'll
have
a
couple
of
minutes.
After
the
call,
it
would
be
really
helped
to
sync
up
on
some
of
the
things
that
were
not
clear.
F
All
right,
so
all
the
work
for
the
actual
support
on
our
site
is
done
other
than
making
sure
that
we've
updated
dependencies
to
what
we
decided
to
go
out
with,
and
the
couple
of
fixes
that
we
require
from
badger
have
not
been
put
into
an
actual
release.
Yet
so
we
need
to
decide
if
we
want
to
wait
on
a
release
or
we
want
to
go
out
with
a
a
specific
commit
and
they
may
they
may
have
some
additional
breaking
changes
that
we
need
to
be
aware
of.
F
So
it's
basically,
we
need
to
decide
what
we
what
and
when
we
want
to
go
out
with
a
particular
badger
version.
Otherwise
we're
good
another
thing
that
got
brought
into
the
badger.
2
changes
was
support
for
batching
so
that
we
are
no
longer
constrained
to
the
limits
of
a
single
transaction
for
high
volume
rights
and
that's
something
that
we'll
get
along
with
this.
This
update
not
specifically
related
to
badger
2
support,
but
it
will
come
along
and
for
both
badger
and
badger.
2.
G
C
Yeah
so
michael
is
trying
to
do
nice.
Things
for
infra
and
js
makes
that
harder
to
do,
because
we
don't
have
dns
at
a
resolution
and
then
that
chain
of
events
kind
of
sucks.
So
normally
our
text
records
include
the
ip
address.
So
if
you
recursively
look
up,
the
dns
addresses
you'll
get
the
ip
address
of
the
node.
C
A
A
Questions
I've
got
a
question
who
controls
the
number
of
travis
runners
that
we
have
anyone
exactly.
Okay,
you
don't
have
to
sacrifice
a
goat
too,
and
I
don't
want
to
sacrifice
to
the
wrong
god
that
would
be
a
disaster.
Another
few
will
work.
It's
going
to
be
terrible.
I
spent
making
ci
faster
right
right
now.
A
The
longest
job
takes
15
minutes
and
everything
is
run
in
parallel,
so,
like
the
whole,
build
would
take
15
minutes
if
we
could
run
them
all
in
parallel,
at
the
same
time,
which
we
need
more
runners
for
which
is
bonkers.
When
you
consider
like
it
wasn't
too
long
ago,
the
jsi
previous
built
two
hours
now
it
takes
15
minutes,
but
it
needs
more
runners
in
order
to
parallelize
it
like
that,
don't
you
laugh
at
dean.
H
H
Well,
I'm
just
wondering
like
if
we
could
get
a
because
so
we're
we're
having
a
long
discussion
in
that
pld.
That's
that's
not
going
to
wrap
up
anytime
soon,
but
basically
moving
everything
to
actions
and
trying
to
standardize
a
lot
more
of
the
build
and
test
infrastructure,
particularly
on
the
go
side,
and
that's
like
a
long
term
thing.
But
this
could
be
something
that
we
looked
at,
but
it
would
be
in
action.
H
H
A
A
G
B
H
That
is
a
good
question
that
I
don't
quite
know
the
answer
to
and
it
may
change
shortly,
but
I
would
ask
daniel
and
eric
about
that
and
if
there's
any
particular
reason
why
you're
asking
I
would
surface
that
as
well,
so
that
they
can
make
sure
that
that
ends
up
in
the
things
that
they're
doing
it's
actually
on
daniel's
plate.
I
think
one
of
his
one
of
his
things
this
quarter
to
work
on
this
so.
B
The
reason
I
was
asking
is
mostly
is
mostly
because
our
circle,
ci
orb,
doesn't
really
play
nicely
with
binaries
that
are
not
go.
Ipfs
libraries
are
all
fine,
but
because
of
like
magic
shenanigans
around
plugins,
it's
like
not
really
it's
causing
some
issues
with
non-go
ipfs
binaries,
and
while
I
could,
while
we
could
go
fix
that
and
go
with
like
go
through
all
of
the
sort
of
al
all
of
the
bash
script,
hacks
required
if
there
was
already
an
action
that
I
could
just
deploy
for
existing
go
ipa
for
existing
go
binaries.
H
Oh
yeah,
no,
that's
that's
happening
like
I
mean
the
the
current
github
action
for
running
go
programs
that
is
just
like
in
the
marketplace,
daniel
wrote
and
he
is
like
he
actually
has
he's
in
the
loop
with
a
couple
people
at
github
who
work
on
actions
to
like
resolve
any
of
his
go
related
problems.
So
you
know
what
whatever
we
end
up
with
at
the
end
of
this.
Well
will
be
that
simple
and
integrated.
I
imagine
okay,
cool.
B
A
A
H
The
sort
of
okr
light
thing,
so
we
took
the
opportunity
to
kind
of
think
about
like
what
would
be
a
better
fit
in
general
for
just
how
we
work
and
surfacing
what
we
do
and
all
of
that.
So
a
lot
like
the
okr
process,
kind
of
has
like
two
sides
to
it.
One
is
that
it's
how
we
communicate
with
the
rest
of
the
org
and
outside
about
a
bunch
of
things
that
are
happening,
and
then
it's
also
kind
of
how
we
do
planning
and
it's
never
really
been
how
ipld
does
planning
we.
H
We
tend
to
be
a
little
bit
more
nimble
than
an
okr
process.
We
we
will
shift
priorities
like
every
week
if
we
need
to
if
a
lot
of
things
are
coming
in
that
are
high
priority,
so
things
just
move
around
a
little
bit
more
and
we
we
like
to
keep
it
a
little
bit
more
fluid
so
yeah.
What
we
did
instead
was.
H
We
came
up
with
a
theme
for
the
quarter,
which
is
protocols
over
projects
and
we're
trying
to
focus
more
on
the
protocol
side
than
we
have
in
the
past,
and
so
there's
a
write-up
about
that.
In
the
team
management
page,
but
there's
also
this
really
cool
list
now
of
everybody
in
our
team
and
then
every
single
priority
item
that
they
have
for
the
quarter.
So
you
know
like
what
they're
working
on
right
now
and
if
something
comes
up,
we
will,
on
that
day
that
that
gets
bumped.
We
will
bump
it.
H
We
will
say
why
it
got
bumped
and
we
will
say
like
now.
This
person
is
working
on
this
because
it's
a
higher
priority
and
also
one
thing
that
we
decided
to
do
kind
of
later
in
the
cycle
was
we
started,
putting
all
of
the
maintenance
burden
that
each
person
has,
because
we
felt
like
that
was
really
not
being
captured
very
well,
and
it
was
not
very
well
appreciated.
H
So
we
started
to
sort
of
add
what
what
different
projects
people
have.
Maintainership
of
that,
we
expect,
like
you,
know,
not
super
frequent
but
relatively
frequent
burden
on
their
time
as
a
result.
So
I
don't
know
now
you
have
kind
of
a
view
of
what
we're
doing
that
we
update
every
week
and
you
can
go
check
that
out
on
the
team
management
repo
in
the
readme
and
yeah.
If
it's,
if
it's
a
format
that
people
like,
I
would
encourage
you
to
try
something
similar.
If
you
want.
A
H
No,
no,
I
I
think
like
look
when,
as
you
know,
the
the
go
epild
prime
stuff
has
reached
like
a
new
stage
of
maturity,
we're
doing
the
hampton
adl
stuff
on
it
now.
There's
some
file
coin
work
that
will
is
doing
that's
going
to
give
us
schemas
for
most
of
the
file
coin,
data
structures,
and
so
we're
going
to
we're
going
to
have
like
a
a
very
new
level
of
maturity
around
globally.
H
Prime,
like
this
quarter,
and
so,
if
you
the
moment
that
you
migrate
to
it,
we
can
stop
maintaining
the
old
packages
and
and
the
same
thing
on
the
javascript
side
too.
Actually,
like
we
gozala
just
finished
up
like
his
last
round
of
revisions
and
I've
just
broken
off
a
bunch
of
projects
to
use
all
the
new
primitives
so
that
I'm
testing
them
out
and
putting
them
through
some
paces
before
advocating
that
other
people
use
them.
H
But
we're
like
really
close
on
that
side
too,
to
just
having
that
that
can
just
be
swapped
out
now
as
well,
and
once
you
know,
ipfs
isn't
relying
on
the
old
apis
anymore,
we're
fine
with
deprecating
them
like
we.
We
already
don't
really
like
to
touch
them,
but
we
do
because
they're
dependent
on
so
yeah
but
yeah
I
mean
that
cycle
is
much
more
dependent
on
you
than
on
us.
H
A
H
Yeah
yeah
and
also
man,
the
the
the
depth
tree,
is
just
going
to
get
way
smaller.
For
you
way
way
smaller
I
mean
the
new
dag
pb
drops
all
of
protoboss
like
we
don't
actually
pull
in
any
of
the
protobuf
dub
tree
anymore,
and
actually
rod
is
working
on
a
new
dagg
seaboard.
That's
native.js,
so
that'll
do
the
same
thing
and
drop
all
those
native
work,
libraries
and
everything.
So
so
yeah
there's
going
to
be
a
huge
number
of
improvements.
H
So
I
think,
like
just
kind
of
the
three
of
us,
should
coordinate
that
and
figure
out
like
exactly
what
the
strategy
is
there
because
yeah,
we
don't
we
don't
mind
pitching
in
at
all,
but
but
also
like
our
familiarity
with
that
code
base
is
a
little
low
like
every
time
I
have
to
jump
in
there.
I'm
like.
Where
are
things,
and
so
that's
always
a
challenge.
H
You
probably
like
you
literally
had
to
look
through
the
code
to
figure
out
how
to
use
it
and
and
like
that
is
definitely
changing
because,
like
just
having
another
person
on
the
team
who's
using
that
code
and
then
like
documenting
it
as
they
go
and
improving
things,
and
we
have
way
more
example-
libraries
using
them
now
as
well.
So,
like
there's
other
code
that
you
can
look
at
that
uses
it.
H
I
think
that,
though,
the
the
way
that
the
apis
and
interfaces
are
structured
is
very
different
from
the
old
system
and
so
there's
a
degree
to
which,
like,
if
you're,
if
you're
porting
over,
if
you're
migrating
over-
and
you
don't
want
to
take
on
a
sort
of
larger
refactor
that
makes
it
more
congruent
with
this
new
interface
style
there.
It
may
be
actually
really
difficult
to
do
that,
and
what
we
may
want
to
look
at
is
like.
Okay.
Is
there
some
library
that
we
sort
of
put
in
between
that?
H
That
makes
this
a
little
bit
easier?
Is
there
some
kind
of
utility
library
that
we
use
or
is?
Is
there
like
another
refactor
of
some
of
the
stuff
that
go
ipfs
wants
to
do
anyway,
and
so
in
that
refactor
you
would
just
make
it
more
congruent
with
our
library
there's
a
lot
of
options
that
we
can
take
and
you're
gonna
have
to
kind
of
dig
in
through
the
code.
H
I
know
at
one
point
really
early
on
peter
and
eric
had
started
to
kind
of
go
through
this
and
just
look
at
the
depth
tree
and
where
all
the
ipld
libraries
are
and
how
they
interact
and
what
you
would
kind
of
have
to
do
to
start
to
break
them
apart,
and
I
that
that
got
to
the
point
where,
like
okay,
we're
ready
to
do
something
and
then
all
the
priorities
shifted,
and
none
of
this
happened.
So
we
would
need
to
like
return
to
that.
H
A
I
think
that
brings
us
almost
to
time
thanks
for
coming
everyone.
This
has
been
the
ipfs
confrontations
with
you
sync
for
monday,
the
12th
of
october
2020,
please
fill
in
your
async
updates.
Some
people
do
read
them.
I've
been
doing
it
recently,
I'm
very
naughty.
I'm
gonna
start
doing
it
again
because
alex
bad
alex
anyway.
Thank
you
very
much
for
coming
be
safe.
Don't
touch
your
face!
There's
still
a
pandemic
happening,
see
you
on
the
internet,
bye.