►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
welcome
to
the
ipfs
core
implementations
weekly
sync
for
monday,
the
28th
of
september
2020..
I
am
making
brain.
I
will
be
your
host.
We
are
going
to
go
through
our
high
priority
initiatives.
A
A
No
cool
all
right
well,
maybe
next
week
pinning
services
any
updates
on
the
pinning
service.
B
C
Yep
we
shipped-
I'm
not,
I'm
not
sure
if
I
mentioned
that
last
week,
but
we've
shipped
a
small
patch
release
of
the
spec
when
we
renamed
some
fields
just
to
have
this
automatically
generated
client
more,
like
ergonomics
of
that
client,
more
developer
friendly,
but
it
does
not
change
the
format
on
the
wire,
so
it's
backwards
compatible
with
any
pre-existing
clients.
A
It
who
I
forgot
to
mention,
I
shipped
a
thing
I
shipped
an
update
to
the
iphone's
npm
registry
mirror,
which
is
now
using
the
latest
version
of
chase
ipfs,
and
it's
currently
rebuilding
the
enormous
sharded
directory
of
all
of
npm
check
back
in
a
month
or
something
anyway.
So
moving
on
the
ed25519
default
keys.
C
Yeah
I
kind
of
put
updates
on
on
the
subdomain
gateway
section,
but
let
me
copy
here
as
well:
I've
updated
the
docs
for
subdomain
gateway
to
include
some
code
examples
and
best
practices
that
include
the
reality
of
go
ipfs
0.7,
which
uses
those
keys
as
the
default.
So
now
it
should
be
more
clear
how
to
use
them
in
some
in
the
subdomain
context
to
load
websites.
Basically,.
A
Sakai
removal,
neither
a
dean
or
jacob
here
I
mean
that
went.
D
A
0.7
of
go
rpfs,
there's
a
pr
open
against
joe's
ipfs,
which
I'm
going
to
merge
later
this
week.
There
you
go
and
man
michael.
A
A
No
one
here
from
yeah
I
just
listened
to
like
ollie
and
his
daughter
like
playing
computers
for
like
20
minutes.
I
think
he
thought
he
was
muted
as
well.
Well,
that
sounds
lovely
though
it
was
very
cute.
It
was
very.
E
F
Hey
so,
regarding
the
first
part
of
it,
the
auto
relay,
which
is
the
task
that
is
mostly
then
by
now
last
week,
jacob
reviewed
and
we
got
merged
the
self-signed
peer
hackers
update
when,
basically
we
bought,
we
get
mine
to
do
a
relay.
Who
announces
our
address
on
the
matter,
and
then
we
do.
The
identify
push
to
a
toll
appears
that
we
are
connected
to
saying
that
yeah.
We
have
this
new
peer.
This
new
address
that
you
can
dial
us
or
announce
to
other
of
your
friends.
F
If
you
like
so
yeah
with
this,
I
unblocked
the
fall,
the
follow-up
pr,
which
basically
is
to
find
other
relays
on
the
network.
For
now
this
is
only
using
delegated
content,
routing
and
yeah.
This
is
also
ready
for
the
view
jacob
will
be
out
this
week.
F
So
I
hope
that
in
the
next
week
I
can
get
it
merchant
going
to
the
follow
follow-up,
which
will
be
we'll
want
to
not
announce
that
the
local
addresses,
which
is
a
thing
that
we
currently
do,
and
it
has
also
some
other
scenarios
that
has
been
problematic
for
users
in
the
browser,
for
example.
F
So
for
this
week
I
want
to
create
a
proposal
for
how
will
we
do
this
announcing
addresses
in
the
context
of
local
local
addresses
or
no
local
artists,
because
there
might
be
some
use
cases
where
people
might
want
to
announce
local
addresses,
for
example,
if
you
are
on
a
local
network,
and
so
basically
my
plan
will
be
to
only
allow
notes
to
announce
local
addresses
if
explicitly
configured
in
the
liberty
configuration
but
yeah.
I
will
need
to
think
a
little
bit
more
about
this
and
create
a
proposal.
F
So
last
week
I
didn't
have
time
to
get
to
the
connection
manager
overall,
epic,
so
no
update
on
that
front
and
regarding
the
rendezvous,
I
basically
got
back
to
it.
Last
week
I
refreshed
the
open
pr
that
I
had
to
use
the
sign
peer
records
that
finally,
we
got
released
on
lipid2029
and
I
also
refactored
it
to
use
win
tight
arrays,
which
we
also
did
in
the
elephant,
0.29
and
yeah.
So
my
goal
for
the
rendezvous
is
to
have
during
this
week.
F
We
are
ready
for
review
so
that
next
week,
when
jacob
comes
back,
he
will
review
the
both
the
auto
relay
stuff
and
the
renew,
and
with
that
I
will
also
start
the
integration
of
the
libertp
discovery
api
to
leverage,
the
rendezvous
and
the
content
routing.
As
I
mentioned,
for
the
auto
relay
and
yeah,
that's
it
for.
A
Me
awesome:
why
are
you
getting
an
update?
A
wild
mark
henderson
has
has
appeared.
Was
there
any?
Is
there
any
update
on
rust,
ipfs.
G
Yeah,
it's
pretty
significant
update.
The
0.2
crate
has
been
released
to
crates.I
o,
so
it's
officially
official.
G
All
right,
sorry,
yeah
again
the
the
crate
is
out
and
big
ups
to
jonas
and
lucas
for
all
their
work
over
the
past
few
months,
and
that's
really
all
it
for
me
I'll
post,
a
link
in
the
notes.
A
Okay,
I
think
that's
the
end
of
the
high
priority
initiatives
on
to
the
other
initiatives:
sub
domain
gateway.
I
know
you
just
talked
about
it
a
little
bit
in
the
context
of
the
keys.
Is
there
anything
further
on
that.
C
The
only
the
only
change
is
clarification
that
we
in
in
the
previous
version
of
docs.
We
did
not
highlight
the
fact
that
some
domain
gateways
are
fully
backwards
compatible
with
path
gateways.
C
Those
new
docks
highlight
the
fact
that
you
can
just
use
subdomain
gateway
as
a
drop-in
use,
slash,
ipfs
or
ipns
on
the
root
domain
and
go
ipfs
will
automatically
take
care
of
converting
cid
to
a
case
insensitive
base.
If
it's,
if
the
produce
cid
is
too
long,
it
will
use
a
base
36,
which
makes
longer
keys
fit
in
a
dns
label,
so
sort
of
like
added
some
additional
context
and
best
practices
to
that.
But
that's
about
it.
A
Cool
unix
of
sv
1.5,
there's
no
update
here.
D
Yeah
I've
been
working
on
that
I'm
putting
final
ui
touches
on
it
and
I
should
be
done
soon.
Hopefully,
today.
A
This
one
is
mine,
decomposing
the
cli
and
the
core
http
of
ipfs,
so
they're
in
separate
modules.
This
is
done
merged,
not
shipped
sure
it
will
ship
in
the
next
release,
so
that's
cool
trying
to
bring
mp195s
up
to
date.
So,
yes,
I
updated.
The
registry
mirror,
that's
all
deployed
and
it
like.
The
notable
part
of
that
is
that
it
has
libraries
like
shared
modules,
with
the
important
ipfs
project
itself.
A
So
I
want
to
try
and
run
that
against
cod
professional
point
seven
so
that
we
can
then
enable
that
nci
again
as
well
and
hopefully
breathe
a
bit
more
life
into
that
there've
been
some
people
on
the
github
reaper
who
have
expressed
an
interest
in
helping
out.
So
I
want
to
kind
of
get
it
into
a
point
where
I'm
like
here
you
go
and
here's
the
list
of
things
that
you
need
to
do.
That
would
be
super
cool.
A
That
is
that,
okay,
that
is
the
end
of
the
other
initiatives.
Moving
on
to
designer
review
proposals.
Anybody
got
something
they
wanna
stick
in
a
pillar
and
have
examined
in
my
new
detail.
A
These
sessions
are
so
much
fun.
Somebody
want
to
design
something
okay,
fine
blockers
and
asks
anybody
blocked
or
need
to
ask
something.
G
Hey,
I
have
a
just
a
small
thing
to
the
team
now
that
the
crate
is
out
we're
sort
of
pulling
down
the
throttle
on
rust,
fps
work
for
now,
so
I'll
probably
not
be
joining
the
calls
for
a
period
of
time.
G
But
I
am
returning
to
my
natural
habitat
of
orbitdb
and
I
know,
there's
been
a
number
of
team
members
that
want
to
reach
out
and
talk
about
that
too.
So,
please
don't
hesitate
to
get
in
touch
and
hopefully
we'll
be
able
to
work
on
something
like
that,
because
I'm
going
to
be
focusing
on
orbit
a
lot
in
the
coming
weeks
here.
So
that
was
a
good
time.
A
H
I
do
have
a
question
as
far
as
the
design
is
concerned.
One
of
my
upcoming
tasks
is
going
to
be
looking
at
moving
pins
into
the
data
store
and
I
wanted
to
know
if
the
design
of
that
is
how
how
much
more
review
do
we
need.
We
need
to
re-examine
that
to
make
sure
that
that
that
is
in
fact
what
we
want
to
do,
and
we
have
a
good
strategy
for
doing
that.
A
Okay,
I
mean,
I
guess,
yeah
you'd
hash-
that
out
with
the
team,
there's
the
pr
to
js
ipfs,
that
kind
of
set
out
the
design
for
it
and
there's
a
lot
of
back
and
forth
between
go
team
and
the
js
team.
A
A
Okay,
so
now
the
questions
we
can
move
on
to
the
parking
lot.
C
I
got
a
quick,
not
really
a
question
but
like
invitation
for
a
bike
shot,
so
unix
fs
1.5
was
introduced
in
js
ipfs,
but
it's
still
not
in
go,
so
it
would
be
nice
to
figure
it
out.
How
do
we
want
to
present
those
additional
attributes
in
our
ipld
explorer
when
you
inspect
a
dark
pb
right
now
it
looks
the
same
and
you
are
not
able
to
tell
that
modification
time
or
mode
is
different.
C
A
A
Exactly
cool,
if
there's
nothing
else,
then
this
has
been
the
one
of
the
fastest
call
implementation
weekly
things
ever
you
get
10
minutes
back.
Thank
you
all
for
coming.
Is
anyone
gonna
interrupt
me
here?
A
No,
we're
done
amazing!
Thank
you
all
for
coming.
This
has
been
the
ipfs
confrontations
weekly
thing
from
monday,
the
20th
of
september
see
you
all
on
the
internet
stay
safe.
Everyone
bye.