►
From YouTube: IPFS þing 2022 - Opening - Intro & Goals
Description
IPFS þing Orientation and Q&A - presented by @jbenet at IPFS 2022 - IPFS þing Opening - https://2022.ipfs-thing.io
A
I'm
going
to
talk
through
three
things
about
the
event
and
then
we're
gonna
hear
about
some
logistics.
A
So
why
this
thing,
as
many
of
you
have
picked
up
a
thing,
is
a
parliament
or
a
council
or
an
assembly,
and
it's
an
it,
comes
from
the
old
norse
word-
and
this
was
another
word
for
us,
because
we
wanted
to
host
iprefestcamp
this
year
right
around
this
timing.
But,
alas,
it
was
not
in
the
stars,
and
so
we
shifted
the
event
into
this
thing.
A
We
decided
to
host
it
here
next
to
thinkville,
where
the
all
thing
one
of
the
oldest
parliaments
ever,
I
think
the
oldest
running
one
is
going
and
that's
why
it's
called
a
thing.
But
why
bring
everyone
together?
A
So
many
of
you
know
that
there
we've
been
struggling
with
some
implementation
bottlenecks
in
the
last
few
years,
the
the
most
no
there's
a
bunch
of
them,
but
one
notable
one
was
that
go.
A
Thank
you.
Everyone
who
worked
on
this,
because
that
was
that
still
is,
and
will
continue
to
be,
an
ongoing
important
thing.
So
thanks
for
thanks
for
that
renaming.
But
what
that
means
is
that
now
everyone
is
free
to
roam
around
and
build
whatever
implementations
you
want
with
with
all
these
protocols,
and
you
can
make
your
own
version
of
ipfs.
A
The
thing
that
we
have
to
figure
out
is
what
exactly
is
an
ipfs
node
and
what
exactly
is
the
ipfs
protocol?
I've
heard
lots
of
different
different
things.
Kind
of
the
working
I
used
to
say,
oh
well,
ipfs
is
really
just
kind
of
like
unix
of
s
and
ipld
and
lipid2p
in
a
trench
coat
and
like.
If
you
have
those
things,
then
it's
an
ipfs
node,
but
then
people
pointed
out
well.
Does
it
really
have
to
go
over
lip3p?
What,
if
it
doesn't
what
if
it
goes
over
http
like?
A
Well,
I
guess
that's
technically
that,
but
what?
If
it's
not
unixfs?
What
if
it's
like
some
other
data
structures?
Well,
that's
probably
that's
probably
fine
too,
so
I
think
a
lot
of
the
community
is
landing
on
if
it's
got
content
address
data
and
you
can
move
it
around
and
it
can
interrupt
and
it's
basically
hypermedia
or
an
app
or
something
like
that-
something
like
the
web.
If
it's
the
content
address
web,
that's
ipfs
that
yeah
cool.
A
Labs
person
in
me
is
like
that's
not
a
protocol,
but
but
maybe
it
is-
and
so
I
think
it's
up
to
us
to
up
to
this
group
to
figure
out
what
it
will
be,
but
anyway,
the
next
thing
that
we
wanted
to
do
after
busting.
That
bottleneck
is
to
have
a
bunch
of
innovations
discussions.
A
So,
of
course,
there's
a
bunch
of
content
and
so
on.
There's
a
lot
of
different
implementations.
Here's
just
a
few
that
are
represented
here,
there's
many
many
more
and
what
I
kind
of
want
is
to
have
a
bunch
of
discussions
this
week
by
the
way
this
is
this
is
stock
imagery
and
for
the
first
time
ever,
the
stock
imagery
is
actually
us
like
we're
actually
talking
about
like
gears
and
java
applets
and
goals
and
financial
transactions
and
mail.
It's
pretty
cool
and
we
should
have
a
cambrian
explosion
of
implementation
tools
and
systems
and
success.
A
So
that's
why
we're
all
coming
together.
The
other
thing
that
I
think
can
come
out
of
this
is
a
lot
of
community
growth.
So
often
when
we
get
together
and
we
share
knowledge
and
we
talk
about
things
and
we
record
talks
that
tends
to
diffuse
a
lot
of
our
knowledge
and
help
a
lot
more
people
on
board
onto
these
systems
and
these
protocols,
and
so
on
so
use
the
talks
during
this
week
as
a
way
not
just
to
inform
everybody
else
here,
but
to
inform
the
audience
of
the
future.
A
So
remember
that
when
there's
a
recording,
usually
the
vast
majority
of
the
audience
is
not
in
that
room.
It's
in
the
future,
and
so
now
you
can
include
of
course,
discussion
either
after
your
talk
or
around
it
or
in
the
hallway
track
or
in
separate
sessions,
to
spend
the
time
with
the
people
here,
but
use
both
use
both
to
your
success,
meaning
remember
that
part
of
the
talks
and
what
you're
going
to
record
is
going
to
be
for
many
other
people
who
are
not
here
today
or
this
week.
A
Who
will
be
watching
you,
but
also
the
people
here
so
tune
tuned
both
and
that
can
yield
a
lot
of
protocol
growth,
not
pictured.
Here.
Something
happened
to
my
image.
So
that's
this
is
why
we're
having
the
thing.
So
it's
like
a
smaller
version
of
ippfest
camp,
we're
still
deciding,
and
I
mean
we
are
still
deciding
whether
or
not
we
should
have
ipfs
camp
still
this
year
like
late
this
year.
We
can
do
that.
A
Ipfs
camp
will
tend
to
be
much
larger,
with
a
lot
more
people
and
a
lot
more
of
the
community
who
couldn't
make
it
make
it
here
so
yeah
again
implementation
bottlenecks,
let's
bust
those,
let's
have
a
bunch
of
innovation
discussions,
let's
yield
an
implementation,
cambrian
explosion
and
funnel
that
into
community
growth
and
protocol
growth.
A
So
some
goals
as
we
walk
across
the
implementation.
Glaciers,
let's
focus
on
advancing
ipfs
implementations
and
it's
easy
to
kind
of
think
you're
advancing
them,
but
not
really
oftentimes
and
I'm
like
very
prone
to
this.
We'll
talk
a
lot
about
possibilities
or
and
very
concretely-
and
you
know,
there's
some
plan
for
the
future,
but
that
plan
is
actually
quite
far
away.
It's
not
actually
that
useful.
It's
not
actually
useful
to
many
people,
so
I
would
encourage
you
to
focus
on
the
near
and
mid
term.
A
Instead
of
the
long
term,
like
focus
the
long
term,
to
the
extent
that
you
need
to
figure
out
the
near
and
mid
term
and
focus
on
solving
the
key
problems
that
you've
been
encountering
and
have
been
huge
pain
points
for
you
for
the
last
year
or
two
things
like
encryption,
things
like
codecs
things
like
the
lack
of
computing
in
the
runtime
all
that
kind
of
stuff,
and
I
encourage
you
to
explore
ideas
together
so
share
your
knowledge,
get
feedback
on
ideas,
discuss
possibilities,
propose
things,
propose
things
that
are
out
there
and
if
you
share
a
lot
of
what
you've
been
thinking
or
planning
to
build,
then
maybe
somebody
else
will
go
and
build
that.
A
So
maybe
you
don't
have
to
do
it
all
alone.
Maybe
you
don't
have
to
to
go
through
all
of
the
work
yourself.
Maybe
a
lot
of
the
other
people
here
can
help
you
in
your
journey
and
orient
towards
catalyzing
action.
So
a
lot
of
ideas
and
a
lot
of
things
can
be
really
good
and
help
advance
our
understanding.
A
But
if
we
don't
turn
those
into
plants
of
some
sort,
if
we
don't
commit
to
shipping
something
at
some
point
in
time,
if
we
don't
yield
some
improvement,
then
it'll
sort
of
like
become
this
amorphous
knowledge
in
our
in
our
minds
or
in
documents
and
so
on,
and
it
won't
actually
have
impact
yet
potential
impact
potential
for
the
future.
But
I
think
all
of
us
in
this
room
want
to
have
impact
this
year,
and
so
I
urge
you
to
with
a
lot
of
these
plans,
orient
towards
catalyzing
action
and
build
relationships.
A
There's
a
lot
of
people
here
who
we've
heard,
are
working
on
similar
things
and
could
totally
like
tackle
that
together
and
divide
and
conquer
those
problems
and
also
have
us
a
goal
to
learn
new
things.
These.
It
was
great
to
hear
in
a
lot
of
people's
what
they
want
to
get
out
of.
The
thing
was
learning
a
bunch
of
things
and
that's
great,
explore
new
concepts.
Get
out
of
your
comfort
zone,
go
to
go
to
talks
or
tracks
or
sessions
that
you
don't
know
anything
about
and
learn
more
those
kinds
of.
A
A
So
when
you
go
and
present
something
try
to
explain
things
clearly
beyond
the
people
in
the
room,
so
the
people
in
the
room
here
have
a
ton
of
context
and
a
ton
of
knowledge
and
so
they're
going
to
be
able
to
understand
a
lot
of
what
you're,
saying
and
you'll
be
able
to
kind
of
give
very
succinct
descriptions.
A
However,
a
lot
of
people
that
might
be
watching
you
in
the
future
may
not,
and
so,
if
you
kind
of
like
expand
your
your
definitions,
a
bit
and
you
expand
your
thinking
and
so
on,
you'll
be
able
to
support
newcomers
a
lot
better
and
also
there
are
some
newcomers
in
the
room
so
as
you
find
them
help
them
out
and
help
them
learn
a
lot
of
the
stack,
help,
explain
things
and
so
on
pay
it
forward
and,
as
you
do
also
help
be
bridges
and
connect
people.
A
So
the
structure
of
the
event
is
very
autonomy,
oriented
and
choose
your
own
adventure
oriented.
So
there's,
as
probably
most
of
you
know
now
separate
tracks.
Each
track
has
is
oriented
around
a
different
topic.
The
tracks
follow
different
formats.
Some
of
them
are
like
more
talk,
oriented
some
much
more
discussion.
Oriented
some
are
just
hack,
hacking,
oriented
and
each
track
is
up
to
the
track
lead.
So
each
track
lead
each
organizer
sort
of
decides.
Like
the
format
of
that
track.
A
Again
choose
your
own
adventure
attend
the
things
that
you
want.
So
this
is
the
only
time
when
we're
all
together
between
now
and
the
closing.
That's
it,
although
I
think
those
teal
ones
that
I
highlighted
project
and
community
and
road
mapping.
Next
steps
probably
really
useful
for
a
lot
of
folks.
So
that's
why
I
highlighted
those
and
the
event
also
has
a
lot
of
downtime
together.
So
lots
of
dinners
together
lots
of
outings
together
and
so
on.
That's
so
you
can
get
to
know
each
other,
build
relationships,
learn
from
each
other,
discuss
and
so
on.