►
From YouTube: IPFS & WASM - @jbenet - Roadmapping Next Steps
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
now,
the
most
epic
epic
tracks,
so
the
I
profess
and
wasm
track
had
a
ton
of
mind-blowing
presentations
and
demos.
We,
it
was
a
whole
discussion
about
all
of
what
we
have
ever
wanted
about
computation
in
hash,
linked
things,
and
we
had
many
architecture
discussions.
A
So
we
started
with
just
an
intro
to
the
whole
model
and
what
we
talked
about
in
the
past.
We
had
a
really
awesome
demo
from
adeen
going
into
working
code
today
with
wasan
my
pld
and
a
codec
working,
and
that
was
pretty
epic
here
there
were
some
awesome
reactions,
kind
of
had
to
be
there.
Then
there
was
a
really
good.
I
guess
you
can
watch
the
recording.
A
There
was
a
pretty
good
fem,
deep
dive
from
steb
and
then
his
vision
for
wasm
and
ipld
and
lenses
and
data
structures
and
whatnot.
A
Then
we
heard
about
using
ipfs
and
ipld
from
wasm
and
a
whole
set
of
like
the
interfaces
and
the
stack
that
is
powering
all
the
fission
and
winifs
and
so
on
stuck
then
we
had
a
mind
blowing
talk
about
vm
from
brooke,
which
was
super
awesome
and
she
was
expecting
a
lot
of
people
to
think
this
is
super
controversial
and
we
were
all
like
sounds
great.
Let's
do
it
so
we
then
we
had
a
bunch
of
discussions
about
many
different
runtime
possibilities.
Oh
and
autocodec.
A
We
also
heard
about
an
existing
autocodec
structure
to
wrap
objects,
to
be
able
to
point
to
wasp
modules
that
do
all
of
the
ipld
data
model
translations.
So
that's
there
and
and
really
awesome.
Then
we
had
a
discussion
around
many
different
architectural
models
for
how
to
approach
implementing
ipvm.
A
Then
we
decided
to
not
do
planning
that
day
when
we
were
all
exhausted,
and
so
that
pushed
it
off
to
the
next
day
and
we
were
like.
I
wonder
what
will
come
out
of
this.
Well,
we,
what
came
out
of
it
is
that
we
now
have
a
working
group
assembled
and
we
went
through
a
ton
of
specific
project
proposals
that
we
that
we
want
to
have,
and
we
articulated
the
the
whole
design
space
of
things
that
we
have
to
figure
out
and
we
form
the
group.
A
We
there's
a
bunch
of
work
that
we
need
to
do
to
structure
this
project
and
so
on,
but
a
ton
of
progress
was
made,
we're
all
feeling
pretty
pretty
excited
about
it.
So
here's
a
bunch
of
the
learnings
and
takeaways
and
action
items
so
first
off
there's
a
bunch
of
models
and
thinking
that
we
still
need
to
evaluate
and
learn
from
specifically,
there
are
some
areas
around
capabilities
and
yeah
capabilities
in
the
execution
layer.
A
There
are
a
lot
of
different.
There
are
a
ton
of
different
use
cases
for
this,
so
what
we
can
end
up
is
a
very
general
purpose:
self-describing
computational
layer
and
invocation
layer
for
arbitrary
compute
and
so
on.
We
want
to
do
a
lot
of
this
with
extremely
concrete
use
cases
in
mind
and
early,
so
we
want
to
kind
of
go
towards
implementing
some
working
code
with
components,
so
we
can
start
testing
out
candidate
implementations
quickly
and
not
kind
of
like
defer
that
to
the
future.
There's
a
lot
of
kind
of
shared
goals.
A
Here
many
groups
are
already
doing
all
the
stuff
that
are
very
aligned
on
where
it
should
go.
So
there's
a
lot
of
potential
for
collaboration,
and
so
a
lot
of
rough
consensus
has
been
achieved
very
quickly,
which
is
great
and
we
have
some
running
code,
but
we
don't
have
like
the
full
running
code
and
that's
where
we
need
to
get
to
so
action.
Items
for
us
include.
You
know
the
proper
working
group
formation
so
have
some
basics
in
terms
of
communication
tools,
forums
and
so
on.
A
We
want
to
schedule
some
meetings
and
we
want
to
form
a
roadmap.
Then
we
want
to
get
concrete,
which
means
defining
the
set
of
interesting
and
valuable
demos
to
target
then
set
kind
of
those
in
the
roadmap
and
get
experience
by
building
real
things,
learn
from
those
and
adjust
specs
over
time,
and
there
is
some
important
model
exploration
that
we
need
to
do
still
so
capabilities
cross,
runtime,
self-describing
your
vocations
and
arrive
at
a
pretty
strong
content
address
process
model
here
are
some
milestones.
A
So
this
quarter
we're
going
to
ship
the
ipvm
working
group
and
subgroups.
There's
some
good
there's
a
good
structure
for
two
or
three
subgroups.
We
have.
We
want
to
have
a
rough
roadmap
for
ipvm
and
these
sub
projects.
A
We
want
to
communicate
with
the
wasm
community
and
with
the
aquari
community,
because
a
lot
of
overlap
in
areas
and
a
lot
of
shared
work
and
then
question
marks,
probably
sometime.
We
want
to
arrive
at
a
rough
ipvm
spec,
certainly
less
than
a
year
at
least
some
candidate
spec
that
we
can
kind
of
work
through.
A
We
want
to
define
the
the
the
invocation.
What
was
the
description
apply?
Fpil
yeah?
What?
What?
What
did
it
say?
What
do
you
mean?
A
Linkedin,
location,
yeah,
so
not
linked
data
linked
in
location,
link
compensation,
and
then
we
want
to
have
a
running
app
vm
implementation
sometime
soon
with
some
strong
compelling
demos,
so
we
need
to
set
some
dates
there,
but
I
was
comfortable
putting
some
question
marks
because
we're
way
ahead
on
the
working
group
formation
and
we're
pretty
excited
about
the
trucks
work.