►
From YouTube: 🙌 IPFS Weekly Call 📡 💫 2019-11-04
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
Hello,
everyone
welcome
to
the
ipfs
weekly
pop
or
Monday
November
4th
hello,
it's
a
great
day
and
we're
gonna
start
with
an
iDevice
weekly
update
and
then
move
on
to
any
other
items.
If
folks
have
feel
free
to
add
some
topics
in
the
side
band
and
if
there's
anything
cool,
that's
happening
or
anything
happening
in
the
wider
community
and
ecosystem
that
people
want
to
discuss
all
right,
weekly
update,
looking
across
stuff,
that's
happening
there,
I
guess!
A
A
So
here
we
are,
there
is
a
new
go
I
profess
as
a
library
tutorial
that
de'vide
actually
put
together,
despite
having
had
his
fingers
in
J's
IP
Westland
historically,
as
he's
working
on
helping
make
test
ground
phenomenal
tests
grande,
is
our
new
kind
of
network
simulation
testing
tool
that
we
plan
to
use
to
validate
and
subsequent
releases
of
IP
of
us,
so
that
we
can
compare
things
like
all
right.
How
did
performance
change
between
master
and
prod?
A
As
me,
you
know
iterated
on
bit
swap
functionality
so
that
is
launched
and
super
cool,
so
I
believe
this
yeah.
This
is
our
first
one
of
using
globe,
Cabezas
library.
So
if
that
is
something
that
you
want
to
do
or
want
to
see
how
others
do
you
can
go
check
that
out?
Jas
oh
39
was
released,
there's
a
lot
of
cool
stuff
in
there
and
if
you
want
to
know
more,
ask
Alex
or
Alan
generally
profiles,
theirs
in
browser
requests,
throttling,
there's
lots
of
stuff
going.
A
A
Maybe
we
can
improve
that
and
and
get
those
latency
gains
and
so
either
way,
I
think
there's
some
some
once
we
once
we
identify
that,
there's
some
improvements
that
fall
out
of
it,
but
and
hopefully
make
ads
in
general
much
faster,
which
is
really
exciting.
On
the
other
side
of
things,
Dirk
has
been
hard
at
work
on
improving
bit
swap
and
adding
some
some
new
functionality.
A
C
A
More
space
cool,
so
that
that
is
not
happening
on
the
performance
side.
On
the
documentation
side,
we
have
a
new
Docs
content
writer
who's
working
with
us
welcome
John.
If
you're
watching
this
call
and
we're
also
working
on
a
beta
version
of
IP,
miss
documentation
and
there's
a
v2
repo
in
the
works.
That's
getting
some
stuff
transferred
over
with
a
new
information
for
protector
and
a
lot
of
other
cool
stuff,
so
feel
free
to
drop
a
note
there.
A
If
you
have
ideas
for
how
we
can
improve
a
refractor
documentation
and
finally,
there's
a
discussion
about
Lib
p2p
ODOT
for
and
how
we
can
mitigate
its
lack
of
support
for
or
or
decision
to,
not
support,
intentionally
1040
1024,
bit
keys,
I'm
going
forward
and
so
worried.
If
you
use
1024
bit
keys
in
your
application
today,
please
reach
out
because
we're
going
to
be
migrating
away
from
that
I
think
I
give
us
for
a
long
time.
D
What
one
thing
I
don't
know
if
ladle
is
on
the
call
next
I
can't
see
in
if
you
right
now,
but
one
thing
that
and
I'll,
like
the
issue
here-
that
we've
been
hitting
in
the
companion
world
is,
are
the
changes
that
that
chrome
has
made
to
MIT
for
a
manifest
b3
as
they're
calling
it,
which
is
at
this
point.
It
caused
some
things
like
delayed
reviews
of
the
Chrome
extension.
D
This
is
starting
to
show
up
in
broader
tech,
news
tech
press
as
well,
because
these
are
some
pretty
controversial
and
restrictive
changes
to
the
capabilities
that
that
add-ons
have
when
running
inside
Chrome,
but
I
just
wanted
to
like
that.
You
know
kind
of
let
everybody
know
that
over
on
the
companion
side
of
things,
this
is
I
can
cut
both
the
I'll
go
challenge
to
be
able
to
make
a
code
base
that
supports
and
ships
on
several
different
browser.
D
Vendor
platforms
that
have
differences
but
also
might
be
an
ongoing
challenge
for
us,
as
chrome,
starts
to
restrict
the
type
of
capabilities
that
we
need
to
be
able
to
get
a
little
level.
Access
to
network
requests
the
kind
of
things
that
we
need
to
be
able
to
understand
what
it's
asking
for
are
PFS
resources
or
how,
to
compute
direct,
say,
a
failed
request
to
and
ipfs
resource
all
the
different.
D
You
know
things
that
we
do
to
be
able
to
use
companion
to
augment
the
basic
browser
browser
experience
so
I'll
add
a
link
in
there,
but
it's
something
that
is
becoming
you
know
more
and
more
of
a
challenge
for
everybody
writing
extensions,
but
definitely
specifically
affects
our
ability
to
ship
in
chrome
at
this
point,
but
no
other
browsers
that
I
know
of
or
have
announced
an
adoption
or
support
for
these
type
of
restrictions.
So
it
should
be
chrome
only
at
this
point,
I.
E
Can
just
add
additional
a
concern
on
top
of
that?
What's
the
Dziedzic
said
is
that
it
not
only
like
slows
down
our
release
cycle
so,
let's
say,
there's
a
bug
which
we
fixed.
It
may
take
a
few
days
up
to
a
few
weeks
to
get
to
push
this
change
to
users
of
Google
Chrome.
That's
that's
the
main
concern.
E
The
explanation
is
that
we
are
using
those
powerful
API
switch.
We
should
not
use
and
use
something
else.
The
problem
is
the
manifest
be
free
does
not
provide
a
replacement
which
is
as
powerful
or
as
capable
as
existing
manifest
v2.
So
we
are
being
punished
for
using
existing
KPIs
and
we
are
not
provided
with
a
replacement.
It
is
even
more
unfortunate
for
adblocks.
We
are
using
similar.
Api
sets
a
block,
so
we
are
impacted
by
the
same
problem.
I.
A
Guess
giving
like
Google
Chrome
just
released
like
a
paid
ad
block
feature
not
that's
surprising.
What
they're,
making
it
much
harder
for
other
adblock
features.
B
On
the
counter,
like
the
current
API
is
really
difficult
to
optimize
for
performance
like
they
have
to
ask
every
extension
for
every
request.
Would
you
like
to
redirect
this
request
that
has
a
performance
impact
so
to
play
the
advocate
for
the
unpleasant?
It's
not
a
completely
unreasonable
performance
optimization.
It
just
shows
that
they're
not
interested
in
the
extensions
community.
Oh
yeah.
E
A
C
C
A
D
D
Yeah
there
so
I
wanted
to
give
a
quick
introduction
to
a
project
that
we're
going
to
be
doing
possibly
over
the
next
couple
of
months
called
the
activist
browser
design
guidelines,
as
we've
been
working
with
several
browser
vendors
to
implement
IP
fest
natively.
There
are
some
things
that
come
up
when
you
learn
ipfs
resource
in
a
browser
that
are
different
from
when
you
load
in
it
should
be
resources.
The
browser,
the
fact
that
you
can
cryptographically
here
and
find
the
content
you've
got
like
profess,
is
really
nice.
D
That's
something
we
should
communicate
to
people
the
fact
that
that
content
can
come
from
anywhere.
This
is
also
interesting
and
has
some
side
effects
that
we
also
want
to
communicate
to
people
as
well.
Some
of
those
are
really
good.
I
mean
the
come.
The
content
could
come
really
fast
because
it
might
come
from
all
those
people
in
the
same
room
with
you,
but
also
might,
if
they're
not
in
the
same
way
with
you,
it
might
take
a
little
longer.
D
So
when
we
talk
with
groups
like
the
w3c
or
the
ITF
around
I
professed,
we
can
now
have
a
clearly
communicated
body
of
knowledge
around
the
decisions
that
they
have
to
make
around.
Both
availability
of
capabilities,
things
like
lower
level,
Network,
API
access
kind
of
like
the
stuff
that
we
were
just
talking
about.
We
go
to
Chrome,
but
all
newer
paradigms
around
browser
to
browser
communication.
So
you
know
the
one
of
the
optimal
scenarios
in
that.
D
Like
offline
networks
situation,
you
have
a
bunch
of
people
in
a
room
together
and
there
have
resources
on
ipfs
that
they
could
share
with
each
other
not
having
to
run
a
server
but
being
able
to
do
that
from
directly
from
the
browser
and
to
be
able
to
share
with
all
those
other
browsers.
It's
a
really
powerful
use
case.
So
this
is
a
project
that
we
have.
A
designer
room
will
hopefully
be
joining
us
for
a
couple
months
to
do.
D
Some
of
this
work
might
reach
out
and
talk
to
some
of
you
and
we'll
be
sharing
this
work,
probably
in
the
future
iteration
of
this
meeting.
What
so
does
concluded?
We
have
things
to
share,
but
more,
they
thing
wanted
the
community
and
the
core
team
of
people
that
are
watching
this
meeting
every
week
to
have
a
view
into
how
we're
thinking
about
these
next
phases
of
browser
integration
and
how
we're
setting
ourselves
up
to
be
able
to
have
that.
Have
that
router
conversation
with
the
people
that
are
in
browser
in
web
standards,
world
thanks.
A
Thank
You
dieter.
That's
awesome
as
everyone's
gotten
a
chance
to
go
through
Hector's
thing:
where
shall
we
hop
to
Alan.
C
A
F
C
I,
just
don't
know
if,
if
this
works,
like
so
I,
have
like
a
bootstrapper
deployed
for
this
and
I,
don't
know
if
we
will
stay
connected
to
the
bootstrapper
little
drunk
and
I
think
it's
on
the
regular
ipfs
network.
So
your
view
will
connect
to
the
regular
idea
first
night,
weird,
even
though
it
doesn't
use
it,
but
I
use
it
to
discover
other
beers,
and
it
may
not
work
very
well.
As
I
said,
this
was
like
very,
very
just
getting
it
up
right
now.
It's.
C
A
A
G
Okay,
I
shall
try
just
super
quickly,
as
some
of
you
I've
been
working
on
this
week
and
it's
something
that
we've
been
talking
about
since
let's
say
like
2016
or
so,
and
so
it's
by
far
time
to
do
it.
But
the
idea
is
that
we've
got
two
separate
files.
Api's
we've
got
like
a
root
level
file,
API
for
like
adding
cutting
and
getting
and
we've
got
this
whole
em
FS
thing
and
so
idea
was
proposed
a
long
time
ago
to
maybe
unite
them
and
create
1:1
files,
API
to
rule
them
all.
G
And
so
what
I've
been
working
on
this
week?
It's
not
ready
yet,
but
I
just
wanted
to
kind
of
I,
don't
know,
say
something
things
about
it
just
for
fun,
but
you
know
it
ranges
from,
like
maybe
renaming
ipfs
add
like
import,
because
actually
you're
you're
bringing
things
in
from
the
outside
and
people
often
confuse,
add
and
write,
because
they're
very
similar
in
name-
and
you
know
when
you're
writing
things
you're
kind
of
adding
things
to
IVFs
to
so
it's
just
difficult,
but
it
goes
like
it.
G
It
would
also
maybe
help
people
with
understanding
or
not
having
to
understand
the
whole
pinning
concept
which
is
sort
of
alien
to
people
who
are
outside
of
the
ipfs
world.
So
it
ranges
from
things
like
that
and
to
like.
Maybe
we
should
just
stream
all
of
the
api's,
because
at
the
moment,
they're
kind
of
buffering
and
that's
not
great,
because
we
have
huge
directories
of
things
like
npm
on
ipfs.
G
We
can't
even
use
IIP
FS
LS
because
it
there's
too
much
stuff
in
the
directory
to
LS
like
where
your
node
will
run
out
of
memory
before
it
can
return
the
result
to
you.
So
things
like
we
should
stream
those
results
not
only
for
LS
but
feel
like
when
we
getting
files
out
of
IP,
FS
or
just
King
and
the
values
just
help
with
that.
G
Maybe
and
the
stuff
like
if
we
import
things-
and
we
add
them
to
MF
s
by
default-
maybe
maybe
we
could
even
remove
the
pin
option
for
maybe
we
could
even
remove
this
whole
rap
with
directory
option,
because
if
we
add
them
to
IDF
to
MF
s,
they
are
kind
of
wrapped
in
the
directory.
Already
so
I'm
kind
of
looking
at
things
like
that
and
what
else
so
stuff
like
cat
IQ
test
cat
is
cat
a
cat,
or
does
that?
G
So
I'm,
just
working
on
this
kind
of
proposal
for
for
things
like
this
at
the
same
time,
trying
not
to
not
to
change
things
so
that
they're
completely
completely
different
to
how
they
were
before
just
make
things
better
within
the
boundaries
of
what
we've
already
got
to
some
extent.
So
it's
not
completely
different
and
that
the
the
kind
of
Delta
between
where
we
are
now.
C
A
That's
awesome,
Thank,
You,
Alan,
I,
think
yeah.
We
are.
We
are
way
overdue
for
a
V,
whatever
post
version
we're
at
which
takes
all
of
the
learnings
from
you
know,
what's
worked
well
and
and
some
things
that
we've
added
over
time
that
have
grown
kind
of
as
weird
sideways
arms
instead
of
nice
organized
branches.
So
that
sounds
phenomenal.
A
H
A
G
H
Sounds
lovely
one
I,
usually
I,
guess
in
the
m
FS
one
at
least.
Maybe
we
haven't
done
in
the
files
one.
But
if
you
like
search
the
code
for
the
word
gotcha,
you
will
find
thanks.
Terry
thinks
were
silly
about
the
current
API,
so
I
will.
G
A
H
G
H
And
I
think
some
of
this
stuff
like
when
you
say,
should
we
change
what
cat
is
like
I'm,
a
person
who
doesn't
use
the
command
line
very
much
and
someone
who
does
use
the
command
line?
What
maybe
they
do
think
that
makes
sense
because
they've
seen
it
before,
whereas
for
me
something
like
the
word
right
or
the
word,
which
is
normal
verb
horses,
not
that
I'm
suggesting
those
are
news
for
Kansas.