►
From YouTube: [Swarm Mini Summit] Building Unstoppable Chat
Description
Doug Leonard - Mainframe
The Mainframe team has leveraged Swarm mutable resources to provide fully decentralized, unstoppable mailboxing functionality. This will be demonstrated in an example chat dApp. This talk will walk you through our experience going from conception to implementation, describing briefly how swarm feeds work and how we applied them to the needs of our messaging dApp.
Biography - Doug Leonard
Doug breeds cryptokitties, loves blockchain tech, entrepreneurship and software engineering. He has been working as a full-stack engineer for over five years, with experience in mobile development, distributed systems and information security. Doug runs a podcast with his wife that focuses on married entrepreneurs. He has a Masters in Information Systems from Brigham Young University.
A
Doug
really
loves
to
breed
Krypto
kitties,
and
he
thinks
that
the
main
value
proposition
of
swarm
is
that
it's
going
to
make
crypto
kitties
unstoppable,
so
Doug
also
recently
had
a
second
child.
So
he
has
a
slide
of
that,
and
Doug
is
actually
one
of
my
favorite
employees
that
mainframe
and
in
fact,
I
like
to
think
that
Doug
embodies
all
of
the
core
values
of
mainframe.
A
A
So
that's
a
little
bit
about
Doug.
So
today,
I'm
gonna
present
to
you
some
of
the
work
that
Doug
did
and
quite
honestly,
I
think
he
deserves
a
substantial
raise
after
his
work
and
and
so
we
were,
we
meaning
exclusively
Doug,
set
out
to
build
a
reference
DAP
on
top
of
swarm
feeds,
so
unstoppable
in
this
context,
really
to
Doug
means
that
it's
sufficiently
difficult
to
stop
such
that
restricting
access
effectively
means
removing
access
to
an
open
Internet.
A
So
just
to
get
our
vernacular
clear,
that's
what
unstoppable
means
in
this
context,
so
Doug
wanted
me
to
let
you
know
that
the
code
that
I'm
going
to
demo
on
his
behalf
is
open
source,
it's
free
and
open
for
anyone
to
build
on
top
of
and
was
written
during
a
bout
of
food
poisoning.
And
so,
if
you
get
into
the
code
and
things
look
a
little
off
things
were
off.
A
A
So
you've
got
your
hello
world,
your
hello
world
website
and,
typically
what
you
do
you
would
upload
it
to
swarm,
and
that
would
be
your
first
update
and
then
you
come
along
and
you
don't
have
slides
that
correlate
to
what
you're
actually
communicating
and
you
have
your
updates
and
over
periods
of
time
you
have
those
updates
map
to
the
new
content
and
you're
pushing
up
this
whole
new
document
every
time
and
most
people
are
just
going
to
consume.
This
last
instance
of
your
of
your
document
so.
A
Now,
let's
now
Doug
took
this
paradigm
and
he
decided
to
turn
it
on
its
head,
and
so
let's
take
time
and
make
it
vertical
and
let's
think
about
what,
if
we
instead,
since
I,
can
access
any
of
those
previous
versions
of
my
swarm
feed.
What?
If
each
instance
of
the
document
was
entirely
distinct
and
unique
and
represented
an
event
rather
than
an
update
of
the
entire
document.
So
you
would
start
with
you
know
and
chat.
A
We
would
create
like
a
channel
structure
and
and
then
you
would
create
a
user
feed
and
then
you
would
want
to
update
the
channel
structure
to
reference
the
user
fee.
This
is
analogous
to
adding
someone
to
a
channel
and
slack,
and
then
you
would
want
a
second
user,
so
you're
not
just
talking
to
yourself
and
then
you
would
want
to
reference
that
second
user
from
the
channel.
So
this
is
the
architecture
and
then
people
can
then
converse
with
each
other
and
then
a
client
would
use
the
time
stance
to.
A
Interpolate,
all
of
these
events
into
time
series
data
such
that
it's
a
normal
chat
client.
So
this
is
a
Doug's
initial
idea,
and
so
you
set
out
to
build
it
and
so,
along
with
one
of
his
colleagues
Paul,
they
defined
a
swarm
feed
chat
protocol
trade
Mike.
So
this
is
what
the
metadata
so
you've
got.
Your
typical
you
know
definition
and
then
the
type
of
message
it's
going
to
be
any
extensions
that
you're
gonna
have
the
timestamp,
which
is
super
important
for
clients
and
then
a
pointer
to
the
previous
event,
and
then
your
payload.
A
So
this
is
this:
is
the
type
of
structure
you're
going
to
have
in
every
single
event,
regardless
of
its
type?
So
then
we
have
our
channel
that
I
described
earlier,
and
the
important
part
here
is
both
the
name
of
the
channel
and
the
identities
that
you're
using
and
again
an
identity
is
just
going
to
be
a
pointer
to
user
feed.
And
then
this
is
what
the
event
that
is.
A
message
looks
like.
So
this
is
what
users
end
up
posting
to
their
users,
stream
and
and
and
really
the
only
parts
to
highlight
again.
A
Are
that
important
time
stamp
for
clients
and
then
the
payload
and
then
optionally?
We
were
very
forward-thinking
and
thought
you
know.
Maybe
people
are
going
to
want
to
use
markup,
and
so
we
have
accounted
for
an
extensions
array
that
that
enables
you
to
arbitrarily
add
features
on
top
of
what
I'm
going
to
present
to
you
so
just
to
walk
through
it,
one
more
time
before
I'm
going
to
actually
demo
it.
A
So
this
is
for
clients
to
be
able
to
deterministically
know
where
to
look
for
messages
that
are
intended
to
be
consumed
in
the
same
theme,
and
so
then
you're
gonna
have
to
update
your
channel
and
actually
add
that
first
user,
and
then
you
do
the
same
thing
with
your
second
user
and
update
your
channel
again.
So
now
we
are
ready
to
chat
and
you
have
your
events
for
chit
chat.
Ok,
so
you
get
the
basic
gist
of
the
architecture,
it's
time
to
sacrifice
something
important
to
our
demo
gods.
A
A
A
A
I
I
wanted
to
make
sure
I
have
reference
to
all
the
data
before
I
hit
submit
and
then
here
I'm
going
to
paste
in
the
owner
of
the
channel.
That's
about
to
be
created
public
key,
because
I
need
that
information
to
be
able
to
find
where
this
information,
where
the
feed
is
going
to
be
pasted.
So
I've
set
a
default.
A
A
There
we
go
all
right
and
then
we
will
send
it
on
up
and
hopefully,
in
ten
or
20
seconds,
an
average
of
15
seconds.
You
will
see
an
update
appear
on
this
screen.
Next,
we
will
submit
over
here
which
is
going
to
create
this
user
feed,
and
then
it
gives
me
this
user
feed
swarm
manifest
pass
and
I
will
come
over
to
this
window
and
paste
in
to
have
the
owner
of
the
channel.
Now
add
this
user
and
so
I
will
hit.
Add
Hey
look
hello
world.
A
A
Send
that
and
we
are
off
and
chatting
in
a
very
not
so
real-time
way
this
is
this
is
analogous
to
using
your
Gmail
for
instant
messaging
type
use
cases,
but
I
think
I,
think
that
demonstrates
everything
of
this
form
chat
demo
so
well.
This
is
the
beginning.
It's
built
directly
on
top
of
swarm
feeds.
A
A
A
So
Erebos
is
the
client,
the
client
library
Erebos,
is
the
client
library
that
we
at
mainframe
are
working
on
building
and
its
goal
is
to
make
it
easy
to
consume
all
of
the
swarm
things.
So
we
have
intentions
to
here's.
Here's
a
screen
shot
of
the
website.
Err
boast
je
s,
dot
org
did
I,
get
it
yeah
I'm
the
CTO.
What's
up
so
you
go
to
this
website,
we've
got
beautiful
documentation
and
you
can
do
many
things
except
not
yet
swarm
feeds,
and
so
we
will
be
continuing
to
update
this.
A
As
far
as
I'm
aware
it's
one
of
the
most
up-to-date
swarm,
JavaScript
client
libraries.
We
happily
accept
pull,
requests
and
collaboration
on
this
and
so
make
yourself
familiar
with
this
tool
if
you're
building
on
top
of
swarm,
because
it
is
a
beautiful
piece
of
work
so
that
that's
all
for
me
any
questions.