►
From YouTube: wasmCloud Community Meeting - 26 Jul 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
Alrighty,
hello:
everyone
welcome
to
wasn't
Cloud
Wednesday
for
July
26th.
We've
got
a
pretty
quick
and
short
and
sweet
agenda
for
today.
Taylor
is
actually
not
in
the
office
today.
A
So
we're
going
to
push
the
demo
of
the
wit
provider
to
next
week,
but
I'd
love
to
just
start
off
by
doing
a
status
update
on
where
we
are
in
terms
of
moving,
to
wit,
I
know
it's
kind
of
starting
around
the
provider
discussion,
but
we've
also
got
things
around
actors
as
well,
so
we'll
just
go
ahead
and
get
started
with
that
and
then
later
we
can
talk
a
little
more
about
Autumn,
so
just
to
kind
of
give
the
background
for
where
Taylor
was
at
and
and
like
what
he
would
have
demoed
being
here.
A
We
have
a
new
PR
into
the
wasmcloud,
wasn't
cloudy
repo
around
a
provider
SDK
for
wasm
cloud
providers
for
generating
them,
from
wit,
with
IDL
interfaces.
So
this
is
a.
This
is
a
really
interesting
PR.
If
you
wanted
to
see
the
kind
of
back
end
of
all
of
the
you
know,
kind
of
the
code
gin
and
how
it
works
behind
the
wasmcloud
SDK.
A
But
you
know,
essentially,
this
is
a
part
adapted
from
wasn't
bus,
RPC
and
and
part
new
to
work
with
interfaces,
using
wit
instead
of
Smithy
and
also
included
in
this
PR
is
the
essentially
wasn't
Cloud
Core
wit,
that
defines
things
like
our
link.
Definition,
settings
host
environment
value,
basically
just
interacting
with
lots
and
Cloud
providers
and
oh,
if
you'd
like
to
see
an
example
of
the
output
of
this
essentially
Cogen
or
provider
SDK,
you
can
take
a
look
at
Taylor's
repository
for
the
mats
messaging
wit.
A
So
if
you
look
at
the
this,
this
actual
repository
is
using
the
new
SDK
for
providers.
You
can
look
in
the
wit
folder
to
take
a
look
at
the
actual
messaging
contract.
So
this
is,
you
know,
an
actor
would
Define
a
messaging
Handler
that
receives
a
message
and
can
return.
You
know
an
error
or
just
you
know
nothing
saying
it's
okay
and
then
actors
can
make
requests
on
capability
providers
with
the
request,
request,
multi
and
publish
operations.
A
So
from
this
messaging
interface,
the
wit
interface
there's
also
a
world
but
I'll
kind
of
skip
over
some
of
the
lower
webassembly
stuff.
The
the
really
important
thing
is
that
the
new
actual
code
that's
generated
actually
might
be
in
messaging.
Is
nice
and
simple.
A
So
you
know
I
know,
there's
a
couple
of
Lifetime
indicators
and
things
here,
but
we
essentially
and
you
can
instantiate
a
new
Handler
and
then
the
way
that
it
works
in
order
to
like
for
each
of
the
operations
that
you
can
invoke
on
a
provider,
there
is
a
a
trait
and
an
actual
method
that
can
be
implemented
by
a
specific
capability
provider,
so
I
think
as
far
as
this
goes
I'd
actually
like
to
leave
it
to
Taylor,
to
talk
a
little
bit
more
around
the
specifics
on
on
implementation.
A
Just
because
you
know
I
wasn't
present
for
a
lot
of
it,
but
I
will
say
something
which
is
really
exciting
where
this
actual
provider.
A
You
know
this,
this
provider
SDK,
is
working
and
being
generated
from
a
wit
interface.
This
is
for
rust.
So
essentially,
as
we
move
forward
with
this
effort,
we're
going
to
be
trying
to
change
the
wasm
cloud.
First
party
capability
providers
to
use
with,
and
then
you
know
examples
and
everything
from
there.
A
I
guess
I'll
share
one
more
thing
that
I
forgot
to
bring
up
is
that
Roman
excuse
me:
Roman
actually
created
a
issue
milestone
in
the
wasmcloud
wasmcloud
repository,
it's
kind
of
the
first
of
its
kind.
This
one
is
just
talking
the
the
Epic
is,
is
called
widify
and
there's
just
a
couple
of
small
tasks
that
he's
outlined
in
order
to
get
to
this
Milestone
of
using
all
wit
contracts
for
for
our
various
actors
and
capability
providers.
A
So
we're
tracking
some
of
the
work
here,
there's
a
larger
effort
around
creating
a
wasm
cloud
roadmap
that
I
hope
to
share
an
update
with
soon,
but
for
now,
I'd
actually
like
to
ask
Jordan
I,
know:
you've
been
really
involved
in
this
effort.
Did
I
say
anything
super
wrong,
or
would
you
like
to
add
anything
else
here
to
how
this
is
going.
B
No
I
talked
with
Taylor
for
about
an
hour
and
a
half
yesterday
and
yeah
you
pretty
much
nailed
it,
so
him
and
I
are
actually
working
in
parallel,
so
I
think
Brooks
shows
the
the
Taylor's
rust
one.
We
actually
have
the
entire
provider
SDK
being
Rewritten
in
go,
for
wit
as
well
and
I,
think
I
I
shared
about
last
week.
We
have
a
it's,
not
Taylor.
Did
an
example
with
like
a
wasi
contract
with
a
few
edits.
The
was
he
messaging.
B
I
did
a
custom
contract
to
test
something
else
which
is
just
a
ping
pong
you
just
the
actor
pings
the
actors,
the
provider
pings
actor
pongs,
but
the
good
news
is,
we
do
have
both
languages
working
and
then
the
only
other
difference
is
where
Taylor
is
using
a
lot
of
the
bytecode
alliance.
Crates
that
are
provided
I'm
also
have
work
and
I
shared
it
in
slack
somewhere.
B
Porting
the
wit
file
parser
to
go,
which
is
duh
well
done
to
a
POC
level
and
then
from
that
also
go
native
code,
gen,
not
importing
anything
like
rust,
headers
or
C
headers
or
whatever.
So
there,
the
two
are
going
in
parallel
and
if
you're
wondering
why
this
is
necessary.
Yes
Justin.
That
is
it.
B
If
you
look
in
well
I'll
talk
about
it
and
if
you
ask
why
this
is
necessary,
it's
necessary.
As
long
as
providers
are
Standalone
binaries
the
day
we
get
to
componentize
Providers,
we
will
only
need
one
or
the
other.
We
will
not
need
both,
but
that
day
is
in
the
future
somewhere.
So
until
then,
we
we
need
a
language
support
So
if
you
hit
command
and
then
go
into
wazifil.
B
So
this
repo
is
the
the
lexer
in
the
parser,
and
this
little
Toy
command
is
essentially
the
co-generation.
So
it
Imports
that
that
rpc.tommel
and
parses
it
all
to
Wasim
cloth,
specific
code,
gen
and
then
actually
I'll
share
one
thing:
Brooks.
If
I
can
yeah.
C
B
It
because
Bailey
approved
my
picture
this
morning,
try
not
to
share
my
whole
desktop.
So
essentially,
this
is
kind
of
where
we're
at
right.
So
you
have
the
wasm
cloud
host
up
here.
It's
going
to
export
host,
call
and
import
guest
call.
You
have
your
actors
and
your
providers
here.
So
when
I
say
wasifil
I
essentially
have
this
blue
box
created
and
I.
Think
speaking
of
Taylor
he's
in
the
same
spot
at
the
moment
we're
compiling
in
the
capabilities
to
do
this,
which
is
not
what
we
want.
B
Essentially,
this
will
be
its
own
webassembly
component
that
you
use
like.
Was
it
wasn't
tool,
componentized
or
whatever,
and
then
the
actor
will
then
so?
The
actor
being
a
web
assembly
file,
the
Wazi
field
being
a
web
Suite
file
and
then
you'll
push
some
magic
button
and
they'll
become
one
giant
component.
So
right
now
we're
both
working
on.
Essentially
the
imports
and
exports
of
what
is
a
Wazi
fill
at
the
moment.
B
A
Yeah
so
Jordan
with
this
picture,
which
I
actually
really
like
it
says
like
it
says.
One
thing
to
me
and
I
want
to
make
sure
that
I
understand
the
motivation
for
the
swazi
pill.
A
So
the
way
that
I
understand
it
is
when
you
write
a
webassembly
component,
you
can
do
all
kinds
of
component
linking,
but
all
of
that
needs
to
be
deterministic,
so
whether
it's
at
you
know
whether
it's
a
build
time
or
at
instant
sheet
or
just
before,
instantiation
time,
each
individual
interface
or
component
that
you
depend
on
for
an
import
or
an
export.
A
You
have
to
specify
and
then
and
then
satisfy
it,
and
what
I
understand
this
to
essentially
enable
like,
with
the
way
that
was
on
cloud,
is
going
to
do
awazi
film
is
it
preserves
a
similar
way
to
how
we
have
actors
and
providers
communicate
now,
where,
even
if
it's
a
custom
contract
or
one
that
we
expect,
we
can
basically
have
the
flexibility
of
the
webassembly
component
model,
but
still
communicate
over
the
wasmcloud
lattice
to
a
provider.
That's
running
somewhere
else.
B
Yeah,
so
I
don't
want
to
misspeak,
because,
especially
since
Bailey's,
not
here
to
correct
me,
but
essentially
what
I'm
being
told
is
that
wasn't
Cloud
host
will
have
pretty
much
the
whole
Wazi
Cloud
contract
built
in
which
we
can
drop
a
link,
but
is
like
95
of
functionality
that
all
people
will
need.
However,
when
it
comes
to
custom
contracts,
we
will
require
this
Wazi
fill
because
essentially
the
flow.
B
Let's
just
go
this
way
an
actor
you
know,
creates
an
invocation
and
wants
to
send
to
the
provider
and
then
the
payload
inside
the
invocation
can
be
at
this
point.
Whatever
deserialization
serialization
method,
we
want
the
the
envelope
itself
is
message
pack
and
those
and-
and
that
is
a
awesome
Cloud
decision,
and
that
will
stay
that
way.
B
However,
this
Wazi
fill
is
necessary
because
with
a
Custom
Contract,
it
does
not
know
what
to
do
with
that
inside
payload.
So
when
the
host
call
comes,
let's
even
say
when
the
actor
sends
something
like
Ping,
the
swazi
field
will
wasn't,
Cloud
ties
it
and
then
send
it
to
the
host.
If
I
were
using
one
of
the
Wazi
Cloud
built-in
contracts,
I
would
not
necessarily
need
the
swazi
fill.
The
actor
could
go
straight
to
host
call
and
it
can
handle
it.
A
B
Cloud
my
understanding,
because
I,
don't
obviously
you'll,
know
better
me.
My
understanding
is
wash
build,
will
cover
all
of
this
for
us,
because
the
what
the
wasm
tools
componentized
is
a
crate
So,
eventually
wash
bill,
will
have
all
that
built
into
it.
So,
where
right
now
you
get
to
do
it,
the
command
line
confuses
me.
We
go
to
that.
B
What
is
that
web
app
that
like
wasm
Builder
or
whatever
the
component
Builder
thingy
yeah,
so
once
I'm
hoping
soon
we'll
actually
be
able
to
put
a
Wazi
fill
in
put
an
actor
in
and
then
we
can
see
visualize
the
line?
Well,
essentially,
this
exact
picture
because
then,
once
we
have
essentially
these
two
made
into
a
component,
then
we
can
load
it
into
wasm
cloud
and
host
call
it
guest
callability
things
that
these
two
communicate
over.
A
Okay,
super
cool.
The
the
other
thing
that
I
was
going
to
say
is
that
you
know
I
think
that
adding
on
this
Wazi
fill
may
seem
like
more
than
it
is.
It
really
just
seems
like
an
extra
step
of
like
you're,
going
to
be
passing
a
small
payload
and
in
order
to
actually
make
it
work
with
wasmcloud,
especially
with
our
security
requirements.
We
just
have
to
have
a
small
little
wrapper
layer
around
that
that,
like
will
do
a
serialization
trip
so
that
we
can
send
it
over
the
wire.
A
B
B
A
Right
right,
which
is
really
cool:
okay,
great
yeah,
I'm,
really
looking
forward
to
and
I
I
know
that
Victor
is
working
on
some
of
this
and
and
I'm
trying
to
get
caught
up
with
it
as
soon
as
I
can
wrap
up.
A
Some
of
my
work
that
I'm
doing
on
wadham
would
love
to
talk
and
get
some
diagrams
out
for
how
the
wash
build
process
or
if
it's
washed
componentized,
you
know
whatever
we
use,
how
that
all
is
going
to
Stitch
things
together,
because
I
think
it's
going
to
be
a
really
important
part
for
you
know
taking
a
webassembly
component
and
then,
of
course,
with
wasm
Cloud.
We
require
that
all
of
the
webassembly
modules
that
you
run
on
a
waslam
cloud
hosts
are
signed
by
an
issuer,
an
identity
key.
A
We
require
them
to
declare
the
essentially
with
webassembly
now
with
imports
and
exports
you're
kind
of
declaring
what
contracts
you
want
to
use,
but
I
think
doing
it
not
just
at
the
Import
and
Export
level,
because,
like
a
library
could
do
that
and
doing
it
at
the
claims
is
still
a
good
idea
really
teasing
out,
like
the
added
benefit
of
adding
that
adding
the
wasal
cloud
Security
on
top
of
a
component
will
be
a
great
I.
Think
that'll
be
a
great
topic
for
discussion.
A
B
A
You
can
see
that
okay
cool
well
Jordan.
Thank
you
so
much
for
adding
more
info.
There
I
keep
learning
more
and
more
things
about
this
and
I'm
looking
forward
to
getting
involved
more
with
the
the
componentized
effort.
Does
anybody
else
have
any
other
questions
for
me?
I
can
try
or
Jordan.
A
All
right,
sweet,
well,
Justin
did
you,
did
you
want
to
meet
there
or
I
might
have
just
seen
a
seen
a
little
flicker.
A
Nope,
okay,
A
little
flicker,
then
all
right.
Well,
then,
we
can
move
on
to
the
next
part
of
the
the
call
which
I
think
is
just
gonna,
be
a
little
a
little
short
and
sweet.
But
I
just
wanted
to
call
attention
to
the
fact
that
I
started
cutting
out
for
releases
for
Autumn
0.5
yesterday,
and
there
are
a
couple
of
main
things
that
are
going
to
be
going
into
the
0.5
release.
A
It's
going
to
be
going
to
include
some
new
features
that,
of
course,
are
minor
breaking
changes,
so
we're
gonna
bump
my
bump,
a
minor
version,
there's
a
lot
of
fixes
and
features
around
the
multi-tenant
flag
which,
if
you're
looking
in
the
readme
for
wadham
down
at
the
bottom
under
the
advanced
section,
the
multi-tenant
mode
essentially
allows
a
bottom
instance
to
monitor
multiple
lattices
and
one
other
thing
that
I'll
show
for
there
is.
There
is
actually
a
wobbing
cloud
in
production
guide
on.
A
Where
is
it?
There
is
something
under
the
bottom.
Here
we
go
under
the
Autumn,
guys
under
fundamentals,
there's
a
deploying
bottom
guide
and
this
kind
of
talks
through
the
process
of
generating
Nat's
operators
accounts
users.
It's
a
little
bit
of
a
deeper
dive
than
I
expect
anybody
who
is
developing
applications
with
wasm
Cloud
to
go
through.
A
This
is
really
more
on
the
platform
engineer
side,
where
you're
setting
up
your
naps
cluster,
we're
really
trying
to
I,
guess
help
the
documentation
and
how
you
may
use
this
specifically
with
wadham
here
that
you
know,
there's
a
link
to
the
nas
documentation,
but
I
just
want
to
call
out
that
we
are
kind
of
fleshing
out
that
one
feature
the
the
monitoring,
multiple
lattices
or
multi-tenant
feature,
and
then
there
are
a
couple
of
issues
that
I'd
also
love
to
see,
make
it
into
the
0.5
Milestone,
which
is
why
I
started
cutting
Alpha
releases
over
release
candidates
because
there's
new
features
that
are
going
to
come
in
I'd,
specifically
love
to
add
in
logic,
to
validate
manifest,
so
that
when
you
do
a
wash
app
put
or
you
kind
of
try
to
put
a
manifest
for
a
new
application,
we
do
essentially
for
this
version.
A
It
may
end
up
being
a
a
bare
minimum
of
validating.
A
couple
of
fields
are
correct
or
maybe
comparing
a
manifest
to
a
Json
schema.
But
what
I
really
want
to
do
is
add
in
a
couple
of
things
that
just
kind
of
round
out
the
bottom
experience
you
may
have
noticed.
If
you
deploy
an
application
now
the
status
is
always
kind
of
static.
It
doesn't
change.
I'd,
also
love
to
implement
that
so
that
you
can
see
if
your
Autumn
application
is
fully
deployed.
A
So
one
thing
that
you
can't
do
with
Autumn
right
now
is
set
up
an
application,
say
you're
going
to
deploy
an
actor
like
Echo
version
three,
and
then
you
know
later
you
upgrade
your
actor
to
version
four
and
you
say
Hey.
You
know
Autumn,
please,
here's
a
new
version
of
the
Manifest
we're
going
to
run
Echo
version
for
Autumn,
just
Compares
public
keys
right
now,
so
it
sees
that
an
echo
actor
is
running
and
will
be
satisfied.
You
kind
of
have
to
stop
it
manually.
A
So
what
I
really
want
to
do
is
if
you
do
upgrade
a
component,
you
know
whether
that's
an
actor
or
a
provider,
and
you
have
a
newer
version
that
wadham
can
handle
doing
that
upgrade.
A
So
with
that
being
said,
the
just
the
heads
up
there's
a
couple
of
things
that
I'd
like
to
push
into
this
Alpha
release.
I
can
send
a
command
actually
in
the
awesome
Cloud
slack
if
you're
interested
in
trying
any
of
them
out
just
how
to
get
wash
to
download
the
Alpha
version
for
you,
but
I
should
have
a
more
fully
featured
demo
next
week.
I
can
show
off
a
couple
other
things,
depending
on
what
we
can
get
done.
A
I
think
the
last
call
out
there
if
you're
interested
in
contributing
to
Autumn,
which
is
just
a
rust
project.
We've
got
a
couple
of
these
issues
marked
as
good
first
issue
and
feel
free
to
reach
out
to
me
on
or
Taylor
on
slack.
If
that's
something
that
you
find
yourself
interested
in
right,
any
questions
on
the
wadham05
roadmap.
C
A
Right
I
know:
I
didn't
put
it
on
the
agenda
for
today,
but
Liam
I
know
that
there
are
a
couple
of
conferences
that
are
coming
up
that
you
wanted
to
highlight.
At
least
you
sent
me
a
couple
last
week
and
we
didn't
get
to
it
in
time.
For
the
end
of
the
call,
do
you
have
those
handy?
Did
you
want
to
share
some
of
the
upcoming
events
that
we've
got
going
on.
D
I
do
absolutely
let
me
just
pull
up
a
a
couple
posts
here,
all
right,
so
hopefully,
everybody
this
week
saw
the
release
of
the
by
code.
Alliance
updated
roadmap
for
a
webassembly.
D
D
I
want
to
those
documents
going
to
come
at
a
better
time,
because
we
have
two
great
events
that
are
imminent:
we've
got
bacon
the,
which
is
what
I
want
to
call
it.
The
bytecode
alliance,
webassembly
hackathon
nominally
referred
to
as
componentized
the
world,
and
we
also
have
the
Linux
Foundation
was
and
con
cosmotic
will
be
there
and
you
should
too.
D
Let
me
tell
you
why
over
was
incon,
which
I'm
co-chair
of
we've
got
an
incredible
schedule
pulled
together,
highlighting
some
of
the
most
some
of
the
most
exciting
webassembly
projects
from
a
speaker's
perspective,
as
well
as
many
of
The
Usual
Suspects
in
the
webassembly
ecosystem,
I
like
cosmonic
and
wozni
Cloud.
D
This
is
September
6th
and
7th,
so
you'll
see
all
the
exciting
things
and
then
Friday
September
the
8th,
Microsoft
to
generously
agreed
to
host
the
componentize
the
world
hackathon,
where
we're
going
to
take
all
that
knowledge
that
you've
learned
a
breakup
into
groups
by
language
such
as
rust,
Python
and
JavaScript,
and
then
start
porting
popular
Frameworks
to
components.
D
So
it
should
be
a
great
time
to
get
a
lot
of
practical
Hands-On
help
to
socialize
Network
and,
as
always,
you
know
just
continue
to
move
the
ball
for
all
things
was
on
down
the
field.
D
I
also
want
to
go
ahead
and
just
do
a
call
out
that
wasm
day
us,
the
cfp
is
still
open
for
this.
This
is
November
6th
in
Chicago
Illinois.
The
cfp
is
open
until
August
the
6th,
so
please
feel
free
to
reach
out
with
your
proposals
on
anything
that
falls
in
the
intersection
of
cloud
native
and
webassembly.
A
Always
me
who
gets
stuck
on
weather
Duty.
Thank
you.
Liam
I
think
that
thank
you
for
actually
mentioning
the
the
bicode
alliance,
the
updated
roadmap
for
developers,
I,
put
that
link
on
our
YouTube,
and
it's
here
in
the
here
in
the
zoom
as
well.
I.
Think
in
our
slack,
it's
all
over
the
place.
I
really
want
to
call
attention
to
this.
This
is
a
really
sweet.
A
This
is
a
really
sweet
article
to
go
through,
and
the
video
I
I
would
say
is
a
I
mean
it's
not
mandatory,
but
it's
Bailey
has
a
way
of
expressing
things
with
words
and
diagrams
that
beats
text.
So
I
would
highly
recommend
watching
the
video
here
just
to
understand
where
things
are
going
in
the
webassembly
standards
space-
and
you
know
maybe
next
week,
if
we
can
get
our
guest
star
Bailey
to
come
back
on,
we
could
actually
have
her
go
over.
Some
of
this
in
the
community
call
as
well.
A
Some
of
the
things
that
she's
got.
You
know
kind
of
laid
out
on
that
diagram.
I
think
that
was
what
I
had
planned
to
talk
about
during
the
community
call
today.
Does
anyone
have
any
any
other
questions
about
what
we've
talked
to
today?
Otherwise
we
can
move
on
to
just
a
little
bit
of
free
time.
A
Awesome
well
thanks.
Everyone
well,
then,
I
think
we'll
go
ahead
and
open
it
up.
We'll
stay
on
live
stream
just
to
see,
if
there's
anything
interesting
that
we
wanted
to
chat
about.
But
does
anybody
have
anything
that
they'd
like
to
talk
about
in
the
wasmcloud
community?
Some
of
the
efforts
that
we
have
going
on
or
just
general
wasm
community.
E
A
can't
help
but
feel
like
it
would
be
helpful
at
this
point
for
webassembly,
because
there
is
so
much
churn
and
change
going
on
under
the
hood
and
there's
lots
of
different
terminology
being
generated
around
those
new.
You
know
projects
those
new
ways
of
executing
things
that
I
think
it's
it's
easy,
if
you're,
not
on
the
inside
of
that
to
kind
of
lose
track
of
where
things
are
what's
happening
or
what
maybe
even
new
terms
can
mean.
E
So
the
roadmap
is
great
from
like
a
functional
perspective.
If
you
understand
what
those
pieces
are
going
to
bring
to
the
table,
but
I
I
can't
help
but
feel
like
there's
an
opportunity
for
another.
Like
summary,
Style
of
the
landscape.
Sorry,
unless
you
got
your
hand
up
there,
I.
D
Already,
like
yeah
the
when
we
pulled
together
the
the
what's
going
on,
we
realized
immediately
that
it
doesn't
effectively
convey
this.
So
what?
What
does
this
mean
and
those
sort
of
impacts
so
we're
already
working
on
the
next
blog
post?
That
is
the
sort
of
update
to
the
ecosystem
that
drives
pulling
I,
think
the
sort
of
implications
of
what
it
means
and
what
it
means
to
developers
just
the
greater
story.
Here
we
really
had
thought
about
even
holding
it.
D
Nick
Fitzgerald
had
given
us
the
feedback
that
we
should
think
about
adding
that
into
the
blog
post,
but
we
honestly
just
needed
to
get
the
Tactical
road
map
out
there
and
in
a
way
so
that
everybody
understood
what
was
the
state
of
all
the
work
streams
and
how
they
were
related
to
each
other.
What
was
going
to
be
in
Wazi
Preview
2,
what
was
maybe
being
released
at
the
same
time,
but
wasn't
officially
going
to
be
it
and
it
just
get
the
tactics.
The
Tactical
update
out.
D
That's
a
very
insightful
comment
and
if
you're
open
to
it,
maybe
I
could
pull
you
in
as
a
reviewer,
Justin
and
I'd
love
to
get
your
feedback
on
the
post
as
we
pull
it
together.
E
D
I
was
I
was
a
good
person
to
dial
in
those
road
maps.
I
did
the
bulk
of
the
authorship
on
on
the
post,
but
it
was
all
based
on
Bailey's
great
presentation,
that's
recorded
in
the
video.
In
fact,
the
video
came
before
the
post
to
get
it
out
there,
because
that's
where
she'd
done
I
think
most
of
the
hard
work
to
negotiate.
D
What's
in,
what's
out,
but
I
think
I
played
the
role
of
a
five-year-old
very
well
and
a
five-year-old's
understanding,
so
I
think
that
if
I
can
get
it
to
a
level
where
it
means
something
to
me,
I
think
that
that's
super
helpful
and
I
would
certainly
appreciate
both
your
opinion
and
everyone
else's
opinion
on
this
call
for
how
we
dial
that
in
right
for
this.
So
what.
A
Some
yeah
definitely
look
forward
to
the
kind
of
the
higher
level.
Why
wasn't
that'll
be
a
really
that'll,
be
a
great
article.
C
Is
there
a
blog
post
format
that
lets
you
start
it
like
explain
like
I'm,
five
and
then
jump
to
15
and
then
25
and
then
35.
I,
just
think
that'd
be
cool
I've.
D
This
sounds
like
a
great
chat.
Gpt
ask
right
like
the
advanced
version
and
then
to
have
the
all
the
versions
in
between.
A
I
really
like
the
I,
feel
like
I.
Have
this
like
fantasy
sci-fi
thing
in
my
head,
where
you
have
a
blog
post
that,
like
by
default
it
all,
the
text
is
just
like
the
five
minute
or
the
the
five-year-old
level
of
understanding,
and
then
you
have
this
like
slider,
where
the
further
you
slide
it.
The
more
text
can
kind
of
pop
out
the
more
paragraphs
and
explainers
that'd
be
a
pretty
sweet,
pretty
sweet,
little
blog
format.
E
Yeah,
that's
kind
of
what
I've
been
wanting
for
a
while
and
then
having
it
all
in
just
an
easy
text
with
basically
no
external
links,
so
everything
that
is
a
new
term
is
defined
within
the
blog
post
as
well.
It's
all
there.
It's
in
one
place,
I
mean
that
is
also
friendly
to
people
who
might
be
site
impaired
right,
who
kind
of
need
to
just
Deep
dive
on
something
I
feel
like
it'd
be
helpful,
and
then
it
can
be.
C
A
Yeah
I
gotta
say
the
the
best.
The
best
thing
that
I
found
for
documentation
in
recent
years
is
is
docosaurus.
That's
what
was
Some
Cloud
uses.
Now
it's
just
a
really
nice
framework
for
turning
mark
down
in
the
docks
and
and
all
that.
But
there
are
some
Advanced
features
in
it.
I
wonder
if
some
of
them
could
address
this
like
I
know,
there's
versioning
and
internationalization.
You
could
like
hijack
into
one
of
those
to
to
change
like
the
education
level.
A
This
is
like
a
whole
other.
This
is
definitely
a
rabbit
hole
where
we're
totally
off
of
the
talking
about
laws
and
Cloud
things,
but
that
is
it'd
be
a
really
interesting
thing.
John.
If
you
keep
working
on
that.
B
A
All
right,
everyone
well
I,
think
that
probably
I
think
that
probably
marks
the
end
of
this
community
called
short
and
sweet,
just
kind
of
updates
on
the
road
maps
which
I
think
is
totally
fine.
I
really
appreciate
you
all
coming
and
hanging
out
for
a
little
bit
today,
but
we'll
we'll
see
you
next
week
and
see
if
we
can
get
that
woodified
provider
demo
going.