►
Description
Carson - js-threads in Textile
Matt - Pinata Regions and Replications
Dietrich - EthDenver recap
Alan - IPFS Browser Sandbox
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
A
Today
is
the
lightening
talk
day,
which
means,
if
you've
never
heard
lightning
talks
before,
where
have
you
been
lightning
talks
about
the
best
talks
ever
because
you
get
a
small
snippet
of
information,
usually
fired
at
you
quite
rapidly
over
the
duration
of
five
minutes,
just
five
five
minutes,
so
you
guys
who
are
presenting
today
I'll,
give
you
a
warning
in
the
chat
after
four
minutes
or
so
and
then
after
five
minutes
I
will
kick
you
out
of
the
room?
No,
not
really
I
can
probably
just
say:
hey.
It's
been
five
minutes.
A
You
should
probably
think
about
stalling
now.
So,
okay,
today,
at
the
moment,
we
have
we're
gonna,
try
and
get
through
Carson
who's.
Gonna
talk
about
chairs
fred's.
We've
got
Matt
talking
about
pinata
news,
Dietrich's
gonna
talk
to
us
about
f,
Denver
and
I'm
gonna
talk
to
you
something
out
something
called
the
idea.
First,
browser
sandbox.
A
If
we
have
time,
if
anyone
else
has
a
lightning
talk
that
they'd
like
to
give
he's
editor
list,
if
we
don't
get
it
today
get
to
it
today,
then
we
do
lightning
talks
every
few
weeks
or
so
so
we
can
add
you
to
that
slot.
Instead,
so
no
no
worries
on
there
and
cool
would
this
is
always
fun.
I'm
I
got
permission
to
do.
Recording
with
someone
like
to
take
notes
today,.
A
C
A
D
D
But
anyway,
thanks
for
having
me
I
just
wanted
to
talk
really
quickly
about
something
that
we
have
just
sort
of
silently
released,
called
Jay
s,
threads
Jay
s,
threads
is
a
protocol
and
event
source
database
for
decentralized
user
siloed
data,
it's
our
JavaScript
implementation
of
a
project
that
we
have
been
working
on
for
a
while
now.
So
some
quick
background
on
that.
D
Some
of
you
might
remember
textile.
We
release
something
called
photos
and
photos
was
backed
by
essentially
a
protocol
for
exchanging
updates
between
a
set
of
peers,
and
we
learned
a
lot
in
that
experiment
and
we
literally
went
back
to
the
drawing
board,
wrote
a
white
paper.
This
is
it
right
here
you
can
check
it
out
at
that
short
link.
D
There
went
right
back
to
the
drawing
board
and
started
from
scratch,
and
we
started
building
this
protocol,
an
event
source
database
on
top
of
IP
FS
and
p2p,
an
IP
LD
and
all
of
the
great
projects
that
fall
under
the
banner
of
ipfs
and
our
first
implementation
was
a
reference
implementation
which
is
in
go.
Second,
implementation,
which
we
just
sort
of
stealthily
released,
is
typescript
fully
typed,
typescript
and
I'm
really
really
excited
about
it
for
a
bunch
of
reasons.
D
So
I'm
just
gonna
give
you
a
high-level
overview
of
what
is
threads
and
then,
hopefully
that
will
tickle
your
fancy
enough
to
go
check
it
out
on
github,
etc.
So,
threads,
roughly
speaking,
is
a
document
store
and
a
datastore
compliant
key
value
store.
It
has
a
MongoDB
like
interface,
so
it
just
feels
like
you're
working
with
a
local
database.
It
embraces
offline
first
and
remote,
sync
from
the
get-go.
D
So
if
you
add
something
to
the
database
and
you're
not
connected
to
any
other
peers,
it'll
feel
like
you've,
just
added
something
to
a
database
and
the
next
time
you
actually
have
a
connection.
It
will
fire
that
stuff
off.
In
the
background,
textiles,
developed
user
and
developer
authentication,
so
you
can
actually
do
authentication
database
stuff
on
a
cloud
if
you
want-
or
you
can
run
it
locally
or
you
can
run
your
own
instance
to
keep
it
fully
decentralized.
You
have
multiple
transport
options,
so
does
pub/sub
it
does
direct
peer-to-peer.
D
D
Actually
it
has
cryptographic
key
based
access
control
and
that's
pretty
nuanced
access
control,
so
you
can
have
things
like
readers
and
writers
and
followers,
and
all
this
good
stuff
and
all
that
stuff
is
backed
by
sort
of
best-in-class
encryption
and
wrapped
up
in
Nice
IP
LD
objects
so
that
you
can
pass
them
along
and
your
users
will
know
how
to
read
it.
I
don't
see
the
chat,
so
if
I
need
to
stop,
maybe
just
someone
wave
their
hands
vigorously
like
this
and
I
will
hopefully
see
that
we
also
have
configurable
codecs.
D
So
if
you
have
a
very
specific
use
case
where
you
need
like
a
CR
DT
to
make
sure
that
your
peers
are
always
going
to
be
able
to
resolve
any
conflicts,
then
you
can
plug
in
custom
CR
DTS
by
default.
We
have
a
couple
simple
ones,
including
some
operational
transport
ones,
so
you
can
do
things
like
you
know,
JSON
put
events
and
stuff
like
that,
and
all
the
peers
will
receive
the
same
types
of
events
in
the
same
order.
D
D
This
print
I'm
actually
focused
on
documentation.
So
don't
judge
me
if
you
go
there
today.
Judge
me
when
you
go
there
next
week,
but
we'll
have
pub/sub.
Only
transport
coming
up
soon
for
people
who
want
really
lightweight
decentralized
MongoDB
database
will
be
adding
indexing,
which
stack
codes
already
ready
to
go.
Just
hasn't
been
merged,
a
bunch
of
minimal
config,
pinning
setups.
So
textile
can
pin
your
stuff,
you
can
use
pinata
to
pin
your
stuff.
D
You
can
ask
your
friend
to
pin
your
stuff
whatever
you
want,
and
very
soon
we're
going
to
have
a
bunch
of
large
data
options
so
that
you
can
actually
put
large
data
in
your
document
stores.
So
there
you
go
I,
think
I'm
out
of
time,
so
come
build
stuff
with
us,
go
check
out
textile
I/o,
jeaious
threads
on
github,
and
then
you
can
check
out
our
reference
implementation
and
it's
all
backed
by
a
white
paper
that
is
rendered
in
latex.
So
you
know
it's
sciency
thanks
very
much.
B
D
Cool
looks
like
I
have
one
minute:
if
no
questions
the
one
slide
I
did
skip,
which
was
the
one
that
said,
network
of
trustless
peers.
So
one
feature
we
added
two
threads
that
we
learned
about
in
our
first
iteration
was
by
having
sort
of
a
hierarchy
of
keys.
You
can
actually
give
out
a
service
key
to
say
a
service
provider
and
they
can
backup
the
data
without
actually
knowing
what
the
contents
of
that
data
looks
like.
D
D
Yeah
good
question:
we've
been
thinking
about
this
a
bunch,
so
ultimately
it's
it's
like
a
alternative
to
orbit.
Tb
does
a
bunch
of
things
that
are
beneath
be
doesn't
in
orbit.
Tb
has
things
that
it
doesn't
do,
but
I
think,
given
that
we
do
also
support
pub/sub,
you
could
also
intercept
pub/sub
messages
that
were
intended
for
an
orbit
DB
instance
and
write
a
codec
to
handle
those.
So
the
answer
I
think
is,
is
a
is
a
pretty
positive.
Yes,
Thanks.
B
A
F
Si
some
freaked
me
out
here
a
second
I
didn't
say:
I
didn't
still
scares
me
all
right.
Here's
what
we
got
I
guess
so,
a
few
weeks
ago
this
is
no
project.
We've
been
working
on
for
quite
a
while
early
on.
We
were
looking
for
more
ways
to
horizontally
scale
out
pinata
more
and
a
lot
of
our
users
had
been
asking
for
more
of
options
for
speed
redundancy.
You
know
how
do
I
get
my
contents
in
multiple
parts
of
the
world.
F
So
basically,
what
this
allows
you
to
do
is
in
your
content,
multiple
times
in
multiple
regions,
the
simple
way
to
do
it.
This
is
on
the
test
server
by
the
way,
as
so
many
accounts
information
is
fake.
Okay,
so
no
don't
turn
scam
our
main
servers,
but
it
comes
down
to
this
thing.
We
call
a
pin
policy
and
right
now
we're
letting
users
panic
content
in
both
Germany
and
then
New
York
City.
F
This
is
kind
of
what
your
account
settings
will
be
by
default,
and
you
say:
hey
I,
wanted
pin
once
in
Frankfurt
and
once
in
New,
York,
City
or
I
can
set
it
up
to
twice
in
New
York
City,
as
maybe
I,
have
a
lot
more
users
there
that
are
touching
data,
so
you
can
set
that
as
your
default
account
level
one
now.
You
can
also
send
in
custom
and
policy
for
a
unique
upload
via
the
API.
F
If
you
want
to
as
well
so,
let's
say
like
we
want
to
upload
a
file
here,
we'll
set
it
up
there
and
then
you'll
notice.
Here
it
kinda
it'll,
take
you
can
look
at
your
PIN
list
and
say
hey.
F
But
if
we
update
it,
we
should
notice
that
it
replicated
all
behind
the
scenes
using
swap
and
all
the
fun
stuff
we
have
all
these
multi
microserver
see
things
going
on,
but
yeah,
that's
let's
say
we
changed
our
minds.
Now
we
wanted
zero
times
in
New.
York
City
turns
out
nobody
lives
there.
We
can
do
that
and
now
it's
still
in
Frankfurt,
it's
been
deleted
off
the
New
York
City
servers.
A
F
Yeah
yeah
yep
yep,
so
so
we
have
like
all
of
our
all
of
our
data
by
default.
You
know,
is
a
racial
coded,
like
multi
server
racks
setup,
so
the
data
is
not
going
to
die,
but
we
wanted
to
give
people
the
ability
to
say:
okay,
I
want
multiple
nodes,
announcing
this
contents
in
specific
regions,
so
it
kind
of
gives
you
the
ability
to
fine-tune
your
CDN.
F
If
you
will
so
each
each
replication,
that's
gonna,
be
you
know
a
node,
so
this
one
would
have
three
different
nodes,
one
in
New,
York,
City
and
then
two
and
Frankfurt
announcing
the
content
and
then,
if
people
want
to
as
well,
we
can
also
set
up
custom
regions
for
them.
So
then
in
then
give
their
accounts
permission
to
it.
So
let's
say
that
you're
from
India
we
could
set
up
one
kind
of
an
Eastern
Asian
or
like
Bangladesh,
and
then
you
know
that
would
give
your
account
access
to
that
and
then
you
would
have.
F
F
Yeah
yeah,
it's
specially
wherever
you
want
and
the
cool
thing
what
we
can
do
with
this
now
is
we
can
do
private
networking
if
you
want,
we
can
do
cross
clouds.
So
let's
say
you
want
a
one
in
GCP.
You
won't
want
to
have
your
AWS
digitalocean.
You
can
run.
You
know
four
different
cloud
providers
if
he
wants
and
we
can
set
that
up
for
you,
so
that
your
data
is
pretty
much
never
going
to
be
taken
offline.
F
A
You
know
because
Hector
being
the
cluster
lead
has
been
yes,
yes,
yes,
first
or
ma'am
yeah
cool
all
right.
Thank
you
very
much
Matt.
That
was
awesome.
That's
really
cool
good
news,
and
sometimes,
if
you'd
like
to
stop
sharing
absolutely
okay.
So
next
up
we
have
Dietrich
and
he's
gonna
talk
to
us
a
little
bit
about
air.
If
Denver.
C
Everybody
ace
something
from
someone
about
someone
who
looks
familiar
about.
C
So
I
what
seems
like
several
years
ago
in
a
planet
far
far
away,
there
was
actually
a
very
large
a
3m
Developers
Conference
in
Colorado
in
Denver.
Before
that
conference,
however,
was
a
pretty
amazing
event
called
the
distance
wise
networks
in
it.
This
was
basically
a
I
profess
and
friends
and
interested
parties
day.
A
bunch
of
people
were
building
stuff
on
top
of
IP
fess,
doing
talks
about
decentralized
networks
using
it
building,
ipfs
and
kind
of
showing
off
to
the
community
there.
C
Thank
you.
The
main
event
was
the
next
few
days
viii,
denver
f-number.
However,
you
dip
it
if
you're
from
the
UK.
How
do
you
pronounce
it?
This
is
over
2000
people
building
things
on
top
of
the
etherium
stack
a
lot
of
people
using
IP,
FS
I.
We
had
a
table
there
with
the
IP
fest
open
source
project
represented
well
by
textile
three-box
and
bunch
of
other
projects.
People
hanging
out
for
a
few
days
asked
answering
questions,
hundreds
and
hundreds
of
people
coming
by
this
table,
and
it
was
very
interesting
to
see
division
of
people's
reaction.
C
But
we
love
you.
Thank
you
so
much
O'keefe
s
build
everyone's
building
on
top
of
you
and
the
other
half
for
people
who
pretty
much
never
really
been
to
before
I
walked
up
to
the
table
and
said
what
what's
the
piece?
Could
you
tell
me
where
about
this?
So
it's
very
very
interesting
to
see
new
people
coming
into
the
space
and
then
people
very
mature
people,
building
mature,
more
mature
solutions.
C
On
top
of
this
still
nascent
early
early
times
in
the
stack
and
and
really
a
lot
of
support
from
from
the
folks
that
are
building
on
us,
you
can
see
the
buffa
corn,
the
official
mascot
event
in
full
three
chlorines
there.
It
was
really
really
amazing
venue
as
well
the
sports
castle.
You
ever
get
a
chance
to
go
there
very
nice,
please
there
is
a
hackathon
main
event
of
the
f-number
conference
and
wouldn't
one
of
the
most
important
and
really
just
fantastic
parts
for
our
community.
C
So
thanks
really
a
lot
to
to
pinata
and
textile
and
all
the
other
folks
who
who
showed
up
and
invested
their
time
and
their
effort
and
conversations
with
all
these
random
folks
and
people
who
are
part
of
the
community
in
supporting
them
and
in
building
their
web.
Three
top
three
solutions
and
applications.
On
top
of
my
PFS
thanks.
C
That's
a
good
question.
We
actually
did
get
poke
from
where
the
folks
in
the
brave
community
who
is
organizing
an
event
just
like
that,
basically
I
think
several
days
of
trainings
workshops
and
talks
around
distributed
networking
so
not
specific
to
aetherium
this
one
I'm,
not
sure
about
in
the
ertharin
community.
There
might
be
more
events
like
that,
but
we'll
definitely
be
sharing
news
about
those
people
working
on
strand,
decentralized
networks
for
sure
and
I
think
so
far.
That's
including
people
from
ipfs
folks
from
that
community
scuttlebutt
community.
A
A
A
A
Well,
you
can
now.
This
is
the
interplanetary
file
system
browser
and
it's
a
peer-to-peer
web
browser,
it's
kind
of
like
Beeker
browser,
if
you've
heard
of
that,
but
for
ipfs.
If
you've
not
heard
of
bigger
browser,
you
should
check
it
out
because
it
is
a
browser
that
works
with
that
and
it's
doing
a
similar
sort
of
thing
I
mean.
A
A
If
we
want
to
consider
ipfs
resources
in
the
secure
context,
then
we
can
array
and
if
we
want
to,
if
we
want
our
web
extensions
to
have
access
to
low-level
tcp,
UDP
or
mdns
api's,
then
we
can-
and
we
can
also
allow
every
website
that
that
we
visit
to
have
access
to
our
IP
FS.
No
that's
running
in
the
browser
hooray.
So
anyway,
you
get
a
picture
alright
enough
talking.
So
what
is
this?
This
is
so
like.
A
My
slides
are
actually
showing
in
this
browser
that
I'm
talking
about,
which
is
super
cool.
There's
got
tabs
and
not
there's
not
a
lot
of
stuff
here.
Basically,
but
you
can
do
you
can
navigate
to
things
like
you
do
in
a
normal
browser,
because
it's
over
Elsa,
you
know
what
to
do,
but
you
can
also
look
at
ipfs
resources.
So
I've
got
a
CID
hast.
A
Whoa,
it's
our
favorite
image.
Okay,
its
lightest,
favorite
image
looks
like
kind
of
partial
to
it.
I've
grown
to
love
it
now,
like
you,
can
look
like
this
Guardian,
so
slightly
freaky,
but
look
it's
an
IPS
and
beauty,
but
what's
also
kind
of
way
better
is
if
the
ipfs
resources
are
actually
like
web
pages.
So
you
can
like
look
at
the
octopus
blog
by
that
and
like
with
never
getting
around
ipfs
resources
in
the
browser
hooray.
A
So
that's
that's
pretty
awesome
completely
natively,
so
you
can
even
do
like
sea
ball.
Encoded.
C
A
Okay
put
that
here
again
and
then
I
should
just
be
able
to
paste
this
into
here.
Hey,
and
it
comes
up.
Alright,
that's
great
but
like
what's
even
more
interesting
is
if
I
do
something
like
ooh,
okay
bear
with
me
here.
So,
if
I
have
like
a
link
to
some
to
that
that
thing,
I
can
do
something
like
this.
A
A
Put
it
in
I
give
s
hooray.
We
got
a
new
CI
D.
Let's
have
a
look
get
that
one.
So
I
should
be
able
to
pair
less
there's
even
a
different
time
than
that.
Doesn't
matter,
hey,
there's
our
data
and
it's
got
a
link
in
it
which
I'm
certain
I
can
just
you
know,
look
at
that
data
like
like
that,
but
if
I
just
put
in
slash
link
here,
I
should
also
be
able
to
access
it
through
the
magic
of
IP
OD
and
linking
and
I
should
also
be
able
to
secure
data.
A
So
just
get
the
data
out
so
hooray
for
that.
That
is
the
ipfs
browser,
sandbox
for
experimentation
and
fun
times
and
the
possibilities
of
what
you
could
do
in
a
p2p
browser
and
that's
about
all
I
have
to
say:
let's
stop
the
share.
Okay,
any
quick
questions
we're
over
time
now,
I'm.
Sorry,
it's
a
complete
one.
That's.
E
E
A
So
it's
it's
just
electron
under
the
hood,
so
if
I
can
keep
electron
up-to-date,
then
they're
doing
that
for
me,
basically,
whatever
gets
broken
or
changed
by
the
bike.
Rome
is
kind
of
up
for
grabs,
but
like
the
electron
API
is
meant
to
be
reasonably
stable,
so
hopefully
not
too
much.
I
must
stress
that
you
know.
A
A
All
right,
if
there's
no
more
questions,
then
thank
you
very
much.
Everyone
for
coming,
it's
been,
it's
been
really
fun
and
I
obviously
enjoyed
it.
Lots
Lionel,
thank
you
for
taking
notes,
and
we
will
see
you
next
well
next
week
for
a
new
for
a
new
ipfs
weekly
cool.
It
went
lightly
talks,
but
would
do
nightly
talks
again
soon,
but
thank
you
again
for
coming
and
have
a
nice
rest
of
your
day.