►
Description
Meeting description here:
https://github.com/ipfs/team-mgmt/issues/992#issuecomment-593505874
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
C
To
I
feel
yeah
okay,
we
can
start
up
I'm
just
trying
to
hypnotize
for
the
first
enemy.
Okay,
welcome
to
the
core
of
limitations.
Meeting
March
3rd
2020
first
up
is
upcoming
and
shift
releases.
So
as
this
typing
here,
practically
the
godfest
0.5
1
0
release
is
on
white.
We're
missing
a
couple
of
components.
So
we're
like
the
primary
concerns.
Right
now
are
the
PS
door
and
and
then
potential
dependencies
on
noise
I.
C
We
may
or
may
not
ship
noise
with
this
release
and
if
that
doesn't
happen,
it's
something
of
the
world,
but
we
do
have
a
lot
of
tht
work
booked
on
Pierce
or
factors.
So
we
may
have
to
find
some
way
to
work
around
that.
That
is,
the
only
update,
I
have
they're
testing
infra.
Do
we
have
anyone
on
that
team
here.
B
C
E
B
Jacob
get
the
update
yes,
so
there
is
two
weeks
left
until
we
are
doing
the
RC
so
scramble
time
yeah.
So,
as
Steven
mentioned,
we
have
an
issue
with
signed
pure
records,
where
we
need
to
make
sure
that
we're
not
just
ignoring
all
of
the
records
for
addresses
that
aren't
signed,
because
then
we
wouldn't
be
able
to
dial
with,
like
a
ipfs
warm
connecting
given
an
address
that
wouldn't
work.
So
that's
bad,
so
we're
gonna
be
working
on
getting
support
for
that
fixed
and
then
the
rest
of
the
work
is
pretty
much
on
track.
B
We
didn't
have
an
issue
that
we
need
to
take
care
of,
making
sure
that
we
support
private
dhts,
but
that
shouldn't
be
too
much
effort,
so
we
should
be
able
to
land
that
in
that
two-week
period,
so
biggest
biggest
concern
item
right
now,
as
Steven
mentioned,
is
the
sign
peer
records
so
we'll
work
on
making
sure
everything's.
Okay
with
that.
F
Me
again
yeah
this
week,
I
did
not
manage
to
land
the
PR,
but
I
managed
to
fix
proxy
tunneling,
which
is
a
mode
of
vegetative
proxy.
That
starts.
We
connect
it's
similar
to
HTTP
connect
a
lot
of
people
use
that
mode
for
avoiding
like
firewalls
corporate
firewalls
and
basically
a
lot
of
people,
don't
really
know
which
mode
is
used,
so
it
was
kinda
important,
but
not
really
to
support
that
mode.
F
In
case
someone
is
using
it
for
our
subdomain
feature,
so
I
found
a
way
to
make
it
work
with
less
code,
so
I
removed
some
code
instead
of
adding
it.
But
overall,
it's
good
I
think
suddenly,
I
had
to
put
up
some
fires
did
not
manage
to
London
s
link
tests
but
I've
seen
Stephen.
You've
wrote
some
note,
so
my
plan
for
this
week
is
to
address
those
nodes,
LAN
DNS
link
tests
and
hopefully
get
the
PR
to
the
point
when
it's
ready
for
like
with
you,
that's
it
for
me.
D
Yeah
so
we're
also
heading
towards
0.5.
It
looks
like
we're
pretty
much
on
track
with
the
content,
routing
changes
that
are
happening
so
this
last
week,
I
I
made
a
couple
of
fixes
and
optimizations,
and
thank
you
to
everyone
who
helped
review
javascript
bits
work
still
a
little
bit
more
to
do
there,
but
it's
close
to
being
merged.
A
Cooking
research
improvements.
Yes,
so
after
my
conversation
last
week
with
Hulk's
got
even
more
stuff
into
the
into
the
UX,
so
to
speak,
of
the
command
line
got
almost
the
stacked
chunker
interface
working.
There
are
still
some
corner
cases
that
I
need
to
figure
out
how
to
how
to
deal
with
need
to
land.
A
The
three
codec
linker,
which
they
like
it's
almost
almost
there
to
commercial
ipfs
I,
just
need
to
do
another
pass
on
it
and
also
to
get
car
output
actually
working
so
that
we
can
get
others
like
them,
for
example,
to
be
able
to
quickly
inject
stuff
into
an
existing
BFS
data
store,
and
there
is
some
lack
of
clarity
when
the
greatest
set
of
this
will
land,
maybe
I'll.
Take
that
one
I'm
not
sure
yet.
A
G
So
I've
been
working
on
hardest.
Well,
this
basically
aims
to
improve
browser
connectivity
for
Jessop
FS.
This
is
particularly
important
because,
after
the
super
factor,
we
are
duplicating
WebSockets
star.
So
basically,
this
was
the
previous
people
concept
from
machi
and
I've
been
basically
rewritten
all
the
implementation
using
a
sink,
as
well
as
with
the
new
connection,
transport
and
discovery
interfaces.
H
H
C
I
C
Like
his
work,
getting
down
to
the
wire
here,
like
seems
to
company,
be
changed
it
right
down
the
wire,
which
would
mean
we'd
end
up
having
a
protocol
version
bump.
But
it's
not
going
to
be
a
big
issue
because
like
well
basically
have
two
three
protocol
versions
have
the
old
DHT
I'll
have
like.
Then
you
will
have
the
new
DHT,
which
has
no
protocol
changes,
but
it's
like
faster
and
then
we'll
have
the
new
new
DHT.
It
is
like
has
no
like
query,
launcher
changes,
but
has
the
solution
protocol,
but.
C
I
H
A
C
Giving
you
volunteer
to
take
a
look
at
it
and
given
it
I'm
not
looking
at
my
day
and
it's
kind
of
full,
would
you
like
to
take
a
look
at
it?
Yes,
I.
Basically,
we
need
to
few
minutes.
We
need
I,
confess,
dag
export
I
profess
Dyke
import.
Then
you
do
the
opposite
of
each
other.
There's
already
a
library
go
car
which
should
you
ever
think
we
need
for
us
so.
C
A
number
of
cars
passed
the
command
line
and
read
them
in
bag.
Export
needs
to
take
a
like
a
single
CID
out
for
now
we
don't
need
selectors
in
the
future.
We
need
to
make
sure
we
can
upgrade
to
selectors.
So
what
I
recommend
is
like
if
it's
using
a
CID,
but
we
have
like
a
pass
as
like:
/
IP,
FS,
/
CI,
D
string
selectors,
like
that.
C
A
A
C
J
J
H
We
have
already
notifications
of
like
hi
I
know
it
looks
these
two
repos
like
you
could
reuse
the
same
repo
and
run
a
J
s.
Note
in
the
dono
didn't
work
like.
Please
don't
do
that
as
far
as
I
know
the
first
breaking
the
first
change
that
will
make
it
so
that
then
we
foes
don't
interact
with
each
other,
which
is
fine.
We
want
to
go
down
that
route
anyway.
I
just
want
to
make
sure
there's
enough
flags.
I
was.
J
C
A
H
C
J
J
J
C
Know
if
it's
ready
for
it
as
well
I,
don't
know
3%
review
because,
like
oh
sorry,
the
pinning
is
never
ready
for
as
everything
you
want
to
design
view
on
that
the
whole
general
like
cross
compatibility
discussion
thing
like
that's
a
discussion
which
I
guess
maybe
we
should
have
a
meeting
on
but
like
that's
like
a
very
open-ended
things,
it's
not
really
design.
Every
reason
like
we
have
a
single.
The
answer
was
the
answer,
but.