►
From YouTube: IPFS þing 2022 - Opening - Track Summaries
Description
IPFS þing Orientation and Q&A - presented by @jbenet at IPFS 2022 - IPFS þing Opening - https://2022.ipfs-thing.io
A
So
we
just
need
the
leads
of
the
tracks
to
come
on
and
pitch
their
tracks,
and
I
will
demo
since
I
am
leading
a
track.
So
hey
everyone,
I'm
going
to
lead
ipfs
implementations.
A
The
this
track
is
about
just
giving
a
rapid-fire
view
into
a
ton
of
ipfs.
Implementations.
Is
lots
of
these.
There
are
so
many
that
we
only
have
15
minutes
per
talk.
As
a
speaker,
you
can
decide
whether
to
do
full
talk
for
15
minutes
or
in
some
cases.
Some
people
want
to
do
a
lightning
talk
for
five
minutes
and
then
do
10
minutes
of
discussion
either
way
if
you
want
to
go
and
discuss
right
after
that,
talk
totally
able
to
get
up
and
go
discuss
for
that
implementation.
A
The
goal
is
to
just
hear
from
a
lot
of
folks
working
on
different
iphone
implementations
and
here
are,
from
the
whole
community
what's
going
on.
So
this
is
the
only
track
for
today
and
yeah.
That's
it
and
I
think
next,
one
yeah,
oh
yeah,
and
so
we
can
yeah.
Do
you
want
to
introduce.
B
B
B
C
A
One
more
general
track
like
that:
there's
a
hack,
co-work
and
discuss
track
through
wednesday
through
saturday
it'll,
be
in
floyd.
The
the
space
right
below
here,
there's
just
gonna,
be
tables
and
comfy
seats,
and
so
on.
So
you
can
go
and
hang
out
hack
on
things
and
so
on.
So
for
all
the
people
that
have
always
wanted
an
ipfs
event
with
just
a
lot
of
hack
time.
There
you
go,
it
does
require
the
for,
like
the
willpower
to
not
go
to
a
room.
A
Sure
I'll
go
yeah,
so
will
scott
and
I
are
going
to
lead
a
content,
routing
double
feature
on
wednesday
and
thursday.
The
first
day
is
on
performance,
so
this
is
all
about.
How
do
we
scale
content
routing
and
how
do
we
make
it
really
fast
and
how
do
we
make
it
of
one
and
how
to
make
it
scale
to
10
to
the
18
objects?
That's
a
lot
and
day
two
is
all
about
privacy.
A
So
how
do
we
make
reader
write
writer,
privacy,
preserving
content,
routing
systems,
so
this
is
a
super
key
area
for
actually
building
secure,
secure
systems,
so
the
performance
one
is
short
to
midterm
oriented
the
privacy.
One
is
mid
to
long
term
oriented
and
there's
a
lot
of
like
cool
crypto
in
the
privacy.
One.
D
Cool,
hey
everybody,
emma
din,
there's,
a
data
and
ipfs
track,
has
two
components:
models
which
I'll
be
talking
about
in
leading
and
transfer
which
hannah
was
coming
after
me,
we'll
be
talking
about
it,
leading
so
some
models.
So
if
you
ever
thought
you
looked
an
ips
implementation
and
thought
unix
fs,
it
solves
all
of
my
problems.
This
is
not
the
track
for
you.
D
If,
instead,
you
have
thought
about
ipld
things
or
you're.
Thinking
of
how
you
would
like
to
work
with
data
in
an
ipvs
context,
continuous
context
differently,
what
abstractions
you
need,
what
might
be
there
what's
missing?
Do
you
hate
block
limits?
This
is
the
track.
There's
a
link
here,
asking
you
to
fill
out
a
little
about
your
your
vision
for
ipfs
and
how
you
work
with
data
will
help
us
learn
a
little
bit
about
each
other
and
the
perspectives
that
we're
coming
from
before
we
show
up,
which
will
help
make
our
conversations
better.
E
E
So
once
we
have
all
come
to
complete
agreement
about
how
we're
going
to
build
ipld
we're
going
to
talk
about
moving
it
around
the
internet
and
we're
gonna
talk
about
multi-party
data
transfer
there'll
be
a
30
minute
session,
where
you
can
throw
up
peanuts
at
me
for
graph
sync
and
then
they're
all
you
know
we're
talking
about
bitswap
we're
going
to
talk
about
a
bunch
of
other
experiments
in
data
transfer
and
that's
gonna,
be
in
the
morning
on
thursday
and
then,
since
two
parts
on
data
and
ipfs
are
not
enough.
E
There's
a
whole
other
special
oncom
for
the
afternoon
on
thursday,
where
anyone
can
propose
discussions
in
case
we're
not
all
wrapped
up
with
all
those
topics
by
then
cool
all
right.
That's
it
yes,
who's!
Next,
I
guess.
F
All
right
click
yeah,
so
this
track
is
all
about
sort
of
meeting
user
needs
by
connecting
fps
to
other
protocols,
whether
that's
http
or
dids
or
whatnot.
So
we're
talking
about
ucans
and
ipns
and
gateways
the
the
first
part
of
the
day
before
lunch
is
all
talks
that
are
going
to
be
20
minutes
each
and
then
we're
going
to
do
a
big
hour-long
discussion
on
just
writable
gateway,
because
it
needs
that
amount
of
time
and
then
the
rest
of
the
day
is
all
uncomf.
So
that'll
be
really
fun.
C
Hello,
I'm
going
to
be
hosting
the
building
apps
on
ipfs
track
and
really
what
I
want
to
bring
to
together.
Everyone
who
wants
to
take
ipfs
beyond
infrastructure,
so
everything
from
like
a
default
deployment
experience
can
we
actually
get
people
not
using
ipfs
just
as
a
file
system,
but
using
it
as
a
global
substrate
that
people
can
that
you
know
some
of
my
goals
is
that
every
human
on
the
planet
can
put
content
on
the
internet
and
it's
hosted
for
free,
essentially
forever.
C
So
things
like
data
portability,
actual
apps,
encryption,
privacy
identity
is
the
types
of
things
that
we'll
talk
about.
We've
got
a
number
of
people
joining
sessions,
they'll
all
be
generally
workshoppy,
facilitated
discussions,
and
so,
for
example,
the
fission
team,
piergos
team
ceramic
team
talking
about
some
of
identity
capabilities
and
private
data.
C
Chris
is
building
an
app
on
top
of
ipfs
and
one
of
the
few
ones
that
is
going
to
be
dealing
with
native
ios
clients.
So
going
to
talk
about
some
of
those
choices,
brendan's
going
to
join
us,
basically
going
a
little
further
beyond
unix
fs
and
different
applications
around
metadata
and
wasm
runtimes,
and
so
on.
Very
focused
on
building
and
adoption
in
the
afternoon
we'll
have
the
fluence
team
from
afghani
and
and
david
from
the
compute
on
on
data
over
data
working
group
talk
as
well.
C
C
G
Hello,
so
I'm
here
with
fluence
and
we
work
on
aqua,
which
is
programming
language
for
building
distributed
algorithms
and
perturbed
protocols
which,
like
radically
simplifies
this
stuff-
and
we
are
here
like
to
you,
know-
think
together
about
how
this
new
approach
can
help.
Ipfs
can
build.
You
know,
optimized
content,
routine
content,
indexing
and
like
make
ipfs
better
and
they
like
at
the
networking
level
academy
and
so
on
and
so
forth.
So
we're
gonna
have
this
short
track
on
thursday
and
we're
gonna.
G
G
We
participate
in
the
building,
apps
and
ipfs
session,
and
I
think
bfs
implementations
as
well,
but
I'm
not
sure
I
think
we
have
the
top
here.
Yeah.
A
G
A
So
there's
a
project
and
community
track
to
add
to
create
the
space
to
advance
the
project
and
the
community.
So
there's
all
kinds
of
talks
related
to
how
like
the
interplanetary
improvement
process,
ipips,
which
I
just
learned
about,
which
is
pretty
awesome,
shaping
standards,
the
content,
addressing
alliance
funding,
ipfs
implementations
and
many
other
things
so
come
to
this
track
to
help
orient
the
entire
project
and
lead
it
into
the
future.
H
Hey
everybody:
I've
been
working
on
browsers
for
about
a
third
of
my
life.
I'm
super
excited
about
what
things
like
ipvs
can
do
to
close
the
gaps
that
the
web
that
we
have
today
has
not
quite
filled
yet,
but
the
way
we've
been
doing
that
so
far
is
to
duct
tape,
ipfs
and
http,
together
or
just
shove
ipfs
in
weird
places
where
we
have
to
sacrifice
a
bunch
of
benefits
you
can
get
from
it.
H
So,
with
this
track,
we're
going
to
learn
from
a
few
different
projects
that
have
been
experimenting
in
the
place
like
web
recorder
and
agrigore,
and
others
we're
going
to
talk
about
the
things
that
we
have
to
do
for
web
extensions
to
actually
work
and
be
able
to
get
some
of
the
benefits
of
our
stack
in
there
and
finally,
on
the
last
part
of
the
track,
we're
going
to
focus
on
what
does
a
ipfs
native
web
look
like
where
we
don't
have
to
make
those
sacrifices
where
we
can
reimagine
what
the
web
platform
would
be
if
these
technologies
and
capabilities
were
native
to
it,
instead
of
having
to
kind
of
use
the
duct
tape
approach
thanks.
A
So
I'm
leading
a
an
ipfs
and
wasm
track,
so
this
is
come
and
discuss
how
ipfs
and
wasom
can
blend
into
a
magical
system.
So
there's
going
to
be
all
kinds
of
discussions
around
some
of
the
experiments
with
wasm
ipld
fvm
and
how
we
can
derive
rip
the
flat
coin.
Blockchain
parts
out
of
that
lots
of
vision
around
what
a
distributed
programming,
ipld
environment
would
look
like
an
awesome
talk
about
ipvm
and
autocodec
and
there's
a
set
of
open
slots
for
anybody
else.
A
Who
wants
to
talk
about
computing
and
kind
of
like
the
goal
here
is
to
figure
out
what
the
future
of
ipfs
looks
like
once
you
blend
put
computation
in
many
people
have
heard
me
say
this
before
I'll
say
it
again.
The
biggest
mistake
in
the
ipfs
project
that
I
ever
made
is
not
putting
a
vm
from
the
get-go
into
ipfs,
so
I
should
have
pushed
v8
into
go
ipfs
from
day
one,
and
so
this
is
undoing
that
and
trying
to
push
into
a
much
brighter
future
with
wasm.
So
at
least,
let's
make
it
better.
I
So
there
is
a
session
on
friday,
which
looks
like
it's
just
before
dinner,
which
doesn't
look
good,
but
it's
all
day.
So
I
thought
in
the
beginning
that
sucks
you
know,
people
will
want
to
go
for
dinner.
So
what
this
is
about?
It's
going
to
be
yeah.
There
is
a
team
that
is
doing
measurements
on
ipfs,
that
is
both
within
pl
and
outside,
and
we're
going
to
be
discussing
several
important
components
of
the
stack
such
as
the
dht
routing
table,
which
is
something
that
several
peers
in
the
dht
have.
I
So
you
know
in
order
for
the
system
to
work,
this
needs
to
be.
You
know,
populated
correctly,
so
we're
going
to
learn
whether
it
is
the
case
or
not.
There
are
other
things
like
the
provider
records,
for
example,
which
also
need
to
be
placed
correctly
and
replicated
correctly
and
so
on.
So
if
you
want
to
hear
about
whether
this
is
actually
happening,
that's
the
place
where
these
things
are
going
to
be
discussed.
I
We're
also
going
to
have
people
from
cloudflare
and
from
pinata
to
see
what
outside
what
other
partners
are
building
and
what
measurement
monitoring
and
benchmarking
they
need.
So,
if
you're
interested
to
hear
about
that
come
along
as
well
and
ultimately
the
second
part
of
the
of
the
session
from
I
don't
know,
yeah
early
afternoon
afterwards,
is
going
to
be
setting
the
plan
for
the
future.
I
A
A
J
So
I
I
know,
we've
heard
a
ton
of
fantastic
tracks,
and
I
know
everyone's
going
to
have
intense
fomo
this
week
for
trying
to
attend
everything
all
at
once.
So
this
track
is
an
opportunity
for
us
to
get
back
together
as
a
group
before
the
closing
to
actually
share
back
the
next
steps,
action
items
and
turn
all
of
the
ideas
we've
had
into
concrete
plans.
For
what
are
we
actually
going
to
do
together?
J
What
are
we
going
to
commit
this
driving
towards
action,
and
especially
try
and
orient
ourselves
to
some
next
opportunities
to
share
out
our
work
as
people
who
are
part
of
the
ipfs
community
and
project
in
kind
of
upcoming
milestones,
where
we
can
get
back
together
and
have
a
lot
of
amazing
things
to
report
for
for
what
we've
done?
So
this
is
an
opportunity
to
do
some
discussion
and
road
map
ai
work
to
to
make
sure
that
that
all
lands
into
implementations
really
nicely.
A
And
that'll
take
us
into
the
closing,
which
will
have
a
few
sessions,
including
some
of
the
report
backs
from
road
mapping
and
some
summaries
across
the
board
and
some
like
retroing
and
so
on
and
like
some
like
goodbye
talks.