►
From YouTube: wasmCloud Community Meeting - 15 March 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
A
Nope,
it's
me
sorry
about
that.
I
figured
it
out
okay
anyway,
so
the
agenda
today
we're
gonna
start
with
I'm
gonna
do
a
little
bit
of
demo
on
link
definitions
and
Link
names,
meaning
usage,
some
powerful
things.
A
You
can
do
it's
actually
what
what
powered
a
really
cool
thing
about
our
scale
talk
a
couple
of
days
ago,
so
I
want
to
talk
about
that
I'm
gonna,
throw
it
over
to
Roman
who's
gonna,
give
a
Wazi
wasm
Cloud
component
model
update
where
we
are
with
wasmcloud
and
then
to
tailor
to
talk
about
proper
usage
of
our
wasm
Cloud
GitHub
projects
and
kind
of
rolling
through
a
little
example.
A
There
we'll
talk
about
scale,
the
conference
that
Taylor
and
I
went
to
this
past
weekend
a
little
bit
of
a
little
bit
of
a
call
out
there
and
then
talk
about
the
hackathon
that
cosmonic
officially
is
putting
on,
but
we're
actually
going
to
be
doing
some
office
hours
today.
So
without
further
Ado,
let's
go
ahead
and
get
started
so
I
want
to
talk
a
little
bit
about
link
definitions
and
link
names,
so
throughout
our
throughout
the
purpose
of
creating
wasmcloud
applications.
A
We
talk
a
lot
about
these
link
definitions
and,
most
of
the
time
when
people
are
using
them,
you
know
you
the
their
biggest
purpose.
Their
main
purpose
is
to
link
an
actor
to
a
capability
provider
at
runtime
optionally,
providing
some
configuration
for
that
specific
link.
So
the
link
does
two
things
in
that
main
purpose:
one.
It
tells
the
wasm
cloud
runtime
across
the
whole
or
any
wasn't
Cloud
runtime
across
the
lattice,
that
this
actor
is
allowed
to
communicate
with
this
provider.
A
And
then
the
configuration
step
is
what's
really
important
for
setting
up
things
like
runtime
config,
like
for
an
HTTP
server,
hey,
you
need
to
listen
on
this
port
in
order
to
receive
an
HTTP
request
or
for
the
redis
key
Value
Store,
hey,
you
need
to
connect
for
for
the
redis
connector,
you
need
to
connect
to
this
redis
URL.
So
this
is
how
you're
able
to
do
runtime
configuration
what
you
may
have
built
into
your
application
before
you
change
based
on
environment.
A
That
is
all
kind
of
done
at
runtime,
but
one
specific
part
of
Link
definitions
I
feel
like
we
most
of
the
time
just
gloss
over,
and
that
is
the
link
name
and
I
want
to
talk
about
that
specifically
today,
because
it's
probably
not
needed
in
I
would
say
approximately
90
percent
of
the
use
cases
for
wasm
cloud.
You
don't
have
to
use
it
you'll
see
that
it's
actually
here
on
the
Watson
Cloud
dashboard.
A
You
see
a
lot
of
defaults
down
the
down
the
tabs
here
for
providers
and
for
link
definitions
because
default
works
most
of
the
time.
Normally
you
don't
have
to
supply
a
link
name.
So
a
link
name
as
defined
in
our
documentation
is
a
logical
separation
that
you
can
run
different
instances
of
capability
providers
on
most
of
the
time.
If
you're
just
using
the
HTTP
server,
you
can
run
it
on
default.
You
can
link
on
default
and
that
all
works
fine
and
good.
A
But
for
some
specific
use
cases
you
can
actually
do
some
really
cool
things
by
having
additional
link
names.
So
let
me
let
me
go
ahead
and
show
you
one
of
those
examples.
So
I
have
the
key
value
counter
application
here.
This
is
just
our
example
that
we
use
all
the
time
and
what
I
actually
have
going
on
I'm,
just
going
to
rearrange
things
a
little
bit.
I
have
an
HTTP
server
provider,
that's
running
on
my
local
machine
and
on
a
Raspberry.
A
A
And
so
now
we
basically
told
wasmcloud
hey
this.
Webassembly
actor
is
allowed
to
communicate
with
this
HTTP
server,
and
this
this
redis
database.
The
thing
that
I
didn't
really
talk
about.
We
don't
do
for
a
lot
of
our
demos.
I've
actually
set
up
this
HTTP
server
with
the
link
name
of
local,
and
there
is
something
really
cool
that
you
can
do
with
this
so
I'm
going
to
switch
over
to.
Let
me
actually
just
share
my
whole
screen.
A
It
might
be
easier
because
I'm
going
to
go
back
and
forth
all
right
that
should
come
up
okay,
so
this
kiwi
counter
is
linked
to
http
server
on
local
and
redis
on
local
another
alternate
view
in
the
WASP
dashboard.
This
is
pretty
much
what
you're
used
to
so
locally.
What
I've
done
is
created
a
listener
on
localhost,
8080
and
so
I
can
curl
or
8
000.
I
can
curl
the
counter
at
this
localhost
endpoint
and
get
back
the
counter.
So
this
is
you
know.
A
This
is
the
way
that
we
work
with
the
KB
counter.
Actually,
this
is
the
new
and
improved
one
that
has
the
UI,
so
I
want
to
go
ahead
and
use
that
I
can,
of
course,
now
I'm
going
to
do
it
and
then
okay,
it's
loading,
but
I,
can
hit
localhost,
8000
and
I
can
actually
see
that
I'm
hitting
this
actor
now,
let's
say
I'm
I'm
doing
this
as
a
development
process,
I'm
running
everything
on
local
I'm,
developing
and
now
it's
time
to
move
this
application
to
like
a
QA
or
like
a
staging
environment.
A
Basically,
I
want
to
take
this
from
my
local
machine
and
put
it
in
the
cloud,
so
you
can
actually
use
Link
names
to
do
this
in
a
a
gradual
way,
even
if
you're
doing
this
imperatively,
like
through
the
Watson
Cloud
dashboard
or
through
cosmonic
I,
can
actually
create
multiple
links
to
the
same
capability
using
link
names.
So
this
HTTP
server
is
running
on
local.
A
The
localhost,
endpoint
or
I
can
hit
the
KV
counter
by
actually
going
to
this
URL,
the
URL
that
that
cosmotic
is
exposing
and
I'm
actually
using
the
bucket
Community.
That's
why
the
the
counter
is
a
different
number.
So
now
this
is
effectively
how
you
can
do
all
kinds
of
canary
testing.
You
know
kind
of
like
an
A
B
failover
to
use
different
link
names
and
have
them
all
route
to
the
same
actor.
The
same
database
and
the
cool
thing
is
that
again,
there's
nothing
in
your
code.
A
A
Another
way
that
you
can
use
linked
names
is
not
from
a
provider
to
an
actor,
but
instead
you
know
the
other
direction
so
pointing
from
the
key
value
counter
to
a
provider
that
has
a
different
link
name
now,
if
again,
if
we
look
at
the
code,
the
way
that
we
create
this
increment
request,
we
create
a
key
value
sender,
a
new
key
Value,
Center
sender
and
then
call
increment
on
it.
This
is
just
interacting
with
the
key
value
store.
A
The
process
for
using
a
different
link,
name
with
a
provider
call
you
actually
do,
have
to
specifically
call
out
and
that's
with
the
new,
with
link
function
on
any
of
the
senders
that
you
have
for
a
capability
provider
so
doing
key
value.
Sender
new
is
effectively
the
same
as
doing
key
value.
Sender
new,
with
link
on
default,
so
we're
creating
a
new
sender
to
the
provider
on
link
name
default
and
then
sending
it.
A
The
increment
request
now,
if
I
were
to
do
the
same
thing
that
I
was
doing
before,
like
with
a
local
host
endpoint
I,
would
have
to
I
would
have
to
specify
the
link
name
as
local
now.
What
this
is
really
useful
for
what
we've
actually
done
before
in
a
couple
of
demos,
is
have
an
inbound
and
an
outbound
Nats
connection
and
use
a
different
Nats
configuration
for
each
one.
A
So
we
publish
on
different
topics
than
what
we're
receiving
on,
which
is
pretty
sweet,
but
really
the
the
ability
for
for
for
this
for
publishing
the
different
providers
lets
you
do
fancy
things
like.
Okay,
I'm
gonna
store
this
information
in
more
than
one
database
with
the
same
capability.
A
So
link
names
are
kind
of
there,
so
you
can
provide
additional
configuration
to
those
capability
providers,
so
that
was
most
of
what
I
wanted
to
talk
about
today
and
I
really
hope
that
this
would
generate
a
couple
of
questions
talking
about
link
names
because
again,
most
of
the
time
when
you're
developing
with
wasmcloud,
you
can
just
use
the
default
link.
Name
you're,
not
doing
anything.
That
requires
multiple.
But
this
really
lets
you
do
the
different
League
names
really
lets.
A
A
So
any
any
questions
on
link
names.
A
I
just
saw
the
comment:
I
typed
one,
two:
seven:
zero:
zero:
zero.
Instead
of
zero
zero
one
cool
thanks,
Kevin.
A
All
right,
well
what
I?
What
I
really
hope
to
do
is
put
together
a
couple
of
examples
for
this
in
our
examples
repository
so
you
know
the
the
example
of
routing
to
different
databases,
and
you
know
doing
gradual.
A
b
testing
from
one
environment
to
another
is
really
a
neat
aspect
of
Link
names
that
is
kind
of
sitting
there.
A
In
the
background,
if
you
didn't
know
about
the
feature
so
love
to
actually
get
that
formalized
in
a
couple
examples
and
and
get
that
out
to
you
all
foreign
in
terms
of
the
demo,
what
I'm
going
to
go
ahead
and
do
next
thing
on
our
agenda
is
talking
about
Wazi,
wasm,
Cloud
component
model
updates,
so
Roman
I
think
I'll
go
ahead
and
throw
it
over
to
you
look.
Let
me
give
you
screen
sharing,
so
you
can
share.
If
you
want.
C
C
Okay,
let's
do
watch
so
hey
everyone,
so
as
you,
oh
probably
already
I'm
working
on
this
watching
Cloud
cross
host
SDK
and
we
also
working
currently
on
Kevin,
actually
is
working
on
wrapping
that
host
in
a
nif
to
actually
use
that
in
odd
and
there's
a
FDR
for
that.
C
C
So
actors
can
now
be
both
assembly,
module
and
diversary
component,
and
we
have
a
nice
actor
abstraction
for
it.
So
you
know
that
you
don't
actually
need
to
care
about
the
low
level
details
of
this,
because
essentially
you
can
compile
after
constructing
runtime.
You
can
then
compile
your
room
assembly
and
you
can
just
call
whatever
function.
You
want
in
that
webassembly
actor.
So
it
could
be
a
component.
It
could
be
a
module,
it
doesn't
really
matter.
C
There
are
times
going
to
determine
that
for
you,
and
essentially
this
is
where
you
would
call
things
like.
Http
server,
you
know,
handle
requests
right
and
you
pass
some
payloads
or
not.
If
there's
no
payload
to
pass
by
the
way
are
looking
at
my
local
liquidation
right
now,
but
this
the
current
development
implementation
actually
now
published
on
what
about
github.io
Slash
lesson
Cloud
mind
capital
c,
so
that's
very
useful,
I
think
for
development.
Well,
at
least
we
have
the
yeah
the
Creator
top
list,
I
actually
notice.
C
We
already
had
some
crazy
phones
before
so
I'm,
probably
gonna
have
to
think
about
virtually
there,
but
yeah
I'm
doing
some
changes
by
the
way
to
the
API.
You
can
notice
that
there's
quite
a
bit
quite
a
few
engineering
about
the
severe
down
in
the
new
situation,
so
there's
CPR
coming
for
this,
also
making
this
easier
to
use
so
in
general,
I'm,
just
working
on
polishing
the
API
right
now.
C
So
one
of
the
things
I
can
show,
for
example,
is
runtime,
so
we
can
now
construct
a
runtime
given
just
a
simple
callback
for
the
yeah
for
handling
cost
calls
right,
so
he's
going
to
use
just
default
built-in
Handler
implementations
and
you
could
just
pass
it
around
an
arbitrary
handle
for
invocation
by
the
way.
Yes,
we
also
introduced
I
introduced
the
struct
for
the
sales
application,
so
it
now
contains
all
the
fuels,
so
it
also
the
signatures
a
bit
smaller.
So
it
explains
that
easier
to
implement
and
maintain
yeah.
B
Basically,
what
we're
working
on
is
a
rust
host
SDK.
So
how
do
I
load
actors
basically
within
lesson,
called
that
that's
what
it
does
and
it
provides
a
very
high
level
API
that
Roman
was
showing,
and
he
he's
just
refined
that
even
more
so
it's
super
easy
for
embedders
to
call
this
top
level.
B
High
level
like
invoke
this
actor
and
and
the
high
level
piece
doesn't
even
need
to
know
if
it's
working
with
a
module
or
if
it's
working
with
a
component
we've
we've
we've
popped
components
before,
but
basically
it's
a
different
binary
API
that
provides
high
level
types
so
that
I
can
take
different
components,
maybe
of
different
libraries
and
Link
them
together.
I
can
also
take
things
that
weren't
built
for
Watson
Cloud,
for
example.
B
This
is
a
secret
for
watching
what
will
happen
next
week
at
Wesson
IO,
but
link
that
with
another
component
that
lets
me
run
it
within
wasenclaw,
which
is
very,
very
powerful.
So
basically,
one
of
the
first
places
that
you
can
use
was
a
component
model
support
without
doing
a
lot
of
heavy
lifting
yourself
and
Romans
made
that
super
easy,
there's
it's.
This
is
all
it's
on
the
preview
to
prototyping
Branch
using
you
know,
preview,
two
drafts
blah
blah
blah
all
the
like
experimental.
B
Please
don't
ship
this
to
production,
kind
of
kind
of
verbiage,
but
this
is
this
is
one
of
those
first
places
that
we're
able
to
dig
in
and
experiment
Brooks.
A
Yeah
I
I
wanted
to
ask
a
couple
of
a
couple
really
simple
questions.
What
what's
the
because
I
know
that
there
are
a
couple
of
different
web
assembly
engines?
What
webassembly
engine
is
running
under
this
Roman.
C
Yeah,
so
that's
awesome
time
to
use
all
the
latest
developers
from
the
bytecode
the
lines
so
things
like
providing
the
components
enabled
YZ.
So
it's
all
it's
a
tricky
so
that
that
we
are
making
it
simpler.
So.
A
So
that's
kind
of
the
whole
point
of
this
okay,
nice
and
I
wanted
to
ask.
You
know:
I
know
that
you
mentioned
you
know.
If
anybody
had
any
questions
about
implementation,
do
you
have
any
examples
that
people
could
look
at
for
like
what
does
it
look
like
to
instantiate
a
runtime
and
then
run
an
actor.
C
So
I,
actually,
since
the
beginning
of
the
Streetball
I've,
been
maintaining
the
example
like
there's
an
echo
example,
which
is
just
you
know,
running
the
echo
actor
but
also
good
place
to
look
at
could
be
the
test,
so
there's
the
components
and
there's
an
actor:
a
module
both
are
compiled
at
Toronto
they're
compiled
using
just
cargo
functionality.
C
So
you
can.
You
can
also
look
at
those
but
like
if
you,
if
you
would
want
to
see
like
so
this
is
basically
what
you
would
do
with
wash
right,
where
you
would
sign
your
components
right
and
build
it
and
sign
it,
and
then
that's
what
it
takes
to
yeah
essentiate
the
runtime.
So
you
just
pass
it
some
function
which
handles
host
calls
in
this
case.
It's
just
well,
it
doesn't
do
anything,
but
this
is
basically
where
you
would
evoke
Nets.
C
You
know
to
send
your
host
call
overness
and
get
back
a
response
and
so
yeah,
and
then
you
can
just
read
your
actor.
So
in
this
case
is
going
to
well
read
about
our
device.
You
know
compile
the
component,
the
kapali
actor,
either
a
command
or
a
module
right,
and
then
you
can
just
do
actor
just
call
like
I
showed
earlier.
C
Hopefully
this
is
big
enough
for
me.
I'll
do
what
it
is
so
yeah,
but
this
is
basically
what
it
takes
to
instantiate
the
runtime
load
applicator,
but
pre-compile
it
right
and
just
call,
and
you
can
also
call
nectar
multiple
times
so
after
it's
meant
to
be
a
long-lived
object
right.
So
it's
it's
easy
to.
It
is
cheap
to
call
it
right.
So
it's
only
pre-compiled
in
memory
and
you
could,
you
know,
store
it
somewhere.
Maybe
you
know
reuse.
It.
A
And
I
I'm,
just
gonna,
maybe
drive
this
whole
point
home,
because
this
is
my
understanding,
but
tell
me
if
I'm
wrong.
So
all
of
this
stuff
is
the
it's
the
Watson
Cloud
Library.
You
would
interact
with
if
you're
writing
a
waslam
cloud
host
or
or
looking
at
contributing
on
on
our
side,
but
from
the
wasm
cloud
or
really
webassembly.
Now
application
developer
standpoint.
They
don't
really
need
to
interact
with
these
Primitives
right
like
it's.
C
Yeah,
so
this
is
just
Quantum
class
specific
just
for
the
host
we
yeah
just
runs
any
normal
web
assembly
modular
components.
Of
course
we
use
the
wasn't
called
API
in
the
component
model,
for
example
right
or
the
API
in
in
the
in
the
bus
API
in
the
in
in
the
modules
right.
So
again.
What
I
guess
watch
takes
care
of
that
and
then
basically
just
take
a
component
for
auto
module
and
just
run
it
in
awesome
cloud.
B
Yeah
Brooks,
that's
a
good
question
so
differently.
Kevin
has
been
working
on
creating
a
nif
that
embeds
this
host
crate.
So
before
we
were
using
a
third
party
Library
made
by
an
amazing
maintainer
Tessie,
but
it's
that
was
a
general
journal,
purpose,
Elixir
Library
and
there
there
was
quite
a
bit
of
like
and-
and
you
know
this,
because
you
did
a
lot
of
the
performance
analysis.
B
Some
copying
across
the
nif
boundary
there's
complexity
in
the
breadth
of
the
API.
That
needs
to
be
provided
for
a
general
purpose,
Library
versus
something
that's
very
specific
to
Watson
Cloud's
use
case,
and
so
with
this
host
to
SDK.
We're
able
to
get
something,
that's
specific
to
what
we're
using
eliminate
boundaries
across
function,
calls
between
like
the
nif
and
what
happens
on
the
rough
side
of
things
and
still
be
able
to
take
advantage
of
all
the
existing
stuff
that
we've
done
within
the
OTP
host.
A
Oh
my
hand
is
just
continually
staying
up.
Well,
I
did
have
one
more
question
and
then
I
will
finally
yield
the
time.
So
I
know
that
you
know
we.
We
talk
about
this
as
the
wildly
profuse
bleeding
edge,
it's
very,
very
new
stuff,
with
with
the
status
that
we're
in
right
now
and
implementing
it
as
a
nif
in
the
host.
How
do
we
feel
about
you
know
we're
about
to
release
wasmcloud
0.61?
A
This
seems
to
have
full
backwards
compatibility
with
regular
Watson,
Cloud
actors.
So
that's
great.
How
do
we
feel
about
releasing
this
in
the
next
version
of
wasmcloud
or
or
maybe
even
like
the
next
next
version
like?
Are
we
pinned
to
a
really
specific,
like
git,
hash
or
something
in
wasm
time
and
using
like
the
rust
I?
Don't
know
rust
super
nightly
like?
Is
there
any?
Are
there
any
concerns
there
in
terms
of
breaking
changes
and
and
actually
releasing
this
in
awesome
cloud.
E
Oh
yeah
I
feel
bad
because
I
was
just
gonna.
I
was
just
gonna,
make
a
joke.
I
was
going
to
suggest
that
the
the
version
of
all
the
stuff
that
we're
using
is
pinned
on
the
hard
drive
in
my
desk.
So
we
should
be
safe.
B
Yeah,
we
should
be
totally
fine,
we're
using
rest
nightly,
like
the
latest
nightly.
That's
got
some
bug
fixes
for
the
component
models,
and
so
a
lot
of
the
pieces
and
parts
here
are
obviously
moving
very
quickly,
especially
because
we're
not
the
only
ones
that
are
are
driving
to
a
very
cool
dinner
for
wazam
Io,
which
is
next
Wednesday
and
Thursday,
and
so
basically
it's
pretty
it's
pretty
active
right
now.
B
So,
as
far
as
components
go,
we
might
be
a
little
bit
more
slower
to
release
that,
because
we
know
that
it's
missing
some
things
that
we
wanted,
but
we
were
willing
to,
like
you,
know,
toothpick
and
duct
tape
together
for
a
demo,
but
for
the
like
route
of
hey,
we've
got
existing
actors,
they're
compiled
to
wazen
32,
but
no,
no,
no,
like
just
a
plain
old
core
module.
B
I
do
see
that
as
in
a
a
very
soon
thing,
I'm,
not
gonna,
say
it's
next
OTP
release
because
hey
what
if
we
have
a
patch
release
right
that
that's
all
cool,
but
it
does
feel
very
close.
We
need
to
get
some
feedback
and
that's
definitely
why
we're
like
hey,
y'all,
we're
making
a
thing,
and
it's
actually
looking
like
it's
come
together
really
fast,
so
yeah
would
love
other
people
to
get
some
eyes
on
it.
A
Well,
hey
I
know
that
we
discussed
a
couple
of
yeah
rc1.alpha
dot.
Experimental
I
know
that
we've
discussed
a
couple
of
ways
to
bring
experimental
or
a
new
features
into
the
Watson
Cloud
hosts.
Maybe
when
we're
still
like,
we
don't
want
them
to
become
mainstream
features
because
they're
still
likely
to
like
have
breaking
API
changes
and
we
want
to
release
stable
things
in
the
Watson
Cloud
host.
But
I
I
would
be
very
happy
to
have
a
discussion.
A
Maybe
in
the
next
I
mean
we
can
do
it
now,
but
we
have
more
stuff
on
the
agenda.
Maybe
maybe
at
the
end
of
this
call
where
we
can
talk
about
having
a
feature
flag
for
was
on
cloud
where
you
know
you
can
run
it
with.
You
can
run
with
components.
A
You
have
to
run
it
with
an
environment
variable
enabled
to
kind
of
tick
that
box
and
the
API
is
likely
to
change,
but
I
mean
I
would
be
really
happy
to
have
that
in
the
Watson
Cloud
host,
especially
with
the
the
backwards
compatibility
of
of
the
notes.
Yeah
exactly
the
same
way.
Bailey
just
put
in
the
chat
which
Bailey
you
can
say
it
I
don't
have
to
read
it,
but.
B
Yeah,
so,
basically,
right
now,
this
host
SDK
enables
a
the
component
model
flag
on
wasm
time
on
the
Upstream
plasm
runtime,
that
that
we
embed
Roman.
C
Yeah
also
there's
a
k
itself
has
a
couple
of
model
a
feature
flag
as
well,
and
it's
absolutely
possible
to
also
like,
for
example,
we
could.
If
you
were
to
use
a
component
model
for
flag,
then
we'd
use
the
latest
watching
time
and
if
you
didn't,
we
could
use
another
latest
stable,
for
example
right.
So
that's
totally
possible
to
do
as
well.
A
Nice
yeah
I
love
the
idea
of
having
that
discussion,
because
I
don't
I,
don't
want
to
hold
something
so
cool
back
forever.
While
we
wait
for,
like
an
arbitrary
point
of
stability,
cool
all
right,
I,
totally
monopolized
a
lot
of
that
time
to
ask
a
ton
of
questions.
Does
anybody
else
have
any
questions
for
for
Roman
and
Bailey.
A
A
All
right,
let's
see,
I
knew
that
Taylor
was
coming
in
Taylor
I,
see
you.
Are
you
ready
to
talk
about
our
GitHub
projects
and
show
us
some
cool
stuff.
D
Yep
now
that
I
have
that
you
gave
me
sharing
permissions
just
in
time.
Brooks
I
think
this
is
the
right
one.
Yes,
okay,.
D
The
share
okay,
hi,
everyone
hi.
This
is
your
local
Friendly,
Community
Wrangler,
here
again
I'm
here
to
talk
to
you
about
projects
which
we
mentioned
before
and
I
just
want
to
mention
one
more
time
so
buckle
in
and
stay
ready
for
all
this
okay.
D
So
what
we're
doing
I
just
want
to
go
back
and
review
what
we're
doing
with
GitHub
projects
and
I
wanted
to
see
if
people
liked
what
we
were
doing
and
Brooks
brought
up
the
really
good
suggestion
that,
as
we
talk
about
it
one
more
time
before
we
start
adopting
it
everywhere.
D
That
I
should
like
show
how
this
could
work
show
how
this
could
work
like
when
we're
using
this
for
real
so
like
what
we're
expecting
like
maintainers
of
projects
to
do,
and
then
what
people
in
the
community
can
see
and
look
at
inside
of
these
projects.
So
I'm
just
gonna
do
like
two
issues
like
what
happens
through
here
to
show
you
like
what
we're
doing
and
how
we
expect
this
to
be
used.
So
what
happens
is
anything?
D
That's
new
comes
straight
PR's
and
issues
comes
into
this
Trio
triage
section
and
we're
able
to
come
click
on
this
and
like
get
the
The
View
through
here
and
I,
put
all
of
our
current
ones
on
there,
because
I
wanted
to
make
sure
we
had
triage
them
all
into
the
right
buckets,
even
though
we've
talked
about
it
so
like
right
here
we
have
this
idea
of
like
oh,
like
can
I
do
something
with
like
common
typos
and
do
all
that
and
there's
like
like
aliases
or
like
spelling
harder.
D
You
know
like
Brooks,
Brick
City
didn't
want
to
learn
how
to
spell
so.
Essentially,
this
issue
looks
like
okay.
We
know
what
it
is
it's
well
scoped
somebody
could
take
it.
So
I
can
just
move
this
to
like
to
do,
which
means
it
is
open
and
ready
for
someone
to
take
and
then
over
here
which
we
might
have
I,
don't
even
see.
If
there's
one
that's
actually
more
like
a
discussion,
I,
don't
know
if
we
have
one
left
on
here.
D
Maybe
this
one,
but
if
not
I,
have
one
that
I
can
pull
out
can't
so.
Okay,
yeah
this
one's
pretty
straightforward
too
he's
just
saying
this
is
another
one,
that
this
is
Brookshire.
Basically,
if
Brooks
wrote
it
I
don't
have
to
worry
about,
it
is
what
I'm
learning
here,
and
so
this
one
is
also
pretty
much
just
in
to
do
now.
D
Let
me
show
you
one
that
we
that
I
was
working
on
this
morning
actually
with
Brooks,
as
we
were
going
through
this
about
one
that
might
require
some
more
discussion
or
isn't
necessarily
fully
scoped,
and
that's
this
one
where
we
discovered
a
weird
bug,
turns
out
it's
Tokyo.
We
have
no
idea
why
that's
causing
the
web
assembly
modules
to
pull
incorrect
sizes
so
yeah.
D
We
have
no
idea
why
that's
happening
but
like
this
isn't
super
this
isn't
super
well
scoped
someone
couldn't
come
in
who's,
looking
for
like
new,
like
they
want
to
get
involved
with
wash
or
whatever,
and
so
we
said
this
is
still
in
discussion
now,
if
you're,
like
an
advanced
wash
user,
of
which
many
people
in
this
call
are.
This
is
totally
open
for
you
to
go.
Try
to
look
at
and
figure
out
what
in
the
world
is
happening
here,
because.
D
But
like
those
are
the
kinds
of
things
that
go
into
discussion
like
oh,
hey,
we're
working
through
this
RFC
we're
going
through
this
stuff,
and
it
goes
right
here
and
then
you
come
over
and
you
say
you
can
take
a
look
at
these
and
you
say:
okay,
these
are
all
the
to
Do's.
These
are
things
that
could
need,
could
need
work.
D
And
so
especially,
if
it's
an
issue,
you
can
come
here
and
say:
hey,
you
know
what
like
I
want
to
be
able
to
consolidate
those
two
commands,
so
you
can
look
at
it
and
then
just
you
can
you
can
come
here
to
the
comments
and
mention
like
hey
I'd
like
to
take
this
and
I,
don't
think
in
GitHub
still
we
can
like
assign
you
unless
you're
part
of
like
the
wasm
cloud
org,
but
we'll
basically
note
that
it's
ready
to
go
and
you're
working
on
it
and
we'll
move
it
in
progress
so
that
people
know
that
this
is
being
worked
on
and
no
one
else
takes
it
and
then
it
goes
over
to
done.
D
And
then
this
gets
cleaned
up
every
once
in
a
while.
If
I
set
up
the
workflows
right,
which
I
can't
remember
if
I
did
so,
that's
how
this
is
going
to
work,
you
can
act
and
the
and
it
should
be
easy
to
access
for
every
single
thing.
So
if
we
go
to
go
to
wash.
D
E
D
Can
also
see
them
viewed
here,
grouped
by
tags,
so
if
you
want
to
see
like
which
things
are
bugs,
which
things
are
enhancements
and
so
on
you're
able
to
come
in
here
and
see
it
viewed,
viewed
grouped
basically
by
like
any
Milestone,
we
put
them
in,
we
haven't
really
used
the
Milestones,
yet
I
set
them
up.
We
might
not
use
them,
though,
but
you'll
still
be
able
to
see
everything
grouped
together
by
tag
or
label.
I
should
say
so
anyway.
D
That's
the
big
overview
of
that
I'm
going
to
go
ahead
and
make
sure
there
is
nothing
in
chat
that
actually
had
to
do
with
me
looks
like
we
were
talking
about
water,
so,
okay
yeah.
It
doesn't
look
like
there's
anything
there
right
now
that
we
need
to
talk
about
any
other
questions
from
the
audience.
D
A
Thank
you,
Taylor,
speaking
of,
if
you
really
enjoy
Taylor
talking
and
having
him
talk
at
you
and
not
having
the
opportunity
to
ask
him
questions,
we
actually
Taylor
and
I
went
to
scale
which
is
Southern
California,
Linux,
Expo
yeah
last
weekend,
I'm
wearing
the
shirt
right
now
it
was
a
lot
of
fun.
We
met
a
couple
of
met,
a
couple
of
cool
people
and
and
had
some
fun
doing
some
talks.
A
What
I
will
share
is
just
the
links
really
quick
to
our
two
talks:
I'm
going
to
throw
them
in
the
chat.
This
one
is
Taylor's
with
timestamp
and
everything
Taylor's
talk
that
he
did
on
Friday
a
webassembly,
a
recovering
kubernetes
Engineers
view
of
the
future.
This
is
at
the
co-located
kubernetes
community
day
and
I.
Think
people
had
a
lot
of
a
lot
of
fun.
With
this
one.
Did
you
have
any
like
high
level
snippet?
You
want
to
say
for
this
one
Taylor.
D
Yeah,
if
you're
one
of
the
people
who
came
from
the
kubernetes
space
and
or
are
still
running
kubernetes
services
in
production,
which
is
probably
a
lot
of
people-
and
you
want
to
use,
wasn't
cloud
with
it.
This
shows
you
exactly
how
to
do
it
with
cosmotic
or
with
normal,
was
in
Cloud.
It's
I.
Did
it
with
cosmonic
I
I
mean
I,
could
literally
whip
it
up
right
now,
but
yeah
I'm,
not
gonna,
do
promise
anything
anyway.
So
the
so
yeah
you're
you're
completely
welcome
to
try
anything.
D
I
actually
did
in
this
talk,
but
that's
the
big
one
is
that
I
show
kubernetes
working
with
this
like
live
and
failing
over
between
things
like
my
laptop
and
a
cosmonic,
hosted,
awesome,
Cloud
host
and
then
a
bunch
of
hosts
running
in
kubernetes,
and
so
like
it's
a
fun
one.
It's
where
it's
it's
worth
watching
at
least
for
the
demo
you're.
D
Just
provided
some
advice,
yeah
I
found
some
buttons
when
I
was
doing
it
and
those
bugs
were
already
released.
Just
the
latest
chart
version,
so
you
can
do
exactly
what
I'm
doing
here
pretty
easily
and
then
we're
also
looking
at
just
a
tease
of
this
eventually
we're
going
to
add
all
this
to
automatically
happen
inside
of
cosmonic.
If
you
want
to
join
cosmonic
notes,
I
have
a
nice
little
script.
D
That
can
do
it
for
you
at
this
point,
so
we'll
we'll
be
showing
that
at
a
workshop
next
week,
and
then
people
can
look
at
it
price.
A
Well,
yeah,
so
this
one,
this
one's
super
fun
I,
think
by
the
way,
I'm
linking
to
like
time,
stamps
and
stuff,
but
I
I
think
that
scale
will
actually
kind
of
slice
this
up
by
talk
and
publish
like
the
individual
videos,
so
we'll
get
that
out
as
well
as
soon
as
that
comes
out
and
then
later
the
next
day,
Taylor
and
I
actually
did
a
joint
talk,
which
was
pretty
fun.
We've
done
a
couple
of
these.
A
So
far,
this
one
was
really
aimed
at
the
you
know:
the
Linux
developer,
someone
who
has
seen
webassembly
as
something
that
you
can
play
with
something
that's
a
toy
or
Works
in
really
limited
domains,
and
we
showed
obviously
with
wasmcloud
how
that
can
be
a
lot
easier
to
get
into
now
and
the
real
kind
of
applications
that
you
can
build
with
it.
So
I'll
send
this
one
as
well.
A
There's
a
ton
of
activity
in
the
chat
that
I'm
not
going
to
read
so
I'll
freak
out,
and
it
was
both
of
these-
were
really
fun.
I,
don't
really
have
anything
to
say
here
other
than
maybe
the
same
call
out
from
from
Taylor
that
anybody
who's
seen
wasmcloud
before
you
can
probably
skip
about
halfway
through
the
talk
to
see
the
fun
demo.
A
I
showed
off
a
really
similar
demo
to
the
beginning
of
the
community,
call
where
I
had
key
value
counter
on
local
and
then
swapped
it
all
to
the
cloud
and
then
went
on
from
there.
But
we
had
a
lot
of
fun
with
this
with
this
conference
and
it
was
great
great
to
meet
some
people
in
person
who
are
interested
in
the
technology.
A
I'm,
probably
not
going
to
Spur
too
many
questions
from
that,
so
I'll
just
move
on
to
our
last
agenda
item
really
quick.
I
know
that,
for
the
you
know,
cosmonic
is
putting
on
the
devpost
hackathon
for
distributed
webassembly
applications.
It's
completely
a
wasm
cloud,
compliant
application
that
you
can
build
and
submit
and
I
know
that
a
lot
of
people
in
the
wasm
cloud
Community
are
looking
at
that
and
looking
to
contribute
their
Solutions
as
something
for
the
hackathon
and
I
just
wanted
to
call
out
that
we're
out.
A
We
are
actually
going
to
be
holding
office
hours
today
from
three
to
four.
Let
me
double
check.
I
think
it's
that
time
get
from
3
to
4
pm
eastern
time,
so
it's
going
to
be
about
an
hour
after
this
call
wraps
up
we're
going
to
be
doing
it
in
the
cosmotic
Discord,
which
you
can
join
just
on
the
cosmotic
side,
if
you
haven't
done
it
before,
but
I
just
wanted
to
call
that
out
to
the
community
if
you've
been
running
into
anything.
A
A
A
B
I
was
actually
curious
about
the
questions
that
you
or
Taylor
got
during
scale
like
what
were
some
of
the
things
that
people
were
talking
to
you
about.
A
Yeah
Taylor
can
you
know
I
think
during
the
during
the
Friday
session
we
got
a
couple
of
kubernetes
specific
questions,
but
all
all
I
remember
from
Saturday
is
getting
really
awesome,
questions
that
we
had
really
good
answers
to
with
Watson
cloud
and
it
kind
of
felt
like
we
had
audience
plants
I'll,
be
honest
but
like
I
I
remember,
somebody
asked
you
know
each
each
webassembly
actor
that
you
have
or
each
wasmcloud
actor.
How
can
I
provide
configuration
for
this?
A
Like
can
I
change
that
which,
of
course,
the
answer
is,
is
link
definitions
and
things
you
can
change
at
runtime,
Taylor
I
feel
like
we
had
a
really
good
question
about
security
like
yeah.
What
was.
D
That
it
was,
it
was
a
follow-on
to
that
same
question
that
you
were
just
asking.
They
were
saying
well,
do
I
have
to
like
manually
like
set
up
this
for
every
single
webassembly
module
I'm
using
and
like
how
do
I
know
that
it's
that's!
Okay
to
use
and
I
went
through
the
fact
that
we
have
the
security
and
depth
with
the
different
layers
of
invocation,
signing
actor
and
provider,
signing
like
all
the
different
levels
that
we
have
there,
so
that
that
was
one
of
them,
the
kubernetes
side
of
stuff.
D
It
was
good
what
I
call
good
skeptical
questions,
because
people
are
when
you're
new
to
a
technology
or
initially
skeptical.
Everyone
is
and
about
technology,
and
so
having
those
questions
about
the
really
just
good.
Like
honest
questions
about
how
webassembly
Works,
how
it
can
interact
with
things
and
and
in
kubernetes
like
how
basically
was
more
interacts
with
kubernetes,
there's
a
whole
bunch
of
questions
around
that,
and
most
of
them
are
on
the
the
video.
If
you
want
to
hear
all
of
them,.
B
Thanks
for
that,
I
was
mostly
asking
like
what
do
I
need
to
prepare
for
mentally
before
I
answer
any
questions
over
it
wasn't.
My
oh
I
was
just
you
know,
cheating
trying
to
steal
your
answers.
A
I
think
that
well
wasn't
my
oh
I
guess
is
a
wasm
specific
conference,
so
people
are
probably
going
to
be
knowledgeable,
but
one
thing
that
I
feel
like
we
answered
really
well
in
the
second
day
was
you
know
somebody
was
asking
about
how
webassembly
is
is
still
single
threaded
currently
and
like
running
performance.
Intensive
things
in
the
browser
may
not
really
work
like
it
doesn't
really
seem
like
you
can
do
real
real
things
with
it.
A
There
were
some
more
questions
about
threading,
but
one
really
good
thing
to
have
in
the
back
pocket
is
like
Google,
Earth,
Amazon,
Prime
figma
renders
there
like
entire
product
with
with
webassembly
or
they
use
webassembly.
You
know
adobe's
using
it
for
Photoshop,
so
it
is
yeah.
A
Auto,
Autodesk
or
AutoCAD
is
huge
so
like
there
are
really
performance,
critical
applications
using
webassembly
in
the
browser
and
I
I
personally
kind
of
gloss
over
the
the
browser
use
case
because
I
feel
like
it
already
works
great
in
my
brain,
but
that
one's
a
good
one
to
have
in
the
back
pocket.
If
people
question
you
know
the
ability
to
do
something
high
performance
in
the
browser
Taylor,
you
raise
your
hand,
did
you
have
another
one?
You.
D
This
week
we
have
was
on
my
own
coming
up
next
week
for
those
in
the
EU
I
think
those
are
being
recorded,
question
mark,
so
those
might
be
recorded
for
for
future
consumption.
We're
doing
some
fun
like
we're
doing
a
workshop.
There,
Bailey
and
I
are
there's
a
whole
bunch
of
talks.
D
D
Brooks
has
these
on
like
speed
dial
so
for
for.
D
Going
to
be
in
the
EU
as
well,
those
are
coming
in
for
cloud
native
wasm,
day
EU,
and
so
that's
something
to
keep
an
eye
out
on
as
well
and
then
eventually
we'll
get
some
dates
for
the
webassembly
summit,
which
is
sometime
in
the
summer
in
the
UK.
So
those
are
the
big
ones
coming
up
here,
but
we
will
be
there
to
talk
to
anybody
at
Cloud
native
wasm
day.
D
We
love
to
connect
with
people
during
those
times,
so
just
wanted
to
call
that
out
too
and
if
you're
coming
to
wazam
IO,
please
let
us
know
we'd
love
to
talk
to
you.
There.
B
Yeah
next
week,
specifically
I'm
going
to
get
to
show
off
the
work
that
Kevin
and
Roman
and
Steve
and
Victor
have
all
been
working
on.
We've
been
doing
some
pretty
curriculum
changes
to
support
the
component
model
and
and
show
being
able
to
take
something
that
knows
nothing
about
wasmcloud
and
be
able
to
run
it
through
our
system
so
that
you
can
run
it
any
Cloud
anywhere
at
any
scale,
which
is
cool
and
I'm
pairing
up
with
that
talk
with
a
Microsoft
engineer,.
A
Well,
super
exciting
stuff,
I
kind
of
had
them
in
the
pocket,
but
I
need
to
just
have
a
folder
of
all
the
upcoming
events,
so
that
I
can
can
bring
it
up.
Got
a
lot
of
stuff
going
on
Bailey
and
I
are
going
to
devops
days
Nashville
here
in
a
couple
of
weeks
before
kubecon
there's
so
much
all
right.
I'm
gonna,
I'm
gonna
lay
off
before
I
get
people
yeah
panic.
A
All
right
still
still
in
free
time,
anybody
have
anything
else
that
they'd
like
to
talk
about
in
the
in
the
web
assembly
or
watsonflat
ecosystem.