►
From YouTube: IPFS All Hands 🙌🏽 📞 Dec 12, 2017
Description
IPFS Companion Demo on Brave
B
A
B
A
A
A
C
D
A
A
B
So
that's
me
this
saturday,
which
is
the
16
of
the
summer.
We
would
do
the
the
second
ipfs
barcelona
meetup
in
a
different
different
place,
this
one.
If
your
co-star,
you
can
obviously
come
and
you
can
RSVP.
Otherwise,
if
your
remote,
we
will
have
the
IRC
channel
and
I
am
gonna,
do
the
same
as
I
did
last
time
to
stream
everything
and
would
be
super
appreciated
if
you
want
to
to
participate,
remotely
and
help
answering
questions
for
people,
and
things
like
that.
B
So
if
you
could
align
your
time
zone
with
personal,
no
time
zone
for
that
day,
if
you're
in
a
different
one,
that
would
be
very,
very
cool
and
what
we're
gonna
do
is
basically
hack
on
different
things.
There
are
a
few
projects
that
people
are
working
with
and
some
people
are
trying
to
do
bug
fixes
to
the
implementations
we
have
or
they
work
on
their
completely
unrelated
projects,
but
they
feel
like
the
space.
Is
this
good
to
be
in
in
general?
B
B
B
So
we
have
Jenkins
for
a
while,
but
Jenkins
from
you
know
an
unstable
environment
and
kind
of
leave
be
a
doctor
where
everything
is
synced
on
the
file
system,
which
turned
out
to
be
a
terrible
idea
for
a
performance.
So
now
I've
been
working
on
a
fully
automatic
environment
which
from
Caleb
is
better
which
I
am
gonna
migrate
to
today.
So
I
know
people
had
some
issues
during
the
weekend
with
the
go.
B
A
B
So
I
started
working
on
all
that,
but
the
performance
issues
cannot
put
a
step
of
taking
the
wheels
for
that
effort
and
we
also
have
to
figure
out
how
we
can,
because
right
now,
all
the
piers
I
do
I
verify
every
single
CI
mr1,
which
works
fine
for
circle
CR,
but
the
queuing
of
is
it's
a
bit
known
and
it's
gonna
be
longer
when
we
do
more
piers,
so
we're
gonna
have
to
talk
about
how
we
can
how
we
can
move
forward
with
Travis,
specifically
otherwise.
As
soon
as
I
deployed
the
new
environment.
A
Sounds
good,
so,
what's
working,
you
is
because
you
wait
for
all
the
sea
ice
to
be
green
to
actually
merge
yeah,
that
that
is
a
safe
thing
to
do.
Audio
like
if
master,
is
going
and
actually
then
touch
the
Travis.
Something
then,
like
you,
don't
have
to
wait
for
Travis.
It
would
be
just
like
a
profession,
sir,
but
if
you
can
like
trust,
that's
changing,
like
am
a
Jenkins.
Config
doesn't
affect
struggles
at
all,
should
work
fine,
yeah.
B
A
A
E
So
I've
been
looking
at
IPS
encryption
for
the
last
couple
of
weeks,
which
is
leading
into
the
first
thing,
is
really
key
management,
I
think
Warren
said
someplace
in
one
of
the
PRS.
You
can't
have
encryption
without
super
key
management.
So
that's
what
I've
been
looking
at
right
now.
Why
are
you
sleeping
put
up
a
proposal
for
about
full
commands
in
IPS
for
key
management,
basically
create
regain
updated,
cetera,
I'm
trying
to
follow
the
pkcs
standards
if
anybody
so
I'm
familiar
with
them?
Yes,.
A
E
One
thing
that
has
to
get
solved
is
how
to
actually
exchange
the
keys
okay,
because
we
have
to
assume
in
a
distributed
environment
where
machines
are
not
all
continuously
online.
How
do
we
really
do
a
key
exchange?
I
clip
those
stuff
so
that
only
on
the
intended
recipient
can
read
the
key,
but
how
do
they
get
it
and
how
do
they
ask
for
the
key
so.
F
What
I
would
do
is
you
can
you
should
make
sure
they're
both
online?
So
you
can
it's
fine
to
require
that
they're
both
online
for
a
key
exchange
and
then
you'd
have
to
open
some
new
lib,
p2p
stream
or
something
well
I.
Guess
we
can
discuss
this
new
issue
some
more
but
open
a
stream
between
them
and
then
just
transfer
the
key
yeah.
F
Right,
they
can
definitely
use
secret
right
now,
but
yeah
I
think
I
think
you
probably
probably
can
add
in
like
this
doesn't
need
to
be
happen
soon,
but
we
can
just
add
in
a
open,
open
the
connection
to
the
Perth
to
the
peer
send
the
file.
They
say
that
encrypted
and
oh
yeah
yeah.
E
E
E
F
D
F
Yeah,
so
on
the
on
the
IP,
that's
not
object,
there's
the
host
thing,
which
is
like
the
interface
to
all
the
network
stuff
and
on
that,
if
you
just
call
dot
new
stream
and
you
give
the
idea
the
peer
you
want
to
talk
to
and
the
protocol
name
you
want
to
talk
to
them
on.
It
will
give
you
a
new
stream,
and
that,
though,
then,
that
receive
with
a
given
handler
I'll.
A
So
that
will
be
like
encryption
of
the
content
at
rest
and
there
is
like
what
is
missing
for
I
think
your
use
case,
but
maybe
I
don't
understand
it
fully.
So
you
know,
what's
perhaps
like
for
this
one
issue
like
on
your
IPS
encryption
repo
and
make
sure
that
we
are
targeting
bodies
that
beyond
me
here
and
that
we
don't
repeat
something
that's
over.
There
agree.
E
Awesome.
The
other
issue
I
have
is
as
you're,
where
David
is
that
there's
going
to
be
some
crypto
war,
that's
required
in
live
p2p,
crypto,
mm-hmm,
I'm,
just
concerned.
It's
it's
a
lot
to
work
and
right
now
I'm
using
a
package
I'm
not
too
happy
with
node
forts.
Neither
you
at
least
it
gives
me
the
primitives
I
need
to
to
do
things.
I
would
like
to
go
forward
so
I
can
get
the
key
management
and
the
encryption
done
using
this
package,
which
is
only
referenced
in
the
keychain
library
and.
F
A
Absolutely,
and
until
note,
Forge
is
an
amazing
package
because
it
has
a
wolf
one
of
the
first
of
its
kind.
It
has
a
lot
of
critter
primitives
the
main
issue
in
node
Forge.
It
was
like
built
using
AMD,
so
it's
not
using
common
J's
nor
ACMA
script.
Six
modules,
which
makes
it
really
hard
to
import
squash,
require
into
a
node
GS
or
browser
project.
Today,
essentially,.
A
E
A
E
A
A
We
used
it
in
the
best,
like
the
first
version,
the
first
six
months
or
eight
months
of
just
ipfs.
We
used
it
and
then
essentially
we
phased
it
out
because
it
was
such
a
huge
beast
to
carry
with
us
at
all
times,
but
yeah
well,
I
identify
exactly
what
we
need
like.
What's
make
sure
that
we
understand
if
it
takes
weeks
for
maybe
a
couple
of
days,
just
like
the
refactor,
the
code
that
we
need
or
also
chat
with
a
note
for
team
to
see
if
they
are
interested
on,
like
modularizing
module
right
now,.
A
A
A
A
G
So
it's
a
very
quick
update,
I
just
I,
just
like
it's
the
first
update
after
Firefox
57,
five
box,
quantum
and
I
guess
I'll.
Just
maybe
show
my
screen
quickly
and
just
go
over
those
talking
points.
I
want
to
just
quickly
yeah,
so
I
previous
companion
is
doing
well.
We've
went
and
got
accepted
at
the
Mozilla
store.
We've
also
had
the
first
feedback
from
Mozilla
team.
First
serious
feedback
after
web
extensions
became
the
default
and
legacy
extension
stopped
working
in
Firefox
the
first
well,
maybe
I'll
just
go.
G
This
is
like
our
extensions
in
Mozilla
store
and
we've
got
somewhere
between
500
and
600.
It
varies,
but
usually
we've
got
like
quite
a
nice
user
base,
and
if
we
look
at
the
statistics,
it's
slowly
growing,
we
can
usually
see
when
there's
like
talk
or
maybe
a
meet-up
where
someone
presents
ipfs,
there's,
usually
a
lot
of
downloads
in
one
day
and
most
of
our
users
is
on
latest
Firefox.
G
This,
like
those
stats,
are
kind
of
junky
sometimes
but
give
us
good
feedback
about
the
direction
we
are
going
through
and
that's
a
better
channel
when
we
usually
publish
a
new
version
every
week,
or
maybe
more
often,
if
there's
like
change
that
we
want
to
smoke
test.
This
can
be
installed
instead
of
the
stable
version
and
can
switch
between
beta
and
release
versions.
G
If
you
will
find
that
the
beta
version
is
not
up
to
par
with
quality,
or
so,
if
you
experience
some
kind
of
a
bug,
he
would
just
report
it
and
switch
to
the
standard
one
until
you
fix
it
and
what
we've
created
I.
Think,
since
my
last
demo
is
the
translation
project,
we've
got
some
interesting
transact
translations,
usually
nearly
100%,
and
if
anyone
finds
that
his
or
her
native
language
is
missing-
or
maybe
you
want
to
go
over
all
the
already
existing
translations
and
approve
them.
G
There's
like
a
special
role
of
language
maintainer
on
this
crowd,
crowding
tool
we
are
using
and
just
let
me
know,
sent
an
email
or
create
a
ticket
on
github
that
you
want
to
maintain
a
language,
and
that
way
you
will
have
like
more
more
rights.
You
could
select,
which
translation
is
better
if
there
are
multiple
competing
ones
and
stuff
like
that
and
yeah
going
back
to
the
list.
The
most
important
thing
that
we
addressed
was
oh
yeah,.
G
G
We
had
some
issues
with
browser
if
I'd
dependencies
such
as
such,
like
JSI,
PFS,
api
and
infidels,
so
we
switch
to
we
switch
to
browse
verifying
entire
extension
thanks
to
great
help
from
all
right
and
so
far
we've
released
the
version
using
this
new
built
pipeline,
and
so
far
so
good
seems
that
most
delays
please.
So
this
one
is
kind
of
another
code
development
here
and
the
most
exciting
thing
that
I
wanted
to
talk
today
is
that
all
I
and
Alan
are
I.
G
Don't
think,
are
there
present
on
this
call,
but
they
will
probably
present
this
at
some
point
in
future.
I
just
want
to
teach
you
a
little
bit.
They
are
working
on
integration
with
brave
browser.
What
we
want
to
do
is
to
reuse
ipfs,
companion,
codebase.
We've
got
like
a
lot
of
boilerplate
and
background
code.
G
That
can
be
very
useful
and
is
reused
in
other
browsers,
even
in
browsers
that
do
not
support
web
extension
api's
to
the
same
extent
that
firefox
and
chrome
are
supporting
them
right
now
and,
as
you
can
see,
each
one's
the
current
version
runs,
but
that's
not
not
all.
What
we
are
planning
to
do
all
is
working
in
in
a
working
progress
for
requests.
G
What
we
wanted
to
do
is
to
leverage
the
more
liberal
security
model
of
brave
browser,
and
we
want
to
let
brave
browser
users
to
run
jas
ipfs
embedded
in
the
browser.
So
what
we
wanted
to
do
is
to
provide
a
switch
that
lets
users
to
select
if
they
wanted
to
run
the
old
version
which
I,
which
is
like
external
demon,
so
usually
go
ipfs
or
if
user
wants
to
run
embedded
pure
javascript
note
within
the
browser,
and
there
will
be
like
probably
some
kind
of
nice
UI
for
that.
G
Oh,
maybe
this
one
yeah,
so
that's
the
plan,
we'll
probably
have
a
like
this
switch.
The
great
thing
is
that
we
agreed
that
we
want
to
maintain
a
single
code
base
and
we
want
to
reuse
as
much
as
we
can
and
the
brave
specific
or
let's
say
Firefox
specific
code
will
be
in
a
module
on.
Maybe
it
will
be
up
behind
the
check
box
or
maybe
it
will
be
automatically
hidden
or
shown
on
the
specific
browser
that
enables
us
to
provide
additional
functionality.
G
This
embedded
feature
will
be
under
brave,
but
I
think
this
is
a
great
demonstration
for
let's
say
we
when
we
talk
with
muscle
at
some
point,
it's
a
great
illustration
of
what
we
want
to
do
in
mainstream
browser
and
it's
great
of
of
concept,
and
if
someone
wants
to
run
it
in
the
browser
natively,
they
can
just
install
brave
it's
not
ready.
Yet
it's
just
a
teaser,
but
it's
the
direction
we
are
working
towards
and
there
will
be
much
coming
soon
right
and
I
hope
we'll
have
another
team
demo.
G
Probably
all
I
will
show
you
something
when
it's
fully
baked
so
I
think.
That's
all
I
just
wanted
to
update
you
that
the
IP
first
companion
is
is
gaining
some
speed
and
we'll
have
a
separate
initiative
to
like
create
a
nexus
between
web
UI,
ipfs,
companion
and
ipfs
station.
What
we
want
to
is
to
provide
like
a
single
visual
language,
so
all
free
looks
like
will
look
like
the
same.
The
same
application
may
be
like
parts
from
the
same
ecosystem
and
we
will
hope
to
provide
a
tighter
integration
between
them.
G
A
This
is
awesome,
thank
you
so
much
for
demo,
so
much
cool
stuff,
so
much
forward
a-and.
Why
don't
was
being
a
ball
there
like
there's
a
lot
of
staff
that
like
are
in
PR,
so
you
have
to
stitch
things
together,
but
they
actually
work
pretty
well
and
you
can
like
switch
between
both
nodes
and
like
enable
certain
features,
drag
and
drop
files
into
the
extension
and
then
shared.
A
G
G
Yeah,
so
what
we
do
in
chrome
is
that
there
is
no
like
developer
channel.
So
if
you
are
using
Chrome,
you
will
always
have
the
the
release
version,
which
is
the
most
stable
and
polished
and
under
Firefox.
You
have
a
like
possibility
to
to
choose
between
a
release
version
and
the
developer
beta
version,
so
development
and
beta
versions
will
update
more
frequently,
but
at
some
point,
when
we
will
stab
you
lie
when
it
will
be
stable
enough,
there
will
be
a
full
release,
told
that
crumbs
or
also.
A
B
G
B
G
B
G
No,
that's
a
separate
thing.
This
background
page
is
in
different
namespace.
It's
like
a
separate
sandbox.
It
does
not
have
direct
access
to
your
pages.
There
are
api's
that
lets
you
to
introdu,
introduce
communication
between
background
pages
and
scripts
in
your
tabs,
but
that's
not
something
we
will
introduce
at
least
not
initially.
G
We
need
some
of
access
control
if
you
want
to
expose
local
node
to
the
to
the
JavaScript
running
in
taps.
That's
like
a
separate,
separate
discussion
and
I
think
we'll
until
we've
got
like
some
token
based
authorization
with
probably
won't
risk,
exposing
it
or
maybe
we'll
expose
only
read-only
API.
That's
a
prediction.