►
From YouTube: wasmCloud: v.15 Release, New Branding
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
A
All
right,
hey
everybody!
Welcome
to
the
wasn't
cloud
community
meeting
for
february
the
17th
2021.
we've
got
a
couple
new
folks
joining
us
today,
steve
I'll
hand
it
off
to
you
for
a
quick
intro.
B
Hello,
I'm
I'm
really
impressed
by
the
things
that
you
guys
are
building
I've
been
playing
with
cloudflare
workers
for
a
few
months
and
am
thinking
about
some
some
enterprise
applications
for
wasm
cloud.
So
I'm
excited
to
get
involved.
A
That's
awesome
and
I'm
really
excited.
I
know
some
things.
You're
working
on
with
cloudflare
workers
was
like
an
oauth
provider
that
you've
been
working
through,
so
I
I
was
just
really
excited
when
we
got
a
chance
to
touch
base
the
other
day.
I
think
everyone
else
has
been
here
before
so
we've
got
two
quick
demos
that
we're
gonna
walk
through
oh
well,
wicker's
on.
Let
me
actually
put
you
on
the
spot
wicker.
A
Do
you
want
to
take
a
quick
minute
and
introduce
yourself
or
you
just
oh
you're,
you're,
good,
yeah,
yeah,
happy
too
yeah,
so
a
car
for
wasmer?
I
am
running
product
management
for
the
company.
I
recently
joined
about
two
months
ago.
Prior
to
wasmer
I
had
my
own
startup
in
the
edge
computing
space
primarily
focused
on
integrating
highly
distributed.
A
I
guess
legacy
systems
is
the
best
way
that
you
can
call
it.
The
company
primarily
worked
in
the
defense
space,
where
we
integrated
a
bunch
of
like
radar
missile
type
systems.
If
you
look
up
the
advanced
battle
management
systems
for
the
air
force,
we're
part
of
that
that
group
I
decided
to
leave
that
company
to
join
westmer,
because
I
felt
like
webassembly
would
have
actually
made
that
company
much
much
more
successful.
A
A
I'm
excited
we've
been
working
behind
the
scenes
on
branding
and
I've
got
three
concepts
to
go
through
and
then
to
announce
our
new
logos
and
we'll
get
our
color
palettes
and
all
that
stuff
in
flight
for
all
the
work
we've
got
on
documentation
and
websites,
so
kevin,
and
I
worked
pretty
closely
on
the
planning
on
this
and
we
worked
with
an
incredible
shop
out
of
austin
called
legacy
79.
juan
down.
A
There
is
phenomenal
if
you
ever
need
work
like
this
he's
really
intentional,
and
the
first
concept
was
interlocking
pieces
plus
portability
plus
the
w
monogram,
and
we
came
up
with
this,
which
obviously
evokes
a
w
a
bit
of
a
box.
A
If
you
look
at
it
right,
both
inward
and
outward,
and
then
there
it
is
mocked
up
in
green
option,
two
was
to
think
through
interlocking
pieces
and
if
you
know
me,
you
know
that
I
love
my
hexagons
clouds
and
systems
working
together,
and
this
was
a
set
of
hexagons
that
evoke
the
cloud
logo.
A
You
know
when
you
were
looking
at
like
the
classic
little
cloud
sketch
there
mocked
up
in
a
few
different
colors
here
and
then
the
third
option
that
we
kind
of
worked
through
was
the
idea
of
scalability
plus
pre-built
modules
and
bits
of
information,
and
that
was
a
wasm
cloud
like
this,
and
here
it
is
mocked
up
in
a
few
different
colors,
and
we
got
some
feedback
from
a
couple
different
folks
and
we've
decided
to
go
with
the
a
w
a
logo
here,
so
assets
will
be
put
up
onto
slack
and
distributed
up
through
github,
hopefully
today.
A
So
we
can
start
integrating
those
and
we
did
experiment
with
a
few
different
color
schemes
here
you
know.
Ultimately,
when
we
went
back
to
color
theory,
you
know
we
really
wanted
to
communicate
something
that
was
calm
and
you
know
collected.
So
we
were
thinking
the
greens
and
the
blues
and
after
a
quick
discussion,
we
ended
up
selecting
the
green
as
our
sort
of
standard
color
palette.
A
So
we'll
get
some
colors
out
to
folks
here
and
logos
over
the
next
couple
days,
and
we
can
start
you
know,
branding
all
the
things
it'll
certainly
be
less
painful
than
another
name
change
which,
if
you've
been
with
the
product
or
the
project
for
a
while.
You
know
that
we
started
as
waxosuit
a
brief
tour
of
duty
as
wasca
than
wasc
and
then
finally,
our
forever
home
with
watson
cloud.
Any
questions
about
branding
are
the
sort
of
concepts
here.
I.
C
Have
I
have
one
liam
jordan,
so
we've
been
when
typing
out
wasm
cloud
in
a
lot
of
places,
we've
been
capitalizing
to
see
from
now
on.
Are
we
going
to
go
with
the
lowercase
c.
A
That
is
a
great
question.
I
I
had
always
kind
of
thought
that
I
like
the
using
the
capital
c,
because
then
even
in
plain
text,
you
know,
like
you
see
up
here
at
the
top.
You
know
you
get
the
emphasis
and
the
sort
of
carry
around
with
the
words.
A
Let
me
talk
to
a
juan
and
just
ask
as
a
suggestion
what
his
thoughts
are
on
on
that
you
know
we
could
as
a
as
a
brand
guide
just
whenever
it's
written,
we
use
blossom
cloud
with
a
c,
but
whenever
it's
our
logo
mark
here,
where
you
have
where
you
can
carry
the
emphasis
that
we
just
go
this
way,
I'm
ultimately
open
to
feedback
on
this
from
everybody.
If
anyone
has
any
ideas.
A
If
we
want
to
avoid
clippy
errors
yeah,
maybe
if
we
get
it
all
in
our
default
dictionaries,
I've
added
it
to
mine
so
that
it
auto-corrects
ralph
any
thoughts
you
know
or
the
microsoft
folks.
You
guys
had
some
awesome
ideas
on
taglines
and
and
some
of
the
branding
stuff
we
worked
on
or
we
discussed
last
week.
D
A
D
So
I
mean
I,
I
actually
like
it
as
laid
out
here.
It's
the
thing
about
the
camel
casing
in
branding
and
logoing.
Now
is
that
it
varies
very
much
smells
like
and
to
me
it
smells
like
yahoo.
It's
same
kind
of
thing.
It's
like
you
know
in
10
years
now
you're
going
to
sit
there
and
go
god.
I
really
wish
that
c
was
lowercase,
but
you
know
I
wouldn't
say
that
that's
a
strong
case,
because
I
think
for
your
from
your
point,
two
is
just
as
good,
which
is
typographically.
D
A
A
D
A
E
A
So
then,
what
about
so?
What
about
for
our
written
marks?
Do
you
think
it
should
all
be
lower
case
than
as
the
written
mark
for
you
know
like
when
we're
using
it
in
text
and
writing.
E
Having
having
the
the
capital
c
in
some
of
the
things
that
we've
been
doing,
you
know
github
wise.
A
That's
actually
kind
of
his
technical
problems.
I
know
he's
had
a
routing
issue
the
other
day
with
what
creates
that
io
wouldn't
route.
You
know
failed
if
you
try
to
pass
it
to
the
capital
versus
the
lower
case
or
something
like
that
yeah.
I
don't
remember
what
the
exact.
E
Issue
was,
but
I
know
every
once
in
a
while,
we
run
into
something
that
doesn't
like
the
capital
c
yeah,
but
other
than
that.
I
really
don't
have
any
strong
opinion
on
what
it
looks
like
written
out
in
text,
and
you
know
I
do
prefer
the
logos
the
way
they
are.
A
Okay,
well,
I
I
think
if
we
have
some,
we
certainly
don't
want.
You
know
a
brand
standard
to
be
a
barrier
to
any
technical.
You
know
functionality
of
the
project,
so
I
I
think
I'm
inclined
to
say
that
now
that
we
have
the
the
nice
logos,
we
can
just
use
those
when
we
need
to-
and
you
know
we'd
lower
case,
but
we
can.
We
can
talk
to
this
more
on
slack
and
just
sort
of
move
through
that,
but
that
was
a
great,
a
great
point
there.
A
F
I
think
we
were
going
to
err
on
the
side
of
announcing
the
releases
for
today.
F
Yeah,
I'm
happy
to
do
that
as
well.
That'd
be
awesome,
so
everybody
should
be
able
to
see
my
screen
and
now
we're
on
a
github
releases
page.
So
as
a
I'm
proud
to
announce
that
we
have
announced,
we
have
released
wasmcloud
odot15,
so
all
of
the
assets
that
we
released
for
everything
with
the
wasm
cloud
host
with
odot
15,
we
released
wash
version
2.0,
which
is
like
our
milestone
release
and
had
I
pointed
out
in
the
slack
channel,
we
had
contributions
for
many
people,
including
jared
and
gustav
both.
F
Thank
you
for
contributing
to
this.
All
of
this
has
been
released
with
our
cicd
github
actions.
So
you
know
releasing
in
the
future
is
going
to
be
much
much
easier
across
the
board.
We've
improved
our
documentation
in
not
only
just
on
wasmcloud
wasmcloudbut.dev,
but
we
also
have
better
readmes
for
actor
interfaces.
For
example,
we
have
automatically
updating
versions
for
each
interface,
regardless
of
language
for
capability
providers.
F
We
also
have
an
auto
updating
list
of
our
first
party
capability
providers
and
their
oci
references
to
keep
it
easy
for
anybody
to
be
able
to
run
their
own
examples
and
same
with
our
example.
Actors,
there's
a
pr
out
there
right
now
that
opens
up
a
table
with
oci
references
for
all
of
our
example
actors.
So
across
the
board,
we
have
released
all
of
the
work
that
we've
been
doing
over
the
past
few
months,
and
I
mean
personally
feels
like
a
huge
weight
off
the
chest
to
get
this
out
there.
F
But
we
now
have
wasmcloud
and
wash
installable
for
deb
and
rpm
through
brew
for
mac
os
and
of
course
you
can
also
still
install
it
with
like
cloning
it
or
installing
it,
through
crates.I,
o
so
really
happy
to
announce.
A
Emoji,
all
right
that
is,
awesome,
brooks
and
kevin
and
bill
and
everybody
jared
everybody-
that's
been
busting
their
butts
the
last
few
months.
This
has
been
such
a
massive
release,
brooks
if
you
could
just
paste
all
those
links
into
chat
I'll
make
sure
they
end
up
in
or
just
add
them
to
the
notes
directly.
I
will
go
ahead
and
make
sure
that
that
shows
up.
You
know.
A
We've
still
got
a
lot
of
work
to
do
here
on
you
know,
documentation
and
storytelling,
and
you
know
building
out
some
of
the
examples
and
still
some
of
the
actor
interfaces,
but
there's
no
doubt
that
this
has
just
been
a
a
real
labor
of
love
for
the
last
few
months
to
get
this
over
the
hill.
So
everybody
certainly
feels
proud
and
we
will
do
a
formal.
You
know
team
celebration
here
in
the
next
few
weeks.
I
just
need
to
get
the
form
into
slack
and
we'll.
A
Let
folks
start
signing
up
and
we'll
block
out
some
time
just
to
sit
around
and
hang
out
and
just
commemorate
all
the
hard
work
and
everything
just
some
quick
community
announcements
may
the
fourth.
We
have
a
cloud
native
wasm
day.
The
cfp
closes
on
friday.
A
A
There
is
also
the
the
webassembly
summit
which
is
being
put
on
by
fastly
april
22nd
2021
the
cfp
for
that
is
closed,
and
then
we've
got
the
wasn't
time
bi-weekly
meeting
next
week
at
one
o'clock
on
thursday.
If
anybody
is
looking
for
an
invite
for
that,
I
can
slide
on
your
way
and,
unfortunately
I
hope
everybody
got
their
valentine's
day
gift
of
the
early
bird
kubecon
wasm
day
registration
special
for
ten
dollars.
A
It
is
now
up
to
normal
price,
but
still
discounted
from
final
price,
so
make
sure
you
get
set
up
for
kubecon
eu
for
those
on
the
east
coast.
That
will
be
starting
at
something
like
3
a.m.
A
Most
days
I
will
be
blocked
out
and
engaged
very
heavily
in
the
wasm
day
stuff,
as
well
as
some
of
the
kubecon
activities.
We're
trying
to
get
more
wasm
into
the
schedule
wherever
we
can
and
I
just
do
an
open
call.
Does
anybody
else
have
any
community
motions
or
meetings
that
that
they'd
like
to
raise
at
this
time.
A
Okay,
I
think
just
brooks
you
already,
you
know
kind
of
reviewed
the
in-flight
actor
interfaces,
there's
still
a
handful
of
these
left
to
be
written
in
various
languages.
Here.
Speaking
of
my
dictionary
there,
so
thank
you
very
much
for
the
table
and
these
are
all
laid
out
as
well.
I
know
we're
looking
for
help
on
that.
The
rebel
brooks
this
is
all
tidied
up
for
2.0.
This
is
a
done
right.
F
Yep,
it's
tidied
up
for
2.0.
There
are
a
couple
issues
in
the
backlog
here:
they're
all
marked
for
like
an
ephemeral,
3.0
release,
which
is
just
in
the
future.
Once
we
get
enough
features
or
break
the
api
in
a
in
a
way
that
warrants
a
minor
version
release.
So
I
guess
one
thing
we
can
point
out
on
wasn't
cloud
and
on
the
wash
like
in
the
main,
repo
readme,
we
now
have
a
badge
that
shows
how
many
issues
are
marked
as
good
first
issue
and
we're
so
we're
trying
to
keep
up
with
that.
F
To
make
sure
that
you
know
we
can
easily
show
what's
available
for
people
to
hop
in
and
and
get
working
on,
so
that
that's
a
great
place
to
look
if
you're
looking
to
get
involved.
A
Great
and
I
I
know-
we've
had
some
bunch
of
discussions
privately
on
this,
but
you
know
when
we're
trying
to
build
a
big
community.
There
is
a
lot
of
behaviors
that
you
need
to
adopt
around.
You,
know,
documentation
and
welcoming
and
inviting-
and
this
is
part
of
that
effort
to
to
lay
lay
some
things
out.
Let's
see
taylor
are
you
on
radio,
I'm
not
sure
or
matt
does
somebody?
How
are
we
on
the
crustlet
cloud
provider?
This
is
all
wrapped
up.
A
It's
moved
over.
I
haven't
updated
it
to
all
the
new
versions
yet,
and
don't
ask
me
about
updating
versions
right
now,
I'm
still
in
the
midst
of
doing
tokyo
upgrades
on
the
main
crestlit
repo.
So
I'm
going
to
be
stuck
doing
that
for
a
little
while,
but
it
will
come
there.
It's
still,
it's
builds,
it
builds
and
it
does
what
it's
supposed
to
it's.
Just
it's
not
using
the
new
versions.
Yet
so
it's
everything
that
it
currently
is
in
crossfit
0.6
just
been
moved
over.
A
Okay,
great,
is
there,
you
know
from
a
how
do
we
support
you?
You
know
perspective.
Are
there
any
calls
to
action?
You
want
to
make
or
asks
you
know
that
you
need
no
there's
no
ask
here.
A
If
someone
is
feeling
so
inclined,
they
can
go
through
and
try
to
update
the
libraries
to
the
proper
versions,
but
I
mean
I
don't
know
how
difficult
that
is
based
on
our
current
version,
where
we're
at,
but
that
should
allow
you
to
to
update
those
things
you
should
I
mean
you
should
be
able
to
update
those
things
right
now.
A
Otherwise
I
think
everything
is
is:
is
ready
to
go
there.
If
there's
a
build
pipeline
set
up,
it
builds
the
artifacts.
A
The
artifacts
are
available
in
each
pipeline
run
once
you
do
get
a
like
artifact
storage
location
that
isn't
github,
then
just
let
us
know
and
we'll
update
that
okay
but
yeah
the
idea
to
have
it
there
is
that
if
there's
any
other
experiments,
you
want
to
try
with
it
that
were
kind
of
hard
to
do,
while
it
was
still
within
the
main
crescent
repo.
That's
one
of
the
things
that
having
it
over
here
enables.
A
So
if
you
want
to,
I
don't
know,
mess
around
with
lattice
stuff
with
it
or
you
know
like
any
of
those
kind
of,
like
other
features
that
were
kind
of
hard
to
shove
into
the
normal.
It's
it's
now
out
of
the
crestlet
repo,
so
that
it's
easier
to
do
that
than
having
it
all
intermeshed
and
tangled
with
the
rest.
So
anyway,
I
guess
the
big
help
is
just
if
someone
wants
to
go
update
those
libraries,
because
they
know
the
apis
pretty
well,
then
that'd
be
great,
but
otherwise
I'll
get
to
it
eventually.
A
Okay,
great,
thank
you
so
much
for
all
the
hard
work
on
that,
and
then
let's
see,
I
think
I'd
almost
want
to
just
do
a
call
out
and
ask
if
anyone
else
has
anything
they
want
to
raise
or
discuss.
G
So
there
was
some
confusion
on
how
wash
is
supposed
to
act
with
regards
to
nats
and
wasn't
cloud
host
that
was
deferred
to
today.
I
want
to
make
sure
that
brooks
and
kevin.
You
guys
can
ask
me
any
questions
if
there
are
still
any.
A
Awesome,
and-
and
this
is
the
it's
I
actually
had
this
teed
up
for
after
I
did
that
ask
so
that
was
like
I
couldn't
have
set
you
up-
could've
planted
a
better
question
by
the
way.
So
this
is
the
tutorial
that
you
were
trying
to
follow.
Is
that
right.
G
Yeah,
I
was
just
going
through
step
by
step,
trying
to
to
blindly
copy
and
paste
things
see
how
they
worked
and
they
didn't.
And
after
troubleshooting
it
didn't
look
like
it
was
my
my
environment,
and
then
we
got
to
some
confusion
as
to
what
the
expectation
actually
was
with
wash.
A
Got
it,
and-
and
this
was
the
what
we
attracted
to
was
not
having
nats
running
that's
correct
and
the
fix
was
to
for
you
to
just
use
the
docker
compose
file,
that's
in
the
tools
directory
and
and
spin.
That
up
is
that.
Did
I
recount
that
correctly.
G
Oh
yeah,
I
I
can
get.
I
get
all
these
commands
working
myself
when
running
my
own
hosts
and
setting
nuts
up,
but
as
for
the
documentation
it
was
it
didn't
mention.
Nats
didn't
really
mention
much
about
wasn't
cloud
hosts
at
that
point
and
washington
seemed
to
work
work
well
like
that,
so
either
the
documentation
needs
to
be
adjusted
or
washed
needs
to
be
needs
to
have
that
functionality.
A
A
Your
feedback
like
what
we're
getting
now
is
absolutely
priceless,
because
when
we're
going
through
these
things,
you
know
like
it's
easy
to
forget
that
oh
I
already
have
nats
running
you
know
and
so
that
we
don't
make
the
same
errors
because
we're
bringing
so
much
baggage
and
context
to
it.
So
I
want
to
let
you
know
how
important
your
contributions
are
and
how
grateful
we
are
to
receive
them.
A
Anytime,
you're,
you
know
kind
of
doing
anything
if
you
keep
a
little
get
a
little
notepad
next
to
you
and
just
write
down
your
thoughts
and
experience
and
please
try
to
share
those
with
us.
You
know
that's,
you
know
really
really
amazing
at
some
point.
I'd
love
to
get
to
you
know
like
the
steve
krug
style.
Don't
make
me
think
you
know
usability
studies
and
testing,
but
we
know
that
we
still
have
a
bunch
of
you
know
rough
surfaces
to
polish
down
here.
Oh
god,
it's
the
pinewood
derby.
A
This
weekend
I
have
so
much
work
to
do
speaking
of
polishing
things
down.
So
I
really
appreciate
it
and
brooks:
did
you
want
to
talk
about
what
you
were
kind
of
planning
here
after
post
discussion
on
this
yeah.
F
I'd
love
to
so
yeah
again,
echoing.
What
liam
is
saying
like
thank
you
for
running
through
this,
especially
doing
the
tedious
part
of
like
copying,
pasting
every
command
like
in
a
fresh
environment,
because,
like
liam
said,
you
know
that
stuff
is
easy
to
forget.
So
I
wanted
to
share
two
things.
Do
you
mind
if
I
just
share
my
screen
real,
quick,
liam
or
snapchat?
I
would
love
that
actually,
so
the
the
first
thing
that
we
did
just
to
solve,
or
at
least
add
some
context
immediately.
F
F
You
know
saying
specifically
what
nats
is
required
for
so
here
like
if
you're
in
the
rebel,
you
can
still
do
some
commands
without
nats.
F
So,
for
example,
like
you
could
examine
the
echo
kb
or
the
the
echo
actor
and
that's
totally
fine
without
gnats,
but
you
can't
run
the
control
interface
commands,
which
are
really
important
for
the
tutorials.
So
what
I
just
wanted
to
point
out
there
is
that
the
first
step
to
addressing
this
is
to
at
least
like
stop
it
at
the
source.
You
know
where
somebody
would
run
into
that
confusion,
and
I
think
the
next
step
like
coming
along
with
all
feedback
that
we
can
get
is
to
address
it
in
our
documentation.
F
A
Yeah
and
I
would
really
encourage
feedback
any
way
possible.
You
know
pull
requests
twitter.
All
the
things
are
great
kevin.
There's
a
there's,
a
issue
that
we're
kind
of
talking
through
here.
You
know
it
was
in
an
old
version
of
in
an
earlier
version
about
having
two
different
code
paths
here,
for
you
know,
running
local
only
or
running
with
mats.
Do
you
kind
of
want
to
share?
You
know
your!
You
know
your
perspective
on
that.
E
Yeah,
so
basically
in
the
previous
code
base
the
stuff
that
was
that
existed
prior
to
0.15.
E
You
know
we
had
a
bunch
of
code
that
you
know
would
detect
if
you
were
running
without
nats
and
there
would
essentially
be
all
the
shortcut
paths
through
the
code
and
if
you
were
running
nas,
then
there
would
be
all
these
legitimate
paths
through
the
code
and
the
problem
was
that
it
became
impossible
to
test
and
we
had
too
many
different
edge
cases
to
manage,
and
so,
among
other
things,
that
was
one
of
the
things
that
we
rewrote,
and
so
now
you
can
run
without
lattice,
but
our
our
code
only
takes
one
path
through
through
the
lattice
system.
E
So
one
of
the
things
that
we're
looking
at
doing
in
terms
of
making
this
experience
better
is
so
today
now
that
we've
got
the
little
fix
in
for
for
wash
0.2.
E
E
If
you
don't
have
nets
running
locally,
another
option
is,
we
might
be
able
to
do
something
with
ngs,
which
is
synadia's,
public,
hosted
nets
servers,
and
so
what
we
might
have
is
maybe
some
form
of
limited
user
account
that
will
connect
to
ngs,
and
so,
if
you
don't
have
nats
running,
then
you'll
essentially
connect
to
a
a
lattice
of
some
shape,
and
but
you
know,
as
you
can
imagine
there
there,
the
devil
is
in
the
details
on
that
one.
E
So
there's
a
lot
of
stuff
to
work
out
before
we
throw
that
in
there,
but
in
general
the
idea
is.
We
want
to
make
sure
that
the
developer
experience
just
keeps
getting
better.
So
today
we're
getting
better
about
saying
about
both
documenting
and
requiring
in
the
in
the
tooling
that
nats
is
there
and
then
you
know
once
we
get
to
whatever
whatever
the
release
is
going
to
be
for
that,
we
should
be
able
to
make
that
experience
even
smoother.
A
Yep
kevin,
I
thought
we
know
we
talked
through
it.
I
I
recount
these
conversations,
but
I'd
kind
of
like
to
just
summarize
them
with
with
other
people
here
on
some
of
the
other
options
here
and
some
of
the
challenges
you
know.
First,
where
does
knots
run
today
versus
where
wasm
cloud
runs,
and
you
know
we're
sort
of
like
the
directionality
there?
And
could
we
start
with
a
summary
of
that.
A
What
packages
are
built?
What
you
know
hoster
supported,
you
know
it's
like
all
the
arm
stuff
out
there.
I
thought
there
was
a
concern
around.
You
know
that
the
packaging
wasn't,
you
know
like.
E
There's
no
like
brew
installable
version
of
nats
and
there's
no
apc
or
snap
package
for
nas
that
I
know
of,
but
it's
just
stupid,
simple
to
compile.
So
nets
will
basically
run
anywhere.
You
can
download
anywhere,
you
can
compile,
go
and
their
releases
their
release.
Binaries
are
available.
For
you
know
all
the
major
operating.
A
E
That
if
we
were
to
attempt
to
make
nets
a
prerequisite
of
one
of
our
own
installations,
then
we
are
now
tightly
coupled
to
how
nats
updates
and
manages
its
release
packaging,
and
we
don't.
We
don't
want
to
be
in
that
business.
So
we're
we're
deliberately
not
bundling
nets
with
our
own
installation.
A
Binaries-
and
that
was
going
to
be
my
next
question-
was
that
exact
question
you
know?
Oh
that's
great
now
I
a
new
idea
that
I
had
not
really
heard
before
heard
you
offered
you
know
discussed
before
was
the
concept
of
maybe
having
like
some
limited
use
public.
You
know,
network
available
for
use
or
testing
or
something
that's
super
interesting.
We
should
maybe
kind
of
bounce
it
around
a
bit
and
see
if
there's
something
that
we
can
do
to
make
the
experience
better.
You
know,
do
we
do
it.
E
Yeah,
like
I
said
there,
it's
there's
a
couple
of
possibilities
there
and
some
of
them
might
make
for
some
pretty
cool
developer
experiences.
We
just
need
to
you
know,
go
through
see
what
the
edge
cases
are
and
yeah
you
know,
hopefully
do
it
without
it
ended
up
end
up
ending
up
costing
us
a
ton
of
money.
Every
time
somebody
accidentally
opens
wash
without
a
nas
client
installed
or
without
an
at
server
running
nearby.
F
I
think
an
additional
thing
for
us
to
think
of
we've
been
focusing
really
hard
on
the
initial
developer
experience.
So,
like
the
very
first
time,
somebody
uses
wasm
cloud
and
gets
up
and
running.
You
know
how
easy
is
it
for
them
to
do
that?
Another
experience
that
we
can
start
thinking
about
too.
Is
you
know
how
do
you
go
from
being
on
your
local
machine,
running
wasm
cloud
to
being
on
like
a
server
or
some
other
type
of
edge
infrastructure
somewhere?
That's
not
your
local
machine.
A
Okay,
super
interesting
and
then
there's
you
know,
probably
some
other
work
around.
You
know
thinking
about
the
really
tiny
things
where
space
is
at
a
premium
and
you
know
like
recommendations,
but
I
guess
stuff
all
down
the
road,
as
we
kind
of
think
through
that,
for
is
it
too
early
to
say,
16,
kevin.
E
Nasa
is
a
super,
tiny
binary
and
it
uses
almost
no
memory,
and
you
know
it's
it's
one
of
those
things
where,
if
you
look
at,
if
you
look
at
big
complicated
infrastructure
and
distributed
systems,
the
the
nets
process
is
the
one
thing
that
just
never
dies
for
any
reason.
E
E
We
need
to
make
a
decision
as
to
whether
it's
too
small
to
run
wisely
cloud
at
all,
okay
and
then
after
we
make
that
decision,
we
can
figure
out
whether,
like
there
are
architectural
patterns
where
you
don't
have
to
deploy
nets
physically
on
the
same
machine
or
the
same
virtual
device
where
your
wise
and
cloud
host
is,
you
can
connect
remotely
to
it.
A
E
Mats
also
supports
mqtt,
so
one
of
the
other
patterns
that
nats
enables
is
in
situations
like
that
is
you've
got
wasmcloud
running
on
your
iot
device,
and
then
you
use
mqtt
to
talk
to
your
you
know,
nas
gateway
or
bridge
or
leaf
node
or,
however,
you
set
that
up.
A
Okay,
so
definitely
some
really
solid
options
there
across
the
board
to
think
through
from
a
both
technology
and
user
experience.
Point
of
view,
so
I
I
believe,
that's
everything
that
we
had
on
the
agenda
for
today
for
discussion
wise.
I
know,
there's
a
bunch
of
you
know
tests
still
going
through
slack
open
floor.
Does
anyone
have
anything
that
they
want
to
bring
up
on
the
call
today.
F
I'd
love
to
call
to
action,
you
know
our
tutorials
documentation
and
our
artifacts
are
out
there
now,
so,
if
you're
interested
in
playing
with
with
wasmcloud
or
wash
or
any
of
the
tutorials
that
we
have
written
now
now
is
the
time,
and
it
would
also
be
super
valuable
to
us.
If
you
have
any
comments
about
the
experience
along
the
way.
A
Awesome-
and
you
know
for
the
folks
that
were
new
on
the
call
today,
you
know
wicker
steve,
I
I
would
ask:
do
you
guys
have
any
questions
you'd
want
to
just
ask
while
everybody's
all
together,
you
know
anything
like.
I
know
that
we're
covering
a
lot
of
ground
today
and
there's
probably
a
bunch
of
assumptions
around
what
people
understand
and
what
they
don't
is
that
stuff
you'd
want
to
chat
through
now
or
take
it
offline
later.
A
So
for
me,
I'm
just
listening
and
processing,
so
I
don't
really
have
any
intelligent
questions
that
I
can
ask
right
now.
Hey!
Look
that
I
don't
like
the
I
don't
like
the
qualification
that
we
can
only
ask
intelligent
questions.
Otherwise
I
would
have
to
keep
my
mouth
shut,
the
entire
call.
I
don't
just
play
the
rube
on
the
call
with
her.
It's
not
just
an
act.
I
put
on
to
just
ask
the
next
like
dumb
question
like
it's.
A
Actually
it's
actually
real,
but
it's
super
handy
because,
like
you
know
every
epic
story,
they
always
have
to
give
you
the
character
that,
like
you
know,
brings
along
and
gives
you
the
context
and
always
asks
the
questions
like
you
know
like
this,
like
the
sidekick,
so
you
know
it's
it's
a
good
role
for
me
to
play
steve.
How
about
you.
B
Well,
I
have
a
follow-up
from
the
previous
discussion.
I
thought
that
when
you're
sending
messages
between
actors
in
the
same
host
and
by
host
I
mean
the
weather
cloud
has
that
it
didn't
use
nats.
B
That
is
correct.
So
so,
wouldn't
that
be
a
pass
for
small
devices
that
can't
fit
maps,
they
could
still
run
a
wasm
cloud
with
in-process
actors
yeah.
So
we.
E
Were
talking,
the
discussion
earlier
was
kind
of
a
specifically
around
the
wash
rebel
and
being
able
to
interact
with
a
host
through
it,
and
so
it's
not
an
issue,
but
the
the
requirement
of
the
wash
rebel
to
be
able
to
remotely
control
a
wasm
cloud
host
is
that
it
needs
to
have
access
to
the
lattice
control
interface
and
the
lattice
control
interface
is
nats.
E
So
if
you
want
to
use
the
repel
to
talk
to
and
manipulate
a
host,
you
need
nets,
but
if
you
want
to
just
deploy
a
wasm
cloud
host,
that's
running
an
actor
that
talks
to
a
capability
provider
like
one
of
the
iot
demos
that
we
have
is
the
capability
provider
is
an
led
controller
and
the
actor
is
changing.
The
led
pattern
over
time.
B
B
Okay
thanks
a
couple
of
things
that
I'm
thinking
about
working
on,
if,
if
anybody's
already
started
it,
I'd
love
to
connect
over
slack,
one
is
a
policy
provider
with
open
policy
agent
and
the
other
is
possibly
using
envoy
as
a
service
gateway.
E
The
wasmcloud
has
a
plugable
trait
called
an
authorizer,
and
so
the
the
integration
with
opa
would
essentially
be
creating
an
authorizer
that
defers
the
can
load
and
can
execute
decisions
to
whatever
opa
decides,
and
one
of
the
cool
things
about
opa
is
that
you
can
send
in
the
header
a
bearer
token.
That
is
a
json
web
token.
So
you
can
send
the
actors
credentials
as
a
bearer
token
to
opa
and
that'll,
give
opa
access
to
things
like
the
issuer
and
the
public
keys,
and
all
of
the
claims
that
that
module
has.
A
Kevin
real
quick
is
this:
the
correct
issue
here:
number
72:
the
authorized
retreat
should
include
target
claims.
No,
no
okay,.
E
Nope
not
that
one
either
the
phrase
is
implement
an
authorizer.
So
if
you
search
for
the
word
authorizer,
it
should
show
up
with
an
e.
E
Authors,
which
include
target
claims,
oh
okay,
so
we
have
one
for
nat
server.
I
thought
we
had
an
issue
in
the
backlog
for
the
opa
one
I'll,
take
a
look
and
see,
if
maybe
it's
sitting
in
another
repo
or
something
like
that,
but
yeah
I
I
know
I
saw
it
somewhere.
I
thought
it
was
here
if
we
have
somehow
lost
that
issue
in
one
of
the
rewrites,
then
we'll
just
recreate
it
today,
because
that's
definitely
one
of
the.
A
Still
steve
would
I
love.
I
love
where
you're
interested
in
the
problem.
Space
is,
you
know,
is
a
quick
brain
dump
from
kevin
in
an
issue
the
right
way
to
help
empower
you
to
you
know,
explore
the
issue
further
or
you
know:
how
can
we
help?
You
know,
pull
you
into
the
community.
B
A
Okay,
all
right
great,
well
I'll
leave
the
follow-up
to
that
one
on
slack
kevin,
but
if
you
could
help
me
find
that
issue-
and
I
just
get
in
the
notes
and
call
it
out
to
you
when
we
find
it
that'd
be
awesome
yeah,
but
if
I
don't
find
it
I'll
just
create
and
create
it
great
great
question
by
the
way
steve.
What
else
were
you
interested
in
exploring
I'm
afraid
I
cut
you
off
there
when
we
went
on
the
little
oppa
rabbit
hole?
Was
there
another
topic?
You
were
looking
into.
E
Well
so
most
of
wisdom,
cloud
isn't
at
the
envoy
type
level,
so
the
the
cloud
itself
doesn't
make
any
demands
on
the
type
of
network
interface
that's
used
in
order
to
interact
with
the
actors,
so
you
can
make
direct
calls
to
an
actor
over
the
lattice.
E
If
an
actor
is
bound
to
an
http
server,
then
there's
an
http
endpoint
that
you
can
use
to
get
to
an
actor.
But
whatever
you
want
to
sit
in
front
of
a
lattice
is
is
entirely
up
to
you.
So
we
we
don't.
E
We
don't
have
anyone
working
on
it,
but
there's
also
nothing
preventing
anybody
from
putting
any
form
of
proxy
in
front
of
the
lattice
one
of
the
types
of
proxies
that
we
are
actually
planning
on
building
and
I'm
hoping
to
get
to
this
one
fairly
soon
is
an
open
fas
gateway,
so
we'll
be
able
to
treat
a
wasm
cloud
lattice
as
a
an
open,
fast
provider,
and
so
then,
when
someone
makes
a
a
function
invocation
using
the
open
files.
A
Okay,
that's
great
great
question,
steve
anything
else
on
your
mind,.
A
Thank
you.
We're
excited
to
you
know
continue
to,
you,
know,
discover
and
find
people
that
share
our
enthusiasm
for
the
problem
space
and
how
we're
trying
to
move
forward
together.
So,
thank
you.
Well,
I
guess
last
open
call
and
we
can
stop
recording
and,
as
always,
we
can
hang
out
for
a
little
bit
and
just
chit
chat.
If
people
are
interested,
anyone
else
have
anything
they
wanted
to
raise
today.
A
Okay,
I'll
go
ahead
and
pause,
stop
recording
and
we
can
just
move
into
the
social
part
of
the
call.