►
From YouTube: WebAssembly Filters Meeting (Oct 18th, 2021)
Description
WebAssembly Filters Meeting - October 18th, 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
We're
ready
to
get
rolling
and
people
are
ready
for
me
to
stop.
Making
making
corny
jokes
zayn
is
coming
on
or
he's
coming
back
on.
A
Zane
has
had
a
heck
of
a
time
with
his
network
connectivity
today,
so
we'll
keep
our
fingers
crossed,
but
gents
and
ladies,
we
haven't
been
able
to
have
this
call
for
two
weeks
three
weeks,
one
part
in
part
because
of
kubecon
in
part,
because
a
bunch
of
other
things
going
on
trying
to
get
ready
for
kubecon
trying
to
get
ready
for
the
dot
six
release
and
so
we're
back
though,
and
so
josh.
I
don't
know
that
you've
been
able
to
join
this
particular
call
the
webassembly
filters.
A
B
Yeah
yeah,
hello,
everyone,
I'm
josh,
I'm
from
india,
delhi,
I'm
currently
in
my
second
year
or
which
is
his
sophomore
year
in
college.
I
I
joined
like
a
leopard
community
in
about
like
one
one
and
a
half
months.
I
I
have
come
contributed
in
the
earlier
five
dot,
io
layer,
5
website
and.
A
Awesome,
that's
great
yash
josh,
there's
a
there's,
a
line
of
prior
yash's
that
have
been
that
had
a
similar
story
as
to
yours
and
so
you're
in
good
company
with
the
rest
of
the
yashas.
I
think
a
few
of
them
aren't
active
at
the
moment,
but
so
it's
nice
to
have
it's
nice
to
have
you
here,
though,
there's
we're
going
to
talk
about
a
little
bit
we're
going
to
talk
about
some
reactive
things
on
today's
call,
so
keep
your
ears
perked
up.
A
D
A
A
A
C
And
node.js
yeah
like
open
source
contributor
to
some
different
organizations,
and
I
like
to
be
like
a
part
of
different
communities
to
network
with
people
and
learn
something
from
them.
A
I
got
you
it's
more,
it's
more
of
like
a
mern
stack
for
you.
I
guess
nice
cool,
oh
good,
to
have
you
cindy
yeah,
yeah!
Well,
good!
Let's
talk
about
some
react
stuff
today.
If
we
can
actually,
I
think
that
might
be
what's
first
up
so
garof,
do
you
wanna
you
wanna?
Take
it
away
talk
about
your
item.
D
D
So
the
user
will
now
have
a
single
import
button
with
drop
down
of
all
the
items
of
imports,
which
will
show
the
normal
local
upload,
url
upload,
plus
the
gita
bump
upload,
and
previously
what
we
were.
Having
was
a
model
over
a
model
that
was
carrying
over
all
the
four
options
for
the
imports
and
the
main
thing
that
needs
to
be
discussed
for
the
github
yeah.
D
This
thing
so
in
the
last
call,
the
last
call
of
duty
gave
me
a
good
review
of
what
the
ui
should
look
like
and
how
we
should
proceed
with
the
github
import.
So
currently,
this
is
not
at
all
a
final
or
a
draft.
D
Even
so,
I
was
not
able
to
move
ahead
with
this
thing,
but
the
main
issue
with
the
github
import
is
thing
that,
should
we
go
with
the
icons
approach,
drop
down
or
the
model
with
four
options,
but
that
will
have
one
issue
that
we
are
using
models
for
every
each
and
every
upload
components
so
model
over
a
model.
A
Yeah
right
yeah
anybody
have
feedback
for
garlic.
A
By
the
way,
garv
I
keep
going
back
and
forth
on
putting
emphasis
on
the
first
part
of
your
name
or
the
last
part
and
like
I'm
confused,
can
you
remind
me.
A
Flipping
back
and
I'm
sorry
to
interrupt
and
I
but
it
bugs
the
out
of
me
it's
like
I
don't.
I
didn't
know
if
it
was
yeah
garov,
which
is
what
we
I
think
have
mostly
been
saying.
I
think
what
you
just
said:
gaurav.
D
A
But
there's
a
different
way
of
enunciating,
where
the
emphasis
is
so
anyway,
garf
garth,
good,
we're
good,
we're
good
yeah,
so
to
give
garb
some
feedback
and
everybody
else
that's
on.
The
call
is
welcome
to
give
feedback
here
by
the
way
everybody
else.
That's
on
the
call,
if
you
haven't
spent
a
lot
of
time
in
mesherie's
ui,
so
one
node
that
is
react
based.
It
runs
on
next.js.
A
We'll
talk
about
that
later,
but
but
there's
also
a
figma
design
file.
I
think
that
to
use
figma
vernacular
it's
a
design
file
for
mastery
ui.
If
you
don't
have,
if
you
don't
have
access
just
request
access,
you
should
have
access,
though,
within
there
we
have
some
well,
we
use
material
ui.
We
have
a
little
bit
of
our
own
tweet
design
language
like
not
much
from
what
material
ui
is.
A
It's
like
hardly
even
a
draft,
so
you're
just
kind
of
throwing
things
on
there
to
to
get
stuff
going,
and
so,
if
you
take
all
this
with
a
grain
of
salt
like
it,
I
don't,
but
hopefully
as
you're
just
throwing
things
on
you're
able
to
grab
like
if,
if,
if
our
component
for
a
button
doesn't
by
default,
have
like
a
primary
and
secondary
like
primary,
being
import
and
secondary
being
cancel
and
those
don't
come
with
default.
Sort
of
centralized
styling.
A
Excuse
me
bless
me
that
then
then
we're
in
trouble
like
we
should
go.
Make
sure
that
that
is
the
case.
That
way,
even
just
as
you're
moving
briskly
and
using
a
button
that
you'd
have
to
be
trying
not
to
have
standard
styling.
D
A
Yeah
anyway,
so
the
same
thing
goes
for
the
import
button,
which
I
think
is
pretty
neat
good
good
of
you
and
new
cars
to
discuss
and
try
to
come
up
with
a
good
user
experience.
A
So
this
will
be
the
second
time
that
we're
going
to
use
that
type
of
user
experience
for
those
of
you
that
have
measuring
ui
up
or
have
played
with
it
in
the
lower
left
hand
corner.
There's
a
question
mark
button
that
question
mark
button.
It
does
a
similar
expandable
it'll
expand
into
a
set
of
buttons
and
just
the
same
as
this
import
button
in
the
upper
right
hand,
corner
is
doing
so.
A
That's
nice
we'll
want
to
figure
out
whether
or
not
we
want
to
add
a
gray
background
or
some
other
background
to
make
sure
that
people
can.
You
know,
see
those
actions
a
little
more
visibly
but
but
in
general,
like
that's
great
guys,
because
you
you're
we're
basically
here
in
the
web
assembly
filters
management
area
for
mesheriy,
we're
basically
offering
users
like
four
different
ways
of
importing
a
filter
which
is
a
binary
file
and
so
yep.
This
is
great
like
hey
before
they
even
begin.
A
A
That
makes
a
lot
of
sense,
utkarsh
and
garb,
as
you
guys
think
about
this,
when
that
modal
comes
up
and
they're
being
asked
to
import,
given
we're
going
to
go
ahead
and
treat
the
service
mesh
patterns,
repo
that
that
organization
and
repo
as
us
as
special
and
so-
and
I
think-
and
I
think
you're
doing
it
here-
you've
got
the
beginnings
of
like
treating
that
special
you've
got
the
kind
of
by
default.
A
It's
when
so
ashish
is
with
us,
something
for
the
three
of
you
guys
or
all
of
us
to
kind
of
think
about,
is
and
and
and
rude
rock
is
seated
content.
A
A
I
guess
I'm
just
trying
to
think
out
loud
with
you
all
so
right
now,
literally,
what
garv
is
showing
is
the
patterns,
interface
for
service
mesh
patterns
and
importing
patterns,
but
the
reality
is
between
patterns
applications,
kubernetes
applications,
kubernetes
manifest,
and
then
this
third
content
type
webassembly
filters
like
all
three
of
those
are
just
we.
We
treat
them
as
content
like
some
of
them
are
in
a
yaml
format.
Some
of
them
are
binary
format,
but
we
have
a
dedicated
github
service,
hyphen
mesh
hyphen
patterns.
A
Like
a
dedicated
organization
just
for
patterns,
we
have
a
repo
wasom
hyphen
filters,
a
dedicated
repo
just
for
a
collection
of
filters,
because
those
are
special
and
they're
being
built
in
this
community
and
they're
being
built
for
purposes
of
helping
people
get
at
the
value
of
a
mesh.
We're
going
to
build
in
you
know,
hard
code
pointers
to
those
different
locations
so
that
people
can
pull
in
that
content.
A
Anyway,
that's
just
a
set
of
thoughts
for
me.
A
A
So
cool,
so
anybody
else
have
thought
you
know
utkarsh
rudraksha.
Anyone
else
comments
on
this.
E
A
One
other
piece
of
feedback,
then
so
I'm
not
sure
who
all
was
on.
I
think
it
was
the
community
call.
I
don't
remember
now
we
were
talking
about
having
a
catalog
of
service
mesh
patterns.
We
were
talking
about
mesherie.io
having
a
catalog
of
patterns,
there's
an
open
pull
request
on
meshri.io
to
create
a
catalog
of
service
mesh
patterns
in
some
respects
when
someone
navigates
here,
and
they
want
to
import
a
pattern
from
the
standard
catalog.
It's
like
oh
well,.
A
They're
kind
of
go,
there's
like
we
might
want
to
have
a
catalog
browsing
experience
for
the
existing
service
mesh
patterns,
because
they're
going
to
want
to
choose
the
name
and
they
might
want
to
know
what
does
it
do
so
they
might
want
to
see
a
little
image
about
it.
Maybe
like
basically
the
same
grid
view
of
like
patterns
to
choose
from
that
would
be
pretty
cool.
A
Yeah,
you
know,
I
think
that
that
makes
sense.
I
think
that
like
if
you,
if
you
go
over
here,
you're
trying
to
figure
out
what
patterns
might
be
available
right
now.
We
have
this
table
view.
It's
like
the
default.
It's
like
the
thing
that
you're
interacting
with
when
you're
managing
patterns
is
a
table.
It's
like
okay,
now
abhishek
who's,
not
on
the
call-
and
I
know
maybe
I
could
ask
shayatan.
A
A
Yeah,
exactly
yeah
he's
working
the
reason
we're
poking
him
is
one
he
should
be
on
the
call,
but
two
he's
working
on
a
configurator,
a
different
interface
rather
than
just
the
table
itself.
A
Well,
I
don't
know
something
it
like.
Potentially
is
just
the
catalog
like
a
c
a
grid,
a
carousel,
not
a
carousel,
but
a
god.
What's
the
right
word,
just
a
set
of
service
mesh
patterns
that
are
available
to
them
to
import
and
use
that
describe
them.
A
Basically,
like
a
catalog
view,
a
grid
view-
maybe
it's
on
top,
maybe
it's
just
to
the
left
to
the
right,
and
then
they
can
deal
with
all
the
patterns
that
they
already
have
loaded
and
if
they
want
to
configure
them
and
things
I
don't
know
like.
A
Because
does
the
user?
If,
if
we
have
a
bunch
of
patterns
that
are
predefined
and
ready
for
people
to
use,
do
they
need
to
go
through
this
process
by
which
they
go
to
click
and
then
import
and
browse
the
catalog
and
figure?
Now?
Why
don't?
We
just
show
them
the
catalog,
and
then
we
can.
Let
them
know
that
either
that
pattern
is
locally
available.
It's
already
been
imported
or
not,
but
either
way
it
it
gets
them
to
their
goal
a
little
quicker.
It
gets
them
to
perusing
patterns.
A
It's
the
same
thing
for
the
awesome
filters
is
there'll,
be
a
you
know,
a
collection
of
awesome
filters
available
that
could
be
presented
in
a
catalog
format,
okay,
so
other
than
monov,
who
I
know,
is
tracking
this
mentally
and
who
I'm
going
to
speak
to
about
potentially
doing
those
things
here
for
yosh
or
sandeep
or
others,
maybe
even
alan,
who
might
like
to
put
together
what
that
catalog
looks
like
does
that
resonate
I
mean.
Is
everybody
kind
of
tracking.
A
I
will
pull
up
the
pr
that
I
was
referring
to
that
has
on
meshri.io
that
has
kind
of
an
initial
stab
at
a
pattern.
I'm
sorry
a
catalog
go
ahead
and
share
here.
So
this
these
are
just
the
outstanding
pull
requests
on
meshri
io,
so
a
meshmate
aditya
had
given
a
shot
at
what
that
catalog
might
look
like
a
little
while
ago.
So
if
we
go
take
a
look
at
his
the
preview
for
his
updates.
A
Okay,
I
might
need
to
find
the
specific
url
so.
A
Pages
service
mesh
patterns-
let's
see
that
this
is
it
so
I
know
I
know
this.
We're
talking
about
patterns
and
we're
on
the
webassembly
filters
call
the
the
thing
is:
is
this
same
thing
is
applicable
to
the
exact
same
thing,
the
exact
same
components
that
we
would
make
are
applicable
to
webassembly
filters.
A
So
there's
a
it's
kind
of
a
pre.
It's
just
like
a
shopping
experience
right.
This
is
it's
calling
it
a
catalog
is
fine
and
what's
missing.
Here
is
a
bit
of
like
a
modal
that
you
might
expect.
If
you
were
to
click
on
to
drill
into
a
single
catalog
item,
you
might
expect
to
either
get
redirected
to
a
page
that
describes
that
more
in
detail
or
just
a
modal.
A
That
shows
you
the
thing
more
in
detail
or,
if
there's
not
that
much
additional
detail
to
show
other
contributors
have
thought
of
something
that
that
is
kind
of
interesting
works,
a
little
bit
better.
So
so
here's
just
a
collection
of
a
grid.
A
So
we
could
use
potentially
some
a
catalog
design.
A
From
the
slash
workshops,
layer,
five
io
slash
workshop
yeah
this,
so
it
might
be
nice
not
to
have
to
give
someone
a
modal
or
not
to
have
to
redirect
them
to
a
dedicated
page,
but
let
them
you
know,
expand
and
collapse
things
this
by
the
way.
If,
if
inspiration
is
taken
from
here,
it's
a
little
bit,
it's
great
that
the
default
click
on
a
card
has
the
effect
of
maximizing
great.
A
It's.
It's
not
necessarily
intuitive
like
how
to
minimize.
If,
because,
if
I
just
clicked
on
the
card,
it's
like,
I
should
be
able
to
click
it
again
to
minimize.
You
know,
reverse
the
action
and
instead
it's
a
read
less
also.
This
means
not
to
maximize
to
expand
the
card,
but
this
means
to
go
to
a
page
dedicated
to
just
that
workshop
and
you
can
go
back
so
this
isn't
the
most
intuitive
experience,
but
I
do
think
that
there's
something
to
be
taken
from
there
yeah
that
icon
looks
like
a
maximize
icon.
That's
alan!
Like
it!
A
A
A
I
don't
know
if
I
just
we
just
couldn't
think
of
any
feedback
to
give
you
about
your
topic
today.
I
don't
know
what
to
tell
you.
It's
a
lot
of
feedback,
it's
nice
to
see
that
expandable.
A
A
F
So
the
thing
for
patents
and
filters
were
done
was
done
a
long
time
ago
and
the
pr
was
much
for
the
app
seeding
of
applications
last
week.
So
as
of
now
the
behavior
for
both
for
offer
not
both
for
all
the
applications,
filters
and
patterns
is
exactly
the
same,
and
that
is
being
reflected
in
the
design
spec,
and
that
is
that,
when
the
machine
server
starts
up
all
of
the
no
there
is
no
extra
logic
or
extra
intelligence.
There.
F
All
of
the
filters
all
of
the
patterns
and
applications
that
are
there
inside
of
the
mesh
image.
They
will
be
seated
with
the
meshes,
so
they
will
be
there
available
in
the
database.
So
the
when
the
user
opens
ui
for
the
none
provider
for
the
local
provider,
he
would
be
he
or
she
would
have
those
patents
filters
and
applications
out
of
the
box.
A
G
A
A
Artifacts
that
mesherie
orchestrates,
all
of
those
are
artifacts
that
mescheri
can
import
and
lets
people
manage,
deploy,
deploy
a
kubernetes
application,
apply
a
service
mesh
pattern,
design
a
surface
mesh
pattern.
You
know,
configure
a
filter,
deploy
a
filter,
so
they
all
get
treated
under
that
same
umbrella
of
being
content
thing
you
know
and
then
seeding.
A
The
content
means
that
when
you
start
up
measuring
that,
if
you
go
over
and
look
at
the
applications
area
or
the
patterns
area,
that
garv
was
showing
that
instead
of
the
ui
like,
which
would
be
like
right
here
if
as
a
well
as
a
user,
if
you
were
to
go
over
to
the
patterns
ui
instead
of
being
shown
an
empty
table,
you
would
see
a
bunch
of
content,
a
bunch
of
patterns
available
out
of
the
box,
so
seating
content
just
means
making
patterns
and
filters
and
applications
available
out
of
the
box.
A
Okay,
good
good
next
topic
well
is
configurating
right,
so
obby.
A
H
H
Configuration
configure
option
which
is
common
for
both
application
and
patterns.
So
once
you
press
the
configuration
you
go
into
this
configuration
option
and
as
of
now,
the
code
has
been
repeated
for
the
applications
as
well
as
patterns,
though
they
both
are
doing
the
same
thing.
So
what
I
was
assigned
to
do
is
to
make
them
a
reusable
component
so
as
if
both
are
fine
and
working,
so
I
will
be.
F
F
A
Yep
make
sense
make
sense
yeah.
I
I
don't
know
that
there
is
a
ton
of
feedback
to
give
because
we're
just
looking
to
have
the
same
experience.
Configuring
applications
and
configuring
patterns
like
more
or
less
at
least
to
start.
A
D
Good
yeah,
maybe
I
have
feedback.
So
what
I
think
zen
was
showing
me
that
zen
had
showed
me
earlier
that
in
the
patterns
code
code
base,
if
zhen
can
show
that
from
the
vs
code,
so
the
patterns
configuration
was
already
inbuilt
with
the
patterns
with
the
in
a
single
file.
So
what
zan
did
is
made
a
separate
file
for
the
patent
configuration
and
separated
it
out
and
make
it
as
a
reusable
component
to
use
it
across
the
applications
and
filters.
D
F
So
currently
the
thing
you
are
seeing
in
the
yaml
editor
is
like
fine
grained
for
the
patterns
only,
but
it
should
be
visible
for
applications
too.
I
don't
know
what
should
what
could
be
the
problem.
A
F
Oh
yeah,
so
actually
I'm
stuck
into
a
different
bug
which
is
on
the
match
map.
I
don't
know.
I
just
tried
getting
away
from
the
class
component
for
one
component
like
the
secondary
drawer
and
things
are
not
working
the
way
it
should
so,
I'm
just
talking
for
a
long
time
on
this
thing,
so
it
couldn't
get
the
time
for
patterns
actually
to
open
gotcha.
Okay,.
H
A
A
A
Neither
did
I
I
was
busy
giving
a
talk
at
servicemeshcon
the
same
day,
but
it
strikes
me
that
there
were
a
number
of
interesting
topics
that
might
one
we
might
want
to
invite
a
speaker
to
come
here
and
give
an
update
to
the
extent
that
we
find
one
of
those
topics.
Interesting
enough.
A
To
this
day,
so
here's
the
schedule,
the
the.
A
Some
of
these
will
have
their
presentations
attached
like
this
from
napkin
to
the
cloud,
a
web
assembly,
oh
yeah,
and
then
the
videos
will
be
out
at
some
point
as
well.
So
maybe
take
take
a
look.
Let's
see
if
we
want
to
invite
any
of
these
folks
to
come,
discuss
what
they
presented,
not
necessarily
to
re-present
but
just
to
discuss
and
engage.
A
It's
another
thing:
that's
been
kind
of
in
the
back
of
my
mind
as
we
as
we're
going
through,
and
talking
about
we're
talking
about
public
catalogs,
that
meshery
will
pull
web
assembly
filters
from
it
will
pull
service
mesh
patterns
from
so
here's
the
repo
that
we're
using
today
wassum
filters
within
the
repo
it.
A
That's
probably
an
open
question
for
all
of
us
to
consider,
as
we
go
forth
here
is
well,
is
that
struck
is
okay,
so
there's
been
any
number
of
people
contributing
to
creating
these
filters
as
we
go
to
encourage
others
to
create
filters
and
contribute
here?
Is
this
the
right
model?
Do
we
want
them
contributing
filters
into
this
same
repo,
or
do
we
want
it
to
be
more
of
less
about
a
repo
with
a
bunch
of
filters
and
more
about?
Should
we
have
a
separate
org,
so
you
can
have
a
bring
your
you?
A
A
Have
you
know
issues
their
own
specific
issues
like
that's
something
to
think
about?
I
think
one
other
thing
to
consider,
as
you
all
think
about
that,
is
that
well
what?
A
If
you
know
what,
if
shaytan
ends
up
writing
a
webassembly
filter
and
like
what's
easier
for
him
to
do,
to
push
his
filter
into
like
he,
he
can
when
he
boots
up
measuring
he
can
he
can
point
to
his
own
repo
and
and
pull
it
in
great,
but
if
he
wants
it
to
be
available
kind
of
generally
to
everyone
and
sort
of
promote
it.
And
let
jubrill
know
about
the
fact
that
there's
this
filter
here
and
he
can
try
it
out
and
use
it
and
provide
feedback
and
all
that
that
well
do.
A
We
need
a
filter
hub
or
or
like
one
way.
If
we
move
out
of
many
filters
per
repo
out
of
that
model,
and
we
move
to
a
model
where
it's
one
filter
per
repo.
Well,
then,
then
we
can
potentially
have
an
org
dedicated
to
this,
and
let
people
bring
repos
or
we
can
create
new
repos
as
and
when
people
well
well,
actually,
community
members
they
can
create
their
own
repos
as
well,
and
let
people
begin
to
build
out
independently,
like.
A
A
Yes,
you
would
right
like
when
we
make
the
measuring
release.
You
would
if,
if
one
of
the,
if
you
as
a
user,
you
try
to
go
use
one
and
it
doesn't
work
you're
going
to
complain
that
mesh
3
doesn't
work
very
well
or
that,
like
you're,
going
to
go,
create
an
issue
and
go
fix
it
within
measuring
right.
It's
a
meshy
thing!
A
Okay!
Well,
if
people
are
contributing
new
filters
here
that
that
just
that
means
that
well
all
of
them
need
to
be
qualified,
as
like,
officially
supported
right
like
like
something
that
you
could
create,
a
messy
bug
about
in
track
could
be
good.
I
mean
the
good
part
is
like
yeah
good.
We
take
on
that
responsibility
and
we've
got
to
make
sure
they
all
work.
Good.
A
It's
worked,
though,
or
it
should
be,
the
other
model
is
a
little
more
loose.
You
know
that
each
individual,
if
it's
one
filter
per
repo.
Well,
you
could
have
some
standard
a
standard
descriptor
about
the
status
of
a
filter
like
oh,
it
was
written
by
so,
and
so
it
is
maybe
been
verified
in
terms
of
its
compatibility
with
a
certain
mesh
reversion
or
it
is
an
official
filter.
A
That's
supported
and
you
can
open
up
bugs
about
or
know,
you've
got
to
go,
see
shaytan,
because
it's
a
community
contributed
one
that
he
he
and
only
he
thought
was
cool
and
anybody
else
was
there
to
help
him
and
so
or
like
anyway.
These
are
the
some
things
to
think
about
and
consider
a
little
bit
because,
because
it'd
be
great,
if
there
were
there's
lots
of
filters
to
make
and
have
out
there
lots
of
different
packets
to
manipulate
and
requests
to
deal
with.
It's
like
mescheri
is
a
platform
right.
A
A
A
A
A
A
Then
they
would
be
in
tree
in
source
code,
main
branch
like
in
in
master
in
tree
and
and
if
and
in
a
good
way,
that
means
that
they
work
if
they're
in
there
they
work,
but
in
a
bad
way.
If
a
third
party,
if
a
community
contributor
or
a
different
organization,
is
trying
to
create
their
own
adapter
or
create
their
own
webassembly
filter
and-
and
it's
like
built
into
the
official
repo-
that's
supported
and
must
be.
It's
like.
A
A
So
I
guess
you
know
this
isn't
the
first
time
that
we're
kind
of
having
some
of
these
thoughts
so
should
there
be
a
filter
hub
where
people
can
bring
their
own
repo,
or
should
it
be
in
a
repo
format,
should
they
just
bring
their
own
filter
to
a
single
repo
or
what
like?
What
is
that?
How
should
that
look
so.
G
Yeah
think
a
separate
or
sounds
good,
because
then
we
we
can
set
a
template
for
those
filters,
so
people
can
probably
use
that
template
and
in
that
template
we
can
define
some
of
the
very
basic
things
that
are,
I
mean
you
would
need
for
defining
a
minimal
what
you
call
that
filter
that
would
actually
help
people
in
identifying
their
needs,
because,
right
now
in
the
wasm
filter
repository
everything
we
have
filters
for
all
those
but
they're
all
at
a
single
place,
and
it
is
quite
possible
that
people
might
get
lost
when
they
are
looking
through
them.
A
A
You
know,
assuming
that
that's
a
stated
goal
that
that
we
want
to
facilitate
that
community
that
there
should
be
and
yeah.
Meanwhile,
yeah
yes,
measure
is
a
platform
to
bring
your
own
content.
A
A
A
So
as
we
look
toward
next
week,
potential
future
agenda
items
include
interesting
topics
from
cloud
native
webassembly
cloud
native
day
web
assembly,
potentially
the
seating
of
content
in
a
remote
provider.
A
And
potentially,
obviously
gara
you
got
some
feedback
there.
Abi
is
trying
to
work
toward
a
better
configurator.
A
For
my
part,
I
don't
we
still
don't
really
have
the
best
of
implement
the
best
support
for
externalized
web
assembly
filter
configuration
so
there's
like
there's
kind
of
two
artifacts
that
need
to
come
with
a
filter,
the
the
binary,
the
filter,
which
is
a
binary
and
then
also
its
deployment
model,
it's
which
could
have
any
amount
of
configuration
within
there.
A
A
And
I
think
that's
it
that's
it
and
if
nobody
has
anything
else,
it's
it
is
a
reminder
to
that.
We'll
see
you
all
on
wednesday
for
the
mesh
redevelopment
call
we'll
have
an
announcement
on
the
community
call
on
friday
about
a
learning
opportunity,
so
mesh
nikhil,
lada
he'll,
speak
to
that.