►
Description
On our April 15 call, Jim Kosem walked through the goals, methodology and findings of his research into IPFS and P2P on mobile (7:15), and shared next steps in the project. (Learn more at: https://blog.ipfs.io/2020-04-10-ipfs-mobile-design-research/) We also brainstormed discussion ideas for future calls (56:38).
Learn more about the monthly calls of the IPFS Local Offline Collaboration Special Interest Group: https://github.com/ipfs/local-offline-collab/issues/25
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
A
Hey
everybody,
its
Terry
here
with
the
local
offline
collaboration,
call
on
April
15th
we're
sick.
Today,
Jim
is
going
to
give
us
a
look
at
the
research
he's
been
doing
into
ipfs
and
peer
to
peer
on
mobile
should
be
really
exciting,
and
but
before
we
do
that,
let's
do
just
a
quick
go
around
because
there
are
a
couple
of
new
faces,
so
we
can
just
super
quickly
introduce
who
we
are
and
what
we're
excited
about,
or
working
on
in
this
sort
of
offline,
local
collaboration
space,
so
I
can
get
us
started.
A
My
name
is
Terry
Chadbourne
I
work
at
protocol
labs
run
into
proto
school
project,
but
I
am
also
someone
who's
been
running
offline
camp,
which
is
an
event
for
people
interested
in
offline
first
generally,
not
specifically
Steve.
Oh,
so
that's
where,
where
my
background
is
in
this
space,
I'm
gonna
go
this
way
on
my
screen,
so
Diedrich
you're
up.
C
Yeah,
it's
me
I'm,
working
on
ipfs
and
space
when
ipfs
is
equipping
into
a
browsers,
really
excited
about
work.
Jim
is
doing
it
for
starting
discussion
about
how
do
we
start
thinking
about
content
addressing
in
the
address
bar
when
you
don't
specify
the
source
and
you
can
get
data
in
an
offline
environment?
So
it's
really
exciting
space.
For
me,.
D
Allowing
people
to
use
tools
resilient
ly
without
any
type
of
connectivity
to
who
are
posting
your
data
or
relaying
your
traffic
and
yeah
I'm
super
excited
to
hear
what
Jim
has
come
up
with
I'm
very
excited
about
the
the
mobile
work,
that's
being
done
in
90
FS
space
or
that
birdies
doing
textile
three
box.
A
number
of
other
groups
so
excited
to
see
how
this
will
inform
their
trajectories
forward.
D
A
E
E
We
know
that
half
of
the
population
in
the
world
is
unconnected
and
the
web
and
tools
will
be
one
vehicle
potentially
so
I
am
looking
for
that
connection
in
between
what
Jim
has
produced
and
what
not
only
the
unconnected,
but
also
the
less
privileged
people
in
the
planet
can
get
out
of
his
research
and
the
collaboration
acaba
out,
and
also
am
part
of
the
association
for
digital
communications
and
doing
this
year.
I'm
going
to
be
working
on
strengthening
foundational
technologies
for
community
networks.
A
F
G
Hey-Ya,
an
errand
satola
I
work
at
textile
really
excited
to
kind
of
learn
more
about
this
group.
We've
been
working
on
mobile,
related
ipfs
stuff
for
a
while
here
and
kind
of
with
the
newest
version
of
our
technology
are
really
trying
they're
like
rethink.
What
the
best
way
to
integrate
into
mobile
is
really
excited
to
learn
from
you
all
very.
H
I'm
Jim
Coulson
I'm
a
designer,
a
researcher
or
and
I,
as
Dietrich
mentioned
before
I
work
previously
on
the
browser
design
guidelines,
which
is
also
research
in
a
design
face
to
establish
yeah,
like
Vidal,
said
before
kind
of
how
I
confessed
for
to
work
natively
in
a
browser
for
users
and
then
now
I've
concluded
the
research
end
of
the
ipfs
mobile
guidelines,
which
is
yeah,
wouldn't
you'll,
see
in
a
minute,
basically
yeah.
So.
A
I'm
on
mute,
thank
you
for
telling
me
I
was
on
mute.
That
was
helpful
so
for
today
on
our
agenda.
We
have
that
presentation
by
Jim
and
then
we'll
have
some
time
for
questions
to
talk
more
about
that,
and
then
I
also
put
on
the
agenda
to
do
some
brainstorming
for
future
topics.
We'd
like
to
cover
on
this
monthly
call.
So
we
can
start
thinking
through
some
speakers
and
would
like
to
be
moving
forward
so
Jim
I'll,
let
you
dig
in
feel
free
to
share
your
screen.
H
I
H
H
That
could
mentioned
before,
and
and
we
wanted
to
look
at
how
we
would
involve
users
and
these
guidelines
will
kind
of
bridge
the
user
needs
discovered
in
the
research
and
then
help
that
and
ramp
in
building
out
ipfs
in
particular,
in
mobile,
in
terms
of
they
would
help
unified
thinking
and
best
practices.
And
then
this
obviously,
this
would
move
into
a
design
phase
and
that
design
phase
would
consist
of.
H
So
in
terms
of
its
laid
out
here,
the
user,
sorry,
the
IP
efest
mobile
design
guidelines
therein
get
booked
currently
and
then
this
is
also
in
a
github
repo
which
there's
the
links
for
and
I
can
send
them
around
again
as
well,
and
this
also
goes
to
a
protocol
lab
skip
book
as
well
too
so
yeah,
it's,
you
will
have
your
own.
You
know
obviously
Brendan
and
all
among
that.
H
So
the
first
thing
to
to
look
at
is
you
know
what
are
the
considerations
for
mobile
because
there's
a
I
don't
mentioned
before,
and
somebody
else
did
it
as
well
about
the
browser
design
guidelines
and
that
was
a
distinctly
different
animal
than
a
mobile
phone.
So
we're
looking
at
this
these
these
big
differences
between
mobile
browsers
and
the
desktop.
They
have
a
lot
of
different
interactions
and
then
also
development
is
a
lot
different
for
mobile
than
it
is
for
desktop
as
well
and
there's
obviously
questions
around
development
environments
for
these.
H
So
when
you
have
kind
of
this
Universal
platform,
which
is
a
browser-
and
you
have
standards
versus
this
kind
of
app
centric
world
and
and
kind
of
this
push
back
and
forth
between
using
a
mobile
web
and
not
with
things
with
like
progressive
web
apps
and
then
looking
into
another
consideration
is
a
big
one.
That
I've
spoken
with
a
couple
you
like
Aaron
is
wrong
battery
life
and
power.
You
know
and
wanted
to
find
about
how
much
of
this
it
is
an
issue.
H
So
that's
another
thing
we're
looking
at
so
just
how
it
works
for
people
and
then
the
big
obvious
one
is
connectivity,
bandwidth
signal
that
sort
of
thing?
It's
a
it's
an
obvious
issue
with
connecting
because
there's
none
of
this
will
work
out
without
connection.
But
then
we
have
this
offline
issues
and
kind
of
what
is
the
syncing?
What
are
people
I
people's
ideas
around
syncing
and
finally,
this
kind
of
amalgam
of
privacy,
security
and
identity,
and
this
is
a
bit
of
the
elephant
in
the
room.
H
H
Okay,
so
yeah
just
moving
on
we'll
kind
of
talk
a
bit
about
the
methodology
that
I
used
for
this.
So
there's
three,
a
couple
parts,
the
firt
world,
two
main
parts
was
the
first
is
the
mobile
survey
review
and
that
was
looking
at
I'm.
Sorry
I
just
saw
strain
at
second,
so
we
looked
at
what
was
out
there
and
what
was
the
previous
effort.
H
So
this
is
we'll
get
into
in
a
bit
the
research
interviews
and
kind
of
the
fundings
from
there,
so
the
first
bit
is
in
the
application
survey
is
looking
at
mobile
browsers.
Now
we
looked
at
what
people
use
for
content
and
files
on
the
internet,
for
the
phones,
and
one
thing
that
we
found
talking
to
everybody
is
that
a
browser
on
a
mobile
is
still
kind
of
this.
H
H
H
And
we
wanted
to
do
this
looking
at
that
kind
of
those
patterns
and
I
could
show
you
one
real
quick
for
Android,
so
there's
deeper
investigation,
how
one
kind
of
goes
to
a
photo
shares
through
that
and
there's
also
for
iOS
and
the
same
with
a
browser.
But
we
looked
wanted
to
see
where
the
seams
and
the
interactions
were.
So
we
wanted
to
see
kind
of
what
people
were
up
against
what
their
workarounds
were
kind
of.
H
If
this
was
a
natural
interaction,
kind
of
to
see
where
the
seams
are
and
kind
of
see
where
the
design
and
the
research
might
be
with
following
that
we
looked
at,
we
did
an
application
survey.
So
you
know-
and
we
might
wondering
why
these
bits
of
focus
why
these
particular
apps
would
they
were
chosen
first
to
be
stable
and
available,
so
ones
that
were
released
in
Android
and
iOS
stores,
or
they
were
mobile
web
apps.
And
we
wanted
to
see
what
were
the
previous
approaches
and
under
steals
different
understandings
of
PDP.
H
And
we
wanted
to
see
that
in
kind
of
a
broad
spectrum.
So
p2p
on
mobile
has
quite
a
broad
spectrum
and
covers
a
lot
of
different
things
and
that
in
the
kind
of
big
three
groupings
that
we
discovered
were
messaging
community
or
hosting,
which
is
highly
related
to
messaging
and
then
file-sharing
and
then
some
of
them
as
we'll
learn
kind
of
cross
over
as
well
a
lot
to
which
is
interesting
and
absolutely
covered
and
again
you're
free
to
read
in
more
depth
the
investigations
here
and
the
findings
for
each
of
them
in
particular.
H
We're
many
verse.
So
that's
uses
scuttlebutt
Communications
and
it's
can
run
offline
and
online
and
it's
generally
a
kind
of
a
chat
based
app.
So
it's
generally
fits
into
the
messaging
and
posting
share
drop,
which
is
a
web
app,
which
is
for
kind
of
anonymous.
File-Sharing.
Peer-To-Peer
doesn't
require
accounts
so
that
fits
into
file
sharing
status,
which
is
blockchain
app,
which
is
you
know
you
can
use
messaging
and
posting,
but
you
can
run
the
apps
within
that
frostwire,
which
is
a
torrent
app.
So
it's
for
an
application.
H
Now
and
then,
after
that,
we
looked
at
well.
What
were
the
features
and
again
I've
kind
of
broad
I?
We
broke
it
into
these
three
groups,
the
messaging
posting
and
file
sharing
and
then
breaking
it
down
into
what
kind
of
had
the
same
broad
spectrum
of
features
and
that
for
each
of
them
across
the
board
and
what
didn't
and
so,
for
instance,
if
some
some
sort
of
features
came
out
immediately
already,
which
is
showing
you
know.
H
Let's
say
where
someone's
were
sorry,
some
shared
both
how
they
might
handle
messages,
others
didn't
and
then
this
led
to
a
further
deeper
study,
which
was
the
interaction
study.
Now
in
the
interaction
study,
we
are
showing,
for
instance,
that
chilling
status
was
interesting
in
particular
because
how
it
was
shown
wasn't
consistent
at
all
or,
for
instance,
how
accounts
were
handled
or
unless
a
identity
was
very
different
from
category
to
category
and
from
app
to
app
and
there's
no
real
good
way
of
handling
identity.
H
It
seems
beyond
the
email
and
password
it
looks
like
in
terms
of
ease
of
use
and
again
we
can
see
there's
some
we're
using
private
keys
without
recovery.
Some
had
not
yet
there's
lots
of
interesting
things
around
logging
in
and
out,
and
some
allow
you
to
log
out
and
then
finally
kind
of
confirmations
and
notifications.
So
looking
at
how
the
user
is
understands,
kind
of
what
is
happening
and
how
that
these
different
apps
and
platforms
provided
them.
H
Well,
this
essentially
a
layer
of
comfort-
or
you
know,
there's
this
understanding
of
what's
going
on
and
then
finally,
a
handling
media.
So
we
talked
about
photos
before
but
as
we'll
see
before
here
and
then
you're
free
to
check
in
in
greater
depth
in
terms
of
having
a
media
player,
what
things
they
supported
and
in
in
terms
of
the
findings
it
does
anybody
have
any
questions
so
far.
Should
we
keep
them
to
the
end
and
feel
free
to
chime
in,
if
you
like
know
some
good
thoughts.
H
Are
speaking
behind
your
back
in
the
chat?
Okay,
yeah
I
can
see
yeah
yeah
all
right,
no
problem
yeah,
so
yeah
the
findings
were
kind
of
buried
in
some
I
guess
you'd
say
insist.
Unexpected
things
happened,
so
one
thing
that
was
common
through
most
of
them.
There
was
lots,
perhaps
too
much
onboarding
on
information
a
lot
of
times,
so
it
was
great
that
they
were
showing
that
there
was
no
shortage
of
explaining
the
benefits
of
these
particular
apps,
but
it
maybe
could
have
been
too
much.
H
So
this
is
one
thing
to
bear
in
mind
in
the
mobile
platform.
Is
readings
difficult
if
smaller
screen
sizes
generally
less
time,
so
these
sorts
of
issues
are
interesting
in
terms
of
the
findings
across
the
board.
Keys
are
difficult
to
manage.
You
know
when
you
tell
somebody
they
have
a
48
word
or
whatever.
It
is
seed,
strain
the
words
that
they
need
to
save
somewhere
else,
or
it
all
goes
away.
That's
things
like
this
are
difficult
to
deal
with
so
another
thing
to
bear
in
mind.
H
So
there's
this
always
a
trade-off
versus
security
versus
usability
kind
of
that
highlights
that
torrent
apps.
We're
really
good
at
showing
what
was
going
on
something
I,
wouldn't
suspect
necessarily,
but
in
terms
of
the
status
of
the
Downloads
Peters
connected
that
sort
of
thing
they
generally
handled
that
quite
well
messaging,
wasn't
very
consistent,
especially
in
terms
of
permissions
and
that
sort
of
things
for
a
lot
of
apps.
H
They
were
the
simplest
to
use,
but
still
had
patterns
of
use,
for
instance,
QR
codes
that
might
be
uncommon
and
this
sort
of
thing
but
interesting,
because
it
kind
of
reflects
other
mobile
sharing
patterns.
So,
what's
app,
for
instance,
authenticates
with
QR
codes,
a
lot
of
blockchain
absent
that
they
are,
you
know
they
use
QR
codes
to
to
initiate
the
transfer,
so
that
was
really
interesting
as
well
too
and
then
moving
it
to
the
second
section.
H
So
after
that,
looking
at
all
the
kind
of
let's
say
the
at
the
the
broader
landscape,
you
know
we
moved
into
to
actually
use.
Please
switch
now,
as
I
mentioned
before,
we
ran
a
workshop
before
with
that
I
led
myself
and
then
looking
at
kind
of
where
how
to
frame
this
right
and
that
workshop
led
in
and
then
you
know,
looking
through
materials,
the
going
through
the
understandings
from
the
application.
You
know,
looking
at
the
application
survey,
we're
looking
at
kind
of,
we
need
it
to
start
somewhere.
H
So
he
kind
of
came
with
a
broad
set
of
well
assumptions.
You
know
and
and
to
start
this
inquiry
and
to
frame
this
user
research.
For
example,
people
use
mobile
phones
differently
than
on
the
desktop.
That
was
an
assumption.
That's
not
necessarily
a
hypothesis
that
isn't
something
we
wanted
to
prove,
but
this
is
just
a
way
to
kind
of
lead.
The
questioning
the
conversation
around
things,
another
example-
is
infrastructural
services
on
mobile
devices
such
as
battery
life
and
bandwidth
are
essential
to
all
users.
You
know,
for
instance,
we.
H
This
was
part
of
the
conversation
with
all
three
cohorts
of
users,
but
then
we
found
that
it
wasn't
so
simple.
So
again,
this
is
more
of
the
way
to
start
the
conversation
rather
than
something
to
prove
or
disprove
and
yeah.
Let's
just
move
on
to
the
interviews
really.
So,
as
I
mentioned,
we
had
three
groups,
the
first
of
which
was
experts
earlier,
what
we're
calling
early
adopters
and
then
potential
users,
so
the
first
group,
the
experts,
these
people
all
had
experience
with
IPF
or
similar,
for
example,
at
technologies.
H
One
of
them
is
here
right
now
and
we
wanted
to
find
insights
into
these
deep
Nicias,
for
instance,
offline,
and
that
was
kind
of
again
we're
talking
about
looking
for
the
seems
in
use
and
interaction
and
looking
for
these
edges
to
find
out
what
might
be
in
the
middle
for
people.
So
some
of
the
key
findings
for
that
can
kind
of
click
into
there
and
kind
of
look
at
that.
H
The
rough
groupings,
our
perception
and
adoption,
and
then
data
and
sharing
and
within
that,
for
instance,
one
of
the
things
that
was
interesting
that
came
up
was
that
battery
life
was
assumed
to
be
important
to
users
that
that
was
true
speaking
to
the
other
users
and
their
early
adopters.
But
it
wasn't
so
simple,
so
their
understanding
of
power
and
their
worries
about
power
work,
or
rather
batteries,
where
we're
quite
different
or
nuanced
I,
guess
you
could
say,
and
then
identity
that
it's
hard
to
explain,
but
it
has
but
there's
many
different
ways
of
handling
it.
H
H
One
thing
that
was
interesting
was
a
Ron
notifications
and
status
came
up
a
lot
and
you
know
telling
the
user
what
is
going
on
and
especially
around
something
important,
that's
going
on,
but
then
not
being
overwhelming
about
it.
So
this
came
up
in
the
application
survey.
How
how
it's
different,
how
the
different
notifications
and
kind
of
the
for
instance
syncing,
is
something
syncing.
H
It's
a
fact
all
every
single
person
we
used,
we
talked
to
use
theater,
Google,
Drive
or
Dropbox
I
mean
any
numbers
of
others,
but
they're
every
single
one
was
sort
of
apprehensive
about
it,
which
is
really
interesting
and
then
another
another
key
funding
that
I
thought
was
personally
fascinating,
especially
from
a
design
standpoint
is
that
file
management
is
difficult,
so
you
know
they're,
it's
not
just
about
the
singing,
it's
all
about
the
organization
and
how
you're
dealing
with
what
do
I
have.
Who
has
it
that
sort
of
thing?
H
And
then,
finally,
the
last
group
was
potential
users
and
they
were
chosen
from
a
spread
across
Europe
and
Africa.
So
there's
three
groups
in
each
and
covering
well
generally,
all
corners
of
each
continents
really
and
all
had
to
not
have
anything
to
do
with
software
development,
for
instance,
that
was
the
first
to
run
it
and
they
had
all
used
p2p,
which
was
usually
torrance
in
most
cases
and
cloud
services.
So
we
can
kind
of
compare
these
experiences.
H
Was
media's
was
a
huge
focus
to
their
use
around
files
that
that
wasn't
I
guess
not
too
strange
to
understand,
but
it
was
good
to
have
that
verified
with
this
particular
group
and
all
understood,
p2p
and
actually
liked
the
idea,
but
didn't
really
know
what
they
would
use
it
for
besides
torrents,
so
that
was
kind
of
how
do
we
bridge
that
kind
of
gap?
Right
in
that?
H
The
idea
is
quite
easy
to
explain,
especially
compared
to
things
that
are
kind
of
related,
let's
say
blockchain,
which
is
difficult
to
explain,
but
to
kind
of
potentially
a
non-technical
user.
That
is
quite
easy
to
get
it.
One
computer
connects
to
another
and
then
how
privacy
is
understood
varies,
and
we
kind
of
had
this
assumption-
that
in
different
parts
of
the
world
that
privacy
has
different
kind
of
approaches.
Different
understandings.
But
it's
interesting
that
it's
how
nuanced
it
is
so,
for
instance,
some
of
the
people
in
Africa.
H
We
talked
to
you
weren't
worried
about
privacy,
whereas
some
people
assumed
that
they're
not
and
vice-versa.
So
it
was
quite
interesting,
the
the
nuances,
but
in
general
I,
think
one
of
the
things
that
kept
on
coming
up
was
the
concern
about
it,
but
that
it
just
it's
just
being
it's
difficult,
so
something
that's
just
kind
of
put
off,
and
so
again
these
sorts
of
things
that
were
kind
of
teasing
out
of
these
interviews.
H
I
really
will
feed
into
this
kind
of
development,
of
design,
guidelines
and
kind
of
this
summarized
in
here
in
the
findings
and
and
there's
been
a
lot
of
work
around
for
users
by
by
people
like
Dropbox,
by
apple
with
airdrop
and
with
Google
with
Google
Drive.
So
this
is
they've
done
a
ton
of
work,
and
these
are
long-standing
things
that
people
have
a
lot
of
experience
and
I'm.
More
importantly,
a
lot
of
comfort
with,
but
it's
a
sort
of
weird
ambivalent
comfort,
as
well
too,
that
they
see
it
as
something
that's,
stable
and
dependable.
H
But
then
there's
also
sort
of
this
notion
or
there's
apprehension
around
is
this
service
still
gonna
be
around
a
year?
Do
I,
actually
trust
them
with
this.
Many
files,
like
I,
believe
that
it'll
still
be
there,
because
there's
a
big,
dependable
company-
and
this
idea
about
backup
is
a
big
deal
that
it
will
be
safe
up
there
you
know,
and
who
has
the
file
I
think
that
this
is
an
interesting
thing
talking
to
different
people
about
this.
You
know
this
assumption.
Does
it
matter
where
the
file
actually
is
as
long
as
it's
safe.
H
So
this
is
something
that
came
up
a
lot
in
these
conversations
as
well,
too
and
and
again,
like
I,
said
before
another
interesting
things,
kind
of
in
these
groups
are
I
should
have
mentioned.
There's
these
are
broken
off
into
these
three
groups:
cloud
services,
syncing
and
usability
and
awareness,
and
then
finally,
security
and
identity
will
just
come
up
again
and
again.
H
This
idea
of
security
and
identity
and
again,
as
I,
mentioned
before
kind
of
at
the
beginning,
that
this
idea
of
battery
and
signal
that
it's
all
over
the
place,
the
kind
of
attitudes
and
approaches
to
it
and
a
lot
of
things
were
kind
of
disproven
for
myself,
personal
sumption.
That
battery
would
be
a
bigger
deal
in
certain
parts
of
the
world
and
it
wasn't
necessarily
but
signal
was,
but
what
signals
thought
of,
and
people's
relative
I
guess
acceptance
of
how
what's
good
and
what
isn't
it's?
Also
quite
relative.
H
So
that's
really
interesting
to
kind
of
find
and
hear
these
things,
and
then
you
know
kind
of
see
where
to
design
from
there.
You
know
to
it
well
to
see
how
you
can
design
across
the
board,
for
these
sorts
of
things
really
and
then
finally,
as
I
believe
I
might
have
mentioned
before
privacy
is
understood
differently
in
different
context,
and
that's
not
just
geographically
at
all.
It's
many
times
between
personal
and
work,
so
that
people
are
I
wouldn't
say,
paranoid
necessarily
a
concern
in
different
ways
for
different
stuff.
H
So
a
lot
of
it
has
to
do
with
just
people's
lives,
rather
than
necessarily
where
they
live,
although
that
hasn't
definitely
has
an
influence
as
well
and
then
finally,
we
took
all
of
this.
So
this
this
work
around
the
applications
and
what
work
has
been
done
out
there
before
and
then
the
user,
research
and
kind
of
people's
attitudes,
people's
understandings
things.
People's
opinions
on
what
could
or
should
be
and
then
kind
of
developing
this
well,
this
design
strategy,
which
would
feed
into
the
design
phase
and
ultimately
this
is
all
about
growing
the
user
base.
Ipfs.
H
What
some
of
them
are,
for
instance,
how
might
we
create
seamless
interactions
from
device
to
device?
You
know
and
well
again,
what
is
seamless
mean
right
and
what's
acceptable
for
people
you
know,
what's
kind
of:
where
are
those
breaks
that
are
acceptable?
Where
or
not
again
in?
How
can
I
PFS
be
better,
not
just
as
good
as
what's
out
there,
for
example,
with
file
management?
That's
a
terribly
interesting
design
case
and
notifications
that
status
are
going
to
have
to
have
special
attention
paid
to
them.
H
That
seems
quite
evident,
but
because
you
know
it's
there,
this
way
to
reduce
cognitive
load.
But
again
that
makes
a
better
experience
is
if
ipfs
from
mobile,
handles
notifications
and
status
and
all
these
sorts
of
things
and
settings
better
than
let's
say
existing
cloud
services,
then
it
would
give
it
a
distinct
advantage,
for
instance,
and
a
lot
of
these
things
add
up
to
how
we
can
not
only
make
things
better,
quick
and
not
as
hard
but
actually
better.
H
You
know
looking
for
these
little
scenes
these
little
things
that
can
be
addressed
across
the
board
really,
and
so
what
next
is
largely
about?
Taking
all
of
this
and
designing
the
interaction
and
the
components
that
go
into
them
for
other
people
to
use
and
iterate
on,
and
you
know,
feeding
that
back
into
guidelines
and
building
a
community
of
well
design
and
research
practice
around
this
so
yeah.
That's
it
for
me,
really
I'm
happy
to
take
questions,
address
any
concerns,
or
if
anybody
has
any
comments.
A
I
really
appreciated
that
you
were
looking
at
kind
of
resource
constraints
because
that
offline
camp,
when
I
hear
stories
from
more
like
developing
world's
rural
healthcare
kind
of
scenarios.
We
always
it's
brought
to
light
all
of
the
resources
that
we
take
for
granted
in
our
urban
settings
here,
but
they're
all
kind
of,
inter
playing
and
different
people
value
different.
You
know
battery
life
versus
this
versus
that
differently,
based
on
their
slips
right,
I.
H
So
there's
like
these
little
weird
situations
that
all
of
us
run
into
you
know
where
this
online
offline
and-
and
it's
also
like
data
costs
for
a
lot
of
people.
You
know
it's
not
just
you
know
in
certain
regions
or
certain
parts
of
the
world
that
you
know,
data
on
LTE
or
whatever
might
cost
a
lot
like
for
other
people.
You
know
so
there's
a
teenager
in
London
has
to
pay
in
their
mind,
see
that's
a
lot
of
money.
You
know
for
to
pay,
for
you
know,
X
amount
of
data
per
month,
yeah.
E
I
think
male
in
her
that
Jim
that
the
the
problem
in
London
will
probably
get
solved
by
by
the
ever
growing
market
of
telecommunications,
yeah
I
agree:
you
have
an
issue
in
connectivity
when
you
get
to
the
south,
it
will
probably
get
fixed
by
putting
a
lot
Romina
a
couple
of
millions
of
dollars
somewhere
to
to
other
bigger
pipes
and
putting
longer
cables,
and
that's
not
gonna,
be
an
issue
I
think,
but
for
the
weather.
So.
E
I
H
It's
it's
again.
These
things
are
relative,
so
people's
understanding
of
safety
and
security
is
relative,
but
again
a
teenager
in
London.
If
they
can't
get
the
Spotify,
that's
the
end
of
the
world
for
them
potentially,
but
it
might
not
be.
The
you
know
as
drastic
is
that
they
have
no
communication
whatsoever,
but
I
mean
these
issues
affect
a
lot
of
people.
So
I
guess
that's
just
what
I
was
trying
to
say
that
it's
offline
isn't
just
a
problem
in
certain
markets.
That's
really.
A
We
all
we
all
encounter
in
in
very
different
ways
from
each
other
yeah.
So
one
question
which
I
apologize
if
I
kind
of
miss
this
in
the
intro.
But
let
me
talk
about
this
like
ipfs
on
mobile.
Are
we
is
protocol
labs
about
to
build
a
product
called
ipfs
on
mobile,
or
are
we
creating
a
body
of
research
that
textile
or
anyone
else
in
the
community
can
kind
of
reference
as
they
build
user-facing
things
that
they
want
accessible
on
mobile
I.
B
Can
take
that
one?
This
is
definitely.
This
is
definitely
a
loaded
to
to
inform
ecosystem
as
a
whole.
Some
of
this
we
can
use
to
inform
our
protocol
design
decisions
as
we're
making
decisions
around
high
and
low
water
marks
around
like
whether
to
invest
in
say,
automation
and
regression,
testing
for
things
like
power
consumption
for
given
basic
operations
of
our
network
protocols.
That's
definitely
where
it
can
help
help
us
from
protocol
design.
B
How
do
we
and
we're
in
a
situation
now
with
a
million
terrible
apps,
app
set
like
that,
where
the
user,
the
user
commitment
like
we
did
research
Mozilla
that
showed
that
people
are
very
reticent
to
install
a
native
app
at
all?
How
do
you
get
people
over
that
install
barrier
with
p2p,
it's
even
higher
barrier?
If
the
user
knows
enough
to
know
it's
b2b,
maybe?
But
for
me
this
is
about
important
in
that
it
can
help
the
next
10,000
apps
that
are
written
on
top
of
of
ifs
or
scuttlebutt
or
web
tour.
B
What
doesn't
work,
especially
these
things
that
wearing
out
that
the
glass
right
things
like
notification
and
frequency?
How
much
to
show
like
you
know,
just
showing
showing
pure
count,
is
maybe
a
signal
of
one
part
of
your
connectivity
but
doesn't
necessarily
say
something
about
the
quality
of
those
connections.
How
do
we
communicate
these
more
nuanced
and
complex
concepts
to
users
as
we're
building
the
next
10,000
apps.
A
H
E
H
Also,
a
small
sample,
but
finding
users
to
find
users
to
do
this
is
is
quite
difficult,
so
we're
quite
lucky
to
get
those
people
to
be
honest
and
so
but
yeah.
It
definitely
would
love
to
continue
study
with
different
places
on
in
the
past,
I've
done
field
work
in
Rwanda
and
I
tried
to
get
people
there,
but
I
couldn't
so
it'd
be
great
yeah.
B
E
E
You
know,
I
haven't
got
my
mind
around
how
much
ipfs
is
interested
in
those
population
groups
right
that
are
the
ones
that
we
are
very
much
fun,
so
I'm
not
interested
in
putting
decentralisation
and
peer-to-peer
technologies
on
top
of
those
that
are
already
connected
those
it's
an
interesting
problem.
It's
not
a
problem
that
we
are
focused
on
the
ones
that
we
are
focused
on
are
those
that
are
yet
to
be
connected.
E
That
will
eventually
be
connected,
but
we'll
get
that
done
in
terment
that
we
have
built
for
them
in
a
way,
because
we
are
not
putting
them
much
in
the
driver's
seat
in
the
relationship
with
the
iteration,
with
a
net
worth
at
that
they
use.
We
are
bringing
that
to
them.
You
know
so
our
job
is
to
shift
that
conversation
so
to
put
it
on
their
hands
and
to
allow
them
to
be
layer
infrastructure.
So,
as
long
as
ipfs
is
willing
to
work
on
that
area
closer,
we
are
more
than
happy
to
contribute
to
that
liaison.
B
Even
aside
from
user
research,
I'd
be
super
interested
in
how
those
directed
and
Community
Design
networks
operate,
because
we
can
do
things
like
add
those
into
our
into
our
test
scenarios.
So
we
want
to
understand
how
IP
fest
performs
in
infrastructure.
That's
community
designed
community
run
I
talked.
B
About
this
and
I
would
love
to
be
able
to
have
the
performance
characteristics
of
those
networks,
so
that
we
can
make
sure
like
we
can
add
that
to
our
list
of
like
make
sure
that
I
give
us
operates
for
these.
Given
basic
scenarios
in
these
in
those-
and
you
know,
Dodge
is
designed
kind
of
from
the
ground
up
already
for
things
like
dodgy
networks,
but
I
feel
like
the
areas
we
talked
about
here.
Bandwidth
consumption,
power,
consumption.
B
Those
are
the
areas
where
it's
not
both,
not
optimized
in
tune
or
there's
really
big
unknowns
about
how
it
operates.
So
having
that
even
a
description
of
the
conditions
of
Community
Design
networks
like
a
community
LTE
network,
well,
what
is
tower
strength
when
it's
throughput,
what
is
available
bandwidth
out
even
hours
per
day,
like
if
people
are
extent
on
extended
periods
like
we
found
them
in
Brazil
people
do
three-hour
for
our
train
lines,
so
their
power
and
bandwidth
needs
for
large
chunks
of
the
day
are
very
different.
H
One
example:
I
came
across
in
the
interviews
was
the
one
guy
had
two
phones.
No
sorry,
he
had
four
phones
and
two
sims
in
each
so
which
is
just
that
you're
not
only
dealing
with
different
networks,
but
it
was
never
the
same
connection
on
any
of
them
at
any
given
time
right
and
then
so.
You
have
this
cascading
level
of
different
signals
and
then
battery,
which
is
on
which
sin
for
which
network
and
what
is
what
network
strength
at
different
times.
H
E
Is
fascinating,
I
agree:
it's
passionately
I
when
I
saw
it.
I
I've
been
in
certain
conditions,
so
most
of
them's
global
South,
so
that
those
scenarios
have
come
up
so,
but
also
eating
impressive,
like
why
do
people
need
to
get
into
that?
It
is
because
the
conditions
are
so
bad
so
low
so
that
they
need
to
have
multiple
streams
to
find
the
best
deal
in
it
seem
to
do.
They
call
that
it
gets
its
drain,
it
drains
their
income,
the
less
and
and
in
order,
in
order
to
do
that
they
need
multiple
for
each
stable.
B
B
We
spin
up
700
peers.
You
know
like
whenever
I
see
like
700
peers,
showing
up
in
my
browser
for
I
get
fed
us
or
any
networks
like
the
gathering
peers
is
away
the
more
peers,
the
better
chance.
Your
requests
will
be
fulfilled
quickly
and
that's
the
math
that's
been
done
by
the
designers
at
the
protocol
level.
B
So
when
you
think
about
that,
where
every
single
bytes
that
you
transfer
is
eating
the
money
that
people
bought
to
be
able
to
get
three
megabits
bonus
top-up
on
their
plan
that
week,
the
the
math
doesn't
work
out
at
all
right,
the
more
Pierce
as
an
architectural
design
choice.
It
falls
on
it
on
his
face
immediately.
For
that
whole
class
of
users,
which
is
billion
of
people
around
the
world.
Oh
so
good.
G
Maybe
a
trusted
third
party
hosted
service
that
you
trust
that
you
signed
up
for
I,
don't
know
but
yeah.
Just
this
idea
of
kind
of
you
know
my
phone's
not
online
all
the
time.
It's
it's
hard
to
run
a
full
node
on
my
phone,
it's
expensive
or
it
needs
a
lot
of
battery
or
whatever
so
I'm
gonna
delegate
a
lot
of
the
responsibility
for
my
data
to
this
trusted.
Node
that
lives
somewhere,
and
this
isn't
something
exists,
so
it's
very
common
commonly.
G
G
E
Didn't
even
under
project
one
of
the
things
that
we
see
a
lot
is
this
thing
they
put
on
the
on
your
roof
house
that
connects
you
with
others
within
your
network.
Let's
say
maybe
similar
to.
Maybe
you
have
heard
of
NYC,
mesh
or
LTE
or
other
mesh
networks,
but
it
is
a
gig
free
and
not
focused
on
crypto,
so
you
might
not
have
seen
it
around
your
cover,
but
you
can.
E
You
have
it
in
your
roof,
but
then
you're
inside
your
house
and
the
creativity
between
your
roof
on
your
house
is
tricky
because
what
you
have
out,
probably
a
tin
roof
or
how
or
you're
far
from
the
roof.
So
what
we
usually
do
is
we
run
a
cable,
an
Ethernet
cable
to
the
house,
and
then
we
put
a
low
onion
and
inside
your
house.
You
put
that
access
point
where
any
wireless
affects
access
point
to
give
you
connectivity
within
your
house
and
connect
Duke,
so
the
other
members
of
a
network.
E
So
there
is
a
fixed
computer
all
the
time
in
your
come
in
your
house,
and
that's
it
that's
relevant
because
in
some
countries
where
computers
are
not
a
thing
and
they
only
have
one
phone,
the
one
that
has
the
phone
is
the
man.
So
women
in
general,
don't
have
access
to
computers
when
there's
only
one
computer
house
so
by
by
tying
the
computer
to
the
hub,
but
to
the
home.
E
When
the
man
leaves
the
house
to
come,
the
woman
gets
access
to
the
computer,
so
there's
a
gender
component
there
and
then
it
also
acts
as
a
permanent
peer-to-peer
after
ended
in
the
mesh
network.
So
the
phone
is
still
I
know
a
member
of
the
net
of
the
network,
but
your
own
node
is
your
own
replica
of
your
of
your
peer-to-peer
resources.
E
So
whenever
you
get
offline
or
even
if
you
are
online,
but
you
want
to
have
it
a
content
more
readily
available
for
others,
you
can
push
it
to
your
router
to
your
home
house
and
the
same
could
happen
by
pushing
it
to
the
router.
The
router
could
the
infrastructure
that
never
thought
that
could
also
be
one.
E
H
Here
that
sounds
great
I
was
going
to
say.
A
lot
of
these
situations
are
in
terms
of
user
centered
design,
our
I
guess
what
you
call
the
nikolic
extreme
users,
so,
but
the
the
great
thing
is
about
it
to
explore
these
kind
of
edges
of
things,
then
you
you
always
come
to,
or
you
generally
come
to
like
a
more
happy
middle
and
a
lot
of
what
you're
talking
about
Nikko.
That
would
work
in
many
places.
H
Not
just
you
know
that
these
sorts
of
things
are
on
connecting
to
the
roof
or
to
the
building
and
then
having
your
own
route
or
your
own
sorts
of
hubs
yeah.
This
works
for
a
lot
of
people
as
well
too.
So
it's
about
kind
of
learning,
these
different
examples
and
translating
that
to
to
something
that
works
across
our
products.
Broad
spectrum
of
people.
H
Aaron
I
was
gonna,
I
was
gonna
mention
on
what
you
mentioned
before
about
this.
On
always
like.
Basically,
it's
like
an
outsource,
node,
I
guess
you
could
call
it
or
something
like
that
that
there
is
a
bunch
of
torrent
services
that
do
something
similar
to
this,
so
that
you
they
do
the
downloads
and
then
they
manage
it
up
there
and
then
you,
you
know
you
have
the
account.
The
search
is
done
somewhere
else.
There's
one
called
foot
style
is
one
is
in
Turkey,
but
it's
yeah.
H
E
A
May
be
more
question
for
Dietrich
and
Lydell
I'm,
not
sure,
but
to
what
extent
do
the
relationships
that
we
negotiate
get
harder
when
we're
talking
about
mobile?
So
the
two
of
you
spend
a
lot
of
time
talking
to
like
web
browsers
and
figuring
out
interoperability.
Is
there
a
bigger
hurdle
in
the
mobile
space
than
there
is
in
other
places,
or
is
the
easy
because
everybody
is
being
forced
to
actually
secretly
use
WebKit
and
they're
all
the
same
or
I.
B
Yeah
really
really
pins
iOS
everybody
has
their
hands
tied
behind
their
back.
There
are
a
few
ways
to
punch
through
on
the
web
browser
anyway.
You
know,
Aaron
could
probably
speak
some
more
to
what
things
like
text
on
iOS,
specifically
to
find
what
the
optimal
balance
between
you
know,
performance
to
execution
and
how
they're
implementing
things
like
crypto
there,
but
from
from
the
web
perspective,
even
even
browsers
that
are
browsers
that
are
shipping,
for
example,
on
chromium
rendering
engine
base,
but
shipping
on
Android
also
don't
have
things
like
extension
infrastructure.
B
So
it's
very
hard
to
add
things
like
gonna
be
lower
level
PP
network
architectures
without
either
bundling
in
the
full
node
using
centralized
gateways
or
doing
all
that
kind
of
heavy
lifting
themselves.
So
we're
trying
to
crack
open
these
things
here
and
there
when
we
have
the
opportunity
to,
we
think
there's
some
leverage
to
be
add.
There's
some
of
our
browser's
working
with
are
very
interested
in
those
opportunities,
but
it
really
depends
on.
B
E
Did
you
you,
you
would
be
terrific
to
get
in
touch
with
Andres
talents
from
many
worms
he
has
just
for
the
many
ones
to
iOS.
Of
course
it's
not
the
same
problem
because
I,
don't
so
it's
many
worse.
Doesn't
scarlet
doesn't
do
like
intensive
crypto
activities,
but
he
it's
working.
So
you
should
try
it
out.
B
At
least
well,
yeah
I've
talked
to
him
before
and
it's
interesting
to
see
like
textiles
done,
a
bunch
of
work
and
birdies
and
a
bunch
of
work
as
well
on
iOS,
you
know
utilizing
the
native
stack
birdies
recent
post
about
how
to
get
Android
and
iOS
interoperating
over
ble
and
Wi-Fi
direct
is
kind
of
fascinating
and
really
speaks
to
the
level
of
technical
challenge
there.
If
you
pick
one
one
deployment
channel
or
platform
like
iOS,
it's
easier
to
interoperate
getting
interoperability
in
those
lower
level,
hardware,
network
ability
and
building.
B
I'm
interested
to
see
how
many
works
works
between
Android
and
iOS,
for
example,
the
planetary
scuttlebutt
app
doesn't
work
with
any
other
scuttlebutt
apps
and
it's
iOS
only
and
they're,
like
I'll
figure,
that
out
later,
let's
do
iOS
first
and
then
figure
out
the
other
2
billion
mobile
users.
Later
there
wasn't
have
less
money
and
so
I'm
interested
to
see
what
the
interoperability
story
there
is.
If
it's
just
like,
have
to
hit
the
network,
the
cloud
be
able
to
connect
or
not.
A
H
A
So
I
will
just
take
a
few
notes.
Let's
see
well,
Leo
will
take
a
few
notes.
What
do
people
have
for
ideas?
What
are
related
concepts
in
the
local
and
offline
collaboration
space
that
you
hope
we
can
explore
in
future
discussions
or
people
who
are
building
cool
things,
that
we
should
invite
to
present
or
are
those
kinds
of
things.
B
E
A
C
Did
we
have
someone
from
key
week's
project
in
the
past?
I
was
not
on
every,
however,
however
killings,
yeah
qyx
is
project
for
creating
compressed
snapshots
of
things
like
media
wiki
pages.
That
includes
wikipedia,
but
also
like
all
the
dictionaries,
Stack
Overflow
Project
Gutenberg
and
we
are
collaborating
with
key
weeks
around
putting
those
snapshots
on
ipfs
the
distributed.
Wikipedia
mirror
that
we
have
right
now
is
basically
an
unpacked
snapshot
created
by
the
cubix
project,
and
we
are
looking
into
ways
of
one
putting
zine
files
on
ipfs.
C
So
ipfs
could
act
as
a
distribution
network
for
those
snapshots
and
using
them
directly
from
ipfs.
So
that
way,
only
like
a
single
person
in
a
classroom
would
have
to
have
that
sim
and
it
does
not
matter
if
that's
teacher
or
one
of
students
or
something
like
that,
and
it
would
be
immediately
available
and
at
the
same
time
we
are
also
looking
into
a
web-based
reader.
So
those
snapshots
in
compressed
form
are
binary
and
require
specialized
reader.
C
However,
there's
there's
like
JavaScript
based
one.
The
problem
is,
those
snapshots
are
hundreds
of
gigabytes
in
size
sometimes,
and
if
we
put
them
on
ipfs,
then
you
don't
need
to
fetch
entire
thing.
You
could
fetch
just
a
specific
bite
range
and
you
don't
need
any
fancy.
Api
is
in
a
web
browser
because
JSI,
DFS
or
JS
ipfs
HTTP
client
already
provides
all
the
primitives
for
I
want
this
byte
range
from
this
cid
and
you
don't
need
to
specify
from
where
and
it
ideally,
it
would
work
in
a
web
browser.
C
So
I
think
we
could
have
at
least
maybe
invite
someone
from
cubics
to
tell
us
a
first
part
we'll
just
tell
about
the
project
and
in
the
future
would
probably
could
also
have
a
separate
one
on
how
we
can
leverage
ipfs
or
like
introduce
cubics
j/s.
If
it's
I
think
those
are
my
thoughts.
Sorry
for
speaking
for
you.
A
B
I'm
gonna
get
a
poke
friends
since
I
network
infrastructure
for
refugee
camps
in
Bangladesh.
They
have
to
rig
all
kinds
of
stuff.
His
life
is
like
DNS
is.
The
devil
is
like
it's
like
the
ultimate
stopper
for
everything
they
have
to
do
is
dependence,
and
most
of
the
communication
only
leaves
the
camp.
It's
people
in
the
kept
talking
to
each
other,
so
I
you
see
if
he
will
come
and
talk
about
how
they
set
up
infrastructure
for
these
types
of
like
partial,
closed
network,
where
they're.
D
A
A
E
And
then
so
very
sorry,
I
mentioned
coronavirus,
I
hope
everyone
is
well
and
safe
and
clean
this.
This
has
it
has
affected
everyone
everywhere.
So
it's
something
that
affects
us
all,
but
the
people
that
are
released
by
Malaysia
now
we're
surroundings
are
the
ones
that
are
more
affected
by
this
situation.
E
H
E
Tuesday
I
wonder
I
wonder
if
if
there
was
some
actions
or
if
there
is
some
interest
in
putting
energy
in
how
IP
access
could
continue
to
being
doing,
direct
action
or
I
mean
direct
action
like
supporting
those
that
are
doing
things
like
that
or
doing
things
directly
putting
energy
heads.
But
you
have
so
many
heads,
smart,
let's
say
yeah.
A
B
B
H
I
mean
just
from
I
guess:
you'd
call
a
an
interaction,
theoretical
sort
of
standpoint,
this
this
notion
of
contact
tracing
kind
of
know.
There
seems
to
be
a
relation
between
you
know
that
they're
saying
about
Bluetooth
connections,
but
maybe
there's
some
sort
of
thing
around
there
and
just
kind
of
hops.
Between
phones-
and
you
know,
I,
don't
know,
and
then
there
was
also
I.
Think
did
you
check
the
link
I
sent
you
before
there?
H
There
was
somebody
talking
about
there's
some
company
in
India,
developing
a
blockchain
way
to
to
do
like
anonymous,
anonymous
contact,
tracing
and
they're
they're
talking
about
potentially
using
IP
addresses
that
kind
of
data
store
for
it
so
hold
on
us
and
I'll
put
a
link
in
here.
Their
meaning
is
sure
so.
E
E
Neighborhood
size
deployment,
1,500
families,
so
a
neighbor,
a
network
that
is
a
good
size,
Network
and
I
I.
Imagine
that
these
ideas
of
embedding
peer-to-peer
protocols
in
routers
or
in
this
or
in
network
setups
big
in
these
deployment
or
future
deployments.
We
can
find
opportunities
to
try
this
ideas
out,
prototype
together
and
explore
user
experiences
and
I
wonder
if
that's
something
there
that
we
should
be
experienced,
that
we
are
not
yet
exploring
a
notary
or
Molly
or
who
there's
something
there
that
we
should
be
following
up
on.
Maybe.
A
D
That
folks,
like
Aaron,
are
doing
and
kind
of
looking
at
experimenting
like
just
in
general,
there's
tons
of
people
in
the
ecosystem.
We've
really
been
pushing
mobile
forward,
and
you
know
now.
It's
noticed
all
the
people
who
are
identifying
some
of
these
problems
and
a
chunk
of
the
research
work
that's
happening
here
is
also
like
giving
us
better
feedback.
Loops
I.
A
All
right
I
need
to
drop
in
a
sec
to
hunt.
Another
call,
but
I
just
wanted
to
ask
a
quick
scheduling
question,
so
we
are
experimenting
with
new
meeting
Wednesdays
and
it's
Wednesday,
so
just
checking
as
to
whether
we
have
another
we
can
follow
up
with
us
offline
if
we
want
to,
but
thinking
about
another
day.
That
would
work
well
for
us
house
this
time
of
day
been
working
fairly
well
for
people
get
our
kind
of
time
zone
crossover
here.
A
A
Okay,
so
let's
maybe
see
if
a
Thursday
will
work
for
this
one,
but
I
will
follow
up
in
our
github
thread.
If
anyone
hasn't
seen
it,
we
use
a
github
issue
as
the
place
where
we
announce
what's
coming
up
on
this
call.
So
if
you
want
to
watch
the
issue
and
use
email
notifications,
then
you'll
actually
receive
an
email
from
me.
It
will
look
like
an
email
from
me
saying
balls
coming
out.