►
Description
On the June 18th Local & Offline Collaboration call Jim Kosem will join us once more, to share the final results of his work on IPFS Mobile Design Guidelines.
Topic: IPFS Mobile Design Guidelines: Principles for building user-centered and device-respecting IPFS mobile apps and services.
Summary:
Building on the previous phase of research into how P2P and IPFS are used in apps today and user attitudes around them, we've developed an early set of principles to use when designing and building IPFS and P2P apps and services for mobile devices. We'll walk through the principles and a set of example scenarios that illustrate them in action._
https://github.com/ipfs/local-offline-collab/issues/25
A
To
the
cloud
we
are
now
recording
hello,
everybody
welcome
to
the
June
18th
edition
of
the
monthly
local
and
offline
collaboration
Meetup.
My
name
is
Dietrich
and
I
am
your
very
brief,
emcee
and
host
today,
as
we
listen
to
mr.
Jim
Kusum
will
present
to
us
the
final
output
of
his
last
couple
months:
work
on
IPF,
SPP
mobile
design
guidelines.
B
B
B
There
can
everybody
see
that
all
right,
yeah,
you
see
a
get
book
thing
that
says
finding
soap
at
the
top,
but
yeah,
okay,
yeah
so
yeah,
just
to
quickly
recap
what
you
find
out
in
the
first
half
of
the
project,
which
was
about
the
research
and
just
it's
kind
of
so
we
split
it
up
at
the
findings
and,
of
course,
you're
at
your
leisure
you're.
You
there's
tons
of
interviews
to
look
through
with
different
sorts
of
findings.
B
Survey
of
the
various
interaction
patterns,
yeah,
there's
quite
a
bit
to
go
through
them,
but
the
quick
version
of
it
is:
is
this
right
here
and
it's
kind
of
blocked
into?
You
could
say
these
three
rough
categories,
which
is
around
the
cloud
services,
p2p
usability
and
awareness
of,
and
security
and
identity
and
kind
of
real,
roughly
or
quickly.
Some
of
the
things
we
found
out
is
the
cloud
services
are
pervasive
and
have
done
a
ton
of
work
in
in
terms
of
in
by
no
stretch
we
should
be
throwing
any
of
that
away.
B
But
the
question
is
a
lot
of
people
had
questions
about
these
cloud
services
on
which
we
are
so
dependent,
so
some
people
weren't
quite
sure
about
them,
but
you
know
they
use
them
regardless,
because
they've
become
kind
of
intertwined
within
the
fabric
of
our
lives.
But
there's
the
thing
is:
is
that
file
management
is
a
big
thing
of
it.
You
know-
and
this
includes
access
to
what
and-
and
this
again
brings
up
this
issue
of
privacy,
so
this
kind
of
is
always
underlying
thread
about
privacy.
B
This
is
why
people
are
having
questions
about
cloud
services
and
then
the
usability
seems
from
our
sample
to
be
as
important
as
security,
but
you
know
again,
they're
always
intertwined,
but
it's
about
finding
this
balance
and
kind
of
shredding
that
thin
line
between
the
two
and
one
thing
that
cannot
is
well.
That's
quite
interesting
from
the
research
is
that
users
don't
want
to
necessarily
know
what
is
making
things
work.
So
it's
this
idea
about
trust
about,
especially
on
the
mobile
device.
There
seem
to
be
this.
B
You
know
a
lot
of
context,
switching
a
lot
of
this
kind
of
pervasive
partial
attention
issues
so
that
they
don't
want
to
know
what's
making
work
just
that
it
does
that's
particularly
important
in
mobile.
It
seems
and
PTP
as
a
concept
is
quite
easily
understood
by
everybody.
We
talk
to
again
with
a
sample
size.
This
is
21
to
22
people.
But
again,
that's
going
from
you
know
an
expert
activity.
Well,
they
would
obviously
know
what
it
is,
but
to
early
adopters.
B
They
were
all
familiar
with
the
concepts
behind
this
and
as
well
as
people
in
emerging
markets
and
elsewhere.
That
would
be
potentially
interested
in
this
and
then
the
other
thing
that
came
out
is
about
the
kind
of
mobile
life.
You
could
say
itself,
which
was
about
notifications,
how
notifications
are
kind
of
their
function.
Door.
Pervasiveness
they're
over
pervasiveness
is
quite
an
issue
as
well
and
again
about
the
phone
itself
and
what
separates
it
from
the
desktop
and
what
separates
it
from
these
other
experiences.
Are
we
kind
of
research
before
in
particularly
with
a
browser?
B
This
is
what
you
could
call
the
infrastructure
of
mobile
life,
which
is
this
idea
of
battery
in
Israel
and
signal,
and
you
know
these
two
things
and
nothing
can
work
without
it.
You
know
these
are
the
pipes
that
keep
it
all
going
and,
and
mainly
security
is
hard.
It's
really
hard
a
lot
a
lot
of
times
people,
despite
their
best
intentions.
They
they
just
can't
be
bothered
a
lot
of
times
and
even
a
lot
of
the
early
adopters
we
spoke
with.
B
They
had
similar
sort
of
opinions
as
well
and
kind
of
what
privacy
and
security
means
is
very
nuanced
again
as
well,
so
in
a
context
opponent.
So
again
what
you
place,
what
value
you
place
on
your
online
life
or
what
kind
of
data
you
have
online
also
depends
on
kind
of
how
you
value
privacy
and
what
you
wouldn't
you
want
to
secure
and
how
much
and
again-
and
in
regards
to
the
theme
of
this,
this
meetup
is,
is
the
role
of
offline.
B
Very
into
it,
so
it's
kind
of
looking
at
how
we
can
make
that
fit
into
these
sorts
of
things
and
kind
of
like
nicely
slide
ipfs
into
these
sorts
of
mobile
health
behaviors.
So
again,
on
looking
at
the
offline
kind
of
making,
this
I
guess
dependable,
it
is
part
of
it
and
and
then
looking
at
security
and
all
these
other
sort
of
things
so
moving
on
into
the
actual
design
and
kind
of
the
part
of
it
was
around
the
design
strategy.
B
So
the
the
strategy
itself
was,
we
started
with
with
these
kind
of
key
questions
to
frame
where
to
get
started
with
a
design,
and
these
questions
are
outlined
here
and
you
know
and
they're
largely
about
how
can
design
begin
to
answer
these
questions.
So
we
took
these
and
looked
at
kind
of
how
we
could
arrange
the
the
design,
and
that
was
looking
at
well
into
prints,
dividing
into
principles
and
building
scenarios
based
on
those
principles.
B
So
what
we
wanted,
what
we've
done
is
to
kind
of
build
the
overall
rationale
from
build
based
on
the
research
and
then
from
that.
Then
moving
on
to
examples
and
illustrations
of
that
that
designers
and
developers
and
builders
of
on
ipfs
for
mobile
kind
of
using
examples
and
kind
of
carry
things
forward.
And
it's
all
about
you
know
taking
this
research
and
translating
it
to
conceivable
and
useable
things
and
building
these
interaction
and
interface
design
framework,
which
will
be
illustrated
within
the
scenarios
and
the
principles.
B
And
it's
all
about
this
mobile
design
guidelines
being
this
living
guide
and
it's
in
making
it
a
reality
for
everybody.
So
again
to
kind
of
being
the
living
documents
and
then
kind
of
develop
and
enhance
this
practice.
And
this
is
essentially
designed
for
design
on
and
because
we
can't
necessarily
rely
on
component
libraries
to
describe
it.
B
We've
had
to
again
build
these
principles
and
then,
with
on
on
top
of
those
principles,
build
out
the
scenarios
and
go
from
that
overall
thinking
with
the
principles
to
the
scenarios,
which
are
examples
of
how
to
think
through
and
design
for
particular
issues
which
we'll
get
into
in
a
minute.
The
first
thing
we
did
is
we
had
a
workshop
with
active
idea,
fest
developers,
so
internal
and
external,
to
protocol
labs,
and
we
went
through
the
process
of
taking
those
research
findings
and
taking
those
key
questions
that
were
outlined
in
design
strategy
and
prioritizing
them.
B
But
the-
and
you
can
kind
of
see
here
and
you
can
read
about
key
takeaways
there,
but
what
it
was
is
about.
What
we
wanted
to
do
through
the
workshop
is
link
these
questions
and
to
users,
so
that,
because
we
want
to
make
this
a
user
centered
exercise,
we
looked
at.
Who
is
the
user
and
linking
the
problems
to
them?
And
you
didn't
see
a
bit
of
that
here
and
prioritizing
that
and
then
building
out
their
needs,
filling
out
some
user
personas
and
ranking
them
and
then
finally
linking
those
users
to
problems.
So
again.
B
Is
this
understanding
in
privacy
and
secured,
which
again
came
up
and
kind
of
attaching
that
and
how
to
make
that
kind
of
evident
in
people's
interactions
with
that
applications
and
simplicity
came
up
a
number
of
times
making
things
simple,
not
making
complicated,
which
was
obviously
a
paramount
for
something
like
this,
because
if
you're
introducing
a
new
technology
and
potential
new
methods
of
doing
things,
that's
absolutely
important,
especially
on
mobile,
where
the
attention
is
obviously
drastically
reduced.
And
it's
also
more
frequent
to
so
people's
in
and
out
is
more
frequent
and
shorter.
B
So
and
then
this
idea
about
visibility
and
discovery
and
contacts,
because
a
mobile
device
is
after
all,
well
it's
supposed
to
be
at
integrate
a
communication
device.
So
it's
this
idea
about
the
files
and
the
people
attached
to
them
and
the
privacy
in
your
communications
between
these
people
any
questions
so
far.
Anybody
should
okay,
so
yeah.
The
first
thing,
the
first
half
of
the
the
face.
First
major
half
of
it
is,
of
course,
these
principles
and
we
broke
it
down
into
five
there's
also
five
scenarios
as
well,
so
the
first
is
respect
the
device.
B
The
second
is
explain,
don't
overwhelm
I'll,
go
in
then
in
a
in
depth
in
a
minute,
make
privacy
work
for
the
user,
give
control
over
data
and
be
seamless,
and
these
are
again
sort
of
providing
this
there's
overall
kind
of
this
overarching
thinking
this
rationale
to
the
design
and
how
to
think
about
the
design
and
taking
that
research
in
starting
to
translate
it
into
real
world
applications.
So
the
first
is
respect
the
device
come
on
there.
B
We
go
and
each
of
these
principles
outlines
kind
of
taking
it's
kind
of
particular
bits
from
different
parts
of
the
research
and
outlining
it
and
then
developing
patterns
around
that
so,
for
instance,
with
respect
to
device,
it's
all
about
kind
of
learning,
about
the
nuances
of
smartphones
and
working
with
the
reality
of
people's
lives
on
them.
So
again,
this
is
mobile.
Life
is
a
lot
different
from
desktop,
so
learning
about
these
kind
of
differences
of
whether
to
be
subtle
or
drastic
and
understanding
the
specific
conditions
and
working
with
them
for
a
unique
solution.
B
B
If
there's
signal
and
indicating
that
you're
offline
or
indicating
that
you're
online
and
kind
of
this,
you
know
kind
of
fine
line
between
display,
because
again
the
display
is
very
limited
and
in
thinking
about
time
and
costs
you
know
so
in
particularly
in
emerging
markets.
Data
costs
are
quite
a
big
issue
and
some
they're
not,
but
the
idea
is
likely.
C
B
And
the
next
one
is
next
principle
is
explained,
don't
overwhelm,
and
a
lot
of
that
is
about
just
being
supportive
again
that
when
you're
trying
to
introduce
a
new
way
of
work
or
a
slightly
new
way
of
working
or
new
technology,
people
might
not
be
used
to.
And
it's
kind
of
about
being
supporting.
And
a
lot
of
that
is
before
you
move
on.
B
A
For
some
cards
and
three
phones
right
and
to
part
of
this
in
the
research,
is
it's
really
difficult
to
tease
those
bits
out
right?
So
this
combination
of,
like
the
words
from
the
people,
you
interviewed,
malice,
but
then
also
understanding
those
words
in
context
and
marrying
those
two
to
be
able
to
understand
what
these.
What
these
learnings
were
to
be
able
to
provide
guidance
for
the
next
10,000
p2p
based
application.
Builders
right
so
I
thought
that
respect
advice
when
it
was
was
probably
one
of
the
most
challenging
in
terms
of
understanding
what
the
guidance.
B
Yeah
definitely
a
good
point.
It
was
trying
yeah
because
it's
with
with
phones,
especially
it's
interesting,
but
from
talking
to
so
like
such
a
broad
range
of
users
that
people
just
sort
of
put
up
with
a
lot-
and
they
shouldn't
have
to
so
design-
should
address
like
all
of
that
stuff,
that
people
are
just
kind
of
putting
up
with.
You
know
two
different
phones
for
different
sins:
three
different
battery
packs.
It
shouldn't
be
like
that
I
guess,
but
people
put
up
with
a
lot
more
so
yeah.
There
was
definitely
yeah.
B
This
exactly
like
Dietrich
said,
is
really
hard
to
kind
of
tease
out
I
mean
this.
One
was
also
sort
of
hard
to
tease
out,
which
is
this
idea
about
not
overwhelming
the
user
with
information,
and
it's
a
lot
of
it
is
about
kind
of
just
being
supportive
or
just
enough
supportive,
so
about
what
is
happening
and
when
being
kind
of
gentle
about
things
and
not
overwhelming
the
user,
but
with
the
notifications
or
confirmations
necessarily
and
in
a
lot
of
it,
is
about
onboarding
really.
B
So
we
looked
at
a
lot
of
different
onboarding
processes
with
p2p
and
blockchain
apps,
and
it's
about
focusing
on
the
benefits
and
not
the
technologies,
largely
what
it's
about,
and
it's
how
to
kind
of
make
that
short
and
concise
and
how
to
kind
of
kind
of
put
this
all
throughout
the
apps.
Really,
you
know
these
nice
supportive
messages,
things
highlighting
the
benefits
of
these.
A
B
A
Communicating
what
the
capabilities
are
is
something
that
a
lot
of
these
apps
that
were
looked
at
do
kind
of
implicitly,
but
not
explicitly.
Yeah
I
think
this
one's
really
really
important
design
lesson
around
users,
don't
understand
what
the
value
is.
If
you
don't
explain
it
to
him
to
that
right,
a
lot
of
times,
understanding.
B
Entirely
and
one
of
the
interesting
concepts
I
think
is
well
that
kind
of
kind
of
wraps
us
all
together.
Is
this
idea
by
don't
highlight
what
you're
doing
too
much
you
know
about
you
know
about
this.
You
know
the
IP
FS
at
the
end
in
the
above
screen,
or
that
it's
it's
about
kind
of
putting
this
information,
hiding
the
benefits
upfront,
sorry
displaying
the
benefits
upfront,
getting
the
getting
the
user
in
nicely
and
quickly
and
confidently
and
then
finally
kind
of
trickling
in
this
sort
of
this
thing
is:
oh,
it's
built
on
this
thing.
B
This
thing
that
gif
does
does
all
the
stuff
that
makes
this
app
so
great
to
use.
So
it's
about
some
of
the
deal,
a
lot
of
Z,
Web,
Apps
and
blockchain.
Things
in
particular
are
very
much
about
throw
the
technology
words
at
you,
self,
sovereign,
etc,
etc,
etc,
and
just
overwhelming
people,
and
that
creates
even
bigger
barriers
to
entry,
and
that's
what
one
of
the
principles
is
to
avoid
I.
B
Think
in
again,
privacy
comes
up
in
weird
spots
and
in
different
ways
than
people's
understanding
of
it
varies
drastically,
but
a
lot
of
it
is
related
to
kind
of
their
values,
and
it's
but
fundamentally
is
about
privacy
being
well
a
right.
You
know,
but
it
should
be
easy.
You
know
that's
the
thing
it
has
to
be
easy
and
it
has
to
be
just
enough
and
looking
at
some
patterns
again,
it's
it's
about.
I.
Think
one
of
the
most
effective
ones
is
a
starter
mode.
You
know
that
you
don't
be
easy.
B
B
But
to
kind
of
give
you
know
that
that
onboarding-
because
this
is
part
of
onboarding
is
the
settings
is
getting
that
you
know,
is
quickly
done
as
possible
and
to
make
it
is
less
confusing
as
possible
and-
and
this
is
part
of
it
as
well
too
so
about
accounts,
so
people
all
the
pain.
All
people
interviewed
had
loads
of
accounts
and
I
think
the
least
amount
of
accounts
somebody
interviewed
we
talked
to
it
had
I.
Think
was
five.
B
So
if
you
imagine,
you
have
a
minimum
of
five
different
emails
and
five
different
accounts
that
different
services
are
tied
to.
You,
don't
want
to
truck
another
thing
on
to
that,
without
giving
some
sort
of
added
value
so
trying
to
communicate
that
upfront
and
then
allowing
them
to
get
into
stuff
without
necessarily
signing
up
for
an
account
is
terribly
important
and.
B
Sorry
just
check
in
the
chat
yeah
in
and
being
clear
about
what
the
security
methods
that
were
involved
is
is
also
terribly
important
as
well
too.
So
this
we
looked
at
from
various
kind
of
blockchain,
apps
and
kind
of
peer-to-peer
apps
in
particular
ones
that
used
some
sort
of
kind
of
chatting
or
community
sort
of
stuff,
because
a
lot
of
them
relied
on
having
kind
of
keys
and
recovered
keys,
and
these
are
I
mean
48.
Words
is
a
lot
to
save
or
write
down
somewhere
and
kind
of
waves
around
and
kind
of
making.
B
This
is
easy,
and,
if
you're
going
to
require
somebody
to
write
something
down
in
a
piece
of
paper
or
to
save
it
in
a
text
file
or
something
you
have
to
communicate
like
what
exactly
is
happening,
because
you
can't
assume
that
they're
familiar
with
this
and
an
interesting
one
that
can
I
came
up
and
the
one
that
we
kind
of
included,
because
it's
all
quite
small,
although
this
could
be
quite
massive,
is
about
account.
Fallbacks
people
that
we
spoke
with
were
like
that.
B
You
know
that
there
was
with
their
Gmail
that
it
can
go
to
another
email,
and
then
the
phone
number
has
another
phone
number
attached
to
it:
that
there's
that
there's,
no
there's
a
fallback,
there's
a
fail-safe
there's
a
way
to
get
back
into
it.
It's
not
just
gonna,
be
all
lost
if
I
lose
these
words.
However,
this
obviously
has
a
lot
of
contrast
with
a
lot
of
kind
of
D
web
practices,
which
kind
of
potentially
give
users,
especially
new
users,
perhaps
potentially
too
much
responsibility
and
kind
of
trying
to
deal
with
these.
B
The
next
one
is
give
control
over
data.
So
again,
these
are
kind
of
active
suggestions,
so
so
to
give
control
over
data
is
about.
Who
can
do
what
to
what
you
know
the
the
file?
The
thing
I
have
the
chat
that
I
have:
who
can
access
it?
What
can
they
do
to
it?
What
can
I
do
to
it?
You
know
what
what
is
this
control?
You
know,
what
do
I
have
the
ability
to
do.
The
first
thing
with
that
you
should
probably
do
would
be
to
assure
the
files
are
safe.
B
You
know
if,
if
you
have
a
file
sharing
application
or
something
where
you
can
kind
of
move
things
around,
then
assure
the
user
that
it
just
won't
disappear,
whether
you
know
that
or
assure
that
who
can
see
it
in
somebody,
somebody
else
can't
delete
it
necessarily
and
again,
that's
clearly
related
to
be
clear
about
who
has
access
to
what
you
know.
I'm
kind
of
oh,
that
thing
is
locked,
or
that
thing
is
not.
You
know
these
kind
of
quick
scans
that
you
can
kind
of
look
through.
B
You
can
kind
of
quickly
understand,
because
again,
mobile
is
a
mobile.
Interaction
is
a
very
quick
interaction
and
it's
all
about
kind
of
scanning
and
kind
of
flipping
through
very
quite
quickly
and
finally
is
classic
files
and
folders
there's
spoken
to
a
lot
of
people
about
different
methods
of
file
management
and
how
they're
managing
access
and
stuff
it
seems,
although
there's
I'm
sure
tons
of
research
saying
that
there's
way
better
ways
of
doing
stuff.
B
This
is
what
people
are
used
to
and
we
don't
want
to
innovate
too
much
for
people,
especially
when
you're
on
a
phone
so
kind
of
keeping
to
these
kind
of
classic
paradigms
that
people
are
used
to
and
again
sliding
it
kind
of
nicely
in
and
if
you're
going
to
introduce
new
methods
for
managing
and
stuff,
then
to
kind
of
do
that
quite
gradually
or
quite
easily
and
to
give
fall
backs
to
these
things.
Though,
and.
A
Finally,
it
yes
a
couple,
a
couple
of
notes
on
that
one
yeah
I
feel
like
it
when
we
when
we're
looking
at
this
particular
principle,
there
are
a
few
things
really
at
ipfs
and
how
it
relates
to
the
host
operating
system
that
it's
running
on
that
kind
of
came
up
repeatedly.
You
know
we
have
on
the
desktop.
We
have
an
IP,
fess
repo
and
it's
separate
from
your
desktop
filesystem.
You
don't
see
the
stuff
and
you're
a
professor
repo
and
finder,
or
vice
versa,
and
on
mobile
that
so
I
just
thought.
A
That's
it's
kind
of
like
there's
a
lot
of
applications
that
work
that
way.
So
it's
not
as
big
of
a
deal
but
on
mobile
you,
you
have
fewer
places
to
look,
and
you
know
a
little
bit
more
where
your
stuff
is,
and
so
photos
was
one
of
the
examples
that
we
walked
down
in
detail
and
in
photos.
There's
either
the
photos
that
are
in
your
Photos
app,
that's
part
of
the
OS
and
then
there's
the
things
that
you
have
published
it
uploaded
somewhere.
A
So,
there's
like
it
here
that
being
really
clear,
like
it's
really
clear
that
you
first
have
a
copy.
The
indie
web
principles
have
this
too,
or
you
like:
publish
on
site
passi
like
publish
on
own
site,
first
indicate
elsewhere,
and
mobile
kind
of
works
that
way
by
default,
where
you
take
a
photo
and
unless
you're
using
the
Instagram,
the
actual
app
to
take
the
photo,
in
which
case
like
that.
That
publishing
aspect
is
really
clear.
The
is
generally
unambiguous
around
where
your
data
is.
A
You
know
that
it's
in
your
in
your
photos
have
in
this
most
common
use
case,
but
with
t
web,
it's
not
as
clear
and
the
sharing
part
becomes
interesting,
interestingly
similar
to
how
those
systems
work.
So
when
you
share
something
on
my
BBFS,
you
know
we
often
couch
that,
and
once
you
put
that
data
out
there,
somebody
else
can
keep
posting
it,
and
you
phrase
it
that
way.
That
actually
kind
of
just
sounds
like
what
instagrams
doing
with
your
photo.
Today,
you
put
it
out
there
and
they're
hosting
it.
A
Now
you
could
delete
your
account
that
would
go
away,
but
it
still
doesn't
mean
that
his
script
doesn't
have
a
copy
of
it
or
then
somebody
didn't
take
and
screech
other
or
so
it
was
I
feel
like
we.
We
came
with
to
some
guiding
principles,
I'm
like
high
level
things
for
guidance
here,
but
we
also
ended
up
with
a
lot
of
questions
around.
B
Knowing
again
so
it's
this
about
kind
of
the
local,
the
local
thing
versus
the
maybe
it's
the
offline
or
the
internet,
or
the
network
store
that
kind
of
dealing
with
that
so
and
and
a
lot
of
that
is
sort
of
to
do
with
the
next
one,
which
is
it's
it's
about
being
seamless
and
it's
about
kind
of
going
between
these
nicely
and
telling
the
user
what's
going
on.
So
they
they
understand
what's
happening
and
a
lot
of
that
is
with
around
managing
connections.
B
So
some
apps
require
you
to
switch
modes,
let's
say
or
that
you
have
to
adjust
things
and
they
shouldn't
have
to
do
that
and
in
not
requiring
much
from
the
user.
You
know,
and
a
lot
of
that
is
around
settings.
You
know
settings
are
confusing,
especially
you
know
when
you
create
quick
ways
to
get
people
on,
then
it's
a
it's
about
removing
those
things
and
making
it
really
easy,
and
part
of
that
is
about
doing
the
hard
work
to
take
out
as
much
as
you
can
to
make.
B
You
know
have
as
few
settings
as
possible,
so
in
kind
of
creating
that
kind
of
starter
to
pro
level.
I
guess
you
could
say
and
to
do
it
kind
of
hide
things
away
too,
because
part
of
the
seamless
experience
is
that
is
built
is
confidence
building
so
that
you're
educating
and
use
confidence
building
that
it'll
just
sort
of
work.
B
You
know
that
when
I'm
using
this
thing
built
on
this
ipfs
stuff,
it'll
just
sort
of
work
and
I
don't
have
to
worry
about
it
because
I
don't
want
to
take
off
my
phone
and
kind
of
mess
with
yet
another
app.
So
this
is
kind
of
the
realities
of
mobile
life,
which
are
again
quite
different
from
the
kind
of
context
of
desktop
life.
Yeah.
A
One
of
the
things
we
noticed
we
were
talking
about
this
kind
of
stuff
is
this
confidence
building
right,
so
the
design
of
lid
p2p
is
basically
so
that
you
don't
have
to
worry
about
the
type
of
connection
you
have
it's
supposed
to
make
a
lot
of
that
transparent.
It
just
finds
a
way.
Life
finds
a
way
over
p2p,
whether
it's
through
mdns,
where
the
through
his
direct
ESP
connections,
which
are
whether
it's
bootstrapping
and
then
relaying
over
other
networks.
A
Limb
p2p
is
designed
from
the
ground
up
with
a
principle
of
just
find
the
connection,
so
you
don't
have
to
worry
about
it,
but
right
now
the
reality
of
it
is.
Is
we
do
confidence
building
by
doing
things
like
showing
you
how
many
peers
you
have
and
for
a
lot
of
users?
That's
that's
both
there's
a
combination
of
too
much
in
the
wrong
information
like
like
we.
Don't
we
don't
in
in
our
core
apps.
A
The
in
theory
have
you
come
back
with
this,
like
the
the
growing
number
of
validations
of
a
transaction
which
again
it
I
think,
is
a
very
similar
example
where
you
showed
that
you
showed
the
guts
of
how
the
machine
works
as
a
way
to
build
confidence,
and
it
kind
of
has
the
opposite
of
effect,
so
I
think
they're
still
really
a
like.
This
is
more
like
a
prompt
in
the
beginning
of
an
opening
of
that.
A
B
B
You
know
now
them
of
issues
and
problems,
and
it
is
quite
context
specific
and
again
that
context
is
also
drastic
from
you
know,
place
to
place
from
society
to
society,
geography,
to
geography
from
the
principles
we
built
scenarios
and
again
the
the
principles
are,
let's
say,
a
rationale
like
a
kind
of
a
framing
of
thinking.
You
know
how
to
think
about
these
different
things
about
you
know
again,
respecting
the
device
and
when
I'm
doing
some
when
I'm,
just
starting
to
build
when
I'm
starting
to
design
I
should
be.
This
should
be
seamless
to
the
user.
B
They
should
have
the
ability
to
do
that
and
that
and
that,
and
then
from
that
we
built
these
scenarios
and
scenarios
are
user,
close
or
sort
of
design
patterns.
But
we
chose
to
do
this
through
an
app
X
in
an
app
Y
to
kind
of
illustrate
its
use
so
kind
of
taking
a
problem
or
an
issue
or
basically
scenario.
That
would
be
the
solution
to
an
issue
and
then
kind
of
describing
it
through.
B
Oh
X
and
absol
I
would
professional
apps
so
to
provide
the
description
through
an
interface
essentially,
so
those
are
again
in
detail
and
just
hook
in
whenever
you
want,
or
if
something's,
not
clear,
if
I'm
talking
too
fast,
for
instance
the
first
one
is
these-
are
on
boards
confidently
with
minimal
technical
knowledge.
That's
a
lot
of
what
we're
talking
about
and
that's
why
this
one's
first
basically
and
then
the
user
shares
the
file
through
another
app
again.
You
know
people
don't
want
it.
It
shouldn't
be
like
no.
You
have
to
install
this
thing.
B
B
Fostering
that
you're
farming
that
you're
kind
of
loading
up
and
kind
of
giving
these
companies
all
of
your
data
to
just
kind
of
build
up
all
of
this
stuff
into
these
silos,
and
this
is
about
kind
of
using
the
phone
as
it
already
is,
and
because
it's
about
kind
of
reducing
those
barriers
to
entry,
because
people
don't
need
any
more
apps,
a
large
file
is
sent
to
a
user.
That
sounds
extremely
simple
than
it
is,
but
it's
it's
one
of
the
biggest
issues.
B
It's
like
moving
around
big
stuff
right
and
that's
kind
of
one
of
the
advantages
that
PDP
has
is
that
dealing
with
large
files,
especially
locally
and
offline,
the
user
plays
they
shared
media
file
with
why
without
Wi-Fi
or
a
mobile
network.
So
this
is
very
much
about
the
theme
of
this
talk.
This
meeting
and
one
of
the
advantages
that
that
something
built
in
ipfs
has
that
Dropbox?
Doesn't
you
know
or
that
these
things
that
are
so
pervasive
that
are
just
normal,
that
are
part
of
the
everyday
of
people's
online
lives?
B
And
then,
finally,
a
user
manages
their
chat
identity,
because
ultimately,
identity
is
more
pervasive
with
when
you're
talking
about
communication
between
two
people,
rather
than
kind
of
moving
files
between
two
people.
So
we
looked
at
an
illustration
of
kind
of
look
of
that
as
well
so
the
first
days.
The
first
scenario
is
that
the
user
on
boards
confidently
with
minimal
technical
knowledge
and
just
looking
at
that
real,
quick
right,
so
kind
of
what
we
found
in
the
research
is
yeah.
Well,
the
unborn
is
fast
and
passable.
B
We
have
kind
of
links
to
the
research
we
have
the
design
considerations
and
those
design
considerations
are
things
that
designers
and
builders
should
have
in
mind,
for
particular
its
of
interactions
and
those
are
also
within
the
each
step
of
each
particular
interaction.
And
again,
we
want
to
tie
this
to
a
user.
This
is
we
want
to
do
user
centered
design.
B
We
want
to
think
about
actual
people
using
actual
apps
in
actual
life,
and
so
in
this
particular
thing
we
was
somebody
concerned
about
censorship
and
privacy
and
cool,
and
they
want
to
know
where
this
files
go
and
putting
that
into
practice.
Is
the
actual
user
flow?
The
illustration
of
what
that
looks
like
for
that
particular
user
that
they
would
they
would
download
and
install
the
app
and
it's
open
for
the
first
time
so
again,
they're
interested
in
testing,
but
their
commitment
level
might
be
sort
of
low
at
this
point.
B
They
decide
to
create
the
account
later
and
that's
quite
important
to
give
the
idea
that
they
can
use
it
that
they
have
functionality,
that
it's
not
just
kind
of
barely
workable
without
without
having
an
account
and
kind
of
that
value.
Add
for
that
account,
especially
for
people
concerned
about
privacy,
because
there's
you
know
again,
people
have
tons
of
accounts
have
tons
of
worries.
They
have
tons
of
things
in
the
back
of
their
mind
that
they
they
they
want
to
be
able
to
use
something
without
committing.
B
However,
once
they've
started
using
the
all
of
that
value,
once
they've
started
being
it
but
kind
of
the
benefits
from
this,
then
they
can
kind
of
get
additional
values
and
those
need
to
be
kind
of
communicated
upfront
and
then
the
second
synonym
is,
the
user
shares
a
file
through
another
app
and
again
the
COO.
The
user
is
less
a
student,
their
early
20s
again
these
are
kind
of
generic
user
personas
and
they
want
to
sell.
They
want
to
send
files,
because
that's
what
a
lot
of
people
do.
B
That's
people's
understandings
when
you
talk
to
them
just
like
when
we
ask
users
and
potential
users
and
early
adopters
and
everything's
like
what
is
your
understanding
of
p2p
and
they
say.
Oh,
that
means
I-
can
get
a
file
or
a
data
from
one
computer
to
another
directly,
which
is
exactly
what
it
is
pretty
much
so
in
putting
that
into
practice
is
about
using
again
the
stuff
people
are
already
doing.
You
don't
want
to
create
an
essentially
another
gallery
app
if
people
are
already
using
another.
B
So
if
they
open
up
the
photo
gallery,
let's
say-
and
if
this
was
available
through
the
share
menu
in
well
at
least
iOS
and
Android,
which
are
the
ones
we
looked
at
granted,
there's
others,
but
these
are
obviously
the
most
prevalent.
Then
you
know
this
should
app.
X
is
available
through
the
share
menu,
just
as
telegram
is
available
in
the
share
menu
or
Dropbox
is
available
in
the
show.
Many
thus
app
X,
which
is
built
on
ipfs,
would
also
be
available
there
and
again
the
design
consideration
is
about
using
stuff.
B
People
are
already
doing,
don't
make
their
lives
more
painful
competi.
The
number
one
concern
when
you're
trying
to
base
things
around
the
users
is:
don't
make
it
worse
right
and
they
decide
to
select
and
share
that,
and
then
let's
say
if
this,
if
app
X
had
context,
then
you
know
they
can
choose
the
most
frequent
context
and
they're
gonna
share
that
picture
of
that
really
cute
cat
and
they're
and
then
they're
gonna
show
how
it's
being
shared.
So
it's
being
add
to
network
and
send
link.
B
So
that's
a
bit
of
a
switch
for
some
user,
so
you
need
to
inform
them.
It's
you're,
not
sending
necessarily
your
son,
actually
a
link
to
something
that
has
been
placed
on
the
network,
so
there's
again
education
throughout
all
of
the
interactions
and
saying
that
it's
like.
Oh,
it's
on
the
network.
I
have
confidence,
it'll
be
there
later
and
perhaps
most
important
is
out
of
all.
This
is
the
confirmation
and
then
kind
of
linking
it
back
and
then
showing
there's
that
really
long
bunch
of
letters
and
numbers
and
all
that
other
stuff.
B
A
It
that's
a
really
interesting
point
and
I'm
not
sure
that
we
have
a
lot
of
design
work.
That's
been
done
there
around
like
one
what
it
means
when
there's
a
an
address
that
is
an
IP
address
to
how
we
visually
signify
that
and
then
three
how
we
reinforce
what
that
actually
means.
When
you
see
that
type
of
address
and,
however
visually
signify
it
like,
it
does
mean
a
bunch
of
things,
yeah
and
I
think
we
that's,
maybe
some
follow-on
work
here,
which
is
from
a
visual
design
standpoint.
A
How
do
we
actually
develop
and
mature
that
communication,
especially
as
browsers
or
we
have
a
couple
of
browsers
that
are
implementing
native
ipfs
addresses
in
the
browsers
I
guidelines?
We
asked
that
question
out.
What
does
it
mean
when
you
see
that
in
the
in
the
address
bar
as
opposed
to
HTTP
colon,
slash
slash?
What
do
we
need
to
communicate
well
from
a
risks
and
capabilities
standpoint,
yeah.
B
B
C
B
I
guess
because
we're
gonna
get
into
this
kind
of
pinning
and
publishing,
and
so
this
is
just
looking
at
sorry
yeah.
This
is
definitely
a
good
point,
because
at
this
point
they
think
we
just
have
to
be
an
app
X
user
for
a
while
to
understand
the
idea
of
safety,
but
that
it's
just
gone
somewhere.
I
guess
is
what
I
was
trying
to
describe
to
that
and
then
in
I
think
that's.
C
A
And
like
I
gave
in
the
chat
later,
as
an
example,
beaker
tells
you
how
many
other
people
are
sharing
that
app
right
now.
So
you
have
this
kind
of
view
of
pop
yeah,
the
popularity
of
it
like
from
it
might
disappear
at
any
moment.
Standpoint
and
IP
fuss
doesn't
how's
that
Blitzer
the
protocol,
but
we
don't
do
that
at
the
content
level
at
all,
and
that's
something
that
when
you
read
about
how
people
talk
about
IP
festa,
don't
know
how
it
works.
That's
how
they
talk
about
it.
A
A
Even
have
a
waiting,
yeah
yeah
be
like
who's,
providing
which
blocks
who's,
providing
which
CA
DS
like
that.
Technically,
those
things
are
things
you
can't
find
out
at
the
protocol
level
does
not
something
that
has
percolated
really
up
in
to
how
we
build
applications
or
how
we
communicate
to
users
around
that
level
of
like
the
come.
What
is
the
confidence
threshold
for
for
something
like
that?
How
many
people
are
simultaneously
downloading
this
right?
Now,
all
right.
B
There's
there's
actually
this
brings
up
and
which
could
be
another
scenario,
which
is
what
number
safe
is
my
file,
which
is
how
many
people
are
panicking
at.
Let's
say,
or
you
know,
that
sort
of
thing
that
could
be
an
entirely
different
thing:
oh
it's
six,
it's
fine
and
then
thus,
if
it
goes
to,
one
am
I
warned
that
the
thing
that
I
started
is
only
one
that
means
I
have
to
pin
it
again
or
whatever.
So
yes
is.
A
Think
yeah
I
think
we
can't
jump
to
the
conclusion
or
the
end
there,
especially
because
safe
is
gonna,
be
really
user
tasks
dependent.
So
if
the
user
is
trying
to
take
down
something
and
the
thing
being,
there
is
not
safe
if
the
user
is
trying
to
make
sure
something
stays
up
like
in
a
censorship
regime
that
it
being
up
is
safe,
so
I
think
like
safe.
Maybe
is
they
can
word
but
like
I
like
that
idea
of
health,
maybe
or
accessibility
like,
although
that's
overloaded
with.
B
A
How
long
has
it
been
there?
Just
because
you
have
six
nodes
providing
now
doesn't
mean
they're
gonna,
be
there
when
China
blocks
that
port
that
I
profess
is
running
on
or
you
know
so,
there's
it's
gonna,
be
user
task,
dependent
for
sure
and
I
think
we
do
need
a
higher
level
of
their
nests.
Accessibility
said
yeah.
B
B
This
is
about
yeah
looking
at
the
whole
transfer
process
and
where
is
the
file
and
who
has
it
and
kind
of
we
were
just
talking
about
and
here's
a
potential
illustration
of
how
an
apex
would
handle
that,
and
this
is
again
looking
at
very
mobile,
specific
context
with
that,
and
it's
about
notifications
and
kind
of
putting
that
in
somebody's
sending
you
a
file,
and
so
you
see
that
they
have
an
ID
or
that
there's
somebody.
That's
in
your
contacts,
you've
connected
to
them,
let's
say
somehow
and
again
showing
that
they
can
delete.
B
They
can
stop
stuff.
They
can
kind
of
prevent
things
from
getting
in
this
is
about
giving
control
about
you
know
who
has
access
to
this
thing.
You
know
if
they
can
put
weight,
they
can
put
Stiles
into
my
into
my
phone.
How
does
that
work?
You
know.
So
these
are
things
you
can
try
to
have
to
communicate,
and
let's
say
if
this
image
is
downloaded
and
it's
a
raw
file,
so
it's
you
know
96,
Meg's
or
whatever,
and
they
can.
B
You
know,
look
at
it
and
it
looks
just
like
any
other
photo
app,
let's
say,
and
that
isn't
just
because
it
would
be
easy.
But
it's
just
that
we
need
to
follow
these
conventions.
It
should
look
like
a
regular
file
based
app,
let's
say,
and
one
thing
that
I
think
that
we
didn't
have
time
to
explore
would
be
the
notion
of
history,
so
people
brought
up
versioning
and
kind
of
a
Dropbox.
That
is
that
kind
of
there's
really
nice
feature.
B
So
if
you
give
the
user
in
app
X
the
ability
to
to
sync
with
the
phone
storage,
which
is
let's
say,
they
can
set
that
as
default
or
maybe
they
said
it
is
not
as
default
or
keeping
app
X,
meaning
my
PFS.
Only
then
they
can
kind
of
choose
between
those
and
if
it's
synced
between
and
if
it's
synced
with
the
phone
storage
and
say
well,
I
can
delete
it
from
App
X.
B
But
it's
still
on
my
phone
and
this
kind
of
goes
back
to
the
thing
you
brought
up
before
about
Instagram,
so
that
I
delete
it
from
there.
But
it's
actually
on
their
servers,
but
communicating
these
sort
of
things
that
this
actually
works.
A
lot
different
and
it's
probably
a
potentially
a
lot
safer
and
better
for
you,
and
it's
about
giving
those
preferences
and
kind
of
simplifying
these
as
much
as
humanly
possible,
of
course,
giving
them
the
ability
to
download
it,
and
you
know,
delete
it.
B
That's
part
of
the
safety
issues
as
well
too,
is
trying
to
control
as
much
as
you
can
within
the
realms
of
how
ipfs
works
and
yeah.
In
this
case,
the
user
deletes
it
and
it's
gone,
and
that
seems
like
a
normal
operation
to
them.
Of
course,
that's
because
they
oh
it's
on
my
phone
still,
but
it's
disappeared
from
the
network.
B
So
it's
kind
of
working
with
these
and
trying
to
explain
how
it
works
while
trying
to
make
it
look
like
something
they're
already
used
to
and
the
next
one,
the
second
last
one
in
the
interest
of
time,
I'll,
maybe
kind
of
hurry
up.
Basically,
so
the
user
plays
a
shared
media
file
without
Wi-Fi,
and
this
is
exact
completely
offline
in
trying
to
say
what
offline
is.
This
person
in
this
scenario
is
they're
on
a
train,
so
at
least
in
many,
the
UK
in
particular
train
reception
when
you're
on
the
train
is
pretty
quick
spotty.
B
If
at
all,
so
it's
like
I'm
with
some
others,
somebody
else
how
do
I
get
the
file
to
them
or
like,
if
you're,
in
a
plane,
same
sort
of
thing
and
it's
about
when
in
notifying
them
that
they're
offline
Bluetooth
is
the
thing
that's
working
for
you
right
now.
The
other
stuff
is
not
Wi-Fi
is
gone,
no
signal,
etc.
B
Because
your
phone
is
telling
you
that,
so
this
is
gonna
say
it's
offline,
but
it's
still
store,
it
still
will
work
and
it's
communicating
that
and
they
want
to
preview
the
file
and
there's
you
know
the
wasn't
Rick
Astley
and
so
again
that
you
see
the
kind
of
address
you.
Oh,
that
looks
like
that
code.
That
means
it's
going
somewhere
and
it's
been
published,
meaning.
B
So
this
is
looking
at
this
idea
of
kind
of
pinning
and
what
does
I
mean
and
what
can
we
kind
of
we
work
around
the
meanings
of
these
things
and
what
will
apps
change
their
own
words
for
this?
Potentially
because
who
knows,
but
looking
at
kind
of
what?
What
makes
sense
to
use
this
to
get
them
started
quickly
and
they
used
a
QR
code.
B
What's
the
information,
here's
the
thing
and
it
can
be
all
done
without
the
internet
or
the
internet
as
people
think
about
it
and
about
unpublishing
well,
I
want
to
take
this
thing
down,
so
I
wouldn't
publish
that
and
I
can
control
that
right
from
that
file.
So
it's
about
who
has
control?
Who
can
access?
B
And
finally,
the
last
scenario
is
a
user
manager
search
that
identity
and
there
seems
to
be
like
when
we
looked
at
all
the
apps
in
kind
of
in
the
peer-to-peer
realm,
that
we
found
that
were
released
or
active
for
mobile,
that
they
kind
of
were
quite
quite
distinctly
divided
between
files,
meaning
largely
torrents
and
then
kind
of
some
sort
of
chat
or
community
sort
of
features.
Ie
many
versus
scuttlebutt
those
sort
of
things
but
kind
of
what
we
looked
at
is.
B
Is
this
messaging
scenario,
which
is
about
getting
started
and
discovering,
and
one
of
the
hard
things
about
this?
The
peer-to-peer
world
is
a
discoverability
in
allowing
yourself
to
be
discoverable
and
a
lot
of
these
don't
make
many
of
the
things
we
looked
at
kind
of
that
you
have
to
send
it
directly
in
a
different
way.
B
You
can't
put
yourself
make
yourself
discoverable,
not
that
I
found
it
at
any
rate
in
the
in
the
survey
and
putting
that
into
practice
means
that
if
I'm
getting
started
in
an
app
I
can
I
can
look
at
my
profile
to
make
sure
I'm
discoverable.
So
I
can
put
myself
I
understand
that
I've
looked
at
my
profile
to
make
sure
aware
of
what
I'm
about
to
do.
Let's
say
and
I
have
some
sort
of
recovery
and
trying
to
communicate
that
and
there's
a
lot
of
text
there
on
the
recovery
bit.
B
If
I
type
I,
don't
know
Deitrick
into
telegram,
you
know,
he'll
show
up,
I,
guess
I,
don't
remember
or
somebody
else
that
this
idea
of
discoverability
leads
to
building
the
network
of
users
and
it's
something
that
needs
to
be
taken
quite
well
quite
seriously
and
then.
But
this
also
highly
illustrates
this
notion
of
this.
B
This
really
fine
line
between
security
and
usability
and
kind
of
how
do
we
mix
and
match
those,
or
how
do
we
go
one
way
or
the
other
allow
the
user
to
go
one
way
or
the
other
and
so
to
wrap
up
in
there?
They
found
the
other
user
I'll
be
quick
because
we're
probably
over
time
it's
it's.
A
lot
of
this
work
is
about
playing
to
conventions
but
improving
on
them.
So
again
we
don't
want
to
reinvent
the
wheel
with
this.
B
You
know,
there's
no
need
for
that,
because
Dropbox
and
Google
Drive
and
all
these
things
have
done
tons
of
usability,
work
and
trying
to
understand
how
people
understand
about
files
being
moved
around
and
what
chat
means
and
all
these
other
sorts
of
things
and
notifications
are
everywhere,
but
they
require
I
believe
a
lot
of
testing
to
to
to
get
to
that
fine
balance
of
what
is
enough,
and
what
is
too
much
you
know.
Do
you
want
to
confirm
every
single
thing?
B
Probably
not,
and
do
you
want
to
set
controls
to
come
from
every
single
little
thing?
Probably
not
so.
How
do
you
get
to
that
kind
of
like
that?
Really,
nice
mix
and
user
education
that
pops
up
everywhere
it's
about
the
confidence
building.
It's
about
the
kind
of
saying
that
the
you
know
it's
about
sliding
up.
If
that's
nicely
into
mobile
life,
that
it's
yes,
it
works,
here's
the
benefits,
I
use
this
thing:
it's
you
know
about
showing
the
links
about
maybe
a
subtle
logo,
and
about
kind
of
about
that.
B
What
is
the
equivalent
to
the
padlock?
You
know
what
is
what
is
the
the
analog
to
that
and
telling
the
user
what's
going
on?
You
know
and
doing
it
quickly
and
not
confusing
them
and
not
overburdening
them
one
thing
and
again
explaining
what's
happening
with
pinning
or
publishing
or
whatever
you
want
to
call
it,
and
and
yeah
like
I
said
before,
but
I
probably
can't
say
enough
is:
is
this
fine
line
between
security
and
usability
because
usability
on
a
phone
is
kind
of
a
do-or-die
operation?
B
It's
you,
it's
not
usable
people
will
delete
it
quicker
than
they
will
anything
else.
So
how
do
you
make
that
happen
and
through?
Hopefully,
these
principles
and
scenarios?
Designers
developers
for
IP
paths
will
be
able
to
make
that
happen,
or
in
this
will
you
know
their
work
will
feed
back
into
this
and
likewise
it'll
grow
and
all
of
these
efforts
really
so
sorry
that
was
long-winded.
But
if
there's
any
questions,
yeah
sure.
B
A
A
B
B
A
There's
great
thanks
for
sharing.
Thank
you
didn't
work
all
right.
Thanks
everybody
for
joining,
see
you
in
a
month,
I'll
put
the
topic
and
agenda
I
think
we
already
have
a
speaker
lined
up
for
next
time
who
I
think
Evan
here
might
be
one
of
the
speakers,
so
we
will
talk
to
you
all
and
a
month,
I'll
update
the
issue
with
that
information.
Asap.
Okay,
great
thanks!