►
Description
Top tips for builders about how how turn your IPFS ideas into reality, how best to use the IPFS stack, how to get stuck in on existing projects, how deal with apps and more.
A
It's
hard
to
prepare,
slides
or
give
any
kind
of
advice.
If
you
don't
know
the
audience,
so
here's
the
sort
of
the
rough
outline
of
what
I'm
going
to
show
you
today,
I
want
to
like
take
a
quick
brief
look
at
like
what
is
ibfs
and
then
from
there
I'm
going
to
show
also
the
different
sort
of
interpretations
of
what
ipfs
is
I'm
going
to
share
some
Timeless
Lessons
From
The
Trenches,
a
lot
of
like
insights
that
I've
gathered
over
the
years.
A
You
know
from
other
great
Engineers,
but
also
some
of
the
hard
learned
lessons
that
I
learned
along
the
way
and
then
I
want
to
just
open
it
up.
For
for,
like
an
ask
me
anything,
so
what
is
ipfs
so
I'm
just
getting
a
lot
of
echo.
So
what
is
ipfs
I?
Think
there's
like
an
ongoing
discussion
and
about
this
and,
as
the
name
suggests,
a
lot
of
people
think
that
it
is
a
file
system
in
the
sense
that
it's
a
way
to
store
your
files,
and
that
is
obviously
to
some
degree.
True.
A
But
there's
this
common
misconception
that
comes
up
again
and
again,
which
is
oh
I
added.
My
files
to
ipfs,
why
can't
I
get
them,
and
it
is
true
that
you
can
add
files
but
adding
files
to
ipfs,
contrary
to
Common
belief,
especially
amongst
newcomers,
is
not
a
thing
that
you
do
once
and
then
it's
magically
stored
on
the
network
and
it's
magically
available
on
the
network.
The
act
of
adding
something
to
ipfs
and
making
it
available
is
an
active
process.
A
I
mean
it's
pretty
much
like
running
a
server,
and
so
you
can
pay
a
pinning
service
to
do
this
for
you.
But
ultimately,
ipfs
is
really
it's
a
way
of
moving
data
around
more
so
than
it
is
a
way
to
store
files.
So
it's
not
a
storage
system
as
much.
It
is
a
Content
routing
protocol
or
a
way
to
move
around
bytes
and
so
there's
a
lot
of
sort
of
debates.
A
You
know
about
the
definition:
if
it's
a
you
know
a
file
system
or
is
it
just
content
addressing
but
I
think
there's
sort
of
two
Core
Concepts
that
are
really
key
to
understanding,
ipfs
and
hopefully
clarifying
some
of
the
misconceptions
and
those
are
content
addressing
and
I
think
you've
heard.
You
may
have
heard
this
sound
by
that
content.
Addressing
is
a
way
of
storing
things
and
finding
things
based
on
what
they
are,
rather
than
where
they
are,
and
the
best
analogy
that
I
could
come
up
for
is
like
the
Ikea
article
numbers.
A
So
in
ipfs
we
have
SIDS
Ikea.
You
have
article
numbers
like
you
have
here:
604
169
25
for
this
little
stool
and
it's
very
similar
to
a
seed
in
the
sense
that
it
doesn't
matter
which
country
you
go
to
which
specific
branch
of
Ikea
you
go
to.
You
have
that
article
number
you're
going
to
be
able
to
get
that
stool,
and
so
it
works
the
same
way
with
ipfs
and
Sid.
A
A
From
you
know,
like
analogies,
like
you
know,
in
hotel
chains,
you
know
we
used
to
be
tourists
and
when
we
went
to
a
new
city,
we'd
have
to
find
a
hostel
or
a
hotel,
and
there
was
sort
of
a
clear
division
of
the
roles.
It
had
hotels
and
you
had
tourists
or
you
had
hostels,
and
you
had
tourists,
and
you
know,
as
we
transitioned
into
a
world
in
which
we
have
Airbnb,
then
you
know
you
have
one
account
on
Airbnb.
You
can
be
a
host
or
you
can
be
a
guest.
A
It
depends
on
whether
you're
traveling
right
so
essentially
any
member
of
Airbnb
can
be
productive
in
the
sense
that
they
can
become
hosts
and
in
ipfs
we
have
the
similar
idea
right
by
running
an
ipfs
node.
You
can
actually
make
files
available.
You
can
become
a
productive
member
of
the
network,
so
I
don't
know
I
hope
you
can
see
some
of
the
the
parallels
there.
A
This
kind
of
leads
me
to
this
idea
of
you
know
the
cathedral
in
the
bazaar,
Cathedral
and
a
Bazaar
is
actually
a
a
name
of
a
book
that
was
written
by
Eric
Raymond.
He
was
like
a
long
time,
eunuchs
and
Linux
engineer
he's
like
one
of
these
old
OG
developers
and
he
wrote
this
book
to
describe
how
Linux
became
you
know
the
most
popular
operating
system.
You
know
for
servers
and
for
even
mobile
devices,
and
he
describes
something
like
the
philosophy
behind.
A
You
know
how
Linux
Rose
to
to
fame
that
it
has
do.
We
have
anyone
here:
who's,
an
Android,
User
or
a
Linux
user.
Can
you
put
your
hand
up
yeah,
so
funny
thing
is
Right
Android
devices
they're
actually
using
the
Linux
kernel.
So
really
Linux
today
is
everywhere.
You
know
it's
running
most
of
the
internet
infrastructure,
but
it's
also
made
its
way
into
the
most
popular
or
the
second
most
popular
mobile
platform,
Android
that
is
and
anyways
Eric
Raymond
describes.
A
You
know
a
lot
of
different
ideas
about
what
made
Linux
successful
and
in
this
book
he
sort
of
lays
out
this
quote
in
which
he
says
you
know
any
tool
should
be
useful
in
the
expected
way,
but
a
truly
great
tool
lends
itself
to
users.
You
never
expected
and
I
think
we're
seeing
a
similar
thing
in
the
ipfs
world.
Where,
essentially
you
know,
we
had
all
of
the
ideas
about
what
ipfs
is,
and
you
know
we
designed
it
with
this
kind
of
like
cathedral
in
mind.
You
know
when
Juan
started
working
on
it.
A
He
had
a
very
clear
vision
of
what
he
wanted
to
do,
and
you
know
now,
some
years
later,
I'm
sure
that
many
of
you
were,
if
you,
if
you
attended
the
previous
days
of
ipfs
Camp,
you
had
the
chance
to
see
some
of
the
really
weird
quirky,
interesting
cool
use.
Cases
of
ibfs
and
I
think
we're
just
seeing
this
Cambrian
explosion
of
use
cases,
which
is
also
driving
the
Cambrian
explosion
in
implementations
of
ipfs,
so
ipfs
is
making
its
way
into,
for
example,
the
German
manufacturing
industry.
A
You
know,
as
rudiger
spoke
on
my
track
yesterday,
so
we're
seeing
like
a
lot
of
these
new
use
cases.
You
know
we've
seen
the
metaverse
we're
seeing
internet
infrastructure.
Cloudflare
is
really
betting
on
this,
and
it's
sort
of
making
ipfs
is
making
its
way
into
use
cases
that
we
never
imagined
before.
A
Now
that
was
sort
of
my
introduction
to
what
ipfs
is.
As
I
said,
you
know
it's
often
confused
to
be
a
file
system,
but
in
reality
you
know
it's
it's
it's
more
of
a
way
of
moving
data
around
and
really
the
interpretations
of
what
it
is
are
up
for
us
to
determine.
So
you
know
if
you
have
an
idea
and
you
build
something
and
you're
breaking
all
of
the
rules,
so
to
say
of
ipfs.
That's
a
good
thing.
Don't
don't
doubt
yourself,
you
know
just
go
along
with
it.
A
I
know
some
of
you
have
a
technical
background,
but
these
are
just
ideas
that
I've
collected
and
have
seemed
to
work
out
for
me.
So
the
first
one
is
every
good
work
of
software
starts
by
scratching
a
developer's,
personal,
itch
and
I.
Think
that
you
know,
if
you're,
trying
to
solve
a
problem
that
you
have
in
your
life
or
an
itch
that
you
have.
A
You
know
I'm
a
a
hobbyist,
woodworker
and
so
I
love
building
things
that
are
useful
for
me,
and
you
know
when
you're
working
with
soft
rates,
it's
a
lot
more
abstract
because
it's
all
bits
on
a
computer,
but
you
know
in
woodworking
you
know
you're
essentially
constantly
well
I
love
to
constantly
build
things
to
you
know,
bring
utility
in
my
life
and
so
I
think
this
is
a
really
useful
thing
and
and
sort
of
when
you
bring
your
heart
to
problems
that
you
care
about.
The
software
that
you
build
is
much
better.
A
The
world
of
crypto
is
super
super
complex
and
it's
really
kind
of
hard
to
you
know,
go
beyond
just
the
marketing
speak
and
the
buzz
and
really
understand.
You
know
how
some
of
these
systems
work
and
a
lot
of
these
systems.
I
mean
if
we
just
look
at,
say
Bitcoin,
which
has
been
around
say
12
13
years
Bitcoin
is
I,
mean
pretty
simple
in
the
sense
that
it's
not
like
as
complex
as
some
of
the
stuff
that
we
have
today.
A
You
know
the
tcpip
stack
having
an
understanding
of
how
this
model
Works,
you
don't
have
to
become
a
protocol
expert,
but
you
have
to
understand
how
how
some
of
the
abstractions
were
divided
and
what
were
some
of
the
different
responsibilities
of
say
the
tcpip
stack,
so
that
sort
of
leads
me
to
the
third
one
which
was
Embrace
radical
incrementalies,
radical
incrementalism,
really
small
release.
Often
so
radical
incrementalism
is
just
this
idea
that
you
know
you
make
very
small
iterations
and
you
keep
on
pushing
them
out.
A
A
lot
of
us
has
you
know
when
we're
building
things,
whether
that's
with
ipfs
web
3
or
just
software
in
general,
we're
constantly
experimenting.
We
have
all
sorts
of
assumptions
that
we're
making
about
the
world,
and
then
you
know
we're
testing
them
out
in
the
world
and
the
best
way
to
get
feedback
and
to
create
that
feedback.
Loop
that
improves
whatever
software
you're
building
is
by
releasing
small
releases
in
releasing
them.
Often.
A
I
had
this
earlier
in
my
career,
you
had
this
kind
of,
like
vision
of
you
know,
probably
getting
some
VC
funding
investment
and
then
maybe
you
know,
building
a
unicorn
I.
You
know
I
I
sort
of
glorified.
This
idea
of
building
a
big
company
that
would
be
successful
and
I
think
that
it
was
very
naive
of
me.
I
didn't
realize.
What's
the
life
of
a
founder
of
a
company
and
I
didn't
realize
the
kinds
of
pressures
that
you
know
are
placed
on
you
when
you
go
down
that
path
of
like
founding
a
company?
A
A
So
really
it's
it's
good
to
carefully
think
about
what
it
means,
and
you
know
how
you
measure
success
with
whatever
software
or
tool
You're
Building
these
days,
you
know
I
when
I,
when
I'm
building
things
I
care
a
lot
more
about
you
know:
does
this
project
enable
some
kind
of
creative
freedom
for
me
and
and
for
the
users?
Does
it
Delight
users,
so
user
account?
Isn't
the
only
thing
you
know?
Do
you
want
a
million
users
or
do
you
want
a
million
users
who
find
it?
A
Okay
or
you
know,
150,
who
love
what
you
do
and
you
know
are
part
of
this
tight
community
and
I
think
also
we're
seeing
this
kind
of
tension.
You
know
with
you
know,
centralized
systems
and
decentralized
systems.
You
know
decentralized
systems,
they
don't
always
necessarily
try
to
sort
of
encapsulate
the
whole
world
or,
to
you
know,
capture.
You
know
the
full
population,
it's
you're,
seeing
a
lot
more
like
local,
first
software
and
software
that
is
targeted
at
communities,
and
this
is
another
quote
from
the
cathedral
and
the
bazaar
which
is
good.
A
It's
hard
to
not
mention
open
source.
It
was
sort
of
a
Common
Thread
throughout
this,
but
Embrace
open
source
in
the
power
of
community.
There's
this
misconception
around
the
open
source
that
you
can't
build
a
commercial
company
around
the
open
source
because
everything
is
free,
and
yet
you
know,
if
you
see,
if
you
look
in
this
image,
you
will
see
some
billion
dollar
and
multi-billion
dollar
companies
who've
built
their
complete
business
around
open
source,
so
beyond
sort
of
the
tooling
that
you
get
and
the
utility
of
using
open
source.
A
You
know,
like
also
from
my
previous
slide.
It's
hard
to
not
bet
on
open
source
and
I
mean
almost
everything
we
do
at
PL
is
open
source
and
just
because
you're
doing
open
source
doesn't
mean
that
you
can't
build
a
company
around
it.
So
there's
a
lot
of
utility
and
there's
some
great
examples
here:
hashicorp
Red,
Hat,
Docker,
pivotal
just
to
name
a
few
and,
of
course,
trust
the
process.
I,
don't
think
there's
any
shortcuts.
Success
usually
requires
putting
the
the
work.