►
From YouTube: wasmCloud Community Meeting - 23 Aug 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
B
Sure
I'm
Dave
testman
have
done
probably
gosh
close
to
30
years
in
it
now
currently
I'm
the
Chief
Architect
of
a
startup
in
located
in
Palo
Alto.
That
does
add
fraud
detection
online.
B
So
we,
what
we
do
is
we
take
in
a
bunch
of
data
from
various
ads
as
they
occur,
and
then
we
do
some
big
data
analysis
on
it
and
determine
how
many
you
know
where
the
fraud
is
coming
from,
so
whether
it's
bot
farms
in
the
you
know
in
the
Asia
or
wherever,
and
then
we
provide
a
service
for
for
ad
networks
such
that
customers
come
in
and,
let's
say,
somebody's
bidding
on
an
ad.
They
can
say
they
can
go
to
our
API
and
go
hey.
B
Does
this
IP
address,
you
know
how
reliable
is
this
IP
address?
What's
the
chance
of
this
particular
person
being
fraudulent
from
a
bot
Farm
or
something
like
that,
and
then
we
give
them
a
probability
of
of
the
chance
of
them
being
fraudulent,
so
we've
we're
doing
pretty
good.
We
we've
been
profitable
for
probably
the
last
three
or
four
years
now
and.
B
Run
on
AWS
systems,
so
we've
got
a
whole
slew
of
ec2
instances
out
there
and
all
sorts
of
things.
What
I'm
looking
at
is
sort
of
the
future
of
where
networking
and
the
whole
web
assembly
I'm
pretty
much
a
newbie
to
all
this
stuff
caught
you
guys
on
beyond
the
hype
and
went
wow
that
product
looks
cool
and
loaded
it
down
on
my
system
started
playing
with
it
and
it
is
the
kite
fits
exactly
in
the
kind
of
thing
I've
been
thinking
of
where
we
should
go
for
gosh.
B
The
last
Dozen
Years
I
think
is
I
really
want
to
get
to
the
point
where
I
can
just
create
a
function,
throw
it
throw
it
into
this
massive
cloud
and
just
have
everything
automatically
link
up
together
and
work
as
a
as
an
environment.
So
that's
that's
me.
That's
where
I'm
coming
from
and
I'm
kind
of
interested
in
being
just
sort
of
the
fly
on
the
wall
here
for
a
while
until
I
get
my
sea
legs
and
then
we'll
see
what
happens.
A
That
sounds
great.
Thank
you.
So
much
Dave
for
for
doing
an
intro
super
happy
to
have
you
here
sounds
like
what
you
want
is
what
we
are
doing
slash
trying
to
do.
So
it's
really
really
exciting
cool.
A
It
got
a
really
short
demo:
I
want
to
show
off
wadham
0.5,
manifest
validation,
I
meant
to
show
it
off
last
week
and
just
didn't
quite
get
it
together
with
the
whole
demon
scaler
demo,
so
I
couldn't
couldn't
get
both
of
them
at
the
same
time.
So
I
want
to
show
a
little
bit
of
that.
The
hard
work
that
Aishwarya
did
off
there
and
then
talk
just
a
little
bit
go
over
the
Autumn
version.
A
A
A
So
last
night
actually
cut
wadham
V5
we've
had
a
couple
of
intermediate
releases
going
in
to
going
into
this,
we've
been
doing
some
testing
on
wadum
just
with
a
couple
of
alphas
and
then
a
release
candidate
last
week,
but
you'll
see,
we've
done
a
good
bit
of
work
to
get
to
version
five
with
what
I'm,
adding
that
some
of
the
big
features
are
adding
validation,
support
for
manifests
actually
implementing
and
updating
statuses
with
for
manifests
so
actually
telling
you
if
a
manifest
is
ready
or
if
it's
compensating
or
needs
more
information
to
succeed,
and
then
some
additional
fixes
and
features
around
multi-tenant
mode,
which
is
an
advanced
mode
for
Autumn,
managing
multiple
wasm,
Cloud
networks
or
lattices.
A
Additionally,
we
have
a
another
feature
in.
We
might
go
and
feature
and
upgrade
so
being
able
to
put
a
manifest
and
then
deploy
a
new
version
of
that
manifest
water
will
be
able
to
compute
the
difference
between
the
two,
and
so
you
can
essentially
upgrade
your
applications
upgrade
your
applications
between
versions.
A
C
A
To
deploy
declarative
applications
in
awasm,
Cloud
lattice,
the
the
lattice
or
the
wasmo
cloud
Network
can
span
multiple
different
physical
or
virtual
nodes
and
so
being
able
to
Define
an
application
to
say:
hey,
I
want
to
run
these
resources
and
especially
where
you
want
to
run.
Them
is
really
useful
and
very
powerful,
given
that
you're
just
Distributing
webassembly
modules,
so
you
don't
have
to
worry
about
the
target
architecture
or
operating
system
that
you're
deploying
onto
you
just
specify
a
simple
set
of
labels
and
and
call
it
a
day.
A
So
I
want
to
show
you
just
a
little
bit
of
the
different
types
of
manifest
validation
that
we
do.
This
is
a
kind
of
continually
evolving
story
in
terms
of
what
we're
just
catching
at
the
Manifest
level.
If
we
take
a
look
at
the
applications
that
I
have
deployed
or
put
right
now,
I
just
have
Echo
and
if
you
haven't
seen
a
wada
manifest
before
I'll
go
ahead
and
pull
this
up
just
for
a
little
bit
of
a
sample,
we're
actually
using
the
open
application
model
format
to
do
this.
A
So
it's
an
it's
an
open
standard,
we're
not
Reinventing
the
wheel
here,
but
you
define
a
list
of
components
which
is
primarily
your
webassembly
modules,
the
business
logic
that
you
write
and
then
the
capability
implementations
or
capability
providers,
and
then
you
can
Define
runtime
config
here
in
something
called
a
link
definition.
So
this
simple
application
will
launch
two
components:
a
an
actor
component
and
then
an
HTTP
server
and
then
link
them
together
and
listen
on
Port
8080.
A
A
So
what
I
actually
have
in
this
little
folder
here
is
a
one
valid
water
manifest
and
then
a
bunch
of
invalid
manifests
and
these
invalid
manifests
don't
actually
look
wrong.
They're
not
manifested
or
invalidly
formatted
in
terms
of
the
open
application
model,
they're
just
things
that
don't
logically
work
within
the
wasm
cloud
system
and
so
autumn
is
taking
on
part
of
the
validation
burden
there,
trying
to
prevent
people
from
creating
applications
that
can't
logically
run
in
waso
cloud
and
I
can
talk
a
little
bit
about.
Why
too.
A
So?
Looking
at
the
core
example
here
that
I
have
that
I'm
going
to
be
I'm,
going
to
be
iterating
on
I,
have
the
key
value
counter
watum
manifest,
and
this
has
one
actor
the
key
value
counter
and
then
two
capability
implementations
for
HTTP
server
and
redis
and
then
I'll
be
linking
to
those
different
capabilities
telling
the
KB
counter
to
access
redis
on
localhost
and
then
telling
the
HTTP
server
to
open
up
a
port
on
8080
localhost
8081..
A
Now
I
can
actually
put
this
water
manifest
and
if
I
take
a
look
at
the
app
list,
I
can
see
that
it's
undeployed,
but
it
here
it
exists.
So
you
can.
You
can
distinctly
put
a
new
version
of
a
manifest
and
then
you
can
deploy
that
version
of
the
of
the
Manifest
I.
Don't
actually
have
a
host
running
in
the
background,
so
this
example
isn't
going
to
launch
all
the
way,
but
I
just
wanted
to
show
the
difference
there.
A
Now,
let's
take
a
look
at
some
of
the
invalid
manifests
like
ways
that
you
can
modify
this
manifest
to
make
it
invalid
in
a
wasm
cloud
context,
the
first
one
is
called
invalid
duplicate
actor,
and
this
one
you'll
kind
of
see
right
away
is
a
little
different
because
we
have
a
duplicate
component
here
named
KV
counter
the
image
reference
is
the
same,
and
this
is
it's
not
explicitly
wrong
to
throw
you
know
to
to
run
to
different
replicas
of
a
single
wasmcloud
actor.
A
But
the
stance
that
we're
taking
here
specifically,
is
that
you
shouldn't
have
two
different
components
for
the
same
actor.
If
you
want
to
run
multiple
instances
of
a
single
component,
you
should
be
able
to
modify
that
here
by
changing
your
replica
level.
If
you
want
to
run
this
actor
on
a
different
set
of
Hardware
a
different
set
of
hosts,
then
you
can
do
that
by
specifying
a
spread,
and
so
you
can
do
that
with
a
red
name.
A
You
know
on
the
cloud
and
then
we
can
set
a
requirement
to
run
on
a
host
that
has
the
label
Cloud
equals
Azure.
Something
like
that.
So
we're
we're
essentially
taking
the
stance
that
this
is
how
you
should
be
running.
Different
versions
of
for
different
replicas
of
an
actor
and
putting
this
manifest
will
result
in
a
validation,
error.
Saying
hey,
you
have
a
duplicate
component
called
KB
counter.
A
Let's
take
a
look
at
another
invalid
manifest,
so
this
one
is
called
the
dupe
link
manifest
and
what
this
one
attempts
to
do
is
Define
a
component
KB
counter
link
it
to
http
server,
saying:
hey,
open
up
a
port
on
8081,
please
and
then
another
link
to
the
same
HTTP
server.
Saying
hey,
please
open
up
a
port
on
8082..
A
This
one
may
seem
a
little
bit
more
obvious.
It's
just
conflicting
configuration
for
the
actor
to
use
at
runtime,
and
it's
a
little
it's
it's
ambiguous
from
the
wadham
standpoint,
which
one
should
take
precedence
so
trying
to
put
this
manifests
again
results
in
a
validation
error
when
you
actually
hit
the
right
file,
so
duplicate
Target,
for
link
deaf
and
manifest
it
doesn't
make
sense
to
be
able
to
Define
two
different
sets
of
two
different
sets
of
configuration.
A
Okay,
the
next
one
is
really
similar
to
the
duplicate
actor
under
the
for,
for
the
other
components
we
have
an
HTTP
server
provider
and
another
HTTP
server
provider
with
the
same
parameters.
You
are
not
able
to
run
the
exact
same
instance
of
a
capability
provider
on
a
single
host
and
there's
a
couple
of
reasons
behind
that
one,
but
just
to
keep
it
keep
it
short.
It's
effectively
the
same
reason
as
running
multiple
actor
components.
A
If
you
wanted
to
run
multiple,
if
you
wanted
to
scale
your
HTTP
server,
the
way
to
do
that
is
by
using
the
spreadscaler
replicas
functionality
and
last
but
not
least,
one
that
oops
well.
Of
course,
that's
not
going
to
work
one,
the
last
one
that
I
want
to
take
a
look
at
is
the
duplicate
link
name,
and
this
is
actually
disinvigorating
between
running
two
providers
with
the
same
name
and
instead
this
is
logically
creating
the
exact
same
capability
provider,
just
a
slightly
different
case
of
the
previous
one.
A
But
this
will
also
fail
the
validation
saying,
hey.
You
have
the
exact
same
provider
with
the
exact
same
link
name
and
if
you
haven't
used
linked
names
yet
in
the
wasm
cloud
context,
they're
completely
used
for
they
can
be
used
for
isolation
or
at
least
logical,
different
representations
of
an
a
bit
of
a
capability
provider.
A
So
this
is
just
a
little
bit
of
a
tour
of
the
kind
of
things
that
we're
going
to
catch
with
this
manifest
validation.
It's
really
all
around
preventing
people
from
defining
manifests
that
have
duplicate
components,
duplicate,
logical
things
that
we
won't
be
able
to
start
in
wasmcloud
and
I
know
that
Aishwarya,
who
was
the
the
contributor
that
put
this
together?
She
she
works
at
cosmonic
and
and
put
this
PR
together.
She
also
just
put
in
another
PR
in
wadham.
Let
me
go
ahead
and
pull
that
one
up
real,
quick.
A
Just
to
give
credit
where
credit
is
due
to
add
a
Json
schema
for
for
validating
manifests.
This
is
going
to
make
the
the
validation
of
like
a
an
actual
valid
manifest
and
not
just
wasn't
Cloud
things
really
really
robust
in
terms
of
like
having
the
correct
format
down
to
the
down
to
the
Json
schema
and,
of
course,
and
to
her
credit,
the
tests
are
not
failing
because
of
her
is
because
of
me
and
a
flaky
test
that
I
wrote
so
well.
I
was
super
excited
to
get
that
one
in
all
right.
A
A
Liam
did
have
a
question
about
when
the
demon
scalar
pull
request
will
land.
This
one
is
what
I
demoed
in
the
community
call
last
week,
which
is
essentially
instead
of
saying
Hey
I
want
to
run
one
replica
on
a
host
that
has
the
label
Cloud
equals
Azure.
A
You
can
use
the
Daemon
scaler
to
say:
hey
I
want
to
run
one
instance
of
the
actor
on
every
wasn't
Cloud
host,
that
has
a
certain
label,
and
this
is
a
really
cool
concept
for
like
elastically,
adding
more
instances
or
more
copies
of
your
application
whenever
you
add
a
new
host,
so
this
is
just
kind
of
marked
as
work
in
progress,
but
this
is
something
that
I
am
definitely
going
to
be
demoing
at
wasmcon
when
or
during
my
conference
talk,
so
I
can
expect.
A
C
Thank
you,
Brooks,
that's
cool,
I
I,
actually
am
really
excited
by
this
particular
feature
to
be
able
just
to
specify.
C
You
know
that
I
wanted
to
run
on
all
edges
or
all
devices.
So
I
I'd
like
to
get
that
into
my
demos
and
I,
have
to
talk.
It
was
con
too
I'd
love
to
be
able
to
demonstrate
that
using
Watson
glove.
That
would
be
awesome.
A
Yeah
yeah
well,
I
mostly
have
the
you
know.
Maybe
some
edge
cases
haven't
tested
it
all
the
way,
but
we've
got
I've
got
the
actor
version
of
the
spread.
Scaler
running
I
just
need
to
duplicate
that
for
the
just
need
to
get
the
provider
spread
scaler
for
the
the
demon
scalar
working
as
well,
because
it's
really
useful
to
also
run
providers
out
at
the
the
same
way
that
you
can
run
actors.
A
All
right,
then,
I
think
we
can
go
ahead
and
move
on
to
the
next
section
of
the
the
call
which
is
just
our
our
general
ending
section
on
the
agenda
for
taking
a
look
at
the
Watson
Cloud
roadmap.
Just
doing
a
general
update
if
we
go
and
look
at
the
high
level
was
on
cloud
roadmap
which,
if
you're
new
or
coming
into
the
community,
this
is
actually
just
located.
A
A
If
we
take
a
look
at
our
now
next
later,
we
are
making
solid
progress
on
the
now
and
it's
a
little
easier
to
take
a
look
at
what
we're
working
on
right
now
by
taking
a
look
at
the
work
status
pain,
we
can
see
that
we
are
still
working
on
defining
all
of
our
interfaces,
using
wit
and
the
support
for
wasi
Preview,
2
components.
This
one
is
actually
in
wash
not
in
the
waslam
cloud
host,
because
the
wasmcloud
rust
host
does
have
support
for
Wazi
Preview
2
components,
which
is
super
exciting.
A
If
we
take
a
look
at
the
completed
tab,
this
is
definitely
moved
since
the
last
time
we
met
or
went
over
the
road
map
now
in
in
the
wasmcloud
rust
host.
We
have
support
for
invocation,
claim
verification
command
and
reactor
components
and
custom
lattice
prefixes
in
in
wasm
Cloud.
Now,
a
lot
of
the
things
that
are
in
here
are
under
this
OTP
or
under
one
of
these
milestones
in
the
wasmcloud
wasmcloud
repository,
which
is
where
our
rust
runtime
lives,
and
we
made
some
really
good
progress
here
as
well.
A
The
the
widify
effort
is
all
around
changing
our
interfaces
to
use
the
width,
IDL
and
we've
got
just
a
couple,
more
issues
to
close
out
there
and
then
also
the
OTP
feature
parity
Milestone,
which
will
essentially
make
this
rust
based
host.
That's
fully
compliant
with
all
of
the
new
super
bleeding
edge
standards,
a
drop
in
replacement
for
the
OTP
host.
So
you
can
swap
back
and
forth
between
them
for
now
and
we're
making
really
good
progress
here
on
OTP
feature.
Parity
we've
closed
more
than
we
have
open.
A
A
If
you
go
to
the
pull
request
section
and
look
at
what's
just
been
closed
over
like
the
past
week,
where
we're
exceeding
the
the
single
page
for
for
just
what
we've
done
last
week,
so
lots
of
awesome
stuff
here
I
think
that
that's
all
that
I
had
in
terms
of
the
the
roadmap
update
were
just
steadily
marching
towards
some
of
our
Milestones
here.
A
Trying
to
keep
this
nice
and
available
for
everybody
to
take
a
look
at
the
only
other
thing
that
I
would
love
to
call
out
is,
if
you're
new
to
the
community
or
the
ecosystem,
taking
a
look
at
the
issues
list
and
then
filtering
for
good.
A
First
issue
is
an
awesome
way
to
get
involved
in
these
projects,
since
all
of
our
projects
are
are
most
of
our
main
projects
are
completely
rest
based
and
and
right
up
in
line
with
the
the
webassembly
standards
would
love
to
have
anybody
who's
interested
in
this
space
contribute
and
just
by
filtering
by
label
you
can
see
in
wash
and
the
last
button
at
least
Autumn.
We
have
just
a
couple
of
great
issues
for
people
to
take
a
look
at
if
they're
just
getting
involved.
A
A
Yeah
here
let
me
go
ahead
and
pull
up
the
the
issue:
Milestone
I'm
sure,
I,
think
yep.
So
we've
got
a
couple
of
in
terms
of
what
what
we
have
left.
I
should
probably
assign
this
one
to
me
actually
so
that
it's
easy
to
take.
A
This
is
this
would
be
a
great
issue
to
pick
up,
because
it's
implementing
just
the
additional
functionality
from
the
wasm
cloud
control
interface.
So
from
OTP
you
are
able
to
ask
a
host
for
what
it
knows
about
link,
definitions
and
claims
and
I
think
the
rusto
still
needs
to
needs
to
do
that.
So
this
is
great.
A
I'm,
just
gonna
not
mark
this
as
good
first
issue
yet
because
the
description
leaves
a
little
bit
be
desired,
but
I'd
be
happy
at
that
chunking
for
large
RPC
payloads
is
definitely
something
that
we'll
need
to
carry
over
it's
just
it
actually,
even
really
shouldn't
require
much
implementation,
because
it's
just
copy
paste
and
code
chunking
is
just
a
little.
A
How
can
I
say
this
nicely
a
little
delicate?
It's
it's
very
specific
in
the
way
that
you
have
to
take
a
payload
upload
it
to
the
jet
stream
object,
store
and
then
reconstruct
the
payload.
So
I
worry
about
that
not
being
a
great
place
to
dive
in
and
then
actor
call
aliases
is
another
one
that
Roman
if
you're
on
Roman
is
not
on.
Roman
may
have
started
on
this
one,
but
that's
another
good
one
for
calling
different
actors
by
a
call
Alias
instead
of
public
key.
A
Oh
you
know
what
this
one
that
I
filed
this
morning
is
also
a
great
one
to
to
get
started
with
I
feel
like
I'm
saying.
A
lot
of
them
are
great
to
get
started
with,
but
I
would
specifically
call
out
git
operations
for
links
and
claims
and
validating
actor
and
provider
claims,
as
is
really
impactful
good.
First
issues
here.
A
Let
me
go
ahead
and
label
this
one
so
as
as
you'll
foreign
like
that,
so
when
you,
when
you
start
an
actor
or
a
capability
provider
in
wasmclown,
the
embedded
JWT
that
comes
with
every
actor
and
provider
is
validated
and
ensured
that
one,
it
is
a
valid
signed
resource
that
we
can
run
in
wasmcloud,
but
we
also
want
to
validate
that
the
internal
the
hash
that's
packaged
on
the
JWT
is
the
matches,
the
hash
of
the
resource
itself.
We
can
kind
of
prevent
tampering
in
the
middle.
A
You
know
if
somebody
picked
off
an
actor
and
then
replaced
the
bytes
with
something
else
you
can
tell
when
the
claims
hash
is
invalid,
and
all
of
this
should
be.
All
of
this
is
already
implemented
on
the
OTP
host
side.
So
I'll
come
back
after
this
call
and
just
point
to
a
couple
of
places
in
the
implementation
for
for
inspiration.
D
A
I'm
I've
been
doing
a
good
bit
of
thinking
about
some
of
these
issues,
especially
as
we
start
publicizing
the
the
road
map
and
trying
to
really
keep
that
up
to
date
with
issue
Milestones,
so
I
might
start
trying
to
put
together
a
list
of
I
think
we
actually
did
this.
Maybe
two
years
ago
on
the
community
call
I
think
we
I
think
we
called
it.
The
community
call
out
or
something
like
that,
where
I
tried
to
come
to
the
community
call
with
a
set
of
good
first
issues.
A
That
would
be
really
good
to
pick
up
and
Implement.
So
I'll
see
if
I
can
put
some
of
those
together
and
start
putting
those
out
in
in
slack
I
know
when
I
was
new
to
doing
open
source
stuff
I
always
wanted
to
contribute,
but
never
really
knew
what
was
impactful
or
easy
to
pick
up
so
hopefully
for
anyone
who's
looking
to
contribute.
That
would
be
a
good
resource.
A
Yeah,
thank
you,
CJ
any
other
questions
on
the
roadmap
or
what
we've
got
looking
looking
forward
for
the
next
couple
of
weeks.
A
A
All
right
I
will
do
our
regularly
scheduled
call
out
saying
hello.
This
is
a
conference
that
is
coming
up
and
is
very
exciting
and
we
will
be
at
so
I
hope
that
I
can
see
some
of
you
there.
It's
actually
coming
up
in
two
weeks,
which
is
a
little
wild.
It
is
so
close,
but
this
is
wasam
Khan
hosted
by
the
Linux
Foundation
it's
going
to
be
in
Bellevue
Washington.
A
good
couple
of
us
have,
let's
see
that's
not
it.
A
C
Yeah
then
grid
it's
a
bit
easier
just
to
see
how
much
content
there
really
is.
You
know
somebody
on
the
call
had
hit
me
up
about
recommendations
for
conferences
and
things
to
do.
C
Obviously,
the
big
one
I'd
love
to
recommend
is
there's
tutorials,
so
there's
a
classmatic
crash
course
right
here
at
the
opening
of
the
of
the
day,
that's
a
strong
recommend
there
and,
as
you
scroll
down
into
the
First
Data
conference
here,
obviously
Bailey's
keynote
will
be
great,
both
she's
on
day,
two
I
think
I
do
a
sponsored
keynote
here
on
day.
One-
and
you
know
we
just
worked
really
really
hard
to
invite.
C
You
know
everybody
that's
doing
interesting
stuff
in
webassembly
by
a
whole
bunch
of
topics
here
you
know,
there's
database
talks,
there's
performance
and
troubleshooting
there's
plug-in
use
cases.
You
know
we
really
tried
to
open
the
aperture
here.
Bailey
and
I
are
both
co-chairs
of
this
conference
and
invited
in
some
of
the
folks
I
feel
like
that.
We
really
admire
most
in
in
the
conference,
so
I
strongly
encourage
you
to
attend
in
person.
C
So
you
get
that
hallway
comments,
even
the
best
track
and
outside
of
that
the
conference
will
be
streamed,
live
so
for
those
of
you
that
are
unable
to
attend.
You
should
be
able
to
log
on
and
just
watch
via
YouTube,
so
I'll
be
MC
in
one
track
and
Bailey.
Oh
God,
we
can't
make
you
we
can't
also
make
UMC
in
another
track.
Okay,
maybe
we
didn't
ask
you
to
do
that,
yet
all
right
you've
too
much
going
on
all
right.
C
A
Yeah,
if
anybody
has
figured
out
the
whole
human
cloning
thing,
ethics
aside,
please
let
us
know
we
need
more
Bailey's
if
we
could
get
two
or
three
Baileys.
That
would
really
help
us
out
going
into
this
conference.
So
please
drop
me
a
DM
and
slack.
Let
me
figure
that
out.
E
Yeah
I
I
think
one
another
one
that
I
wanted
to
shout
out
is
that
we'll
be
running
a
host.
I
will
be
hosting
a
panel,
but
there
will
be
representation
from
Apple
and
V8,
so
Google
and
Firefox
all
in
one
little
one
little
panel,
so
I
I'm
most
excited
about
that.
I
had
to
go
through
a
lot
of
legal
and
PR
people
to
get
everybody
to
be
excited
about
that.
Let
us
let
us
actually
do
it.
E
So
that's
another
one,
I
wanted
to
give
a
shout
out
for
and
we'll
be
talking,
basically
webassembly
standards.
E
The
other
event
that
we
didn't
shout
out
yet
is
bacon,
or
at
least
that's
our
code
name
for
it,
the
by
code,
Alliance
conference,
and
so
that
is
on
that
Friday
adjacent
to
lazomcon
and
we're
calling
it
componentize
the
world.
It
is
us
working
with
some
of
this
new
tooling
that
we've
been
building
for
webassembly
components,
yeah,
thank
you
Brooks
and
it's
free.
You
get
to
come,
hang
out
with
folks.
E
All
of
us
will
basically
be
there,
but
also
guy
Bedford,
who
created
Jayco
and
also
works
on
the
tc39
standards
for
a
lot
of
things.
E
Peter
heon,
who
created
cargo
component,
so
all
the
books
that
are
building
a
lot
of
the
ecosystem,
tooling,
are
going
to
be
around
and
will
be
collaboratively
hacking
and
getting
feedback
on
how
to
componentize.
Basically,
the
entire
world
bootstrap
a
components,
native
ecosystem,
so
I
think
that'll
be
an
especially
fun
event.
E
And
and
monetize
the
world
will
be
virtual,
but
I
wish
you
could
join
since
we're
at
the
same
state.
A
E
If
you're
going
to
be
virtual,
we're
going
to
have
a
couple
different
laptops
set
up
in
different
places
and
we've
got
MCS
already
on
the
hook
like
Joel,
Alex
and
Guy
Bedford,
so
I
think
it'll
be
a
good
time.
A
I
I
know
that
that
was
effectively
what
we
had
planned
for
the
community
agenda
today.
So
now
is
great
time
for
open
floor.
This
is
just
just
general
time
if
anybody
has
questions
about
wasm
cloud
or
something
that
they
wanted
to
chat
through
for
for
your
use
case
or
just
general
things
about
the
webassembly
ecosystem.
That
was
a
now's
a
great
time
to
chat
about
that.
B
I've
got
a
quickie
here
just
for
us
noobs.
Where
is
the
best
place
to
start
asking
dumb
questions?
So
what
sort
of
chat
slack
you
know
posts
where,
where
where's
the
best
place
to
go.
A
Anybody
who's
welcome
to
go
and
join
and
I
would
say
any
questions
there
can
go
in
the
wasm
cloud
Channel
anything
around
the
the
entire
wasmcloud
ecosystem.
I
think
we
also
have
a
webassembly
channel
as
well
for
more
specific
web
assembly
questions,
but
you're
not
going
to
get
chastised
by
putting
it
in
the
in
the
WASP
Cloud
Channel,
because
I
know
that
people
really
appreciate
that
too
cool.
A
Thank
you
additionally,
just
for
anybody
who
is
involved
in
the
cloud
native
space
and
doesn't
feel
like
adding
a
new,
a
new
slack
to
their
to
their
repertoire,
you're
always
welcome
to
join
the
wasm
cloud
channel
in
the
cncf
slack,
the
cloud
native
Computing,
Foundation
slack.
We
do
have
a
channel
there
because
wasmcloud
is
the
cncf.
It's
a
Sandbox
application.
Runtime
I'd
like
to
actually
start
getting
some
things
posted
like
our
community
call
and
and
things
over
there.
A
It's
just
a
little
harder
to
have
a
bunch
of
different
discussions
at
the
same
time,
because
it's
just
one
channel,
but
if
anybody's
on
the
scene
and
see
it
cncf
slack
wow.
Please
come
say:
hi.
A
All
right
everyone-
well,
this
might
end
up
being
a
short
community
meeting.
I
know
that
we're
all
pretty
heads
down
with
working
on
conference
talks
and
implementation
on
the
wasm
cloud
slide.
It's
a
really
exciting
point
in
the
ecosystem,
where
we're
we're
starting
to
really
Embrace
these
webassembly
standards
and
get
them
implemented
and
see
them
working,
which
is
which
is
really
fun
so
I
think
we
can
go
ahead
and
end.
This
call
now,
thank
you
all
for
for
coming,
especially
Dave.
A
Thank
you
for
coming
as
a
first
time
member
and
then
you
know
just
getting
to
look
at
the
people
who
are
on
the
call
now
Dwayne,
it's
been
a
long
time,
so
really
really
great
to
see
you
and
advance
and-
and
everybody
I
think
it's
worth
mentioning
for
anybody
who's
watching
this
on
on
live
stream
as
well,
that
we
do
have
this
meeting
like
being
able
to
come
in
here
and
ask
questions
and
interface
with
all
of
us.
It's
a
completely
open
meeting.