►
From YouTube: IPFS All Hands 🙌🏽📞 April 15, 2019
Description
Newsletter: https://tinyletter.com/ipfsnewsletter
A
Hello
welcome
everyone
to
the
ipfs
weekly
call.
My
name
is
Portia
and
at
the
ipfs
week
we
call
this
is
where
we
get
to
show
showcase
and
see
all
the
wonderful
applications
being
built
on
top
of
IPSS.
So
thank
you
for
being
here
and
today
we
are
going
to
speak
to
Joel,
he's
an
engineer
at
angel
he's,
an
engineer
at
three
box
and
three
box
works
on
social
profiles
for
web.
Three
applications
for
peer-to-peer
applications
and
the
thing
about
Joel
is
we're
actually
in
the
same
building.
A
A
B
B
B
So
if
anyone
is
familiar,
Dae
is
short
for
decentralized
identifiers,
which
is
a
standard
developed
by
the
decentralized
identity
foundation.
So
why
are
we
going
three
blocks?
So
the
way
that
started
was
that
we
were
working
and
in
the
etherium
space,
and
we
kind
of
saw
that
a
lot
of
ethereum
gaps
were
kind
of
boring.
B
Basically,
you
had
a
smart
contract.
Then
you
had
a
front-end
that
maybe
was
hosted
on
my
PFS,
and
you
could
only
do
like
very
simple
thing:
I
click
on
the
bottom
and
then
that
triggers
some
smart
contract
function.
You
can't
really
do
rich
applications
like
that,
because
smart
contracts
are
expensive
and
slow.
B
B
B
Basically,
you
can
spin
up
and
they
will
replicate
the
data
in
the
three
box
network,
so
each
user
kind
of
have
their
own
data
store
and
that's
stored
locally
within
the
browser,
but
it's
also
replicated
on
any
nodes
in
the
network
that
are
run
separately.
So
there's
no
drums
with
no
js',
we
I
didn't
go
through
a
little
boat
boat,
so
meat
right
data
for
you
were
serious
and
verify
and
create
claims
and
that
something
has
to
do
with
decentralized
event.
B
Fires,
encrypt
decrypt
data
and
create
threads
and
I'm
gonna,
be
diving
deeper
in
that
there
and
the
painting
now
communicates
with
any
clients.
That's
three
three
box:
J
s,
replicates
Terra
and
provides
a
REST
API
for,
like
the
latest
state
of
users,
profiles
and
data
search,
and
this
also
has
a
module.
So
it
can
communicate
with
as
three
if
you
want
to
have
like
a
more
robust
back
in
then
the
third
component,
that's
still
rather
important,
is
the
three
box
profiles,
tab
so
basically
adapt.
B
We
can
also
see
a
public
activity
that
you
made
so
like
things,
you've
got
they
didn't
in
profile,
but
also,
if
you
tie
this
profile
to
interfere
images,
you
can
see
all
of
this.
This
users
public
key
ATM
activity,
so
the
J's
library
has
a
bunch
of
features
and
there's
like
three
major
ones.
First,
one
is
a
profile
where
you
can
basically
set
and
update
the
profile
of
a
user.
B
B
B
B
It's
basically
a
CR
DT
data
structure
on
top
of
IP
FS,
which
updates
and
replicates
databases
between
peers
that
are
actively
listening
for
those
databases.
And
then
we
are
using
a
DI
key
and
we
have
a
dige
method
and
that's
a
cryptographic
identifier
for
users,
so
basically
giving
each
user
a
unique
identifier
in
the
network.
B
So
kind
of
touch
upon
this,
but
basically
we
have
tap
that
would
use
the
three
Box
J's
library,
this
dap
will
type
in
the
browser
and
you
have
the
j
SI
p
FS.
It
connects
the
orbit
eb
and
you
have
the
v
ID
and
all
this
creates
your
three
box
which,
where
you
can
store
data,
then
we
communicate
with
pub
sub
to
the
paying
node.
Where.
B
Now
you
can
use
query
the
REST
API
for
for
the
state
of
the
profile,
which
is
useful,
if
you
just
like
displaying
something-
and
you
just
want
to
display
profile,
a
lot
of
profiles
for
different
users,
India
and
since
we're
coming
from
this
there
in
space.
The
kind
of
first
application
free
box
is
used
for
is
to
replace,
accept
doses
of
etherium
applications
with
a
picture
and
a
name.
B
So
as
we
can
bootstrap
this
network,
we
have
a
something
called
the
address
server
and
this
is
basically
a
mapping
from
an
aetherium
address
to
a
three
box.
D
ID-
and
this
is
a
component
that
we
have
centralized
right
now,
but
we're
going
to
fold
that
in
into
the
pinning
node
and
then
you
we
are
gonna,
do
lookup
of
the
theory.
Map
goes
to
a
three
box
dat
with
pumps
up
similar
to
the
IP
NS
pub/sub.
B
Alright,
so
I
want
to
talk
a
little
bit
about
things
that
are
interesting
for
us
in
terms
of
research
and
things
that
we
would
like
to
see.
Maybe
collaborate
on
so
data
schema,
so
we
see
is
really
important
like
how
do
we
store
data
in
a
way
where
it's
interoperable?
There
is
a
website
called
schema.org,
but
it's
primarily
focused
on
at
json-ld,
so
it
would
be
cool
also
if
there
was
like
IPL
be
based.
Schemas
I
haven't
seen
very
much
efforts
around
that.
B
So,
if
you
know
something
about
that,
they'll
be
very
interesting
and
then
IPL,
D
and
json-ld
compatibility
I
know
there's
some
work
on
that,
but,
like
that
area,
I
think
needs
a
bunch
of
exploration
and
then,
of
course,
linked
data
signatures.
So
right
now
our
BTB
has
a
system
where
it
kind
of
takes
the
data
in
in
a
nightly.
First
object:
ads
signature
based
on
that
data
in
its
own
custom
way.
B
There
is
a
working
group
I
think
that
works
would
like
these
linked
data
signatures,
I,
don't
think
I
think
they
might
become
interoperable
with
both
json-ld
and
IPL
D,
and
that
would
be
super
cool.
So
we
can
have
like
way
of
signing
data
objects
in
a
in
a
like
standard
way
and
I
think
this.
This
standard
would
also
likely
support
D,
IDs
but
I
think
there's
still
some
open
questions
there
so
yeah.
This
was
like
a
quick
overview
of
three
box
and
we'd
love
to
hear
some
questions.
B
So,
for
example,
Dow
stack
is
very
interested
in
using
our
threads
for
creating
a
commenting
system
for
their
kind
of
Dow.
So
you
can
like
comment
and
proposals
and
interact
with
other
members
of
a
Dow
and
yeah.
Some
other
dolls
are
also
looking
at
using
it
and
there's
a
bunch
of
other
products
looking
at
it
as
well.
A
B
B
So
so
one
thing:
that's
like
a
combination
of
ipfs
in
our
BTB
is
like
as
IP
this
releases
like
a
new
version.
It
takes
a
while
for
Orbitz.
You
like
update
some
other
things.
That
is
like
new
in
the
new
version,
and
we
have
to
kind
of
wait
until
with
updating
the
ipfs
dependency
before
they
have
updated
their
software.
B
Easier
to
understand
like
when
I
can
send
a
message
and
know
that
it
will
be
received
by
another
peer
like
a
specific
ear.
So
like
right
now,
when
I
connect
to
the
pub
sub
network,
I
kind
of
wait
with
sending
my
message
before
I've
actually
been
connected
to
a
node
like
to
to
a
pinning
node.
So
I
kind
of
wait
for
that
and
then
send
the
message.
B
B
B
So
basically,
the
three
box
project
spun
out
of
another
project
is
called
Newport
and
we
were
kind
of
in
Newport
experimenting
with
some
daj
methods,
and
this
one
is
called
Newport,
so
mu
court
and
basically
it's
a
create
a
bunch
of
keys,
add
them
to
a
Nike,
FS
objects
and
then
take
the
hash
of
the
type
FS
objects
would
be
the
identifiers.
We
are
actually
planning
on
creating
another,
a
DAT
method,
that's
very
similar
to
to
Newport,
but
it
has
some
additional
features.
B
That's
useful
for
our
spaces
features.
So
basically
what
we've
been
thinking
is
a
if
a
an
application
requests
access
to
a
specific
space,
and
you
want
to
send
messages
to
different
users
between
different
users.
In
a
space.
You
don't
want
to
encrypt
a
message
such
that
other
depths
that
doesn't
have
access
to
that
space
can
decrypt
them.
So
we
kind
of
had
this
two
layer,
div
system
approach,
where
we
have
a
div
for
each
space,
but
that
theory
also
reference
like
a
root
key
ID.
C
That's
I
wrote
the
the
IP
ID
did
method,
which
is
based
on
IP,
LD
and
so
I
ran
into
the
issue
about
the
JCL
D
and
the
linked
data
signatures.
So
you
can
serialize
json-ld
on
top
of
IP
LD,
but
it's
not
backwards
compatible
and
so
for
backward
backwards
compatibility.
You
need
a
fully
qualified,
URI
and
ipfs
tonight.
B
B
C
A
Thank
you.
Our
next
comment
volker
kind
of
relieved,
sigh
PLD,
there's
the
weekly
meeting,
which
is
actually
today
for
the
IPL
d
teen
that
is
open
for
everyone.
So
if
you
want
to
learn
more
about
IPL
d,
they
do
have
an
open
meeting
as
well
and
there's
a
link
where
you
could
find
more
information
about
it.
Thank
you
both.