►
From YouTube: Backup
Description
Newsletter: https://tinyletter.com/ipfsnewsletter
A
B
B
B
B
A
B
I
can
hear
everyone
and
we
will
end
with
a
Q
&
A
section,
so
I
suggest
have
a
look
at
the
agenda.
Does
anyone
have
anything
they
would
like
to
announce
before
we
get
into
our
main
presentation.
B
Looking
for
hands,
oh
I
see
something
here.
Yes,
I'm
looking
at
looks
like
a
no.
We
will
begin
with
our
main
presentation,
then
so
the
under
lease
take
it
away.
Okay,.
A
A
A
A
Cross
application
data
storage
built
on
IP,
ffs
and
loop
p2p,
and
we
think
of
it
as
like,
a
decentralized
iCloud
in
the
future
or
the
splits
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.
A
C
A
C
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,
you
know,
want
to
share
with
specific
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
build
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.
These
are
management's.
A
C
A
Of
textile
is
what
we
think
of
as
this
account
wallet.
So
it's
an
HD
wallet,
it's
kind
of
inspired
by
Stellar's
wallet,
it's
backed
by
a
monic
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
A
The
time
because
if
you're
in
the
mobile
world
you're
always
going
on
an
offline,
so
you
get
out
of
the
sink
really
fast.
So
we
end
up
having
this
really
wide
patch
Street,
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.
A
If
they
have
the
same
few
parents,
we
know
there
will
always
result
in
the
same
exact
block
ash.
So
all
these
all
these
little
updates,
we
call
them
blocks-
are
stored
on
a
DFS
and
because
they're
hash,
sync
together,
you
can
traverse
back
and
recover
a
thread
or,
if
you're
joining
a
thread
of
someone
else's
thread,
you
can
Traverse
back
and
get
all
the
older
history
and
be
here.
So
this
is
an
example
here.
I
know
this
looks
terrible
explode
up
like
this.
C
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
on
notes
up
into
the
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
So
looking
at
the
internal
components
here,
so
obviously
we're
unlike
the
efest
node,
if
it's
in
the
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
threat
service.
That's
the
CRB
tea
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.
A
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
IVFs.
So
we've
come
up
with
this
system
called
it's
similar
to
the
transloaded
that
I've
used
in
past
lights
and
which
is
a
really
nice
service
or
if
you
wanna,
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
Let
me
call
them
Nils,
because
textile,
so
you
send
the
raw
data
to
the
the
vlog
mill
that
just
groups
it
and
stores
it
not
BFS
and
then
I'm
gonna
taste
the
output
from
that
mill
and
extracts
the
exhibit
a
dot
here
that
I
don't
take
that
simultaneously.
It'll
take
the
output
from
the
raw
and
we'll
create
these
different
sizes.
Here
these
things
image,
at
least
on
the
same
point.
A
A
Let's
see
so
with
the
results
anna'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
you've
got
all
these
different
links
and
then
each
each
link
results
in
a
determined
deed
for
data
link
and
the
/f
here,
which
means
it's
going
to
show
like
the
index
of
the
data.
C
A
Not
ideally
deterministic,
you
know
you
don't
want
to
keep
adding
the
same
file
over
and
over,
so
each
node
locally
will
keep
track
of
all
the
files
that
are
in
its
node,
and
you
can
look
up
the
pre
hash
of
a
file
based
on
it's
Puckle
index.
You
can
use
that
with
in
combination
with
the
options
that
were
used
to
create
that
file
to
determine
if
it's
already
in
the
system,
so
you're
not
continually
adding
the
same
files
so
we're
getting.
A
Having
a
usable
version
that
you
could
build
on
top
of
the
main
pieces
were
finishing
off
the
mechanisms
for
account
recovery,
so
we're
doing
all
the
backup
to
your
cafes,
but
we're
missing
the
piece
where
you
asked
the
network
for
your
all.
Your
thread
back
notes.
So
that's
the
tip
of
all
your
thread
so
would
just
be
like.
Given
the
online
you
know
in
an
icon
world,
it's
really
easy.
A
Just
a
note
about
a
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
run
in
like
a
file
calling
node
in
the
textile
cafe.
A
So
you
can
use
a
Jason,
the
schemas
here,
so
if
your
application
needs
to
this
one's
kind
of
pressing
like
a
bird,
if
you
want
to
ingest
log
data,
for
example,
you
could
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
of
those
would
be
anything
added
to
the
thread
and
then
over
here
really
small,
but
you
can
I
guess
the
simplest.
These
gates
are
the
throat.
Bridle
is
just
like
a
chat.
A
Has
a
chat
self
commands
that
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,
but
I
was
taken
offline?
They
would
communicate
via
the
boxing
so
I.
B
F
I
I
was
a
curious
about
the
way
you
keep
things
private
I
heard
the
word
encryption.
Does
that
mean
you're
encrypting
the
blocks
at
rest
effectively
yeah.
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
private
thread
which
doesn't
accept,
invites,
and
that
would
be
like
for
your
for
your
account
for
device
peers.
We
use
an
internal.
A
B
A
Two
questions,
one
is:
do
you
use
any
of
the
built-in
files
EPA's
like
MF
s
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
for
images
and
manipulating
images?
A
Did
you
consider
using
that
to
use
that
as
a
reference
reference,
but
I
would
think
about
schemas
and
things
so
the
brief
we
don't
use
that
we
just
you
know
the
the
actual
data
is
still
broken
up
into
into
the
blocks.
A
And
you
know
file,
it
could
be
adjacent
objects
or,
but
yes,
it's
when
you
that
was
to
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
be
on
it
into
that
thread.
My
node
might
reject
it,
because
it
will
walk
that
the
tag
figure
I've
required
links
her
in
there
I
look
at
the
red
content
types.
A
But
in
your
second
question
no
I
that
sounds
awesome
though
I
didn't
know
about
that.
We
should
talk
about
yeah.
Let
me
sweets
is
right
right
now.
It's
just
I
mean
I,
guess,
I
kind
of
just
like
it's
fairly
analogous
to
transloaded
the
transloaded
Scribus
in
the
sense
of
like
it'll.
You
know
walks
through
step,
step
wise
and
what
needs
to
happen,
but
yeah
I
mean
so.
We
currently
only
have
like
a
way
to
resize
images
and
extract
exit
from
it.
D
A
A
A
D
B
A
Yeah
pure
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
in
a
business
of
creating
and
yet
another
solution
there
or
something
that
it
requires
you
yeah
in
textile,
so
it
would
be
awesome
to
be
able
to
you
know
in
terms
of
a
textile
into
that
space
with
you
know
an
existing
idea,
even
even
like
it.
C
A
A
A
B
Thank
you
very
much.
We
will
be
following
the
developments
of
textile
photos
and
yeah.
If
you
need
help
from
us,
we're
I
mean
you're
part
could
always
ping
us.
Thank
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,
need.