►
Description
Originally recorded during the Berlin Developers Meetings from July 9-13, 2018.
A
Hi
everybody
so
we're
gonna,
look
at
private
networks
between
go
and
DSi
BFS
and
then
I
will
do
a
best.
Three
data
store
demo,
so
we're
just
gonna
go
ahead
and
get
this
started.
So
what
I
have
set
up
are
a
first
I'm
gonna
run
a
public
version
of
this
and
then
I
will
run
the
actual
private
version,
and
so
this
is
going
to
be
a
Jas
and
a
go
node
talking
to
each
other.
So
first
one
public.
So
this
is
no
swarm
keys.
It'll
take
a
second
to
boot.
Up
then
they're
gonna
run.
A
So
what
we
can
see
here
at
the
beginning
of
the
traffic.
This
is
normal.
We
see
our
multi
stream
protocol
exchange
at
the
top
between
the
nodes
and
then
it
goes
into
our
sick,
IO,
encryption
negotiation
and
then
everything's
encrypted
after
that.
So
what
we
do
with
the
private
networks,
which
will
run
now
and
I'll
just
go
ahead
and
restart.
A
So
you
can
see,
there's
no
multi-stream,
you
don't
see
that
you
don't
see
the
sekai
Oh.
Everything
is
encrypted
after
a
24
bite,
nonce
exchange,
which
we
see
at
the
very
beginning.
Here's
our
length
of
24
bytes,
both
notes
are
gonna,
send
that
and
then
everything's
encrypted
I'm
gonna
run
the
Interop
tests
real
quick.
So
what
we
have
for
the
interrupt
ESTs
is:
we've
got
several
go
nodes.
A
A
So
we
CJ
s
2j
s
with
the
same
private
network.
Key
we
see
go
to
J
s
with
the
same
private
network.
Key.
What
they're
doing
is
they
are
we
put
data
into
one
of
the
nodes
and
then
we
pull
it
out
from
the
other
one.
So
go
we
put
data
into
go,
pull
it
out
with
gas
put
data
in
Jaspal
it
out
with
go,
that's
totally
working
and
when
stuff
isn't
supposed
to
talk
to
each
other,
they
don't
talk
to
each
other
yeah
they'll
past.
A
A
Okay,
so
now
moving
into
the
s3
datastore,
so
jess
has
s3
datastore
support
now
and
you
can
use
it
and
it's
live.
So
there
is
an
S
or
SP
datastore
repo
we're
just
going
to
run
this
right
now.
I
just
have
a
bucket
running
Jacob,
Hyun,
Germany
and
just
a
temp
folder,
because
you
know
data
permanence,
so
I'm,
just
gonna
run
this
on
full
debug
with
time
just
to
see.
So
what
this
is
doing?
You
see
an
error
here.
That's
not
a
real
error,
it's
because
it's
initializing
the
repo.
A
So
this
is
gonna,
take
a
little
bit
longer,
the
first
time
that
repos
initialized
and
then
I'm
just
uploading
like
25
random
kilobytes
of
data,
nothing
super
huge,
but
we
go
to
AZ
3
and
we
refresh-
and
we
have
it
nested
in
attempt
folder
in
our
ipfs
directory,
and
we
see
our
blocks.
Our
data
store
all
of
our
config
inversion.
If
I
run
this
again,
you
know
it
took
like
15
seconds
to
run
the
first
time.
That's
including
node,
boot
I'll
just
run
again.
We
do
the
upload.
A
A
A
So
a
lot
of
people
want
to
backup
information
and
put
it
on
s3
I'm
rather
than
having
it
all
locally,
and
so
this
is
a
great
usage
for
that.
So
you
can
just
stick
it
off
there
and
you
can
split
how
you
want
it
to.
If
you
want
your
keys
or
your
data
store
locally,
you
can
specify
where
and
what
you
want
up
there
so,
and
we
also
support
custom
locks
now
in
datastore,
because
that
was
one
of
the
things
we
needed
for
s3
to
work
properly.
So.