►
From YouTube: 🚀IPFS Core Implementations 2019-07-08🛰
Description
Description: https://github.com/ipfs/team-mgmt/issues/992
Notes: https://cryptpad.fr/code/#/2/code/edit/JDoHm2mS3S5AkT7a1BHX57Uv/
A
For
forgetting
to
record
thanks
for
the
reminder,
daveed
I
think
we
should.
We
should
plan
to
record
these
and
I
and
ideally
make
them
public
to
everyone
and
I
think
that
that
makes
sense.
It
involves
a
lot
of
the
core
design
decisions
on
the
protocol
and
and
was
something
that
we'd
kind
of
the
Jas
team
was
absolutely
already
doing,
and
the
go
team
had
like
agreed
to
do,
but
we
hadn't
really
gotten
around
to
doing
it.
Super
consistently,
so
I
think
Alan
thoughts.
C
The
the
format
of
initiatives
and
talking
through
the
interesting
things
it's
way
more
interesting
for
people
to
watch
than
just
quickfire
like
this,
is
what
I
would
was
doing.
This
is
what
I
got
blocked
on.
This
is
what
I'm
doing
next
so
actually
having
a
proper
agenda
and,
like
the
GUI
team,
were
already
doing
this.
Obviously
they
are
pioneering
away
of
all
of
this
and
yeah.
C
Maybe
we
can
get
towards
that
with
the
the
initiatives
and
just
make
it
a
bit
more
interesting,
but
you
know
if
it's
it's
a
it's
kind
of
a
toss
up,
isn't
it
between
this
being
utility
for
all
of
us
and
this
being
a
community
tool?
And
it's
where
we
want
this
to
fall
and
it
would
be
nice
to
be
like
able
to
engage
the
community
with
this
as
well,
but
I
think
our
primary
goal
is
for
this
to
be
utility
for
us.
A
Think
to
maybe
both
Michelle's
point
and
your
point
like-
and
this
is
not
really
a
meeting
where
we're
gonna
be
like
assigning
a
bunch
of
action
items.
So
much
I
think
it's.
This
is
more
of
a
place
to
unblock
action,
that's
happening
throughout
the
project
and
make
sure
that
the
the
next
steps
have
kind
of
clarity
and
an
agreement
across
kind
of
protocol
design
areas.
So
I'd.
Imagine
something
like,
for
example,
there's
a
proposal
from
some
folks
working
on
package
managers
who
want
to
I
don't
know
make
make
some
useful
change.
A
That's
gonna
make
a
component
of
package
managers
way
faster
and
they're
working
on
this,
and
they
want
to
make
sure
that
the
design
that
they're
approaching
fits
well
like
both
both
for
go
and
for
jeaious,
and
that
kind
of,
like
we
have
a
top
level
design
and
a
method
for
doing
it.
That,
like
everyone,
is
on
board
with,
and
we
can
kind
of
hit
the
ground
running
and
have
like
an
MVP
that
we
can
get
out
the
door
pretty
quickly
in
order
to
just
see
them
return
on
that
and
so
I'd
imagine.
A
This
call
is
something
where
we're
like
hey
here
is
the
proposal
from
this
group.
They
want
to
do
X.
This
is
why
here's
the
feedback-
maybe
you
know,
okay,
we
can
do
X,
but
X
plus
y,
because
of
this
particular
thing
that
someone
might
not
understand
across
the
two
different
implementations
or
something
like
that.
Are
we
all
agreed
that
we
can
move
forward
on
this
great
cool
awesome
initiative
kind
of
like
is
now
in
implementation
state
and
will
stay
that
way
until
it's
like
okay,
we
want
to
actually
be
merging
this.
A
A
Okay,
so
what
I'm
hearing
is
is
well
something
something
between
status,
updates
and
initiatives,
but
maybe
where
the
initiatives
flex
more
frequently
than
they
had
previously
on
other
teams
that
did
initiatives.
So
we
have
kind
of
marva
an
agenda
based
thing
where
people
are
bringing
things
to
to
the
meeting.
D
A
But
kind
of
like
it's
making
sure
that
if,
if
there's
something,
that's
really
important,
we're
kind
of
like
doing
the
prioritization
of
resources
to
get
that
thing
happening.
If
that
makes
sense,
so
I
think,
like
the
agenda.
Items
coming
in
should
be
driven
by
groups.
Groups
that
need
things
from
the
core
protocol
or
things
that
we
we
have.
B
A
Improving
in
significant
ways
so
like
I
know
that
there
are
some
specific
things
on
libels
mind
that
he
needs
to
be
getting
into
JSI
PFS
end
and
that
those
would
kind
of
come
here
if
they
had
any
kind
of
open
design
questions
or,
if,
like
he
needs
a
release
to
get
them
into.
You
know
whatever
brief
browser
or
something,
rather
that
we
need
to
happen,
and
vice
versa.
For,
like
package
manager,
side,
things
I,
think
I
saw
a
hand
from
Allen
yeah.
B
F
A
category
of
caste,
so
it
gets
each
initiative,
is
like
improve
IP
n
s
like
by
implementing
this
thing
and
then
like
we'll,
have
a
bunch
of
tasks
within
that
continue
to
work
on.
The
distinction
here
is
really
like.
We
have
okay,
rkers,
that
we
have
k
arts
initiatives,
but
kr7
issues,
legs
and
tears.
You
to
say
like
by
the
end
of
this
quarter.
We
need
to
like
meet
these
metrics,
but
they
don't
respond.
How
we
should
be
those
metrics.
F
B
Got
it
and
that's
so
that,
leaping
back
to
what
Molly
said
to
me,
it
sounds
like
this
group
will
no
longer
necessarily
have
initiatives,
but
I
might
not
be
understanding
that
correctly.
It
felt
like
what
I
interpreted
was.
Oh
the
task
forces
will
be
tracking
and
implementing
the
initiatives
like
the
things
that
we're
doing
sort
of,
and
then
this
group,
if
we
have
cross
task
force
stuff,
that
we
need
to
work
out
or
talk
about.
A
That's
that's
mostly
the
picture
in
my
head,
where,
like
this
group,
is
not
so
much
coming
up
with
us
initiatives
and
a
set
of
okay
ours
for
the
quarter,
but
it's
taking
the
set
of
initiatives
that
are
on
the
core
protocols.
Jsn
go
and
making
sure
that
they
can
successfully
move
forward
in
a
cross,
coordinated
way.
I
think
with
with
the
understanding
that
some
of
those
will
come
from
like
things
that
people
need
out
of
the
core
protocols,
the
core
implementations,
kind
of
from
a
project
operation
standpoint.
A
We
need
to
make
sure
that
we're
addressing
feedback
from
some
section
of
our
community,
that
that
needs
a
thing
that
is
not
necessarily
a
package
manager
thing
or
a
gateway
thing,
or
some
other
or
a
web
browsers
thing.
But
is
like
a
thing
that
our
community
needs
from
the
core
protocols,
and
so
that
would
become
kind
of
an
initiative
brought
to
this
group
in
order
to
support
our
community.
A
A
F
Good
fist
right
cut
an
RC
1
for
a
patch
release
to
fix
a
bunch
of
burning
bugs.
Unfortunately,
over
infra,
as
far
as
I
know,
is
running
highly
patched
releases.
So
I'd
like
to
find
some
way
of
testing
this
without
like
breaking
other
things,
but
like
testing
I
mean
like
trout,
my
fire
kind
of
testing
like
actually
that
getting
out
in
front
I,
don't
think
it'll
cause
any
problems,
because
we're
only
pulling
in
the
bare
minimum
like
critical
fixes,
but
I
don't
want
to
really
something
hasn't
tested
on
anything.
So.
A
F
C
F
Yeah
I
mean,
like
you,
can
put
it
under
heavy
load
in
allocations.
Check,
go
routines
check
it
like
we
don't
get
random
panics
or
whatever
these
years,
like
our
test
test
a
lot
of
this,
but
especially
cuz,
it's
all
running
in
CI,
like
we
can't
run
this
on
beef
machine.
So
most
of
our
regressions,
like
we
have
been
like.
D
F
Summoned
for
so,
they
usually
would
do
sort
of
play
to
the
gateways
and
look
at
that
and
then
we'll
try
to
play
the
bootstrappers,
although
that
was
in
the
past,
for
a
kind
of
Stockholm
version
at
the
problem.
Right
now
is
that
these
are
all
running
a
highly
patched
version,
but
we
Fest
is
trying
to
stabilize
ADHD
so
concerned
that
we
can't
do
that
and
when
I
wish
subsidies
who
can
brother
on
is.
C
F
Have
that
so
this
for
a
while,
we
had
a
Uruguay
which
we
could
use
and
yeah
so
that
we
could.
We
could
like
that,
would
help
us
have
some
testing,
where
basically
happens,
like
rats
I
think
in
this
case
we
literally
just
duplicate
in
traffic
and
then
blocking
all
the
responses
from
God
with
us.
But
this
still
forced
us
to
actually
do
all
the
work
which
would
give.
F
Amount
of
the
information,
but
it's
the
of
course
that's
not
running
on
bootstrappers.
We
haven't
they're
running
the
stuff
in
boots.
Drivers
anyways
since
like
over
nineteen,
because
everything
is
stuck
actually
this
before
about
1900
for
18
that
were
probably
enough,
I
think
for
me,
that
is
all
still
wired
up.
So
we
can
turn
that
back
on
and
will
sync
up
line.
You
want
to
give
cool
lighting.
You
had
a
blocker
I
think.
E
Yeah
sort
of
low
low
low
key
blockers,
one
is
related
to
delegated
for
routing
short
story
is
that
the
idea
is
to
make
a
sacrifice
running
in
web
browser
being
able
to
discover,
like
Pearson,
basically
have
delegated
access
to
DHD
queries
by
hitting
some
like
it
way.
Right
now
we
have
below
clouds
which
basically
expose
refs
endpoint.
The
difference
is
we
want
to
expose
some
additional
commands
on
the
gateway
port.
E
That
way
people
can
point
at
some
gateway
and
say:
okay,
let's
use
this
gateway
as
a
delegator
tutor
for
those
queries
and
the
problem
is
we
had
this
configuration
option
on
the
Gateway
API
commands
it
got
merged
to
go
I
profess
button.
Fortunately,
it's
not
wild.
So
anything
I
think
this
is
still
like
reps.
It's
still
hard
coded
yeah.
F
E
E
Sort
of
a
block,
soft
blocker
is
blocking
people
from
running
their
own
delegated
Rooter,
and
also
it's
blocking
our
documentation
like
telling
people
that
this
is
a
feature
because
we
people
are
not
able
to
configure
their
own
gateway
to
use
that
our
public
can
act
as
a
delegate
intruder.
But
it's
mostly
because
we
do
that
at
the
nginx
level.
But
we
want
to
go
idea.
Festoon
be
able
to
do
that
out
of
the
box.
E
F
E
C
E
F
G
Yeah,
there's
that
are
incoming
I'm,
trying
to
like
vaguely
I
mean
I'd
done
a
bunch
of
work
previously
and
I'm
trying
to
update
them
and
get
them
in
a
finished
state
before
I
like
officially
move
over
to
grass
sync.
So
there's
one
in
right
now
and
then
there's
gonna
be
another
one
coming
shortly,
and
the
main
goal
here
is
to
just
increase
I,
don't
know,
transfer,
speed
and
also
reduce
duplicates
by
really
tightly
tracking
peers
in
a
session.
G
So
it's
just
sort
of
like
trying
to
push
sessions
to
their
absolute
max
capability,
which
is
kind
of
like
once.
We've
done
that
we've
kind
of
maxed
out
what
its
lot
can
do
on
its
own
without
addressing
or
something
else
and
yeah,
and
then
so
we'll
see,
hopefully
so,
there's
a
PRN
right
now,
I
mean
there's
also
a
PR
in
and
there's
gonna
be
another
PR
and
then
hopefully
that'll
be
it
for
now.
I
It's
not
a
pilot
needs
review,
I've
been
trying
to
push
the
load,
move
a
secret
way
to
stuff
along
injera
slant,
and
so
I've
been
trying
to
do
some
peels
against
a
little
p2p
stuff,
because
that's
the
kind
of
the
area
that
these
numbers
work
at
the
moment
and
so
I've
been
trying
to
find,
like
ones
of
their
own
fpr's,
open
and
then
looking
at
their
dependencies
and
working
out,
which
ones
needs
appears
to
trickle
that
all
back
up.
And
it's
comment
so.
I
Nothing
much
has
happened
for
a
few
months
on
it,
I'm
wondering
maybe
that
was
a
mistake
trying
to
refactor
the
API
and
converts
waste
incarcerated
or
like.
Is
it
going
to
be
worked
on
or
shall
I
pick
it
up
like?
What
do
we
need
to
do
to
take
over
the
line
we're
opening
their
new
PR
that
just
converts
the
existing
API
taste
and
gets
our
areas
be
a
better
way
forward
which
are
then
unblocked,
another
bunch
of
stuff?
And
then
we
can
go
back
and
look
at
the
API
again
later.
J
Are
you
talking
about
the
interface
connection
right?
Okay,
I
intend
to
get
back
to
it
as
soon
as
I'm
able
to
get
to
sing
it's
Reiter's
again
so
hopefully
next
week,
and
basically
it
got
blocked
at
the
time.
Because
of
all
almost
all
the
team
was
with
Agatha's
camp
tasks
and
I
didn't
have
anyone
to
review
stuff
and
so
I
switched
to
priorities
to
another
PRS,
and
this
got
clocked
by
that.
But
now
I
think
I
can
continue.
It.
J
I
I
J
L
A
D
Anyway,
this
is
super
exciting
that
we
know
it's
just
like
a
lonely
dream
so
congrats
to
everyone
and
for
depth.
Green
to
come
will
be
true
and
I
can
make
sure
that
jobs
very
well
I
I,
wonder
if
it
would
be
good
to
have
a
structured
effort
of
onboarding,
the
other
team
into
the
other
team's
function.
It
is
true
that
we,
both
teams,
are
waiting
at
because
I
profess
is
a
protocol
implementations
but
like
there's
definitely
nuances
and
I
think
that
never
got
within
into
the
spec.
D
So
it
would
be
good
to
have
some
kind
of
like
onboarding
process
so
that,
like
the
GS
Peaks
can
I
get
used
to
the
way
that
they
go
team
does
things
and
then
ice
person,
because,
like
there's
learnings
to
doing
both
sides?
Is
this
something
that
people
would
like
to
see
they're
like
help
getting
structured
work
or
is
there
any
equivalent
plan
to.
F
Yeah
I
mean
I.
Think
that
they're
least
brought
are
the
the
contributing
flow
is
pretty
much
the
same
as
anywhere
else
where
you
make
them
a
fork,
or
so
you
make
a
branch,
you
push
the
branch
you
make
a
PR
and
you
go
through
the
cycle
and
if
you
have
a
big
feature,
human
gives
you
a
family,
I
think.
A
The
beads
point
is
not
that
contributing
process,
but
the
code
base
itself
and
so
effectively
doing
like
previous
teams,
called
this.
A
stumble
like
some
sort
of
walkthrough
of
the
code
base
and
kind
of
going
section
by
section
or
doing
kind
of
an
overview
of
how
things
actually
are
and
work
on
each
side
and
which
gives
other
language
of
limitations
better
visibility
into
how
things
are
actually
playing
out
today.
And
so
you
could
start
having
people
on
the
dais.
F
D
Like
think
about
exactly
what
I've
always
said,
so
thinking
about
like
doing
some
pair
programming
sessions
that
can
be
recorded
and
I
can
even
be
my
subsystem.
I'd
imagine
like
having
one
of
the
go
core
developers
with
a
couple
of
ones
and
I
just
do
beat
swap
for
one
day
and
then
do
like
whatever
he's
unique,
surf,
S&M
FS
and
like
where
those
ripples
are
in
and
kind
of,
I
just
invite
to
fix
some
of
the
problems.
D
G
From
the
SWAT
side,
something
I'm
actually
working
on
with
a
community
contributors
trying
to
get
like
did
slots,
go
bits,
lost
architecture,
more
documented,
so
I
feel
like
if
I
had
like
a
month
to
get
that
into
a
better
place.
I'd
be
in
a
better
place
to
lead
such
a
like
an
introduction
to
bits
law
on
the
go
side
which
I
realize
is
totally
necessary
and
a
good
thing
to
build
towards,
but
but
I
actually
don't
feel.
G
F
That's
I
think
this
would
be
really
useful
has
like
a
prepared,
recorded
presentation
of
like
this
is
the
architecture
of
each
of
these
components
that
help
we
won't
be
out
or
updated
too
quickly,
rather
than
like
hey.
Let's
just
sit
down
and
pair
program
on
this,
because
I
thought
its
components
are
pretty
complicated
and
like
so,
if
it's
just
a
one
on
one,
it's
great,
because
I
can
like
see
what
someone's
thinking
what
they're
missing
and
like
you
can
really
work
it
out.
D
D
C
There
are
definitely
parts
of
the
go
code
base.
Well,
I
mean
the
majority
of
the
code
base.
I
do
not
know
I'm,
and
there
are
definitely
things
that
I
would
like
to
know
better,
and
so
maybe,
if
I
were
to
make
a
list
of
those
things
and
that
would
better
better
inform
a
session
on
those
things,
I'm
I'm
still
trying
to
work
out.
If
this
proposal
is
is
like
we
all
work
together
every
day
or
if
this
is
just
like.
G
G
A
A
Having
people
more
able
to
focus
on
like
stuff,
that's
really
important,
as
it
comes
up
in
on
either
side,
so
it
just
means
we
have
like
more
flexible
humans
who
can
can
jump
in
on
stuff
as
it's
needed
and
I.
Don't
think
the
proposal
is
say
everyone
on
dais
must
work
on
NGO
or
anything
like
that.
Cuz.
A
We
have
stuff
that
we,
you
know,
need
to
be
doing
on
the
Jay
s
side
for
web
browsers
and
stuff
like
that
anyway,
and
but
I
think
having
that
capability
and
having
a
group
that
is
able
to
be
fixing
areas
of
of
kawaii
PFS.
That's
a
big
focus
for
us
would
be
really
useful
and
having
people
on-the-go,
ipfs
ID,
with
enough
understanding
of
JSI
PFS
to
kind
of
have
that
that
visibility
and
and
be
able
to
own
more
of
the
kind
of
multi-language
implementation
design,
that's
I,
think
would
be
really
useful.
A
C
Yes,
so
there's
some
areas
where
I
see
this
to
be
really
beneficial
is,
for
example,
like
the
stuff
that
he
go
brought
up
about
the
config
and
changing
that
that
it
doesn't
feel
to
me,
like
that's
a
huge
thing
to
do
in
Ingo
ipfs,
but
it
would
be
beneficial
if,
like
Hugo
were
able
to
to.
You
know,
send
a
PR
to
at
least
get
the
ball
rolling
for
changing
this
config.
If
not,
do
it
completely?
F
Okay,
so
they
could
keep
our
tears,
it
will
be
recorded,
so
we
can
give
it
up
to
other
people
who
join
the
team
right
now,
like
basically
every
time
we
on
port
somebody
kind
of
like
introduce
them
to
each
sub
module
independently,
often
impose
its
for
subsection
figure.
What
it's
currently
doing,
because
things
change
in
operations
update.
It's
like
that.
F
But
it's
why
I
think
I
don't
know
if
a
pepper
coming
like
that,
we
that
helpful,
there's
a
group
pair
program
with
all
that
helpful
more
than
like
having
to
a
thought-out
well-organized,
a
presentation
effectively
on
each
supplement
will
be
really
helpful
and
then
like
independently.
We
can
do
like
pair,
like
101
pepper
I
mean
are
certain.
Things
were
like.
We
actually
have
a
double
channel.
That
means
Charlie,
Virgo
I'm
gonna,
see
if
we
can
open
it
up
to
everyone
and
then,
like
you,
can
like
jump
on
just
like,
say:
hey,
like
I.
F
L
A
A
Cool
I'm,
I'm
super
pro.
This
idea,
I
think
it
sounds
great
and
I
think
the
next
step
is
to
kind
of
define
at
least
a
first
set
of
areas
that
we
think
are
going
to
be
the
highest
value
and
start
with
those
and
see
how
things
go
and
I
think
having
someone
who
coordinates
it
if,
if
feasible,
would
be
great
in
terms
of
like
being
able
to
schedule
these
times
and
and
kind
of
coordinate
dris
for
doing
those
leave
maintainer
presentations
on
subsections,
I
think
Alan
mentioned
he
had
some
ideas
and
said
to
be.
D
D
This
is
a
new
call,
so
maybe
like
when
we
get
this
full
request,
like
just
like
a
quick
iteration
over
the
full
request.
Just
like
that,
you
comment
put
their
ideas
on
and
then
like
what?
Let's
see
if
people
want
to
a
little
bit
more
structure
on
this
onboarding
for
the
next
few
weeks,
I
guess
I'm
more
than
happy.
If
people
feel
confident
for
going
out
of
my
setting
meeting
a
lot
of
contributions,
and
let's
do
it,
nothing
can
stop
you.
D
A
A
Yeah
I
would
agree
that
if
we're
gonna
spend
a
week
on
things,
I
like
that
idea,
I
think
maybe
we
should
chew
on
that
one.
A
little
bit
more,
maybe
like
create
an
issue,
and
we
can
can
discuss
like
how
to
do
that
really
effectively
and
when
to
fit
it
in,
because
I
think
the
beginning
of
the
quarter
is
not
the
best
fit
so
that
we
can
like
start
working
on
our
on
our
ok
hours
and
getting
stuff
done.
A
A
Do
we
have
any
other?
Are
we
out
of
time
just
meeting
over
think
we're
out
of
time
I?
My
time
zone
is
still
set
to
see
CET
CST,
whatever
the
Barcelona
time
is
so
I
have
no
idea
what
actual
time
of
day
it
is
the
wonders
of
jet
lag
but
I
think
this
meeting
is
over
and
very,
very
useful
c
EST.
Thank
you.
I
had
all
of
the
right
letters
just
not
in
the
right
order.
A
Awesome
I
think
we
have
a
number
of
action
items
that
we've
unblocked
and
next
week.
Let's
take
a
pass
through
at
the
very
beginning
of
the
call
the
set
of
initiatives
to
kind
of
define
our
list
and
role
and
if
iterate,
as
we
continue
going,
and
hopefully
we
have
a
a
wonderful
code
stumble-through
to
look
forward
to
as
well
Tec
s
text,
perfect,
okay,
cool!