►
From YouTube: IPFS Weekly Call 🙌🏽📞December 10th, 2018
Description
Newsletter: https://tinyletter.com/ipfsnewsletter
Textile.io Github Repo: https://github.com/textileio/textile-go
A
We
originally
started
because
we
wanted
to
build
a
really
useful
application
on
top
of
ipfs
and
we
figured
that
mobile
was
the
place
to
do
it
because
it
didn't
seem
like
a
lot
of
people
were
attacking
that
space
and
slowly
over
time,
we've
kind
of
grown
our
vision.
Our
mission
is
found
more
into
wanting
to
provide
a
a
more
like
a
distributed
database
and
application
platform
kind
of
like
a
we
like
to
think
of
it
as
a
decentralized
iCloud.
A
A
Cross
application
data
storage,
those
on
IP,
ffs
and
loop
p2p
again,
we
think
of
it
as
like,
a
decentralized
iCloud
in
the
future,
or
that's
that's
kind
of
our
mission,
decentralize
an
overnight
cloud
that
developers
and
users
can
build
upon.
So
the
what
we
want
to
enable
people
to
do
with
textile
and
talk
about
users
is
to
the
applications
and
services
securely
store,
your
photos,
videos,
documents
or
any
other
type
of
file,
chat
with
friends
and
family
and
access
your
data
from
anywhere
wherever
you
are,
so
these
are
kind
of
a
poor.
D
A
A
A
D
A
To
think
about
in
terms
of
like
user
ownership,
so
everyone
understands
what
you
can
do
with
photos.
People
understand,
you
know
they
there's
different
types
of
privacy
around
your
photos.
You
don't
want
your
entire
camera
roll
to
the
beat
open
to
the
public,
but
you
might
want
to
share
with
the
groups
and
so
I'll
skip
some
of
this
stuff.
We
are
trying
to
enable
people
to
build
other
apps
like
textile
photos.
A
We
have
a
mobile
SDK
that
you
can
plug
in
for
iOS
and
Android
and
we're
trying
to
Bill
it
as
something
that
just
for
the
average
application
developer
is
someone
that
might
not
really
be
sold
on
decentralization.
This
is
fairly
but
that
they
can
dive
into
and
actually
find
that
it
makes
their
life
easier
so
like
they
can
maybe
skip
user
management.
A
A
Textile
is
what
we
think
of
as
an
account
wallet.
So
it's
an
HD
wallet,
it's
kind
of
inspired
by
Stellar's
wallet,
it's
backed
by
a
mnemonic
phrase.
So
you
can
generate
all
these
any
number
of
deterministic
accounts
in
in
this
wallet
and
then
you
would
use
each
one
of
those
to
initialize
the
textile
node
and
that's
how
your
data,
the
syncs,
between
your
different
devices
at
a
high
level,
so
the
the
main
sort
of
most
important
data
structure.
A
There's
peers
joining
leaving
data
being
added
comments,
messages,
and
it's
really
just
to
get
like
half
Street
where
each
you
know,
if
there's
a
case
where
a
large
misshapen,
which
is
almost
all
the
time,
because
if
you're
in
the
mobile
world
you're
always
going
on
and
offline,
so
you
get
out
of
the
sync
really
fast.
So
we
end
up
having
this
really
wide
hash
tree.
A
But
this
is
our
sort
of
our
first
stab
at
this.
That's
really
not
terribly
complicated.
It's
just
there's
a
deterministic
merge
rule.
That
happens.
It
basically
just
takes
the
earlier
date
and
creates
another
block
in
the
thread
that
can
be
recreated
on
other
peers
so
like
if
they
have
the
same
few
parents.
We
know
they'll
always
result
in
the
same
exact
block
ash.
A
So
all
these
all
these
little
updates
we
call
them
blocks,
are
stored
on
my
PFS
and
because
they're
hash
linked
together,
you
can
Traverse
back
and
recover
a
thread
or,
if
you're
joining
it,
someone
else's
thread.
You
can
traverse
back
and
get
all
the
older
history
and
it's
to
here.
So
this
is
an
example
here.
I
know
this
looks
terrible
explode
up
like
this.
D
A
A
Obviously,
we
want
to
do
everything
we
can
peer-to-peer,
but
because
of
the
need
for
in
the
mobile
world,
you
want
to
really
handle
offline
robustly.
So
you
run
into
that
all
the
time.
So
what
we
do
is
we
put
the
same
text
down
notes
up
into
cloud.
We
run,
we
run
them
in
on
Amazon
and
they
provide
offline
name
boxing
services
to
other
peers.
So
if
I
send
you
a
message
and
you're
offline
I
will
I
will
know
I
better
from
the
previous
thread
that
I've
been
with
you
or
from
your
IPS
user
profile.
A
I'll
know
where
your
inboxes
are
so
I
can
send
to
your
various
kind
of
a
inboxes
and
then,
when
you
come
back
online,
you
don't
like
those
messages
so
looking
at
the
anode
of
rambling
fast,
who
is
so
feel
free
to
interrupt
me
at
any
point
so
looking
at
the
internal
components
here,
so
obviously
we're,
unlike
the
efest
node,
if
it's
in
them
in
the
mobile
use
case,
it's
just
a
client
node.
So
it's
only
there
to
be
able
to
traverse
the
network
and
we
have
two
p2p
services.
There's
the
thread
service.
A
That's
the
CRB
teeth
service
that
worthless
trinkets,
state
pink
ears,
and
then
we
have
this
cafe
service
that
you
can
register
with
with
different
nodes
and
you'll
open
a
user
session.
Just
a
JWT
session
and
anytime
you've
got
a
data
to
the
network,
you'll
actually
pin
it
on
those
cafes
and
then
there's
the
offline
inboxing
service
I
mentioned
earlier
and
so
locally.
You
want
to
be
able
to
like
list
the
files
or
photos,
you've
added
type
EFS
and
that's
what
this
files
API
is
for.
A
A
So
one
of
the
core
pieces
of
what
we're
doing
is
trying
to
make
as
part
of
this
decentralize
iCloud
mission
is
trying
to
make
a
way
for
people
to
easily
add
structured
data
type
DFS.
So
we've
come
up
with
this
system
called
it's
similar
to
transload
it
that
I've
used
in
past
block
types
and
which
is
a
really
nice
service
or
if
you
wanna
in
your
application,
need
to
define
how,
like
it,
ingests
files
or
videos.
So
I
want
to
take
this
image
and
I
want
to
create
these
multiple
different
sizes
and
thumbnails.
A
A
Not
surprisingly,
becomes
a
dagger
node
link,
so
this
setup
here
says
essentially,
let's
take
the
raw
image
data.
Well,
in
this
case,
it
doesn't
care
if
it's
an
image
so
just
take
the
raw
data.
We
want
to
save
the
original
and
we're
gonna.
Send
it
to
translate
calls
these
robots
like
encoding
robots
and
we
call
them
Nils.
D
A
Textile,
so
you
send
the
raw
data
to
the
vlog
mill
that
just
encrypted
and
stored
it
not
DFS,
and
then
it
takes
the
output
from
that
mill
and
it
extracts
the
exist,
a
dot
here
that
I
don't
take
that
simultaneously.
It'll
take
the
output
from
the
raw
and
will
create
these
different
sizes.
Here,
using
this
image,
we
saw
the
same
point
so
there's
this
is
a
mobile
client
in
the
mobile
world
it.
Actually,
this
is
running
on
the
node
in
the
phone.
A
Let's
see
so
with
the
results
nana's,
this
is
kind
of
small,
but
a
dag
instruction
that
looks
like
this.
So
we've
got
still.
We
only
added
one
file
here,
so
we've
just
got
one
index
and
we've
got
all
these
different
links
and
then
each
each
link
results
in
a
determined
deed
for
data
link
and
this
/f
here,
which
means
it's
going
to
show
like
the
index
of
the
data.
A
So,
oh
just
be
like
give
me
all
my
you
know
in
icon,
world.
That's
really
easy!
You
just
ask
Apple,
hey
I'm,
proving
that
I
am
Who
I.
Am
we
do
that
they
get
out
of
apple
idea,
we're
doing
that
with
your
mnemonic,
see
you
say
to
the
network.
This
is
who
I
am
I.
Need
like
who's
got
my
stuff,
basically
so
we're
doing
that
with
mostly
with
pump
zone
so
dedicated
channels
on
all
the
cafe's
that
we
ask
for
specific
people,
users
back
outs
and.
A
Just
a
note
about
final
coin:
we
we
don't
love
the
we
always
I.
Think
we
see
like
I
need
to
have
these
cafes,
these
federated
nodes.
This
is
something
like
this,
but
in
terms
of
being
the
place
where
everything's
pin
we'd
like
to
swap
that
out
for
for
five
points
every,
hopefully,
we
would
running
like
a
file
calling
node
in
the
excel
cafe.
A
A
So
you
can
use
Jason
the
schemas
here,
so
if
your
application
needs
to
this
one's
kind
of
depressing
like
a
third,
if
you
want
to
ingest
log
data,
for
example,
you
can
define
on
Jason's
team.
That
looks
like
this.
So
it's
got,
you
know
this
is
the
forgot.
The
name
of
the
spec,
but
some
log
spec
requires
these
fields
and
all
those
would
be
anything
out
of
two
threaded
and
then
over
here
really
small,
but
you
can
I
guess
the
simplest.
Each
case
of
the
program
is
just
like
a
chat,
so
we
have
a
textile.
D
A
Line
client
has
a
chat,
sub
commands,
so
you
can
just
invite
people
to
a
thread
and
just
start
chatting.
You
know
so
what's
going
on
here
is
the
each
message
is
being
backed
up
to
their
respective
cafes
and
because
I'm
local
they're
just
talking
directly
to
each
other?
If
I
was
to
take
one
offline,
they
would
communicate
via
the
boxing.
C
E
A
A
A
So
there
are
different
thread
types
that
we
haven't
fully
fleshed
out.
There
is
right
now
the
ones
that
are
flushed
out
are
open
thread,
which
means
anyone
can
create,
invites
anyone
else
and
then
a
private
thread
which
doesn't
accept,
invites,
and
that
would
be
like
for
your
free
or
account
or
device
peers.
We
use
an
internal
party
for
that
I'm.
C
F
Questions,
one
is:
do
you
use
any
of
the
built-in
files
apos
like
em
FS
for
octopus,
or
did
you
build
all
that?
Are
you
directly
manipulating
the
tag
and
you
built
your
own
files
related
API
and
then
totally
unrelated?
Are
you
familiar
with
triple
I
F
the
international
image
interoperability
framework
and
their
API
is
for
images
and
manipulating
images.
Did
you
consider
using
that
to
use
that
as
a
reference
reference
point
but
think
about
schemas
and
things.
A
So
the
brief
we
don't
use
that
we
just
you
know
the
the
actual
data
is
still
broken
up
into
into
the
blocks.
So
it's
kind
of
more
of
our
level
concept
above
file.
A
And
you
know
file,
it
could
be
adjacent
object
or
but
yes,
it's
when
you
create
a
photos,
schema
and
then
create
a
thread
with
that
it
does
do
the
validation
so
like
if
I
send
you
a
DAC
note
that
it's
supposed
to
beat
on
it
into
that
thread.
My
note
might
reject
it,
because
it
will
walk
that
the
data
figure
I've
required
links
her
in
there
I
think
the
right
content
types.
A
But
and
then
a
second
question,
no
I.
That
sounds
awesome
though
I
didn't
know
about
that
one.
We
should
talk
about
yeah.
Let
me
sweets
is
right
right
now.
It's
this
I
mean
I,
guess
I
kind
of
just
like
it's
fairly
analogous
to
transloaded
the
transloaded
purpose
in
the
sense
of
like
it'll.
You
know
walks
through
stuff,
stepwise
some
figured
out
what
needs
to
happen,
but
you
have
em,
you
know,
so
we.
A
B
A
A
A
A
B
A
Your
star,
so
we
have
these
profiles,
that's
really
just
a
super
basic
like
we
don't.
If
someone
had
a
really
nice
identity
solution
or
something
like
that,
it
would
just
we
would
hope
to
just
plug
that
in
like
we
don't
we
don't
really
want
to
be
the
business
of
creating
and
yet
another
solution
there
or
something
that
it
requires
you
be
in
textile,
so
it
would
be
awesome
to
be
able
to.
You
know,
enter
the
textile
into
that
space
with
you
know
an
existing.
Do
you
even
like
it.
A
D
A
A
C
Thank
you
very
much.
We
will
be
following
the
developments
of
textile
photos
and
yeah.
If
you
need
to
get
help
from
us,
we're
I
mean
you're
part,
it
always
ping
us
we
can
with
ping
you.
Thank
you.
Everyone
I
would
like
to
also
thank
Alan
for
taking
notes
and
I'll
see
everyone
next
week
have
a
great
week
take
care
bye.