►
From YouTube: IPFS Weekly Call 2019-02-11 🙌🏽📞
Description
IPFS Newsletter: https://tinyletter.com/ipfsnewsletter
IPFS GUI: https://github.com/ipfs/ipfs-gui/issues/75
B
B
C
What
why
don't
we
officially
begin
hello?
Everyone
welcome
to
the
ipfs
weekly
call
I
love
that
you
guys
welcome
to
the
ipfs
weekly
call.
Will
we
get
to
see
what
we're
building
in
the
ipfs
community
whoa
so
I?
So
before
we
begin,
if
everyone
could
put
their
names
in
the
ipfs
all-hands
weekly
agenda,
I'll
put,
oh
I.
Think
I
just
dropped
it
in
there.
For
you,
it's
the
link
in
the
chat.
Terry
will
be
taking
notes
for
today.
So
yay
Terry.
Let's
give
him
a
round
of
applause.
I'm.
C
Sorry
and
it
looks
like
we
don't-
have
any
special
announcements
today,
so
we
are
going
to
get
right
into
our
presentation,
which
is
going
to
be
presented
by
Michelle
and
she's.
Gonna,
give
us
a
sneak
peek
of
what
protocol
Labs
is
doing
in
terms
of
like
design
and
ipfs
and
ways
that
we
can
think
about
design
so
Michelle.
It's
all
you.
A
A
B
Exactly
don't
even
good,
let's
not
even
start
on
the
tabs
versus
the
windows,
windows
and
ridiculous
amount
of
tabs
going
on.
So
there
we
go
cool,
say
something
if
you
cannot
see
a
very
plain-looking
design,
plus
I
PMS,
starter,
slag,
beautiful,
okay.
Well,
first
of
all,
let
me
introduce
myself
in
case
anyone
McCall
does
not
know
me.
B
My
name
is
Michelle
Hertzfeld
I
joined
the
ipfs
team,
maybe
it's
nine
or
ten
months
now,
y'all,
crazy
town
and
over
the
last,
so
I
was
hired
as
a
product
manager,
but
in
my
past
I
had
built
remote
design
teams.
So
I've
been
trying
to
help
our
design
team
get
off
the
ground.
There's
some
lovely
folks
for
also
for
the
design
team
on
this
call,
so
they
can
weigh
in
at
any
point.
Anyone
can
win
any
points
at
me
and
say:
hey
you're
here
talking
nothing
and
asks
for
what
I'll
talk
about
today.
B
You
know
we'll
just
get
started
and
then
I'll
go
from
there.
Okay,
what
is
designed
we'll
start
with
that?
It's
a
front
word
because
I
mean
there's
a
billion
things
you
could
include
in
this
word
right.
You've
got
like
architecture
and
fashion
design
and
like
software,
design
and
information
architecture,
so
many
different
things,
but,
of
course
when
we
all
are
when
we
hear
the
word
design,
oh
we're
gonna
start
the
design
team
or
something
like
that.
B
Lots
of
folks
go
straight
to
this
specific
subset
of
this
big
grab
bag
of
what
could
be
design
things
that
I
think
a
lot
of
people,
think
of
it
as
visual
stuff
I
like
illustration
and
graphic
design,
visual
design,
maybe
web
design
thrown
in
there.
Remember
that
word
but
I'm
sure
there's
many
of
you
on
this
call
who
also
know
that
it's
much
broader
than
that
and
in
our
field
when
I
say
our
field,
I
mean
software
stuff.
You
know,
building
things
for
the
internet
and
for
computers.
B
This
additional
highlighted
chunk
of
stuff
often
falls
into
the
quote:
unquote
designer
of
you
as
well,
and
things
like
experience,
design,
information,
architecture,
product
design,
so
many
different
words.
So,
every
time
we
talk
about
what
is
the
design
team
that,
because
it's
actually
kind
of
a
bit
of
an
existential
question,
I
would
say
that
one
of
the
things
that
pulls
together
a
lot
of
these
feels,
at
least
on
the
software
side,
is
the
design
process
that
folks
use
to
actually
solve
problems.
It's
more
like
a
problem
solving
process
than
anything
else.
B
I
think
this
there's
lots
and
lots
of
versions
of
a
chart.
That
kind
of
looks
like
this
and
lots
of
different
people
describe
this
in
different
ways,
but
the
overarching
point
and
why
I
chose
this
one-
is
that
there's
a
bit
of
a
at
different
points
in
a
design
process,
you're
focusing
on
different
types
of
design.
So
you
can
go
back
to
oh
wow.
That
first
slide
with
all
the
different
words
as
some
of
us
just
that
you
need
to
make
sure
you're
using
the
right
thing
at
the
right
time.
B
Maybe
at
the
end,
it's
a
little
bit
less
and
you're
doing
more
development
sideways,
but
it's
all
this
big
loop
iterative
process,
how
you
figure
out
what
you
should
be
doing
in
the
world
and
how
you
show
that
to
other
humans
and
make
them
understand
things
right,
using
the
right
technique
at
the
right
time,
as
I
said
so
that
was
a
super-fast
intro
I
know
you
don't
want
to
hear
me
talk
till
the
end
of
time.
So,
okay,
what
about
ipfs?
That's
what
you're
here
for
so
this
is
a
super.
B
B
One
thing
is
that
we're
hoping
to
build
an
open
source
design
practice
we'd
love
to
be
an
open
source
project
that
can
make
great
design
decisions
as
a
lot
of
people
must
call.
Probably
no
open
source
projects
aren't
really
known
for
their
spectacular
design
work
either.
A
visual
or
experience
design,
but
we
believe
we
can
do.
We
can
improve
that
conversation
and
we're
looking
I
at
least
I'm
looking
to
work
with
other
open
source
projects
as
well
to
help
the
kind
of
state
of
the
art
and
that
in
that
included,
more
design
work.
B
The
benefit
that
of
doing
this
sort
of
more
user
centered
design
stuff
is
that
sometimes
it
turns
that
we
will
build
nothing
at
all.
When
you
do
more
research
up
front
sometime,
you
find
out
that
you
would
have
embarked
on
a
very
unhelpful
journey
and
considering
an
art
field,
there's
so
many
places
we
could
go.
You
know
what
should
we
spend
our
time
on
to
build
this
future
of
the
Internet
I?
Have
it's
really
really
valuable
to
do
some
of
that
upfront
research?
B
The
thing
that
we
are
always
lacking
is
product
management
and
design,
design,
work
or
design
folks,
because
up
till
now
it's
taken
a
lot
of
time
and
engagement
to
do
that.
Work,
not
sort
of
not
a
sort
of
thing
where
you
can
like
take
off
a
Help
Wanted
feature
and
do
it
in
a
weekend.
It's
a
much
more
broad,
it's
a
broader
thing.
So
how
can
is
there
a
way
that
we
can
make
that
something
that
I've
sees
easier
to
engage
with?
B
How
do
we
figure
out
the
best
way
to
get
that
information
to
our
protocol
level
decisions
in
a
way
that
supports
a
good
use
cases?
Don't
whine
I
think
that's
a
really
interesting,
spectacular
problem
and
I'm
excited
about
it,
and
then
the
last
note
on
this
designing
IVFs
face
is
that
a
lot
of
our
work
will
be
around
integrating
user
research
techniques
and
other
design
techniques
into
code
and
acts.
You
know
our
work
doesn't
have
a
GUI
a
together,
although
some
of
it
some
of
it
it
does.
B
Some
of
it
does,
of
course,
and
that's
important,
but
for
the
other
parts
that
involve
AP
is
and
CL
is
and
documentation,
I
might
teach
things
that
doesn't
mean
that
that
doesn't
need
some
user
research
or
user
engagement,
as
well
as
lots
of
fun
to
make
experiences
for
developers.
As
you
all
probably
know,
all
right.
B
So
that's
all
of
the
intro
stuff
I
have
and
then
I
wanted
to
just
show
you
one
example
of
what
I've
been
up
to
on
the
user
user
research
side.
So
Porsha
your
introduction
was
correct.
With
one
caveat,
that
is
to
say,
there's
a
lot
of
design
work
going
on
and
ipfs
that
I'm
certainly
not
going
to
cover
all
the
specifics
of
that
work
for
except
you
can
tell
that.
I've
talked
a
lot
about
user
research
and
discovery
process
in
this
presentation.
B
But
of
course,
there's
all
sorts
of
visual
design
work,
graphical
user
interface
work
other
things
going
on
as
well,
and
I
hope
that
our
team
or
design
team
will
continue
to
present
over
the
next
few
months
then
get
maybe
some
specific
examples
of
all
the
other
stuff
but
I'm
showing
this
because
I
think
a
lot
of
people
haven't
seen
it
and
yeah,
and
it
was
something
that
but
I
was
I
was
doing
so
I
can
actually
speak
to.
It.
B
Is
a
user
experience
research
among
other
things,
so
what
we've
been
trying
to
do
is
again
figure
out
how
to
get
input
to
ipfs
protocol
earlier
decision-making
again,
when
the
use
of
it
by
non
developers
is
a
ways
off
one
of
the
ways
we've
been
doing.
This
is
planning
some
user
discovery
workshops
with
likely,
first
adopters
or
people
who
will
be
more
interested,
probably
or
we
think
will
be
more
interested
than
others
in
our
technology.
One
of
those
is
the
scientific
research
community,
and
so
we
went
to
esup
as
the
Earth
Science
Information
partners.
B
Federation
it's
in
the
US
has
lots
and
lots
of
people
who
deal
with
satellite
data,
these
kinds
of
things,
and
we
had
a
workshop
there.
Some
of
the
points
here,
let's
see
what
would
be
interesting
to
you
all.
Let's
see,
yes,
here's
an
example
of
you
know
some
of
the
things
we
presented
the
agenda
and
one
of
the
challenges
we
have
in
our
space
is
that
this
technology
so
new,
you
can't
run
standard
user
research
workshops
where
you're,
just
as
I
know
use
this
thing
or
what
do
you
think
or
like?
B
And
how
do
you
imagine
in
the
future
to
just
do
well,
anyways?
You
have
to
actually
teach
people
around
what
that's
like,
because
first,
and
so
this
workshop
had
half
of
it,
which
was
an
acid
malt,
giving
an
introduction
to
decentralisation
and
the
people
in
the
room.
Some
of
them
were
very
familiar
with
our
technology.
Some
you
know
not
at
all,
and
then
after
that
baseline
was
there
trying
to
figure
out
a
way
to
support
people
to
talk
about
the
benefits
and
kind
of
scary
points
of
that
work.
B
We
ended
up
doing
it
by
asking
people
that
to
write
down
notes
on
different
types
of
post-its
throughout
the
initial
part
of
the
presentation,
you
know
write
as
things
are
coming
up
from
them
about
opportunities
and
things
that
are
a
little
bit,
maybe
not
so
much
had
people
break
into
groups
to
share
notes
with
each
other.
If
you
don't
already
know,
that's
a
very
typical
design
technique
having
a
room
of
40
people
discuss
amongst
40
people
doesn't
really
work
very
well,
because
whoever's
loudest
will
get
their
voices
heard.
B
You
know,
people
drawing
out
their
pathways
and
the
next
step
for
me,
then,
is
synthesizing
that
into
okay.
So
what
does
that
mean?
Overall?
So
I've
been
taking
all
of
that
that
worked
with
some
post-its,
putting
it
into
digital
form
and
then
coding
that
information,
if
you're
not
familiar
with
coding
and
the
user
research
sense.
So.
B
Yet
I
would
like
to
write
up
a
report
that
cuts
all
this
together
and
makes
it
into
a
more
usable
form.
Some
example
of
reports
from
other
things
that
I've
done,
might
look
like
user
journeys
or
presentations.
That's
with
you
know,
quotes
from
folks
different
levels
of
confusion
along
a
process
line
and
then
specific.
B
Given
those
insights
about
where
people
are
confused,
for
example,
what
some
next
steps
might
mean
for
a
product,
and
then
this
is
my
favorite
epic,
huge
service,
blueprint,
plus
emotional
journey
map.
It's
good
stuff
things
like
this,
though,
are
great
because
you
end
up
so
the
horizontal
swim
lanes
on
the
bottom
are
different
parts
of
the
system
and
the
bottom
one.
There
is
like
the
backend
system.
B
Top
Whitman
could
be
like
what
a
user
wants
to
do
you
and
like
how
they
interact
with
a
service
person
like
a
human,
and
so
if
you
then
map
that
along
where
people
are
happy
or
not,
you
can
say.
Oh,
my
goodness,
out
of
all
the
time
we
have
this
quarter,
we
should
definitely
focus
on.
You
know
this
part
over
here,
because
people
are
really
unhappy
and
they
look
down
the
line
and
see
what
processes
interact
right.
There
you're
often
surprised
at
the
part,
that's
broken
once
you
break
it
down
into
those
layers.
B
Okay,
so
then
integrating
human
centered
design
into
your
work.
What
can
you
do
because
really
it's
nothing
unique
or
special,
as
you
probably
know,
to
like
design
folks
that
they
can
do
the
stuff,
it's
only
practice
with
research
techniques
about
how
to
do
this
work.
Well,
so
anybody
can
read
about
how
to
do
that
and
practice.
Unlike
anything
else,
that's
that
you
know
the
more
you
do
it
the
better!
You
go,
I'm,
not
gonna,
go
into
slots
of
details
here,
because
we
don't
have
time
but
feel
free
to
reach
out
to
me
or
I.
B
Think
we
share
these
slides
later.
I'm,
not
sure
how
that
works,
but
I've
grabbed
a
couple
links
to
two
of
my
favorite
books
in
this
area
and
also
I've
got
a
link
to
my
can
board,
with
some
of
my
favorite
articles
like
how
to
get
started
on
this
sort
of
work.
So
there
you
go.
That's
all
I've
got
today.
I
wanted
to
just
make
a
quick
overview
so
now
questions
dive
into
anything
more.
Anyone
else
on
the
design
team
wants
bad
things.
C
I
am
really
excited
that
you
have
a
pin
board
and
really
excited
that
you
added
some
of
the
books
that
inspire
or
inform
your
work,
because
I
think
there's
a
lot
of
people
out
there
who
are
designers
who
want
to
go
about
hey.
How
can
I
design
this
user
experience
or
this
app
to
best
solve
this
problem
so
great
at
this
point,
oh
we're
going
to
go
over
questions.
So
if
you
can
put
your
question
in
a
chat
and
Michelle
can
answer
it
cool.
C
B
So
from
my
experience
and
like
I
said
Code
for
America
these
sorts
of
things,
some
of
the
problem
is
that
experienced,
experienced
designers
not
experienced
design
alone,
might
overlap.
Look
for
the
reasons
behind
like
okay.
Why
do
you
want
that?
Why
do
you
want
to
make
that
decision?
I
need
that
input,
so
I
can
figure
out
what
I
should
design
or
how
I
should
do
it.
This
is
part
of
the
reason
that
I
think,
perhaps
our
team-
that's
you
know.
The
core
ipfs
team
might
end
up
focusing
more
on
the
user
research
side.
B
It
helps
to
be
from
the
original
company
or
whatever
it
is.
So
you
have
some
legitimacy
and
calling
all
these
folks
and
saying,
like
I,
won't
share
your
information.
You
know
all
these
processes
that
make
people
feel
safe
to
share
their
their
insight.
So,
to
summarize
that
I'm
hoping
that,
if
we
can
maybe
do
some
of
the
legwork
up
front
and
then
break
that
down
I'm,
not
sure
how
but
break
that
into
ways,
then
maybe
it'll
be
more
effective,
but
yeah
I'm
curious.
What
other
folks
think
to
you
on
the
call?
E
Sure
I
was
just
thinking
about
what
we
do
as
a
company
and
when
we're
building
a
lot
of
tools
for
developers
which
are
you
know,
they're
code
and
libraries,
and
you
know
how
they
integrate
something
but
I
don't
think
like
we.
It's
generally
programmers
develop
writing
things
for
programmers
and
there's
really
no
designer
in
the
loop,
like
I
heard,
I
think
we
might
be
missing
something
there.
B
Yeah
Jim
I
agree
we're,
hopefully
good
gonna
get
more
folks
to
help
out,
but
yet
the
previous
work
I've
done
API
usability
testing,
you
know
all
sorts
of
CLI,
so
so
there's
no
reason.
These
techniques
can't
be
used
in
that
space
as
well,
and
it
should
be
because
then
you
end
up
with
a
better
tool
that
people
understand
and
use.
So
in
their
regards,
it's
like
right
now.
What
do
we
do
and
if
anyone
is
interested
you
can
reach
out
and
I
can
give
you
some
tips
on
that.
B
But
the
very
high
level
thing
is
show
people
you
know:
have
people
test
your
work
and
if
you're
not
prioritizing
systems
that
make
it
easy
for
people
to
test
your
work
like
if
it
takes.
You
know
like
okay,
it
works
on
your
machine,
but
it
takes
a
half
hour
for
someone
else
to
set
it
up
on
their
machine.
You
should
prioritize
that
work,
so
it's
easier
for
you
to
get
that
feedback
loop
in
yeah
and,
for
example,
some
ap,
some
stuff.
Of
course
you
don't
want
to
release
to
the
whole
world
right
away.
B
B
E
B
Yeah,
hopefully
we'll
get
there
I
mean
I've,
seen
a
typical
pre
development,
space
user
research,
the
more
open-ended
side
of
things
which
I
think
maybe
is
doing
what
you're
referring
to
like.
How
do
you
even
know
what
people
want
and
what
should
we,
what
sort
of
things
input
should
we
get
before?
We
can
start
coding
anything
you
can
do
a
really
solid
run
on
that
in
six
to
eight
weeks,
but
it
does
take
that
long.
B
F
Hey
Michelle
just
sent
a
question
really
right
now.
A
lot
of
ipfs
is
really
sort
of
command
line
based,
but
in
one
of
the
hardest
problems
in
programming
is
naming
things.
So
is
there
a
good
and
during
the
design
process
of
a
tangible
way
of
allowing
the
user
to
to
get
to
some
commonality
on
name
space.
B
Absolutely
you
can
definitely
do
I
use,
adjust
or
usability
testing
on
words
and
workaround.
Okay.
What
should
we
call
the
thing,
or
what
do
people
understand
that
this
thing
is
there's
a
couple,
different
directions
that
can
take
I.
Suppose
if
it's
the
like
do
people
understand
this
at
all,
then
that
one's
a
little
bit
more
straightforward?
It's
like
write
the
sentence,
show
it
to
someone.
What
do
you
think
this
means
or
draw
it
put
it
on
a
page?
B
B
Do
that
with
lots
of
people
in
terms
of
figuring
out
from
the
start,
how
things
might
be
organized
or
called
the
same
thing
or
not,
I
should
say
the
general
like
way
to
get
information
and
a
lot
of
people's
brains
is
to
have
people
if
you're
in
a
room.
You
just
do
this
with
stickies,
but
if
you're
not
you
can
do
it
on
with
a
mural
or
something
like
that.
That's
got
a
digital,
whiteboard
sort
of
thing.
Have
people
write
what
they
think
these
different
things
should
be
called
or
what?
B
What
meaning
they
need
out
of
the
thing
on
two
different
little
stickies
and
drop
them
all
in
a
whiteboard
and
start
grouping
and
rearranging
and
putting
them
together
to
see
where
the
commonalities
and
the
gaps
are,
and
as
people
talk
about
it,
they
tend
to
find
out.
Oh
I
didn't
mean
that
or
oh
I
Memphis
or
no
that's,
not
the
right
group
or
whatever.
That
is
there's
that's
in
a
very,
very
high
level.
Look
at
that,
but
I
can
certainly
look
around
for
some
like
step
by
step.
B
G
Do
you
think
in
the
meantime,
I'm
gonna
create
an
issue
on
ipfs
guru,
which
is
already
public
and
is
almost
that's
the
closest
thing
we've
got
so
I'll
create
an
issue
there
and
I'll
link
to
in
a
chat,
narrow
and
if
anyone
is
interested
in
carrying
on
the
conversation,
they
should
just
comment
on
that
issue,
and
then
we
will
know
who
you
are.
That's
you
when
we
have
a
better
public
forum
for
conversation.
Thank.
B
C
D
Either
ie
awesome
presentation,
I
was
just
thinking
about.
You
said
that
you
were
talking
to
potential
early
users
like
researchers
in
the
sort
and
I
was
wondering
what
other
kinds
of
Democrat
demographics
or
early
users.
He
was
thinking
about
when
identifying
the
requirements
or
design
decisions
to
make
it
easy
for
them.
Yeah.
B
And
I'm
writing
what
you
wrote
in
the
chat,
yep
well,
I'll
answer
what
you
just
asked
for
some,
maybe
to
your
other
point
in
there.
So
one
of
what
we're
trying
to
sort
out,
of
course,
we've
got
developers
want
to
build
apps,
that's
our
very
direct
feedback,
loop
back
and
forth,
and
what
I've
been
trying
to
focus
on
is:
okay,
what's
the
next
step
next,
who
would
be
the
next
layer
after
that?
B
So
it's
looking
for
folks
who
have
relatively
high
tolerance
of
command
line
stuff,
that's
like
folks
who
still
are
in
Louise
a
bit
but
needs
a
slightly
higher
higher
introduction
levels
so
and
whose
area
of
expertise
might
really
benefit
for
something
like
this.
So
that's
how
we
ended
up
that
these,
like
large
science
data,
sets
like
the
verifiability
and
resilience
that
a
system
like
this
provides
could
be
huge.
B
Also,
looking
at
data
archiving
and
library
spaces
like
places
that
have
huge
infrastructure
for
dealing
with,
you
know
stewarding
information
across
like
three
universities
all
together
and
that
kind
of
thing.
But
there
are
people
that
would
also
have
developers
on
staff
or
their
infrastructure
folks,
or
something
like
that
and
then
at
a
next
of
a
lot.
Let's
level
up
from
that
say
something
like
a
local
librarian
who
might
want
to
support
stewarding
data
across
their
local
community
and
yeah.
Maybe
they
do
stuff
there.
B
C
Awesome
and
the
next
question
is
from
Chris
Chris
Waring,
so
he
can't
use
his
mic
at
the
moment.
He's
gotta.
Do
you
want
to
so
it's
a
similar
to
Jim's
question.
Do
you
think
we'll
develop
our
own
human
interface
guidelines
to
help
bootstrap
external
app
developers?
I
suspect
this
will
make
more
sense
once
we
have
an
ipfs
app
store,
yeah.
B
I
think
it'll
be
really
interesting
to
see
what
the
right
right
level
of
guidance
will
be
to
provide
I
think
something
there
will
be
super
helpful
and
also
around
the
experience
side
of
things
like
there
could
be
a
great
opportunity
to
provide
more
guidance
on
like
how
people
look
at
trust
or
how
people
think
of
sharing
that
gets.
Some
of
the
you
know
helps
people
start
it
a
little
bit
higher
level
of
understanding
and
what
they
need
to
provide
in
their
apps,
so
that
people
feel
comfortable
using
the
distributed
web.
B
So
there's
the
you
know,
interface,
human
interface,
side
of
thing
and
there's
also
the
human
experience
side
of
things
and
I
think
there's
a
great
opportunity
to
see
how
we
can
share
that
in
a
way,
that's
approachable
and
not
like.
Oh,
my
gosh
I
have
to
read
ten
years
of
research
to
understand.
What's
going
on
again
back
to
that
like?
C
We're
going
to
end
it
there
Thank
You
Michelle,
for
giving
us
this
talking
for
anyone
who's.
Looking
at
the
video
and
if
you're
interested
in
design
and
ipfs,
we
have
a
link
here.
We
also
have
the
link
in
the
YouTube
video.
If
you
look
below
and
thank
you
very
much
and
I'll
see
you
next
week
at
the
next
ipfs
weekly
meeting,
take
care,
bye,
bye,
thank.