►
From YouTube: 20-Dec-2 wasmCloud Community Call
Description
WebAssembly Secure Capability Connector (waSCC) is a dynamic, elastically scalable WebAssembly host runtime for securely connecting actors and capability providers
https://wascc.dev
https://wasmCloud.com coming soon!
A
B
Hey
guys,
mike
zuper
long
time,
java
developer
working
in
the
corporate
world
doing
my
thing,
but
just
trying
to
participate
here
and
ask
and
wasm
and
rust
and
see
where
I
can
contribute
and
help
as
much
as
I
can
been
following
along.
So
you
guys
are
doing
some
great
stuff
and
look
to
see
where
I
can
contribute.
A
That's
awesome
well
welcome
welcome
along
so
last
week
the
wasm
time
meeting
was
cancelled
with
thanksgiving,
so
no
major
updates
from
there.
Although
the
meeting
before
there
were
quite
a
few
updates,
if
you
want
to
check
the
the
notes
as
far
as
wazi
and
n
getting
merged
in
and
some
of
the
experiments
stuff
that
they're
they're
working
on,
so
why
don't
we
get
started
ralph?
I
think
you've
got
something
on
the
blog
post
list
for
communities
and
stuff.
C
C
I
had
so
I've
been
chatting
with
the
people
that
had
moved
from
the
bca,
the
bike
code
alliance
over
to
fastly,
and
I
was
saying
the
kinds
of
things
that
you
know
we
usually
share
here,
which
is
basically
that
over
the
next
three
months,
first
of
all,
we're
lazy
over
the
holidays.
So
that
means
we
want
to
sit
and
write
about
the
things
we
learn,
because
it's
kind
of
fun
to
do
when
you're
not
really
busting
your
behind.
For
you
know
some
particular
thing
you
want
to
release
at
a
particular
time.
C
We
have
day
jobs,
things
like
that,
so
over
the
next
two
three
months,
it's
a
great
time
and
we
have
a
lot
of
learnings
on
our
side,
and
so
we
were
sitting
there.
Thinking
hey.
We
should
collaborate
on
some
blog
posts,
and
I
was
specifically
in
this
case
thinking
about
writing
something
with
the
various
fastly
people
who
were
in
the
networking
group
about
experiments.
C
Things
like
the
bsd
sockets
work
that
radio
had
done
on
our
our
team
and
stuff,
and
pat
hickey
over
at
fastly,
had
said
that
they
had
a
bunch
of
http
stuff
that
they
had
also
experimented
with
that
they
would
like
to
have
people,
so
we
realized
we
should
do
some
of
this
work,
and
then
it
occurred
to
me
that
we
should
blog
about
it
and,
of
course,
and
then
it
occurred
to
me
that
everybody
should
blog
about
this
stuff.
So
the
issue
here
is
the
blog
plus
list
for
community
folks.
C
C
Gonna,
I'm
gonna
create
it
in
this
meeting
because,
of
course
I
haven't
done
it,
but
the
objective
is
to
do
the
following:
we're
going
to
lay
out
probably
as
many
as
four
or
even
as
many
as
eight
blog
topics
that
we
intend
to
write
about.
That
will
be
about
mainly
geeky
stuff
things,
we've
learned,
experiments
and
so
forth.
C
So
you
could
think
of
this
as,
like
the
web
assembly
newsletter,
the
wasm
newsletter
kind
of
thing,
but
with
a
lot
more
deeper
focus
on
precisely
the
areas
that
we're
we're
playing
with
here
and
especially
experiments.
There's
no
most
of
the
education
that
we
have
is
from
the
experience
that
we've
experiments
that
we've
we
built
and
I
will
throw
it
over
to
everybody.
C
C
C
A
A
D
E
D
F
F
F
But
I'll
leave
that
out
of
this
this
quick
demo,
the
two
extra
commands
that
I've
been
working
on
and
and
working
on,
getting
merged
in
are
our
registry
commands,
which
is
just
interacting
with
an
oci
compliant
registry,
with
some
of
the
code
that
I've
put
into
the
pr
to
the
oci
distribution
crate.
We
can
now
push
and
pull
from
oci
oci
registry,
so
that
includes
like
our
capability
providers,
as
well
as
like
signed
wask
actors.
F
So
just
to
give
you
a
quick
demo,
what
that
looks
like
pulling
a
capability
provider
from
our
azure
container
registry
just
looks
like
wash
reg
pull
and
then
wasc
azure
cr
io.
So
you
can
hear
my
dog
squeaking
a
turkey
in
the
background,
and
then
you
can
just
put
in
the
the
tag
just
like
you
would
do
like
a
docker
pull
and
downloading
this
and
and
pushing
up
is
all
built
into
wash,
and
so
this
kind
of
gives
us
a
really
nice
really
nice
ability
to
script.
Some
of
these
things
later
on.
F
F
F
So,
like
I'm,
not
really
sure
what
this
mio
pull
thing
is.
It
tells
me
whenever
I
type
for
the
first
time
we
can
remove
that
from
the
the
command
output
same
thing.
If
we
like
screw
up
typing
a
command,
we
have
different
log
levels
that
we're
using.
So
we
can
edit
those
out,
and
this
is
going
to
be
huge,
even
though
for
right
now
we're
we're
just
like
we're
just
like
capturing
what
command
we're
we're
typing
and
parsing.
F
It
there's
no
actual
functionality
here,
but
what
this
is
going
to
look
like
in
in
the
future
is
we'll
be
able
to
run
a
full
like
wash
example
in
this
in
this
repel,
and
it's
going
to
be
really
easy
for
a
developer
to
like
get
started
with
just
using
wash
in
the
first
place
or
wasm
cloud
in
the
first
place.
Yeah
the
new,
the.
D
New
getting
started
tutorial
will
actually
end
up
being
essentially
earlier
in
the
journey
than
the
than
the
first
getting
started,
one
that
we
have
now
and
with
that
tutorial
you'll
be
able
to
get
the
wash
cli
from
brew
or
apt
or
any
other
source,
and
then
you
can
go
through
the
entire
tutorial
without
ever
compiling
anything.
You
can
fetch
your
actors
and
play
with
them
and
experiment
with
bindings
and
links
and
all
that
stuff
without
ever
even
opening
an
ide.
F
C
G
C
The
only
thing
I
can
see
is
one
of
the
things
that
happens
when
you
roll
forward
is
that
you
can
optimize
the
developer
experience
all
you
want,
but
if
you
end
up
trapping
the
developers
in
the
cli
you're
also
going
you're
going
to
create
a
future
limitation
for
adoption
and
education
in
a
stupider,
simpler
tool,
so
naturally
I'm
at
microsoft.
So
I
and
I
happen
to
be
the
program
manager
for
the
the
visual
studio
code,
kubernetes
extension,
so
you're
talking
to
somebody.
C
So
you
think
that
in
my
mind,
but
don't
it
doesn't
have
to
be
that
ide.
The
critical
thing
about
something
like
that
is
these
are
this
kind
of
tool?
Is
a
tool
for
optimizing
developer
experience
to
have
a
great
experience
with
wasc
wasn't
cloud?
Do
I
call
it
wasn't
cloud
now
or
do
I
call
it
wasc?
Why
isn't
cloud's.
A
C
You
can
see
where
I'm
going
is
like.
I
want
to
make
sure-
or
at
least
my
offering
would
be-
this
looks
fantastic.
It
really
does
I
love
it,
but
you
would
want
to
have
in
your
brain
in
the
future.
As
you
go.
One
way
to
have
to
increase
accessibility
is
to
be
able
to
plug
the
cli
into
a
very
nice
wizzy
wiggy
front,
end
kind
of
thing
and
have
the
same
information
export,
and
there
are
some
tools
that
I'd
really
love
to
have
a
an
extension
for
that.
C
A
A
Style,
what
are
just
the
functional
things
that
need
to
be
done
in
what
order
and
make
those
as
simple
as
possible?
What
can
we
cut
out,
and
then
this
is
the
this
is
the
the
first
draft
of
the
experience,
but
absolutely
we.
This
is
designed
in
a
way
to
make
it
scriptable
and
pluggable
and
automatable.
C
And
all
I'm
talking
about
is
make
don't
don't
hedge
yourself
in
down
the
line
and
that's
it.
The
experience
that
I
see
here
is
really
cool.
I
really
like
the
accessibility
of
installation
with
all
the
package
managers.
So
that's
critical
right.
You
should,
you
know,
give
developers
like
brew,
brew,
install
or
or
you
know,
apt-get
or
whatever
they
want
and
really
early.
C
So
they
don't
have
to
think
that's
really
good
the
layout
the
ability
to
exit
pretty
much
any
editor
which
I,
like
all
of
those
things,
really
make
ease
of
of
of
use
instant
rather
than
delay
it
right,
and
I
think
that's
fantastic
so
outside
of
that
I
mean
this
looks
fanta.
This
looks
really
great,
so
I'd
invite
radu
and
and
fisher
and
butcher
to
like
wade
in
and
give
their
nits.
A
I
H
D
A
So
if
we
it's
up
here
at
package
cloud,
I
I
don't
know
what
the
status
is
on
making
it
live,
but
we'll
have
it
integratable
into
your
host
operating
system
so
that
we
can
so
that
you
can,
even
you
know,
stay
up
to
date
with
your
standard
package
management
tools,
get
notified
of
any
updates.
You
know
those
those
kind
of
things
and
with
that
maybe
oh
and
brew,
is
on
the
way
we're
trying
to
get
this
finished
in
time.
A
G
Not
not
not
a
whole
lot,
yeah,
mostly
just
like
well
right
now,
I'm
playing
with
like
tui
and
saying
what
kind
of
stuff
they
got
going
on
in
there
and
adding
some
stuff
to
wash
up
also
helping
bill
with
some
of
the
build
stuff,
the
wasm
three
like
rust
package.
It
requires
clang
nine
to
build
and
it
was
not
liking
being
built
in
a
cross
container.
G
A
Let's
see,
and
then
let's
see
on
the
oh,
so
wasm
cloud
is
the
next
discussion
here.
So
what
is
wasn't
cloud
so?
The
last
few
months,
you
know,
we've
been
really
kind
of
like
working
with
this
ecosystem
of
tools
here,
and
you
know
that,
as
more
people
have
continued
to
join
the
community,
I've
been
meeting
with
some
of
the
stakeholders
that
are
building.
A
This
would
all
go
right
into
watson
foundation
today,
like
today,
already
be
there
right,
but
what
we
want
is
a
placeholder
for
the
short
term
six
months
or
a
year,
however
long
that
takes
to
kind
of
get
out.
So
what
we've
done
in
the
interim
is
we've
actually
created
a
new
entity.
This
is
like
a
real,
a
company
called
wasmcloud
and
we're
gonna
be
relaunching.
This
is
the
kind
of
like
vision
for
relaunching
the
site
that
really
starts
to
focus
around
the
experience
of
what
wasn't
cloud
is.
A
We've
got
some
draft
logo
designs,
but
hopefully
we'll
have
that
ready
in
a
week
or
so
here
and
we're
really
thinking
through
more
of
the
community
stuff
compared
to
our
regular.
You
know
site,
which
is,
you
know,
currently
been
at
wasp.dev.
You
know
this
kind
of
takes
you
right
into
the
tactical
without
giving
you
the
kind
of
like
high
level
and
the.
How
do
we
continue
to
onboard
the
community
into
here?
A
So
what
you'll
see
in
the
next
week,
or
or
so
is
us
rebrand
start
rebranding
things
out
to
vosm
cloud,
referring
to
the
suite
of
utilities
that
work
all
together
and
then
also
relaunching
documentation,
our
packaging,
I'm
relaunching
some
new
tutorials
here.
This
is
all
just
you
know,
kind
of
concept,
stuff,
some
high
level
videos,
as
well
as
some
community
resources
here,
so
I'll
link
the
this
as
a
demo
in
to
the
notes.
A
A
Just
haven't
gotten
there
as
a
community
yet
so
we
still
want
to
make
sure
we
keep
that
momentum
going
and
what
would
likely
happen
is
we'll
try
to
join
his
incubating
and
then,
when
watson
foundation,
whatever
by
code
alliance,
picks
up
and
actually
exists,
will
swing
over
and
either
stay
in
both
or
you
know.
However,
however,
we
sort
of
do
the
you
know
the
back
and
forth
any
questions
or
thoughts
about
what
our
plans
are
for
wasn't
cloud,
and
you
know
where
we're
where
we
plan
to
go
with
that.
C
Not
at
all,
I
I
mean
not
on
my
part,
I
think
that
makes
complete
sense.
You
need
to
move
forward.
You
want
to
make
sure
that
you
make
the
statements
about
being
good
community
members
and
looking
forward
to
what
the
overall
community
does,
I
don't
think,
there's
any
blockers
and
that
I
can
think
of
you
know
the
any
issues
at
all
in
that
in
that
idea,.
A
A
B
A
A
B
D
I
am
sorry
for
the
delay
there.
The
the
change
that
we've
been
doing
for
the
the
control
interface
has
essentially
changed
every
single
file
in
that
whole
branch.
So
I
just
wanted
to
get
that
one
merged
and
then
I'm
going
to
go
through
and
see
how
easy
it
is
to
to
fix
up
those
other
ones
but
yeah.
Once
we
merge
what
is
it
number
16?
I'm
gonna
go
through
and
follow
up
on
the
other
ones.
They
should
be
quick.
K
H
Yup
I'll
give
that
vr
a
try
later
this
week,
and
I
think
I
do
have
a
tiny
pr
on
the
wasm
time
provider
for
web
c
that
addresses
one
to
do
in
there.
I'm
not
sure
it's
probably
one
of
the
areas
that
I'm
particularly
interested
in
is
web
c
and
knowing
what
direction
is
taking
given
all
the
changes
that
are
going
on
with
wasm
cloud
and
everything
else.
D
So
in
general,
what
we've
been
doing
is
making
wapc
easier
to
use
and
making
the
difference
between
wapc
and
wasmcloud
to
be
less
brittle.
So
wasmcloud
has
moved
to
completely
generating
all
of
its
data
types
that
it
uses
for
the
webassembly
modules
and
so
now,
essentially,
the
only
real
difference
between
a
straight
wapc
module
and
a
wisem
cloud
module
is
that
wires
and
cloud
ones
are
required
to
implement
health
checks
and
wapc
ones
aren't.
But
that's
essentially
that
plus
the
embedded
signature.
A
Phil's
phil
couldn't
make
it
today,
but
he
is
working
we'll
get
a,
hopefully
an
update
from
him
next
week.
I'll
put
it
on
our
backlog
around
all
of
the
work
around
wapc.
Essentially,
you
know
what
we
really.
The
big
feature
that
we've
been
working
on
pulling
in
has
been
support
for
additional
languages.
That
flow
right
into
us
is
the
first
piece
and
then
down
downstream
on
our
roadmap.
Here,
a
little
bit
is
we've
been
testing.
A
Wasn't
cloud
running
right
in
your
browser,
so
you'll
be
able
to
have
the
back
end
components.
You
know
you
know
the
iot.
You
know
all
the
all
the
things
and
then
also
have
the
same
components
of
running
your
browser
as
well.
We've
done
some
early
testing
on
that
kevin
doesn't
feel
there's
any
blockers
there.
But
that's
that's.
You
know
where
we're
going
with
this,
with
support
for
all
the
languages
in
the
ecosystem
and
all
the
other
pieces
as
well.
H
H
A
Yeah
you
know:
we've
had
there
been
some
real
heart-to-heart
discussions
with
the
bi-code
alliance
crew
on,
like
you,
know,
wpc,
and
you
know
it's
fit
and
some
of
the
components
downstream.
You
know
that
are
on
the
roadmap.
For
you
know,
quora
web
is
someone,
but
I
think
I
don't
know
that
we
have
enough
time
in
the
day
to
finish
that
discussion
and
we're
gonna
need
a
lot
more
bourbon
than
what
what
I
think
we
have
on
hand.
A
I
A
A
You
know,
docusaurus
looks
like
an
early
leader,
but
partly
because
it's
you
know
very
similar
to
what
we're
doing
now
with
hugo.
The
advantage
is,
is
that
it's
just
written
for
logs
so
that
it
has
like
baked
in
support
for
multilingual
and
a
few
other
things.
So
we
have
more
experimentation.
There
we'd
love
to
get
a
update
down
there
down
the
stream
about
where
things
are
heading
with
a
crosslit.
A
The
katakota
tutorials
got
mentioned
earlier,
but
that'll
be
early
on
our
roadmap
in
2021,
as
we
sort
of
finish
the
dot,
15
rewrite
and
look
at
scaling,
onboarding
people
a
bit
better
and
then
there
is
there
was
a
discussion
ralph
you
queued
up
around
crossland
and
wasn't
three
on
small
devices
as
a
potential
discussion
and
then
kevin.
How
are
things
on
your
edx
class
for
january?
Is
that
still,
like
you
know
just
another,
you
know
thing.
You'll!
D
J
J
I
jumped
into
all
this
stuff
right
before
a
lot
of
the
turbulence,
and
I
pointed
a
lot
of
people
to
it
and
they're
they're,
just
like
what
the
hell
are
you
talking
about
nothing
works,
so
I
would
love
to
to
be
able
to
help
out
with
the
with
whatever
gets
people
in
faster
and
to
know
what
repositories
and
where
things
are,
so
I'm
not
contributing
to
things
that
are
gonna
be
out
of
date.
Soon.
A
I'll
grab
some
time
with
you
jared
and
take
you
through
the
new
onboarding
experience,
and
we
can
maybe
have
you
start
running
through
some
tests
on
that
as
we
look
at
you
know
like.
I
always
think
in
you
know,
comic
strips
you
know
so,
like
you
know,
we
can
start,
you
know
kind
of
writing
down.
You
know
the
there's
a
couple
of
ways
we
could
go
here.
You
know
we
could
think
about.
You
know
what
would
a
content
roadmap
look
like
for
a
learning
plan
for
people.
You
know
we
think
about.
A
You,
know
awareness
of
a
project.
You
know
learning
right,
education
for
topics.
You
know
selection
right,
so
we
could
think
about.
You
know
the
types
of
content
that
we
need
here.
You
know
we
need.
You
know
blogs.
We
need.
You
know,
videos,
you
know
we
need.
You
know
the
demo
code.
You
know
stuff
like
that.
You
know
from
a
content
roadmap
point
of
view,
or
we
could
also
think
about
as
you
get
in
and
try
to
run
this
script
here.
A
You
know
we'll
write,
you
know
like
the
jared
comic
and
we
can
say,
like
you
know,
you
know
what
was
your
pain
in
you
know
in
in
each
section
here,
as
we
as
you
go
through
and
say:
oh
man,
guys
this
was
terrible.
It's
supposed
to
just
go
on
crossbones.
Maybe
I
should
stick
to
my
day.
Job!
Oh
wait!
This
is
my
day
job
now
right
and
we
could
you
know,
work
on.
You
know
kind
of
like
sketching
out
some
of
these.
J
B
B
You
know
I
fought
for
a
weekend
with
the
crosslit
stuff
and
you
know
I
got
some
marginal
success
there,
but
I
think
it
could
be
a
lot
cleaner
and
I'd
like
to
be
the
one
helping,
as
jared
pointed
out,
put
providing
that
clarity.
As
long
as
I
have
access
to
some
of
the
source
and
materials
I
can
start
to,
you
know:
try
it
out
myself
and
and
then
get
others
on
it
as
well.
I
I.
A
All
good,
so
you
can,
you
can
continue
awesome
and
I
think
the
only
last
thing
I
have
is
a
team
holiday
party.
So
I'm
happy
to
host
another
bourbon
tasting
that
I
will
link.
I
will
send
out
to
everyone
here
and
we'll
do
the
same
thing
as
we
did
last
time.
You
know
with
the
you
know:
five
unlabeled
spirits
and
we'll
do
you
know
a
team
social
event.
I
will
I,
in
the
on
the
forum
that
I
drop
out
I'll
list
a
couple
of
dates.
A
I
will
try
to
make
them
as
accessible
as
possible,
so
we
can't
be
too
early
in
the
day
you
know,
or
we
can.
We
can't
be
too
late
for
other
people,
so
I
don't
know
who
will
end
up
starting
drinking
at
four
and
who
will
start
drinking
at
noon
and
who
will
start
drinking
at
nine,
but
we'll
have
to
make
a
call
on
that.