►
A
Hi
everyone
welcome
to
the
ipfs
core
implementations
weekly
sync
for
monday,
the
14th
of
september,
I'm
making
brain.
I
will
be
your
host.
We
are
going
to
go
through
our
high
priority
initiatives,
other
initiatives
and
have
q
a
parking
lot.
What
fun?
Let's
get
started
for
the
high
priority
initiatives
upcoming
and
ship
releases.
B
B
C
C
As
it
stands
right
now,
thanks
the
only
things
that
need
to
go
into
0.7
are
a
web
ui
update,
which
is
coming
soon
and
like
a
tiny
bug,
fix
there's
a
little
bit
of
investigating
about
like
some
some
performance
things
just
like
double
check
that
everything
is
is
working
exactly
as
we.
We
think
it
should,
but
everything
looks
good.
C
C
That
that
responds
to
things
we
have
an
http
client
that
responds
to
things
and
sends
requests.
We
have
a
good
chunk
of
the
initial
ipfs
go
ipfs
integration
done
sort
of
enough
for
for
everyone.
For
folks
who
are
working
on
this
in
you
know,
js
land
in
the
http
client
and
in
web
ui
to
play
around
with
things,
and
then
we
need
to
go
in
back
we're.
We
still
need
to
go
and
sort
of
backfill
back
fill
in
all
the
details.
E
E
F
E
C
E
E
E
F
F
So
you
can
see
how
those
two
things
are
interrupt
and
then
we
launched
a
website
called.
Are
we
ipfs
yet.rs,
which
has
the
enumerated
conformance
tests
and
so
is
sort
of
exactly
where
we're
at
with
things
which
I
feel
like
will
be
useful
to
people
and
then
just
a
side
note
goes
allah
rockley.
We
should
talk
soon
because
orbit
db
is
coming
out
with
another
version
and
the
next
version.
After
that
we
could
potentially
target
the
shared
worker.
F
C
F
No,
we
are
not
we're
we're
piggybacking
on
top
of
rustling
p2p,
which
does
not
have
autonet
yet
so
dhd
publication
is
still
a
problem,
but
we
are,
we
can
discover
cids
all
day
or
you
know
discover
content
all
day.
There
is
a
pull
request
in
run
slip
p2p
I'll
paste
it
in
there
that
somebody
took
a
stab
at
doing
up
on
that.
So
if
you
want
to
nudge
that
or
support
that
effort-
or
I
don't
know-
but
that's
that's
sort
of
the
state
of
things
right
now,.
C
F
D
Hey
folks,
so,
regarding
the
auto
relay
part
of
things,
I
basically
addressed
jacob's
review
from
my
initial
pr
initial
implementation.
It
should
be
mostly
ready
just
needs
a
final
review
from
jacob.
Then
I
started
doing
some
follow-up
prs
on
that
with
the
accessibility
to
other
stuff,
like
pr
for
updating
the
network
on
a
new
listing
address
existence.
D
So
the
goal
is
to
have
a
service
discovery
which
uses
content,
routing,
review
discovery
and
other
things
in
the
future.
Where,
basically,
the
goal
is
to
appears
to
register
offering
a
certain
namespace
service,
and
then
you
you
can
find
this
service
in
the
network
and
you'll
get
the
peers
that
offer
this
service,
and
then
you
can
dial
them.
D
Do
this
provide
things
saying
yeah,
I'm
a
relay,
so
you
can
ask
me
to
relay
stuff
for
you.
If
you
want
and
in
the
transport
as
we
basically
fulfill
the
interface
transport,
it
was
not
the
most
good
approach
yeah.
So
that's
my
current
point
in
in
the
auto
relay,
and
I
hope
I
will
finish
over
the
next
two
or
three
days,
all
the
work
in
progress
stuff.
For
this
and
after
that,
I
aim
to
start
the
connection
manager
overall,
epic,
which
is
also
linked
in
the
notes,
and
that's
it.
G
Nothing
really
I've
been
doing
other
stuff.
So
that's
on
a
back
burner
web
ui
file
it.
I
think
it's
there's
one
pull
request
that
it's
kind
of
stuck
on
and
it's
awaiting
on
something
else
that
I
can't
quite
remember
what
I
think
on
changes
to
the
go:
ipfs
http
server,
and
I
think
after
that
we
can
land
it.
G
I
haven't
had
time
to
add
another
item,
but
I'll
talk
about
it
and
then
later
so
I
start
taking
over
some
of
the
typescript
work
from
hugo
there's,
a
giant
pull
request
that
I
sent
to
alex
it's
mostly
comments,
so
it
should
be
not
so
bad,
but
there
are
a
few
changes
that
were
required
because,
as
we
start
generating
type
docs,
it
starts
to
figure
out
some
of
the
issues
that
we
were
not
aware
of.
So
there
are
a
little
bit
of
that.
But
rest
is
just
comments.
G
A
A
C
C
I
guess
I
thought
that
I
had
that.
I
I
posted
to
some
ipld
folks
recently
was
that
it
might
be
interesting
for
us
to
have
for
us
to
have
a
way
to
have
identifiers
for
content
that
are
much
longer
than
than
just
a
multi-hash
and
that
they
include,
like
we'll,
call
it
more
complicated
cryptographic
proofs.
C
I'm
thinking
of
this
in
the
context
of
the
folks
who
want
to
add
gate.
Repos
with,
like
you
know,
100
megabyte
blocks
in
them
through
ipfs,
but
it
won't
work
because,
like
we
won't
process
blocks
bigger
than
a
megabyte,
but
in
order
to
restructure
the
data
and
now
all
the
hashes
change,
and
so
like
there
are
various
proofs
you
could
construct,
but
it's
not
clear
how
we
would
actually
convey
those
like
how
we
would
actually
move
them
around.
Even
once
you
figure
out
how
to
construct
the
proofs.
A
A
Okay,
if
there's
nothing
else,
then
we
can
call
this
meeting
closed.
Everybody
gets
10
minutes
back
or
11
minutes
amazing.
Thank
you
very
much
for
coming
everyone.
This
has
been
the
iphone
core
infinitations
weekly
sync
for
monday,
the
14th
of
september
be
good,
stay
safe,
see
you
on
the
internet,
bye.