►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
how
are
we
doing?
Yes,
that's
what
we
want
to
hear?
Okay,
so
my
name
is
Jonathan
I'm,
a
member
of
the
pure
ghost
team
and
I've
got
five
minutes
to
talk
to
you
about
pure
ghosts.
I
tell
you
what
it
is
its
features
and
how
we're
using
ipfs
to
make
the
dream
come
true.
So
yeah
five
minutes,
one
chance
all
right,
let's
go
so
what
is
pure
ghosts
peer
ghost
is
it's
an
end-to-end
encrypted
peer-to-peer
file,
storage
sharing
and
communication
network,
and
we
have
some
very
particular
things
that
we
want
from
this
network.
A
So
in
particular
we
want
it
to
be
resilient.
So
what
do
I
mean
by
that
I
mean
that
it
should
be
generally
very
difficult
to
disrupt
or
surveil.
We
also
want
it
to
be
independent,
so
we
don't
want
to
have
to
rely
on
any
centralized
trust
architecture
such
as
TLS
CAS
or
the
domain
name
system.
We
also
want
it
to
be
super
secure,
so
we
want
our
users
to
be
able
to
share
files
with
each
other
and
communicate
with
each
other
without
any
metadata
being
generated.
And
finally,
we
want
it
to
be
self
hosted.
A
Anyone
should
be
able
to
download
a
binary
or
clone
the
code
and
assemble
it.
Stick
it
on
a
machine
and
then
get
their
own
social
network
and
communications
communications
platform
happening
as
well.
So
why
should
you
care
about
this
with
all
the
alternatives
that
are
out
there?
They
can
do
things
kind
of
like
this.
Why
should
you
care
about
pure
ghosts?
Well,
number,
one
security,
so
we
offer
safe,
login,
strong
crypto.
In
fact,
if
you're,
just
using
it
for
file
storage,
we're
post
quantum
resistant,
we
hide
all
the
metadata.
A
So
you
can't
see
things
like
file,
size
or
directory
structure
and
again
we're
free
of
any
centralized
trust
architecture
as
well.
So
we
also
give
you
control.
So,
as
I
mentioned,
we
want
it
to
be
self,
hosted
all,
and
we
let
you
do
that.
We
also
allow
you
to
have
very,
very
fine
control
over
who
sees
watch
when
you
share.
We
hide
all
your
contacts,
no
other
users,
and
certainly
our
peer
ghost
server,
can't
see
who
you're,
who
your
contacts
are
in
what
you're
doing
and
we
allow
you
to
remain
pseudonymous.
A
So
by
that
I
mean
we
don't
need
a
phone
number
or
an
email
address
in
order
for
you
to
sign
up
and
use
our
app,
we
really
want
peer
goes
to
be
convenient.
It
should
be
in
our
minds.
It
should
be
as
convenient
as
Dropbox
or
Facebook.
So
we
have
a
web
interface.
We
allow
you
to
log
in
from
any
device.
We
allow
file,
syncing
and,
of
course,
publishing
so
even
within
the
network
and
to
people
outside
of
the
network
as
well.
A
So
we
provide
you
with
the
ability
to
create
public
links
to
so
the
organizers
were
very
explicit
that
we
shouldn't
do
a
live
demo,
so
instead,
what
I'm
going
to
do
is
I'm
going
to
flesh
up
the
URL
to
the
alpha,
so
please
either
write
it
down.
Take
a
photo
point.
Your
brows
brows
read
it
now
and
please
try
it
out
for
yourself.
I'll
leave
that
up
there
for
like
five
more
seconds
and
let's
go
okay.
So
what
does
ipfs
got
to
do
with
all
of
this?
A
Well,
ipfs
is
really
the
backbone
of
peer
goes
so
we're
using
IP
FS
to
store
and
share
our
encrypted
content.
So
ipfs
is
really
a
logical
choice
for
this,
because
we
get
availability
because
it's
distributed,
we
would
get.
The
distribution
also
implies
resiliency
and
control,
and
that's
just
all
part
of
the
package
and
the
fact
that
it's
decentralized
means
that
there's
no
dns
there's
no
centralized
authority
or
a
single
point
of
attack
that
a
malicious
actor
could
go
after
either.
So
this
really
just
fits
the
bill
very
nicely
for
us.
A
So
what
does
peer
cross
actually
do?
Well?
Peer
ghost
is
just
an
encryption
and
access
control
layer
built
on
top
of
IP
FS.
So
we
have
the
peer
ghost
client,
which
talks
to
the
peer
ghost
server.
The
peer
ghost
server
really
just
manages
follow,
requests
and
immutable
pointers
to
the
clients,
data
we're
using
IP
FS,
it's
a
if
you
don't
know
by
now.
A
It's
a
content
to
the
risk
file
store,
so
that
gives
those
hashes
to
the
data
we're
using
our
own
equivalent
of
IP
n
s
to
point
public
keys
to
those
hashes
and,
of
course
our
PKI
server
main
manages
all
our
public
keys
for
our
users
and
in
fact
that,
but
that's
an
IPSS
as
well.
So
how
does
your
data
actually
get
into
there?
A
So
what
the
client
does
is
the
client
will
take
a
raw
file
chunk
that
up
into
five
megabyte
junks,
we
encrypt
all
those
independently
they're,
then
split
up
into
fragments
up
to
40
fragments
of
120
kilobyte
kilobytes
each,
and
that
is
what
gets
uploaded
to
ipfs
along
with
encrypted
metadata
and
the
fragmented
hashes
as
well.
So
I
hope
you
find
that
interesting
and
if
you
are
interested
by
all
means,
please
sign
up
to
the
alpha.
Try
it
out
come
talk
to
us.
A
Tell
us
what
you
like
tell
us,
you
don't
like
tell
ask
us
how
it
works.
You
know
crib,
whatever
you
want
from
it.
You
know,
I
think
these
things
get
better
when
people
complain
and
talk.
So
that's
really
what
we
want.
You
can
check
out
our
github
repo.
You
can
check
out
our
book
we're
on
Twitter
we're
on
reddit
as
well.
Pure
ghost
is
made
with
love
and
effort
and
healthy
distrust
of
the
alternatives
that
are
out
there
and
a
desire
to
make
a
real
alternative.