►
From YouTube: IPFS Pinning Integrations - Molly Mackinlay
Description
IPFS Pinning Services could see increased usage through direct integrations with IPFS applications. In this talk, IPFS project lead Molly Mackinlay discusses some of these applications and specific technical integration points.
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
So
I'm
going
to
talk
today
about
given
we've
just
heard
about
this
awesome,
pinning
services
api's
and
the
the
opportunity
to
kind
of
make
it
easier
for
for
folks
to
integrate
into
other
applications.
We
can
talk
about
where
there's
huge
opportunities
for
that,
how
that
makes
the
user
experience
and
an
adoption
flow
for
people
using
IPS,
more
seamless
and
specifically
within
some
of
the
ipfs
tools
that
the
teams
created
to
kind
of
help,
help
people
on
board
on
type
of
s
and
use
IP
us
kind
of
in
their
day-to-day
life
cycle.
A
We'll
talk
about
how
we'll
make
use
of
these
new
pinning
api's
as
they
solidify
cool,
so
generalized
skinning
api
unlocks
a
whole
ton
of
new
opportunities
for
all
sorts
of
application
developers
in
the
u.s.
ecosystem.
A
number
of
folks
have
already
already
seen
this
pain
point
and
started
just
hand
rolling
this
directly.
So
you
see
the
recent
integration
with
ENS,
where
you
can
upload
files
directly
to
ipfs
I,
think
they
integrated
with
temporal
to
you
know
easily
do
that
handshake.
A
Unstoppable
domains
has
also
done
a
direct
upload
to
ipfs
through
their
website
portal,
and
a
number
of
other
groups
are
doing
this
kind
of
more
manually
and
that
that
process
is
like
right,
now,
very
one-off
and
rather
fragmented,
when
you
think
about
all
of
the
other
tools
that
exist
in
I.
Give
this
ecosystem
crypto
wallets
marketplaces
tools
for
kind
of
content
distribution,
where
you
have
creators
in
charge
of
the
data
they're
uploading.
A
There's
also
things
like
like
with
query:
where
right
now,
you
host
a
lot
of
awesome.
Maybe
very
large
data
sets
that
you're
working
with
other
scientists
or
people
who
are
analyzing
and
manipulating
these.
These
version
datasets.
But
maybe
you
also
would
like
to
have
that
data
persisted
and
when
you
go
offline
or
and
pay
for
additional
folks
to
follow
along
and
persist.
A
The
newer
versions
and
iterations
of
the
work
that
you
and
other
others
are
doing
collaboratively
through
tools
like
query,
video
is
another
big
one
right
now,
there's
already
a
number
of
tools
for
things
like
view
Li
and
D
tube
and
other
video
platforms
that
allow
you
upload
and
persist.
Videos
on
those
chains.
A
I
can
imagine
this
there's
more
opportunity
to
do
this,
a
lot
more
and
integrate
it
more
seamlessly
into
the
places
where
where
people
are
uploading,
video
audience
is
another
example
or
you
can
upload
tracks
to
audience,
but
right
now,
like
making
sure
that
your
audio
track
sticks
around
is
something
that
kind
of
is
still
a
local
IP
of
us,
node
or
kind
of
gateway
service,
sort
of
sort
of
activity
so
again
making
making
these
things
available
in
the
city
of
an
application
or
user
flow.
So
you
don't
have
to
hop
sideways
fleets.
A
Another
example
I
think
they
handle
this
kind
of
for
you,
they
pin
the
content
to
two
ipfs,
but
you
could
imagine
kind
of
making
that
so
that
you,
as
a
user
who
is
uploading
a
website,
can
more
seamlessly
pay
for
long
term.
Persistence
for
for
your
site's
hosting
another
example,
is
open
Bazaar
in
Haven.
So
this
is
where
you're
having
marketplaces
or
stores
and
again
right
now,
you
host
your
own
ipfs
node.
A
So
we
just
talked
about
all
of
the
different
opportunities
here
from
kind
of
an
ecosystem
perspective
places
where
folks
might
want
to
make
use
of
pinning
api's
in
order
to
simplify
the
upload
and
persistence
flow.
Let's
talk
a
little
bit
about
some
specific
tools
that
we
created
just
for
people
in
the
IFS
ecosystem,
who
are
onboarding
where
we're
running
into
right
now,
some
some
challenges
or
kind
of
frustrating
user
flows
that
we
think
we
can
simplify,
having
a
more
kind
of
simplified
and
consistent
API
for
pinning
services.
A
So
this
is
just
a
quote
from
IPS
Desktop
github.
The
the
aim
here
is
just
to
enable
you
to
interact
with
and
use
your
local
IPS
node
really
efficiently,
but
it
also
enables
a
number
of
kind
of
basic
ipfs
actions.
Things
like
adding
data
type
FS
downloading
hashes
you
see
around
the
internet
helping,
pin
and
persist
that
data
Auto,
adding
screenshots
a
lot
of
the
user
flows
that
emerge
out
of
those
capabilities
also
want
things
like
longer
term
persistence
outside
of
your
own
single
local,
ipfs,
node.
So
great.
A
How
could
we
bring
some
of
that
tooling
and
capabilities
to
ipfs
desktop
and
web
UI,
so
I'm
gonna
walk
you
through
a
common
use
case
that
I
have
since
I
spend
a
lot
of
my
time
working
with
an
IP,
FS,
blog
I'm.
Sure
Jen
can
also
a
sympathize
with
this
from
the
IP
fest
newsletter
perspective.
But
a
common
aim
here
is
thinking
about
how
do
I
bring
assets
that
I
want
to
include,
or
reference
in
a
blog
post
and
I
also
want
these
assets
to
be
hosted
on
ipfs
images.
A
You
can
imagine
you
know
great
blogs
can
handle
images,
but
what
about
video
and
there's
a
lot
of
other
types
of
assets
you
might
want
to
include
and
reference
and
you
want
them
all
to
be
distributed
over
IP,
FS
and
right
now.
This
isn't
actually
a
super
seamless
experience
for
a
normal
blog
creator.
A
It's
not
a
great
super,
simplified
user
experience
and
flow
to
hop
between
multiple
different
places,
and
it's
super
similar
to
the
the
kind
of
frustration
you'd
experience
across
a
lot
of
these
other
sites
like
vu,
Lee
or
audience
or
d2.
Hooper
query:
where
again,
you
don't
want
to
upload
data
from
your
local
node
to
one
of
these
services
and
then
also
have
to
hop
to
a
different
UI
I'm
in
order
to
make
sure
that
data
is
persisted
copying
over
hashes
or
me,
uploading
files
we've
already
connected.
A
So
instead
of
that,
how
do
we
bring
two
links
directly
into
the
application?
Having
a
similar,
pinning
API
enables
us
to
actually
integrate
this
work
directly
into
the
products
were
creating,
so
the
the
mocks
we
have
for
this
and
our
attention
to
plan
going
forward
is
to
actually
out
of
space
within
the
web.
Ui
specifically
for
configuring
persistence
options.
So
we
add
a
new
icon
over
here
on
the
left,
and
this
gives
you
the
default,
which
is
great.
You
can
store
things
locally
on
your
local
ipfs
node
and
get
a
little
bit
of
data
about.
A
You
know
how
much
data
you're
storing
how
much
bandwidth
it's
using,
but
you
can
also
add
other
services
and
anyone
can
come
and
PPR
support
for
assistance
services
into
the
web
UI
so
that
you
can
select
one
of
a
one
of
the
pending
service
providers
who
implement
this
pinning
service
API,
and
you
can
then
select
one
of
these
and
configure
it
for
your
local,
ipfs,
node,
and
so,
if
say,
I
selected
in
Fira
I
can
label
it.
If
maybe
I
have
multiple
in
Fira
accounts
a
work
account
in
a
personal
account.
A
I
can
use
my
secret
API
key,
so
I
don't
have
to
worry
about
like
additional
sign-in
or
any
worries
about
like
configuring.
You
know
worried
about
syncing
data
between
two
different
portals
and
I
can
decide
how
much
of
the
content
within
my
node
I
want
to
auto
upload,
either
all
my
content,
or
just
the
things
that
I've
pinned
or
other
things
like
that
and
then
I
can
configure
lots
of
these
and
so
I
have
the
different,
pinning
api's
that
I
support.
A
A
So
we're
excited
to
do
this
specifically
within
I,
could
mess
web
UI
and
desktop,
but
I'm
very
confident
that
many
other
groups
are
going
to
be
very
excited
about
this
as
well,
and
about
integrating
this
sort
of
support
directly
into
their
applications.
You
can
see
that
it
groups
like
ENS
and
unstoppable
domains
have
already
done
it.
I
expect
many
others
to
follow.