►
From YouTube: 🚀IPFS Core Implementations 2020-03-30 🛰
Description
Meeting notes: https://github.com/ipfs/team-mgmt/issues/992#issuecomment-605742635
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
Oh
hi,
everyone
welcome
to
the
IPF
escort
implementations,
weekly,
call
from
Monday
the
30th
of
March
2020.
We
are
slightly
down
our
numbers
today.
That's
why
and
people
are
going
to
leave
their
updates,
that
is
sinking
document,
which
would
be
great.
So
we
have
a
note
taker
away
if
everyone
could
put
their
name
in
the
attendee
list.
That
would
be
rad.
A
Give
a
quick
joke:
ipfs
update,
I'm,
basically
gonna
ship
it
now
now
the
soon
as
you
guys
finished,
gonna
ship
42,
it's
gonna,
be
amazing.
Well,
it's
gonna
be
okay!
Is
that
bug
rent
bug
fix,
release
efficiently,
it's
gonna
be
smaller
and
faster
and
more
focused,
but
with
no
good
features,
but
that's
fine
because
it
steady
though
these
cadence
is
more
important
than
say
yeah.
B
The
content
routing
team
is
taking
their
day
off
today,
so
we
don't
have
Steven.
Today
he
was
up
late
last
night
merging
a
bunch
of
stuff
for
the
first
release
candidate
of
0.5,
but
it
doesn't
look
like
that
got
cut,
so
I
would
expect
that
Tuesday,
but
that
is
also
imminent
to
get
our
release
candidate
out.
C
C
C
C
C
On
my
end,
there's
sort
of
like
a
related
grant
for
native
protocol
handler,
which
builds
on
top
of
sub
domains,
subdomains
bring
CAE
to
be
CID
to
be
a
basis
for
the
origin,
and
the
protocol
handler
would
effectively
make
that
the
only
thing
that
is
used
for
building
the
origin
I'll
put
a
link
into
the
notes.
Sedation.
Anyone
is
interested,
that's
it
for
me,.
A
D
The
big
thing
great
question
that
we
have,
as
we
plan
phase
2,
is
going
to
be,
which
of
the
endpoints
are
going
to
be
most
useful
to
people
as
we
move
forward
and
getting
feedback
from
protocol
labs
would
be
really
helpful
there.
We
do
have
community
contribute
contributions
right
now,
unsolicited
ones
which
is
really
exciting,
one
of
which
is
the
pin
api's.
So
somebody
contributed
that
just
you
know
out
of
the
blue.
D
D
Correct
interface
and
Interop,
there's
going
to
be
some
refactoring
required
for
interfaces
and
drop,
for
example
like
block
get
reuses
the
ipfs
dot.
Add
instead
of
ipfs
block,
put
examples
like
that,
so
we're
gonna
be
making
some
PRS
to
the
interface
change.
You
know
tests
and
stuff
like
that
and
interrupt
as
well,
but
otherwise
it's
going
so
far.
We
have
33
passing
interface
tests
so
far
and
we'll
be
including
them
as
we
move
forward
so
yeah.