►
From YouTube: Jul 17 - IPFS all hands call 🙌🏽
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
Okay,
sorry,
all
right:
this
is
the
ipfs
All
Hands
call
for
July
17th
2017
and
the
agenda
is
up
in
github.
So
and
Hector
is
the
note-taker
and
I'm
Matt
Zumwalt
from
protocol
that
we
have
actually
a
lot
of
new
people
should
and
and
not
a
lot
of
agenda
item.
Should
we
do
a
roll
call,
yeah
good,
yeah,
all.
A
A
B
Right
hoisted
by
my
own
petard,
my
name
is
Michelle
Wie
I'm
part
of
the
protocol
labs
team
focusing
on
product
across
a
few
of
our
different
projects
with
regard
to
ipfs.
The
thing
that
is
capturing
my
attention
right
now
is
how
we
moved
from
a
world
where
we
have
a
lot
of
really
interesting
and
fantastic
pilot
use
cases
to
getting
deeper
into
the
stack
of
organizations
and
becoming
part
of
more
organization
with
critical
infrastructure
and
accordingly,
what
what
what
features
are
capabilities.
We
need
to
build
to
make
that
attractive
and
possible.
E
F
Going
yeah
I'm
in
Seattle
I
think
I
have
North
you
for
a
moment
so
come
on
this
here.
So
I
work
on
if
your
name
stuff,
specifically
meta
mask,
which
is
an
account
manager
under
consensus
and
what
has
been
keeping
me
up,
is
trying
to
build
a
a
like
client
off
of
Nigeria.
My
client
off
of
I'd
be
awesome
would
be
to
be,
and
I'll
be
demoing
that
later
today,.
G
G
Did
an
analysis
of
the
family
breaks
the
other
day
for
a
talk
and
Amazon,
like
all
the
big
cloud
providers,
they'll
charge
the
same
rates
for
bandwidth
that
they
are
charging
in
2007
and
eight
other
those
kind
of
interesting
they're
exactly
ten
years
behind
on
that,
the
current
price
is
banned
within
my
IP
transit
freighters
itself
obviously
have
to
give
us
look
great
way
to
not
have
to
pay
them
to
place
like
that.
So
it's
kind
of
my.
H
E
So
I
guess
I
get
my
turn
so
hi
everyone
into
being
local
Peugeot
labs
and
mostly
focused
on
deaf
activists,
and
we
should
appear-
and
there
are
many
things
that
are
keeping
me
awake
at
night.
But
I
guess,
like
picking
one
I've
been
very
excited
to
push
a
bunch
of
tutorials
and
demos,
using
repute,
appearances
ipfs,
enabling
more
developers
to
like
get
into
the
distributed
world
and
I
keeping
more
apps.
You
might
have
seen
a
lot
of
tweets
recently,
really
appreciate
all
the
feedback
and
support
and
yet
really
kind
about
feeling
more
people.
A
I
A
zip
code
see
yes,
okay
and
I'm.
Sure
many
workers,
new
stars
and
collaborated
with
tamales
on
deploying
the
light
guide
on
top
of
ipfs,
and
what
keeps
you
awake
is
understanding.
How
to
deploy.
Everything
in
a
centralized
network
have
to
try
to
do
that
first
week
as
a
and
then
with
Wikipedia,
which
extend
the
word.
J
I'm
David
I'm
in
Colorados
I
think
I'm
next
I
go
to
Colorado
School
of
Mines
during
my
master's
research
on
bit
swap
and
incentives,
and
things
like
that
and
working
on
at
the
fs
cluster.
Also
and
I
guess.
The
main
thing
I've
been
thinking
about
a
lot
is,
is
implementing
you
know:
incentive
site
mechanisms
that
don't
involve
currencies
in
such
a
decentralized
system
and
not
like
messing
anything
up
in
that
process
of
actually
analyzing
the
real-world
situation
versus
like
the
theoretical
math
side
with.
D
D
It's
just
amazing
and
we're
working
on
a
variety
of
things
with
a
group
here
in
Phoenix
and
we're
working
with
JSI
PF
fests,
we're
working
on
some
interesting
ways
to
maybe
incorporate
the
Internet
of
Things
with
the
ipfs
constructive
protocol
so
forth,
and
we're
also
working
on
some
ways
to
possibly
bridge
and
harmonize
the
old,
with
the
new
in
terms
of
naming
and
addressing
numbering
and
identity.
So
it's
like
a
fire
hose
right
now,
I
think
Jason's
on
the
call
as
well
Jason.
You
want
to
introduce
y'all
I'll.
A
A
Okay,
welcome
anyone
else
in
the
in
sort
of
midwest
ish
areas
all
right.
Well
then,
that
gets
towards
me-
and
I
am
anyone
in
like
you're
sort
of
Boston
New
York,
Strip,
Canada,
Newfoundland,
okay,
I,
so
I'm
I'm
north
of
Michelle,
by
five
minutes
like
ride
so
I'm
NAT
Zumwalt
with
protocol
labs.
What
is
keeping
me
up
is
that
we
will
be
soft
launching
a
website
for
data
together,
org
sometime
this
week
and
I'm
excited
about
it,
but
it
also
has
not
gotten
as
always
gotten.
A
And
another
thing
is
not
keeping
me
awake,
but
I've
been
thinking
about
a
lot
is
that
that
I
didn't
realize
that
there's
been
this
whole
rebranding
of
cloud
services
as
being
server,
and
so
our
use
of
the
term
serverless
is
getting
confused
by
people
who
are
actually
just
selling
cloud
services
and
I'm.
Not
quite
sure
how
I
want
to
like
how
I
want
to
work
with
that,
but
it's
annoying
so
to
be
continued.
Oh
and
Michelle
already
went
so
then
anyone
else
on
this
sort
of
East
Coast
strip,
all
right.
M
And
so
would
your
honor
I'll
go
first
I'm
Matt
Kelly
I'm,
a
PhD
student
Old,
Dominion
University
I
am
currently
working
on
interplanetary
way
back,
which
shouldn't
I
developed
in
we
demoed
at
IIPC
back
in
June
and
we're
kind
of
following
that
to
be
a
little
more
production
worthy
and
big
as
a
test
and
that
kind
of
stuff.
So
we'll
be
demoing
that
today,
as
well.
N
I'm
so
dalam
I'm,
also
from
Old
Dominion
University
of
sitting
next
to
Matt
right
now
and
always
in
the
office,
so
I'll
be
last
year
in
March
we
were
in
a
hackathon
where
we
were
running
out
of
ideas.
What
to
work
on,
and
then
this
ipfs
thing
was
like
hitting
in
my
head
for
long
time.
So
I
thought
hey,
let's
bring
it
to
the
archiving
community
and
we
implemented
an
archival
replay
system
they're
using
at
DFS,
and
we
call
it
our
TV
back.
N
A
O
I
think
maybe
David
already
once
yeah,
okay,
so
I'm
next
I
usually
live
in
in
Barcelona.
Today,
I'm
in
a
Lee
campus
or
with
other
Wes
I
guess
my
name
is
Victor.
I
worked
for
the
collapse
as
well,
mostly
with
JavaScript
things,
some
things
with
the
infrastructure
and
other
stuff
I
think
same
as
many
others.
O
I
have
a
lot
of
things,
keep
me
awake
but,
most
importantly,
the
applications
that
you
are
able
to
build
on
top
of
white
papers
and
being
able
to
have
offline
apps
that
works
together
with
different
kind
of
networks,
and
we
don't
have
to
be
connected
to
the
backbone
itself,
so,
basically
removing
ourselves
from
this
centralized
look
stuff.
Everything
is
quite
pointy.
P
I'll
go
legs,
though:
let's
go
through
the
Mediterranean
with
the
south,
south
south,
so
I'm
Vito
I
mean
30
degrees
and
chemical
backing
for
the
robot
and
well
the
things
that
took
me
neither
portable
Network
protocols.
So
how
do
we
feed
this
book?
Addresses
Plato's?
So
that's
some
words
on
relay
now
and
we're
also
things
like
but
stop
it.
These
are
my
interest
of
this
point.
Q
We
do
Berlin
yeah
bus
to
Berlin,
okay,
some
hectare
for
with
critical
Lots
I
live
in
West
Berlin
and
what
keeps
me
up-
I
work,
mostly
on
ipfs
cluster
and
I,
haven't
been
able
to
put
much
time
into
it
lately,
but
I
have
good
news
is
that
a
new
release
will
be
coming
very
soon.
It
has
a
couple
of
features
and
then
it's
coming
really
close
to
to
a
point
where
it
is
mature
enough
that
you
can
just
use
it
to.
Q
C
Okay,
like
awesome,
I'm
excited
for
that,
my
name
is
Lars.
I
live
in
West,
Berlin
and
I've
recently
had
my
second
anniversary
of
contributing
cat
success,
and,
what's
keeping
me
up
at
night,
is
similar
to
how
a
BFS
is
starting
to
eat
up
the
web.
One
data
set
at
a
time
I,
want
to
see
the
peer
to
peer
eat
the
backbone
of
the
internet,
one
network
at
a
time,
and
so
that's
what
I'm
thinking
about
a
lot
and
there's
going
to
be
some
some
exciting
work
on
that
in
the
second
half
of
the
year.
R
A
A
F
A
A
We
have
two
exciting
demos
and
we
have
plenty
of
time
for
both.
So,
let's
let's
say
go
for
it
on
ten
minutes
and
we
can
even
have
some
time
for
discussion
in
Afrikaans
law
and
then
we
have
a
net
with
the
interplanetary
way
back,
also
being
presented
after
you.
So
two
exciting
demos,
great
take
it
away:
control
yeah.
F
O
F
F
A
little
sort
of
demo
app
where
I've
been
throwing
in
my
latest
experiment.
So
it's
not
not
too
pretty
but
works
for
me.
So
first
thing
I'm
going
to
look
at
the
peers.
We
have.
We
have
some
some
bridge
nodes
for
a
cerium
and
making
the
Xperia
available
on
the
high
DFS.
So
he's
a
mystic
Allah
knows
that
that
Herman
has
helped
set
up
in
various
places
around
the
world.
So
yeah
he's
he's
a
experimenting
with
it
for
the
DevOps
side
of
helping
feed
some
of
this
information
and
there's
so
so.
F
My
goal
here
is
to
to
make
a
a
light
client
for
a
syrian
that
works
over
ipfs,
the
pupae
and
the
main
reason
I
want
to
do.
That
is
to
make
it
to
make
it
work
in
the
browser.
The
etherium
network
is
mostly
TCP,
UDP
based,
and
so
that's
not
something
that
I've
been
able
to
access
directly
from
the
browser
and
so
we're
seeing
if
we
can
sort
of
create
a
secondary
network
and
enrich
them.
F
F
Under
a
query,
lookup
I
started
coming
up
with
my
own
sort
of
like
query
path
specific
to
etherium,
because
if
you,
if
you
sort
of
dissected,
we're
going
inside
aetherium
we're
looking
at
the
latest
block
inside
of
that
we're
looking
at
the
state
and
we're
looking
at
the
state
of
this
particular
address
the
account
of
this
address
and
at
its
balance
and
when
you
translate
that
into
an
IP
LD
path.
It
is
this
less
legible
thing.
F
Here's
the
content
idea
of
the
latest
block
and
then
we're
going
into
its
state
and
then
here
is
like
the
hash
of
the
address
chunked
into
half
bytes,
which
is
how
the
the
state
tree
is
internally
represented.
And
then
we
pull
the
balance
options
via
belief,
which
is
source
the
account
and
so
I
can
go
ahead
and
perform
that
query.
I
can
already
tell
my
computer's
struggling
total
running
a
Tibetan.
F
F
F
Let's
see
if
this
one,
yet
since
we
can
cook
it
so
here
you
can
see
where
we're
starting
to
walk
down
the
state
tree.
We
restarted
at
the
block
we're
going
down
the
first
node
of
the
state
tree
and
we're
going
to
go.
Maybe
six
nodes
deep,
but
yeah
I
can
tell
already
that
it's
performing
a
bit
differently
than
it
does
normally,
it's
very
slow
to
move
from
one
block
to
the
next.
F
F
I
just
plugged
it
in
but
I,
don't
know
if
it's
going
to
affect
performance,
much
okay,
yeah!
Now
it's
that's
kicking
a
little
bit,
so
this
is
well.
This
is
a
work
for
me,
it's
definitely
very
slow
and
if
the
more
data
we
start
pulling
off
of
it,
it's
going
to
be
fun,
continue.
So
okay,
so
we
did
get
our
first
result
here.
F
F
First,
the
ether
is
this
person
who
has
some
near
7,000
ether,
so
my
nan
or
something
and
then
the
sort
of
my
latest,
where
it
was
getting
the
EBM,
via
aetherium
virtual
machine
to
run
based
on
these
hypotheticals.
So
this
one
is
even
it
makes
a
you
know
many
of
these,
these
for
a
lookups
and
so
may
be
quite
slow,
and
maybe
it
won't
finish,
but
we
can
lead
to
a
heavens.
F
So
it's
what
we're
doing
here
is
summons
created
this.
This
token
prognosis,
so
the
whole
idea
behind
etherium,
is
that
it's
a
platform
for
building
other
things
and
so
to
help
run
their
their
their
system,
which
is
a
predictor
market
to
good
topic
for
for
another
time
and
they've
created
this
token,
and
this
token
works
as
a
contract
on
top
of
a
theorem
and
it
records
the
balances
of
people
and
abstract.
F
You
know
lets
you
send
each
other,
and
so
here
we're
sort
of
sending
a
call
into
the
grand
virtual
machine
asking
it
what
its
balance
of
this
account
is,
and
in
order
to
do
that,
it's
going
to
load
the
code
of
the
contract
and
then
lace
and
look
up
the
storage
of
the
conflict,
and
so
when
first
open
it
runs
over
touching.
It
takes
maybe
20
seconds
to
process
the
request,
all
these
things.
F
H
A
S
C
E
I
One
of
the
big
fears-
the
blockchain-
is
already
200
gigabytes
of
weight.
We
believe
that
in
one
gauge
will
will
be
waving
like
three
four
terabytes.
So
one
of
the
beaches,
people,
the
serial
house,
is
to
especially
notes.
You
will
have
notes
for
mining
notes,
yes
from
story
at
notes,
yes
for
writing
perspective
relating
them
and
the
story
will
be
distributed
somehow
so
idea.
This
is
the
first
option
and
a
person
we
want
to
have
a
client.
I
E
Awesome
like
the
the
bit
that
was
going
to
say
real
integration,
so
right
now
the
way
that
come
others
with
this
demo
was
by
getting
different
effects
running
on
the
server
and
attaching
the
parity
equalization
of
it.
You
Liam
so
the
rest
of
evolution
over
here
iam
come
parity
as
a
data
store,
Jessie
peepers,
so
we
use
the
same
model,
but
we
have
Ingo
ipfs
and,
like
we
have
portable
other
source
and
right
now,
priorities
I
can
read
about.
E
We
don't
know
a
data
store
where,
like,
if
someone
searches
for
shaggy,
that
is
from
a
Nigerian
blog
like
it,
will
get
from
the
data
store
and
the
other
story
is
essentially
requesting
it
to
the
parity
client
to
an
HTTP
call
and
and
like
the
practical
ends,
will
get
a
block
and
give
it
to
us
kind
of
like
a
bridge.
It's
really
bridge.
We
can
do
the
same
for
go
ipfs
today,
you
don't
even
need
get.
I
E
I
A
A
I
E
A
Great,
thank
you
very
much
and
then
on
to
our
next.
Oh,
and
could
someone
also
add
those
links
into
the
hackpad,
because
the
chat
remember
well
I,
guess
anyone
know
anything
is
chat
like
the
chat
and
zoom
goes
away.
It
doesn't
stick
with
the
recording.
So
if
you
put
stuff
in
there
that
you
want
to
stay
for
the
long
term
make
sure
they
get
going
to
the
hackpad
as
well
all
right
on
to
our
next
demo
from
side
and
that
about
IP
WV
its
planetary
way
back.
Take
it
away.
A
M
Well,
I
guess:
I'll
get
started
on
this.
Let
me,
through
the
screen,
sharing.
M
M
Okay,
so
I
hiked
this
alright.
So
what
I'll
be
doing
here
is
a
demoing
IP
way
back
some
to
clean
machines
on
the
left
machine
I
have
my
local
one
download
it's
not
actually
on
here.
Yet,
as
you
can
see,
doesn't
exist
this
one
either
either
have
it.
So
this
machine
is
actually
a
remote
server
here.
So
what
I'm
going
to
do
is
I'll
just
pull
this
pull
the
source,
the
sake
of
simplistic
investment,
some
sample
data
there.
M
Alright
and
I
do
have
ipfs
on
here
already,
you
can
say.
Let
me
see,
do
that
and
then
install-
and
you
can
also
pull
this
from
from
pi
PI
as
well,
but
I've
got
some
sample
data
in
the
in
the
github
repo,
so
you
should
be
able
to
use
it
that
way
as
well.
So
alright,
so
from
this
just
show
the
directory,
you
can
run
a
few
different
commands.
M
The
way
the
IP
wayback
works
is
it's
got
an
indexer
that
creates
a
CD
xj
files
and
a
refi
system
that
reads:
oh,
you
can
do
it
in
a
crate
seat
in
creating
a
CH,
a
file
that
stores
the
IDF
ashes
in
there
allow
the
content
to
be
serviced
on
replay.
So
as
an
example,
I
do
I
pu8
I
pw
b
index
and
then
I've
got
like
a
sample
work
here.
It's
called
froggie.
I
can
see
the
output
here,
I
mean,
might
be
the
stuff,
a
demon,
maybe
yeah.
Ok,
so
go
steps
to.
M
M
Then
Plus
again
so
you
can
see
the
output
looks
something
like
this,
so
it
just
has
to
made
a
date
on
top
and
then
for
each
of
these
your
eyes
here
you
can
see
there
is
a
associated
IPS
Beth
hashes
for
this.
This
is
representative
the
HTTP
header
as
extracted
from
the
work-
and
this
is
the
payload
representative
of
this
base
URI
at
this
date
time,
and
so
the
source
is
just
there's
one
HTML
page,
which
I'll
show
you
here
so
anyway.
M
If
you
copy
this
over,
you
can
do
it
some
other
ways,
but
let
me
copy
this
over
to
this
other
machine
here,
which
I
don't
currently
have
IP
wave
economic
beliefs,
so
I'll
just
install
it
play
it
fit.
So
you
can
see
that
it
does
do
that
and
I
don't
think
demon
is
running.
So
let
me
throw
it
in
the
background
all
right
and
then
I
should
be
able
to
on
so
anyway.
M
Once
you
start
at
these
stuff
three
places
you
can
do
this
once
the
demon
is
running,
you
can
actually
hit
it
our
localhost,
as
you
can
see
here,
so
we
didn't
actually
pass
any
CD
XJ
data.
So
it's
not
aware
of
that
file.
Yep.
It
does
have
some
sample
data,
so
an
example
pulls
in
the
sample,
the
editing
to
say
this.
They
just
pull
from
ipfs,
which
is
based
on
these
hashes
here,
but
from
that
one
I
did
before.
M
M
M
You'll
start
that
up
and
locate
it
again,
you
see
there's
three
different
ones
here
in
a
has
different
offices
to
control
the
demon
where
that
stuff
that
we're
into
it
also
use
a
service
worker
on
here
to
do
the
rerouting
so
in
web
archives.
If
you
go
to
replay
the
page,
it'll
reach
out
to
the
live
web
to
try
to
grab
a
live
web
content,
if
you
don't
rewrite
the
link,
so
one
of
the
work
sets
so
it
actually
did
earlier
this
year
was
to
implement
a
service
worker
to
intercept
these
requests.
M
The
live
web
and
point
them
back
to
a
replay
system.
So
in
this
example,
compared
to
last
one
you'll
see
it
also
separates
it
out,
so
you
can
see
the
difference.
So
if
you
want
to
see
all
the
different
resources
that
are
in
it,
those
are
there
as
well.
We
can
see
so
this
resource
here
is
actually
being
pulled
from
the
local
replay
system,
and
if
you
pull
this
up,
you
can
see
the
service
worker
actually
intercept
this
thing
you
say
yeah.
Let
me
redo
this
one.
M
So
you
can
see
the
service
rig
actually
intercept.
This
request.
For
this
image,
but
if
you
look
at
the
URI
of
it,
it's
in
fact
goes
to
the
live
web
page.
So
this
example
kind
of
demonstrates
of
based
on
a
work
file
that
we
use
back
over,
get
licensed
govern
from
this
source.
Here
on
this
remote
machine,
we
index
it
and
you
can
actually
just
replay
so
I've
got
that
same.
M
The
point
is
you
index
on
this
machine,
and
once
you
have
an
index
file,
you
should
be
able
to
replay
it
anywhere
that
can
hit
this
ipfs
node
to
do
that.
So,
if
you've
got
fresh
work
or
contents
on
this,
essentially
pushes
these
work
files
web
archive
file
into
ipfs
and
strips
out
all
the
relevant
content
and
the
responses
and
allows
you
to
serve
those
elsewhere.
M
As
an
example,
here
can
actually
punch
pipe
this
locally
into
the
replay
system
and
when
I
go
back
to
here.
This
is
an
example
where
I
had
multiple
your
eyes.
The
same
thing,
so
you
separate
it
out
and
we
have,
if
you
were
to
just
type
in
the
mental
you've,
asked
the
page
archive
there.
It
gives
you
a
listing
of
all
of
them
on
their
momentum
implement
in
here
the
actual
momenta
protocol.
So
if
you
were
to
hit
this
one
here,
there
should
be
a
time,
gate,
endpoint
or
a
time
app
endpoint
on
here.
M
Okay,
that's
not
they're
having
for
it,
but
if
you
hit
the
actual
Mentos
itself,
you
should
be
able
to
see.
We
implement
come
on.
Okay,
so
maybe
not
so
I
think
it's
under
the
Mentos
itself
anyway,
so
we've
got
limited
support
for
event
apparently
and
we're
currently
working
on
getting
the
rest
of
it
on
there
to
make
it.
So
we
can
associate
these
different
captures
based
on
the
hashes
for
that
the
CD
X
J's
represents
so
using
a
source
like
this.
We
just
have
these
these
surveys.
M
You
are
eyes
at
a
time
and
this
additional
metadata
about
it,
you'll
be
able
to
dereference
the
web
archive
content
from
ipfs
on
there.
So
I
think
there's
done.
We've
done
a
little
bit
of
research
and
integrating
this
with
the
IP
LD,
but
it's
not
in
terms
of
so
it
can
say
a
little
more
about
that
on
the
terms
of
main
retaining
the
old
versions
of
it.
I
guess
there's
some
issues
currently
that
we're
hoping
to
make
more
of
an
index
less
system
in
the
future.
M
N
Hello,
so
I
would
briefly
describe
what
Matt
just
did.
There
is
a
thing
in
the
marketing
called
work
files
where
you
record
each
captures
of
the
pages.
If
all
the
requests
in
response
of
HTTP
records
go
there,
it's
like
the
concatenated
with
some
extra
metadata
around
that
so
with
all
the
headers
in
an
payload
in
typical.
So
what
we
realized
is
the
every
time
you
get
a
response
from
the
server
of
the
headers
are
different,
but
if
it
is
the
same
page,
there
is
chance
that
the
content
will
be
same.
N
So
so,
with
that
in
mind,
what
we
did
is
we
go
through
the
records
of
what
files
that
are
saved
when,
when
page
is
captured
using
any
callers
and
we
go
through
these
records
and
separate
out
the
headers
in
input
payload
and
put
them
in
the
IP
FF
system
separately,
and
this
happens
at
the
indexing
time.
So
we
got
like
a
word
file.
N
We
go
through
each
record,
one
by
one
to
split
a
record
header
and
embody
or
payload
in
in
two
separate
parts
in
the
ipfs
system,
so
that
the
payload,
when
it
is
the
same,
we
get
the
benefit
of
deduplication.
Basically
and
then
we
winnow
down
the
IDF's
hashes
in
an
index
file
and
we
note
down
there
like
what
was
the
URL
that
belongs
to
that
particular
capture.
What
was
the
time
when
we
first
captured
and
what
is
the
header
and
payload
hashes?
N
So
those
are
the
things
that
go
in
the
index
file
be
Colin,
CBS
j5,
so
basically,
what
Matt
did
they
created
or
of
an
existing
work
file
invested?
So
the
content
was
pushed
to
the
local
ipfs,
a
system
that
was
running
on
on
a
remote
machine.
So
the
content
lived
there.
We
just
copied
the
the
index
from
there
on
our
local
machine
and
then
we
clear
em
the
replay
system
and
replay
system
only
needs
to
know
of
each
URL
header
and
payload
references
inside
the
FS
system.
M
N
So
so
that's
it
right
now.
It
requires
us
to
exchange
that
index
file
in
there.
We
really
want
to
make
it
an
index
lab
system,
basically
and
all
the
querying
for
the
records
and
all
the
captures
that
we
can
trim
into
us.
Basically,
they
need
to
exist
in
inside
the
idea
system
itself
and
IPL
be
an
IP.
N
Ns
can
come
in
handy
to
solve
those
issues
and
I
will
share
a
link
where
we
have
some
discussions
and
this
mechanism
that
we
have
like
the
new
architecture
of
the
system
when
that
is
so
so
essentially
what
we
need
is
icns
right
now
does
not
support
history.
Basically,
so
the
moment
you
change
the
IP
NS
record
to
Anu.
Has
you
lost
the
track
of
the
previous
record?
N
It
was
pointing
to
and
that's
something
that
we
want
to
keep
us
an
entire
history
off
in
order
to
make
it
happen,
and
then
they
will
be
for
quitting
mechanism
and
all
we
need
some
help
on
the
IP,
only
implementation,
so
that
get
is
the
network.
Graph
of
you
know,
relationship
between
nodes
when
these
two
pieces
are
in
place
in
perhaps
I
think,
ideally,
is
mature
enough
for
that
purpose.
N
But
I
DNS
is
not
so
for
that
I
Dennis
need
to
be
implementing
some
sake,
know
blockchain
became
ism
or
something
to
keep
all
the
structure
card,
and
then
they
can
put
you
know
of
the
momento
time
maps
in
other
elemental
portal,
complicated
stuff
in
place,
and
then
it
will
be
right
now.
It
is
yet
another
replay
system
that
stores
data
differently,
but
then
it
will
be
a
whole
new
system
that
has
no
other
I
mean
it
will
have
very
little
to
share
with
what
other
existing
web
archival
triplet
systems
have.
N
This
will
be
like
a
more
remarkable
model
which
does
not
require
any
index
or
anything.
Anyone
can
participate
in
in
archiving
the
web,
and
anyone
can
put
a
replay
system.
On
top
of
that,
things
would
be
like
no
aggregate
able
in
replayable
more
easily
than,
and
someone
was
offended
by
the
server
less
thing.
It
can
actually
create
a
server
less
archival
system
in
that
model.
That's
not
the
seller
list
that
that
these
cloud
providers
advertise
for
their
benefit,
so
I
think
I
think
that's
it
and
I
would
we
would
take
any
questions
and
it's
in.
Q
E
It
firsthand
so
yeah
like
this
is
super
exciting
super
awesome
work
and
really
had
a
lots
of
things
that
the
guys
are
doing
without
giveth
and
I
do
yeah
like
we
need
to
chat
again
and
I
like
understand.
What
are
the
next
steps?
I
know
that
you
are
looking
forward
to
have
a
penis
and
I
get
idns
in
a
way
that
can
be
broadcasted
in
a
more
real
time
way
and
diesel,
which
is
also
in
this
call,
or
it
was
well.
If
you
go.
P
P
There
in
the
PR-
and
basically
there
is
one
issue
that
we
do
need
resolve-
is
that
we
don't
have
signed
messages
in
pops
up
right
now,
so
this
open
said
now
looks
at
respect
or
attack.
Okay,
so
it's
something
that
we
either
need
resolve.
Being
you
know,
like
I,
think
we
need
to
resolve
inside
parts
up
and
support
ends
this
other
on
that
it's
mostly
code.
Cosmetics
were
chemical
versus
a
balance
and
about
as
integrated,
but
the
code
is
pretty
much
ready.
So.
N
P
That's
quite
I
mean
you:
can
you
can
keep
the
history
if
you
subscribe
manually
to
the
pub
sub
channel,
but
what
we'll
be
able
to
do
is
it
will
be
able
to
broadcast
wraps
up
update
I
mean
it
so
that
you
don't
stick
to
your
notes.
Back,
would
send
records
from
the
gate,
see
and
just
get
the
pressure
records
from
pop
charge.
So.
P
N
P
The
the
current
implementation
of
whatsapp
is
flooding
flood
sub,
so
it's
fine
for
first
bird
by
4%,
elimination
and
small-scale
dancing
and
everything,
but
it's
quite
inefficient
in
network
in
terms
of
network.
You
should
share
if
we
push
so
much
data
as
could
be
coming
from
the
etherion.
P
N
N
A
Jump
in
there,
and
also
reminding
that
we
have
like
five
minutes
left
that
this
is
a
it's
a
confusion
that
comes
up
really
really
often,
especially
around
I
PMF.
That
IP
NS
is
not
a
data
format
for
representing
history
or
version
history.
It's
just
a
technique
for
publishing
hashes,
in
a
way
that
you
can
be
confident
about
who
published
that
hash
as
a
pointer
to
another
hash.
So
that's
that
and
there's
only
a
current
state
of
that
IP
NFS.
It's
designed
with
that
assumption.
So
if
you
want
version
history,
you
need
to
have
it.
A
You
need
to
choose
a
data
format
for
expressing
the
version
history
and
express
that
version.
History
on
your
side,
the
history
of
what
were
the
hashes
for
that
data,
and
one
way
you
can
do
that
is
you
can
put
that
into
you-
could
use
a
CR
DT,
a
complicated
data
type
to
represent
your
version
history.
You
could
also
use
git
style
version,
graphs
or
lots
of
different
ways
to
represent
version
histories,
where
the
the
values
of
each
entry
is
just
a
hash
and
then
having
created
that
data
structure,
you
can
add,
that's
ipfs.
A
You
now
have
a
hash
for
the
current
state
of
that
version:
history
graph
that
you
can
pass
around
it
effectively
like
a
gate,
commit
hash,
and
so
you
could
so
all
of
that
you
can
do
without
a
blockchain
what
the
blockchain
gets.
You
is
that
you
can.
You
can
assert
publicly
in
a
way
that
the
entire
network
sees
that
assertion
on
a
blockchain,
so
benign
data
validation
that.
N
That's
actually
important
from
historical
perspective,
because
otherwise,
if
it
was
someone's
local
history
and
again,
you
know
on
demand,
I
can
provide
that
something.
Then
they
can
change
things
after
the
fact.
It
is
very
critical
in
archival
systems
that
if
you
say
it
yesterday
that
your
this
URL
belongs
to
this
particular
hash,
then
this
needs
to
be
like
a
mail
in
stone
like
you
cannot
change
like
you
know.
I
didn't
say
that
yesterday.
Actually,
no,
you
cannot
so
so
that's
way
of
putting
it
in
in
a
public
blog
Tim
makes
a
lot
of
sense.
N
E
Now
you
can
start
archiving
pages
as
you
go
and
like
only
instead
of
like
crawling
the
web
pages,
like
you
can
just
capture
the
page
that
you
are
seeing
and
you
can
have
like
the
shared
archives
with
other
people
that
you
keep
like
publishing,
saying:
okay,
as
these
pages
and
experts
alike
had
other
pages,
and
now
you
can
I
like
to
work.
How
been
created
collaboratively
right,
a
key
and
you
can
broadcast,
is
about
over
pups
head
like
make
sure
to
like
their
sign.
E
Basically,
this
my
caller
ID
does
like
it
just
follows
and
I
catch
and
there's
a
new
work
file
created
it
pins
it
to
somewhere
and
again.
This
is
just
like
a
tool
mechanism,
coordination
that
is
responsible
to
archiving
with
what
files
to
follow
these
feeds.
The
the
I
think
the
special
things
here
since
we
have
come
out
this
demo
and
now
your
demo
is
like.
E
So
yeah,
let's
bring
all
this
as
much
fluid
out
like
we
have
like
one
middle.
Let's
bring
all
of
these
two
I
can
note.
I
would
suggest
for
us
to
open
an
issue
on
IP
address
class
notes.
Is
people
like
I
know
if
you
have
a
special
worker
for
discussion
of
ideas
for
interplanetary
way
back
but
like
yeah
like
if
you
have
such
a
variable?
Let's
use
that
it's
not
quite
stressed
out
so
that
everyone
could
like
came
in
with
these
ideas
and
perfected
and
building
blocks.
Oh
good
right.
O
A
I
feel
like
it
was
already
an
IP
WB
issue
somewhere,
it's
not
an
IPF
s
note,
but
let's
go
ahead
and
create
another
one
in
NTFS
notes
all
right.
We're
right
at
time
is
anyone.
Does
anyone
have
anything
final?
They
need
to
call
out
before
we
before
we
end.
This
call
I
will
thank
you
to
our
presenters.
Those
were
both
really
exciting.
I've
been
looking
forward
to
them
for
a
long
time.
Yeah.