►
From YouTube: IPFS Intro & Welcome - Molly Mackinlay
Description
Welcome to the IPFS Pinning Summit! The IPFS ecosystem has grown significantly in the last year, creating new opportunities for services and applications. In this talk, we discuss ecosystem growth, the 2020 project roadmap, and what we hope to accomplish from the inaugural IPFS Pinning Summit.
Read more about the inaugural IPFS Pinning Summit on the website: https://ipfspinningsummit.com/
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
For more information on Filecoin
- visit the project website: https://filecoin.io
- or follow Filecoin on Twitter: https://twitter.com/Filecoin
Get Filecoin community news and announcements in your inbox, monthly: http://eepurl.com/gbfn1n
A
I'm
going
to
start
off
kick
things
off
for
you
this
well
it's
morning
here
in
pst,
talking
about
some
of
the
growth
and
opportunities
and
and
kind
of
new
new
things,
we're
seeing
in
the
ips
ecosystem
and
then
hopefully
also
set
the
stage
for
a
lot
of
our
presenters
later.
For
those
of
you
who
are
not
super
familiar
with,
ipfs
ipvs
is
designed
to
make
the
web
work
peer-to-peer.
A
It
addresses
the
content
directly
by
its
cryptographic,
and
this
allows
us
to
be
much
more
flexible
about
where
we
fetch
data
from
how
we
move
it
around
the
network,
how
we
de-duplicate
it,
how
we
verify
that
data
is
what
we
expect
it
to
be.
Instead
of
you
know,
whatever
example.com
wants
to
send
us
for
baz.png
and
has
a
lot
of
other
great
properties.
A
Ipvs
aims
to
address
a
number
of
problems.
A
couple
of
those
are
censorship,
so
being
more
resistant
to
authoritarian
control
being
more
resilient
to
going
offline,
as
I
mentioned,
being
able
to
collaborate,
even
if
you
are
losing
a
central
connection
to
a
server,
that's
fine
in
ipfs.
You
want
to
be
much
more
resilient
to
the
connections
you
can
make
between
devices
that
also
lets
you
be
more
efficient.
So
if
there's
already
a
copy
of
data
you
care
about
near
you,
you
can
use
that
copy.
A
A
There
are
tons
of
applications
building
in
the
ipvs
ecosystem
and
building
businesses
from
kind
of
content,
curation
and
sharing
to
social
networks,
to
kind
of
data
management,
identity,
services,
blockchains
efi,
a
ton
of
amazing
applications
that
are
all
building
in
this
space
and
collaborating
and
sharing
data
with
each
other,
and
this
is
growing
a
lot
as
well.
We
see
many
more
applications
coming
in
here.
A
I
think
I've
had
to
extend
this
down
a
couple
of
times
from
an
ecosystem
diagram
perspective
to
fit
in
more
applications
that
are
coming
a
couple
notable
highlights
from
just
q1
in
terms
of
the
the
awesome
things
that
have
been
happening
in
the
ipfs
ecosystem.
You
had
opera,
adding
support
default,
built-in
support
for
ippfs
in
their
their
android
browser
brave,
launched
their
swag
store
on
ipfs,
wolfram
alpha
or
from
language
has
default
support
for
ipfs.
A
A
We
did
a
ton
of
work
with
with
netflix
over
kind
of
the
q3
q4
time
frame
and
talked
about
that
as
part
of
the
release.
We
did
making
bitswap
a
lot
faster
and
more
performant.
There's
a
new
rust
ipfs
out
there
that
folks
can
participate
and
contribute
to
that's
optimizing
itself
for
use
in
kind
of
more
more
constrained
devices.
Iot
cases
things
like
that.
Just
recently,
textile
hub
came
on
the
scene,
which
is
really
exciting.
A
It
was
the
largest
launch,
we've
done
in
years
to
the
core,
go
ipfs
implementation
and
and
helped
speed
up
a
ton
of
important
areas
for
the
ipfs
project
kind
of
across
the
gamut,
from
adding
new
new
content
and
data
to
ipfs
to
providing
that
data
and
sending
it
out
sharing
it
in
the
network
to
finding
that
data
quickly
from
other
nodes
that
are
hosting
it
and
then
fetching
that
data
from
them.
Every
single
part
of
the
life
cycle
of
data
in
ipfs
is
faster,
which
is
awesome.
A
One
one
point
in
particular:
a
major
focus
for
this
was
content,
routing
speed.
So
how
quickly
you
can
find
the
data
you
want
in
the
network
and
we've
already
seen
really
serious
improvements
just
in
the
public
network
that
we
only
have.
I
think
you
know
something
between
12
and
20
000
people
have
upgraded
to
the
to
ipfs
0.5,
we're
still
we're
already
seeing
massive
improvements
here
in
terms
of
the
the
content
writing
speed.
I'm
sure
stephen
will
tell
us
more
more
about
the
the
latest
update
soon.
A
In
addition
to
content
routing,
we
also
improve
transfer
speed.
This
is
all
of
the
the
work
that
we
did
with
netflix
in
order
to
benchmark
and
hone
our
data
transfer,
algorithms,
and
so
here
for
our
benchmarks
around
container
image
distribution.
We
went
from
an
original
three
three
seconds
down
to
one
second,
which
is
awesome
and
even
better
in
comparison
to
something
like
docker
hub,
where
we're
able
to
really
improve
on
these
benchmarks,
which
is
great.
A
A
That's
been
happening
over,
you
know,
it's
been
happening
for
a
while,
but
it's
really
picked
up
speed
in
the
last
four
four
months
or
so,
and
I
really
think
it's
thanks
to
the
tools
and
capabilities
that
folks
are
bringing
into
the
the
ecosystem
and
making
it
so
easy
for
someone
to
very
quickly
deploy
their
own
website
or
a
decentralized
front
end
for
their
application
onto
ipfs
it.
You
know
now
there
are
uploaders
built
into
all
of
these
decentralized
domain
names.
A
Fleek
has
come
and
it
is
doing
very
seamless,
like
you
know,
netlify
style,
github
uploading.
I
think
the
tooling
here
has
precipitated
that
massive
increase.
I
originally
had
like
screenshots
of
all
of
almanet.eth
and
the
crypto
domain
listing
because
there
were
just
so
many
sites,
but
it
was
overwhelming.
You
couldn't
even
see
so.
A
A
So
clearly,
web
3
is
like
a
is
the
bread
and
butter
for
a
lot
of
these
tools
and
it's
been
growing
a
lot
as
well.
So
there's
this
is
a
small
subset
of
all
of
the
the
different
applications
that
are
thriving
within
the
web3
ecosystem
and
that
are
using
ipfs
by
default
as
the
way
they
do.
Content
addressable
storage,
to
highlight
just
two
that
I
think
are
particularly
beautiful.
A
One
is
audios
they're
a
distributed
music
platform,
I'm
kind
of
like
a
soundcloud
alternative,
but
where
every
artist
is
uploading,
songs
to
their
own
ipfs
node
can
have
control
over
their
music
and
and
their
relationship
with
their
friends,
and
they
have
a
web
app
a
mobile
app.
I
use
this
regularly
there's
an
indie
artist,
who
has
an
amazing
into
the
unknown
remix
kind
of
re-reshaping
of
the
song.
It's
beautiful
and
really
excited
about
the
kind
of
level
of
polish
that's
coming
to
applications
being
built
in
web3
ecosystem.
A
Today,
where
it's
it's
leaning
into
what
capabilities?
Can
we
add
that
that
really
solve
problems
for
a
user
group?
So
this
one
is,
you
know
making
you
know
supporting
musicians
in
the
relationships
they
want
to
have
with
their
music
and
with
their
fans
and
making
sure
that
the
web
3
part
augments
that
experience
and
enables
that,
while
still
having
the
beautiful,
like
user
journey,
that
you'd
expect
from
kind
of
a
classic
web
2
site,
which
is
amazing.
A
I
also
wanted
to
talk
a
little
bit
about
developer
tooling,
where
I
think
there's
growing
adoption
that
we
don't
quite
have
the
kind
of
diversity
and
and
kind
of
strength
that
web
3
does.
This
is
increasing
a
lot
and
also
a
huge
opportunity
for
us
I'd
class.
The
work
we
did
with
with
netflix
on
improving
bitswap
within
this
world,
where
you're
trying
to
distribute
container
images
very
quickly
peer-to-peer
but
you're
you're
taking
ipfs
and
applying
it
to
a
kind
of
a
devops
pipeline,
ci
cd.
A
How
do
we
make
it
faster?
How
do
we
make
it
more
efficient?
You
know
how
do
we,
how
to
use
content,
addressable
storage
to
solve
problems
either
in
a
web
2
system
or
or
by
upgrading,
just
the
necessary
components
to
to
utilize
web3,
and-
and
I
think
this
is
a
a
great
example
of
where
we
can
kind
of
have
bridge
opportunities
between
the
web
3
world
and
web
2
ecosystems,
where
they're
again
trying
to
fight
for
efficiency
and
performance.
A
This
this
kind
of
talks
to
the
opportunities
here
with
devops,
tooling
things
like
docker
hub
things
with
ci
cd.
I
think
there's
growing
growing
interest
in
adoption
here,
thinking
of
using
ipvs
for
vm
distribution,
other
other
kind
of
workflows
in
the
the
operation
space,
and
so
a
lot
of
of
new
nascent
projects
coming
up
in
this
space.
A
One
I'll
mention
is,
we
did.
We
did
a
chunk
of
work
with
making
ipfs
faster
and
more
efficient
for
package
management
and
so
open
work,
starting
up
with
getting
mix,
which
is
one
of
the
one
of
the
package
managers.
We
we
talked
with
a
lot
working
on
top
of
ipfs.
You
can
have
your
build
outputs
or
even
intermediary,
build
steps
on
ipfs.
A
We
also
have
a
project
for
for
a
while
called
npm
on
ipfs,
which
allows
you
to
more
more
resiliently,
mirror
and
decentralize,
where
you're
fetching
your
your
npm
files
from,
and
this
allowed
you.
I
think
we
actually
brought
to
iqbus
camp
a
seven
terabyte
drive
of
all
of
the
npm
data
so
that
it
was
there
on
site
and
you
didn't
have
to
go
fetch
npm
files
and
repos
from
some
distant
place.
Someone
was
already
hosting
them.
So
if
you
used
npm
on
ipfs,
it
was
right
there
within
our
local
ipfs
camp
wi-fi.
A
We
also
have
pac
command
on
top
of
ipfs.
Ruben
did
this
on
top
of
ifest
cluster,
so
you
can
now
follow
the
pacman
repository
here
and
hold
a
mirror
very
seamlessly,
just
by
kind
of
joining
his
cluster
follow,
and
so
generally,
this
idea
of
taking
decentralizing
the
people
who
are
mirroring
package
manager,
registries
and
doing
that
in
a
content.
Addressable
way
has
benefits
around
deduplication
and
sending
data
peer-to-peer.
A
And
so
finally,
I
wanted
to
talk
briefly
about
large
data.
There's
been
a
ton
of
groups
just
kind
of
one
of
the
aspects
of
ipfs
that
people
have
long
been
excited
about
and
there's
a
number
of
projects
in
the
space,
but
I
think
what
we're
going
to
see
over
the
next
the
next
couple
of
months,
the
next
six
months
or
so,
is
just
a
massive
explosion.
In
this
large
data
space.
A
A
A
There's
the
work
that
the
filecoin
team
has
done
around
starlings,
making
it
really
easy
for
people
to
do
decentralized,
storage
and
data
preservation
and
a
ton
of
other
opportunities
around
vr
and
video
and
other
large
data
sets
a
lot
of
whom
are
are
thinking
in
the
file
coin.
Space.
Where,
like
great,
you
have
huge
amounts
of
data,
how
do
you
find
a
cheap
storage
alternative
where
you
can
make
make
that
data
accessible
and
long
lived.
A
The
inflection
point
happening
with
the
ecosystem,
where
the
proliferation
of
websites,
the
proliferation
of
tooling
and
the
professionalization,
like
the
the
extent
to
which
the
ux
is
upgrading
around
this
tooling,
is
really
amazing
to
see
you
know
all
of
these
applications.
You
know
last
last
year
at
this
time,
like
many
of
these
groups
weren't
on
the
map
for
us,
and
so
it's
awesome
to
think
forward
of
all
of
the
new
groups
that
will
be
coming
and
joining
and
participating
in
this
ecosystem.
A
Just
in
the
past
year,
we
saw
a
30x
increase
in
the
number
of
nodes
participating
in
the
ipfs
network.
So
now
there's
hundreds
of
thousands
of
nodes
who
are
all
you
know,
collaborating
sharing
data
working
together
to
help
make
the
ipvs
ecosystem
so
vibrant,
and
so
that
that
level
of
growth
you
know
we're
we're,
making
sure
that
we're
ready
now
for
that
next
30x
from
a
performance
and
reliability
standpoint.
So
we
can
keep
being
on
this
amazing
trajectory
and
and
we're
seeing
some
signs
that
those
things
are
continuing.
A
So,
for
example,
we
run
one
of
many
ipfs
gateways
on
the
core
team
and
we've
seen
about
a
four
to
five
x
increase
in
the
number
of
requests
we're
seeing
per
day.
So
now
it's
about
13
million
requests
a
day
accessing
about
five
terabytes
of
data,
and
so
we're
definitely
continuing
to
see
increased
adoption
and
utilization
of
the
tools
and
resources
within
the
ips
ecosystem.
A
It's
generally
hard
to
get
a
read
on
these
large
decentralized
networks
and
how
they're
growing
and
improving.
So
we
use
the
signals.
We
can
all
right
so
thinking
a
little
bit
about
the
the
ecosystem
of
infra
tools
within
ipfs
I'll
highlight
two
in
particular,
which
I
think
are
really
well
represented
here
in
the
people
who
are
going
to
be
talking
later
today,
just
as
a
quick
overview
for
folks
who
are
are
new
or
kind
of
nascent
in
the
space.
A
So
one
is
pinning
services
and
these
are
are
our
applications
or
services
where
a
user
say
wants
to.
Pin
some
data
wants
the
data
to
continue
to
be
accessible
in
the
ipvs
network,
even
when
their
own
personal
node
goes
offline,
and
so
a
lot
of
examples
here
are
like
you
know.
I
have
my
own
local
node
running
on
my
laptop,
but
even
when
my
laptop
goes
offline
or
I
go,
I
move
somewhere
else.
A
I
want
to
make
sure
this
data
is
accessible
and
maybe
accessible
in
multiple
different
locations,
maybe
having
resilient
copies
so
replicated
in
a
lot
of
different
areas,
and
I
want
it
to
be
edge
cached.
I
wanted
to
be
close
to
the
people
who
are
trying
to
download
it
and
access
it,
and
so
there's
a
number
of
of
groups
within
the
the
ipfs
ecosystem,
all
of
whom
are
providing
this
sort
of
service.
A
This
persistence
service
to
node
and
ipvs
network
who
want
to
be
more
ephemeral
but
want
the
data
that
they
care
about
their
photo
collection,
their
application
data,
their
you
know,
other
other
important
metadata
about
their
node,
want
that
to
continue
being
accessible.
So
that's
one
major
class.
Another
example
is:
is
gateways,
http
gateways,
so
thriving
network
of
pfs
nodes
that
are
interoperating
with
each
other.
A
As
I
was
mentioning,
there's
cloudflare
infura,
a
ton
of
others,
and
you
can
go
to
this
public
gateway
checker
to
see
all
of
the
the
various
gateways
that
exist.
But
but
this
is
kind
of
also
a
growing
place
where
you
know.
If,
if
you're
storing
data
in
ipvs
network,
you
also
want
to
make
sure
it's
highly
accessible
and
not
just
to
people
who
are
already
running
ipfs
nodes
but
to
the
the
wider
world.
As
we
continue
on
this
upgrade
path
and
trajectory.
A
So
this
implies
some
opportunities
looking
at
the
areas
in
the
that
ipfs
adoption
and
the
ecosystem
is
growing
thinking
about
the
sort
of
tools
that
people
are
already
finding
niches
for
in
the
ibfs
ecosystem.
Today,
there's
opportunities
going
forward
for
ipvs
infrared
to
to
provide
more
so
looking
at
these
opportunities
for
web3
in
particular.
A
This
is
things
like
pinning
services,
so
pinning
application
data
making
sure
that
that
stays
around
as
an
app
developer,
maybe
don't
want
to
run
all
of
your
own
node
infrastructure
and
so
utilizing
a
service
that
helps
back
up
all
of
your
app
data
or
that
even
works
directly
with
your
users
from
an
application
perspective
so
that
they're
backing
up
their
own
app
data
with
a
service
provider.
That's
a
major
area
of
opportunity.
Http
gateways
are
also
very
common.
There's
a
number
of
you
know
many
of
the
web.
A
Three
tools
used
in
some
way
or
another
when
you
have
users
who
don't
have
an
embedded,
ipfs
node
to
make
it
more
accessible,
we're
also
seeing
more
kind
of
network
infrastructure
come
online
that
massively
unlocks
adoption
and
growth.
An
example
I'll
call
out
here
is
ifdns,
which
is
a
project
we
did
with
the
ethereum
name
service
and
and
what
this
does
is
it.
A
This
is
the
part
where
you
can
take
like
ethereum
dot
if
and
add
dot
link
to
the
end
of
it
and
then,
even
if
you
aren't
running
meta,
mask
or
ipvs
companion
or
a
local
node,
or
anything
like
that,
you're
now
able
to
look
up
that
decentralized,
tld
and
those
small
pieces
of
infrastructure
make
make
these
services
and
make
web3
in
general,
just
much
more
easy
for
people
to
adopt
and
come
over
from
web
2.
You
know
gateway.
A
I
guess
it
literally
is
a
gateway
but
pulling
people
from
kind
of
one
one
ecosystem
to
the
next,
making
it
a
very
easy
on-ramp
and
growth.
So
they
can
start
understanding
the
value.
That's
that's
possible
for
them
here,
there's
also
things
like
developer,
tooling,
sdks
and
just
easier
interfaces
or
alternative
interfaces
to
make
it
really
easy
to
use.
Ipfs.
A
Looking
in
the
developer,
tooling,
space,
definitely
tooling
around
ci
cd
pipelines
or
other
aspects
of
developer,
tooling,
that
that
can
be
augmented
by
by
peer-to-peer
tools
or
by
content.
Addressing
the
the
difference
here
is
being
able
to
truly
demonstrate
that
the
performance
is
better.
So
this
is
testing,
tooling
and
and
benchmarks
and
validation,
but
then
also
kind
of
the
seamless
way
that
it
would
fit
into
an
enterprise
use
case,
the
management
layer.
A
You
know
all
of
the
the
diagnostics
telemetry
other
infrastructure
that
you
would
actually
need
to
do
this
to
deploy
ipfs
into
say,
a
local
cloud
or
an
enterprise
pipeline,
or
something
like
that.
I
think
there
are
huge
opportunities
here
that
are
mostly
under
undertaken
advantage
of
so
lots
of
opportunity
for
folks
to
to
build
in
this
space,
and
maybe
we'll
get
the
next.
A
You
can
imagine
more
tools
around
erasure
coding
around
caching
and
route
routing
services,
so
that,
when
you
have
very,
very
large
data
sets
think
internet
archives
scale
of
of
data
that
you
can
quickly
upload
data
sets
like
that
to
ipfs
and
that
you
can
cache
the
most
important
or
the
hot
parts
of
of
that
data.
So
they're
highly
available.
A
You
can
even
do
like
more
intelligent
routing
strategies.
Over
top
of
these
large
data
sets,
and
then
the
sort
of
tooling
and
dashboards
around
managing
data
sets
like
this
for
large
organizations
and
institutions.
I
think
this
is
also
a
huge
opportunity
like
when
you
think
about
groups
who
have
a
lot
of
this
large
data.
A
They
need
the
tooling
that
helps
them,
bring
it
to
the
people
within
web3
who
want
to
take
advantage
of
it,
and
so
this
is,
I
think,
also
a
big
opportunity
from
an
infra
perspective
and
thank
you
so
much
really
excited
for
today.
It's
going
to
be
an
awesome
awesome
time
and
over
to
steven
to
share
some
of
the
notable
improvements
in
ipvs
0.5.