►
From YouTube: Meshery Development Meeting (July 15th, 2020)
Description
Welcome Ankita and Ronald!
A
A
A
A
I
think
you
know
we
were,
we
tend
to
be
well.
We
tend
to
try
to
be
sensitive,
I
think
in
general.
Well,
some
of
us
try
to
be
sensitive
about
sort
of
inclusion
and
diversity
and
things
but
boy
when
it
comes
to
the
Pacific
time
zone
I
mean
people
just
there's,
no
apologies
for
it.
It's
just
like
that's
the
only
time.
That's
that's.
A
A
A
A
B
B
A
As
you're
bringing
that
up,
I'll
say
that
it
was
kind
of
an
open
question
as
to
whether
or
not
the
measure
UI
should
be
mobile-friendly
right,
I
think
it's
not
necessarily
intuitive
that
that's
a
high
priority.
Well,
no,
that's
the
wrong
way
of
saying
it.
It's
not
necessarily
intuitive
that
it
should
be
mobile-friendly
I'll
propose
that
it
is
a
goal.
It's
just
not
a
not
a
high
priority
goal.
A
Three
reasons
why
one
is
because
in
general,
you
should
like
in
general,
you
can't
believe
how
low
of
a
resolution
some
of
the
projectors
that
you
will
display
this
thing,
that
you'll
show
this
to
others
on
our,
so
that
sometimes
you
find
yourselves
in
situations
where,
if
you
can't
see
the
field,
it's
bad,
especially
if
you're
trying
to
present
to
other
people
the
ability
to
collapse.
The
menu
bar
helps,
but
only
gets
you
so
far.
A
C
A
A
C
What
was
going
inside
my
mind
was
that
you
saved
the
would
run
our
instance
of
Mishra
if
you
want
to
save
run
a
tutorial
or
something
like
that
right,
someone
can
interact
with
it.
We
just
deployed
somewhere
I.
Don't
particularly
remember
him
said
things
he
talked
about,
but
over
there.
If
I
think
a
person
can
use
it
in
a
mobile
friendly
way.
Yeah.
A
That's
a
great
example
that,
like
part
of
part
of
that,
was
that
we
could.
We
run
massery
as
a
public
facing
sandbox
for
people
to
come
and
learn
about
service
meshes
that
might
be
kind
of
nice.
People
might
come
to
the
site
and
just
like
they
play
with
docker
or
play
with
kubernetes,
they
might
play
with
service
mush,
both
measure
e
and
so
you're.
Right,
like
that,
might
be
any
number
of
clients.
A
You
know
user
agents
visiting
as
a
matter
of
fact,
like
you
guaranteed
to
get
mobile
people
showing
up
there
so
that
that's
a
good
example,
the
the
other
two
ways
in
which,
and
maybe
now
that
you've
said
that
dhruv,
maybe
there's
sort
of
four
but
the
other
two
ways
in
which
people
will
be
using
mesh.
We
very
earnestly,
like
very
seriously,
is
when
whether
they're
in
a
team
environment
or
not,
they
found
that,
like
oh
there's,
certain
features
on
that
they
use
on
an
ongoing
basis
and
what
will
most
likely
be?
A
The
case
is
that
they
will
take
and
deploy
measure
e
to
the
kubernetes
cluster
or
they'll,
deploy
it
that'll
be
the
most
likely
case
they
might
deploy
it
as
a
docker
compose
that
up
on
a
separate
server.
But
but
point
is
they're
gonna
they're
going
to
deploy
at
once
and
they're
going
to
point
they're
gonna,
remember
where
it
is
and
they're
either
gonna
sign
in
by
themselves.
Are
they
gonna
have
their
their
team's
sign
in
when
they
do?
A
If
they're
doing
it's,
it's
likely
that
they
will
measure
will
at
some
point
produce
it
produces
alerts
today,
but
doesn't
notify
people.
It's
likely
at
some
point
measure
II
might
notify
people,
they
get
an
email
and
they
click
to
go
check
it
out.
They're,
like
you
know,
chances
are,
they
might
be
on
their
mobile
if
they
want
to
come,
run
a
test
or
like
the
results
of
tests
or
or
perform
any
of
the
actions
that
that
Murray
has
it's
possible
that
they
will
but
they'll
hit
it
on
them.
I
guess.
A
My
point
is
like
hey,
once
they've
begun
to
use,
measuring
in
an
operational
way
like
that
that
they
are
likely
to
use
a
mobile
interface
about
as
likely
as
they
go.
Okay,
I
can't
tell
you
how
many
PRS
I've
just
reviewed
this
week
on
my
freshly
downloaded
github
app
for
the
phone
and
that
type
of
a
task.
Where
are
you
doing
it?
You
know
looking
at
code
ifs,
you
wouldn't
think
you'd
want
to
do
in
the
mobile,
but
it's
formatted
in
the
right
way.
You
can
kind
of
get
it
done
anyway.
C
Right
now
mobile
is
usable,
but
it's
not
that
great.
That's
what
do
you
wanna
say:
I
didn't
change
this
according
to
you,
thinking
that
someone
will
use
their
mobile.
I
was
just
thinking
about
the
small
screen
and
a
project
or
something
like
that,
so
yeah
generally,
the
performance
page
is
responsible.
Now,
according
to
what
we
had
before
I
guess.
This
is
the
older
deployment
which
we
had,
which
is
not
so
good,
but
the
new
one.
A
What
it,
no,
it
really
is
better,
as
a
matter
of
fact
like
it's
in
some
respects,
just
a
matter
of
convenience,
as
even
as
a
developer
as
you're
sitting
there
working
on
ma
cherie
you,
especially
the
UI
you're
likely
to
have
want
to
have
it
up
and
be
and
have
your
code
up
at
the
same
time.
So
if
you
have
a
split
screen
going
on
it's
nice
to
yeah,.
C
C
There
are
a
few
workarounds
which
we
can
do.
I
need
to
ask
people
because
they
would
be
I
beg
you
I
changed
like
we
can
remove
the
labels
itself
when
it
is
when
the
break
point
becomes
lower
than
something
or
like
nickel
pointed
out.
We
could
like
shorten
the
description
itself
like
we
can
change
in
form
into
env
and
performance,
so
PRF,
something
like
that.
Totem.
C
D
A
One
is
really
the
notion
that,
when
people
are
earnestly
using
measure
E
as
an
operational
tool
for
like
ongoing
production
use,
it's
most
likely
that
they
will
have
mesh
redeployed
permanently
like
as
a
as
an
app.
You
know
as
a
work
load
deployed
in
kubernetes
that
probably
one
or
more
people
sign
into
as
a
multi-user
thing,
and
they
use
it
to
do
whatever.
A
Whatever
that,
whatever
piece
of
value
that
they're
deriving
from
massery
and
it
is,
it
will
be
some
of
the
time
that
they
will
want
to
go
in
and
either
look
at
a
test
result,
do
a
validation
of
a
how
it's
how
a
service
mesh
is
configured
or
just
sort
of
any
any
of
the
they
might
want
to
invoke
a
test.
They
might
be
it's
it's
bizarre
that
they
will
inevitably
hit
it
through
mobile.
A
Is
likely
that
it
probably
will,
through
email
or
something
else,
and
when
people
get
that
notification
chances
are
higher,
that
they
or
there's
a
decent
chance,
they
might
not
be
at
their
desk,
and
so
it's
in
the
case
that
people
are
like
us
if
we're
working
on
for
developing
mastery
and
we're
running
it
locally
on
our
local
machine.
It's
you
know.
It's
convenient
that
it's
not
critical!
A
There
will
be
a
cases
where
people
won't
care
about
the
UI
at
all.
They
might
just
build
mesh
REE
into
their
pipeline
and
the
UI
isn't
what
they're
looking
for
or
they're,
not
looking
for
it
they're.
Maybe
looking
for
performance
test
results
after
the
fact
or
something
like
that,
and-
and
that
actually
is
another
good
use
case
actually
for
a
mobile
friendly
UI
is
like
they
build
it
into
their
pipeline
they're,
making
a
release
of
their
application
and
part
of
making
that
releases
that
they
deploy
it.
A
They
use
mastery
to
maybe
deploy
a
mesh,
deploy,
the
app
run,
a
performance
test,
and
they
have
a
certain
bar,
a
certain
line
by
which
the
performance
tests
they
consider
that
it
either
passes
or
fails,
which
is
by
the
way,
a
use
case
that
we
need
to
take
on
in
my
sri
yeah,
particularly
in
the
event
that
it
fails,
they're
likely
to
get
a
notification
or
they're
likely
to
see
that
the
pipeline
failed.
That
check
failed
and
out
there.
A
A
C
A
A
A
E
A
The
more
of
a
platform
native
notification-
that's
certainly
nice,
but
we've
yet
to
have
you
know
a
true
mobile
app
and
so
to
facilitate
those
notifications,
a
little
bit
of
infrastructure
necessary
to
so
so
yeah.
We
don't.
We
haven't
quite
made
it
there
yet
and
actually
two
cushions
point
like
cush
had
a
great
question
about
like
hey:
are
we
sure
that
having
a
mobile
friendly
interfaces?
Is
you
know
it's
really
a
goal
like
you
know?
Do
we?
A
How
often
do
we
think
that
we'll
have
people
on
small
devices,
doing
these
big
tasks
and
so
to
krish's
point
I'm,
not
convinced
that
we
will
that
as
a
project
that
we
will
ever
necessarily
try
to
put
out
a
mobile
app
like
like
there
are
mobile
use
cases.
There
is
the
need
to
see
a
performance
results
of
a
performance
report
or
the
results
of
a
best
practices
check.
A
A
B
A
Creating
this
performance
specification
for
the
casual
visitor,
the
only
thing
that
really
kind
of
give
content-
you
know,
really
explains
what
this
specification
is
about.
Is
this
animated
gif,
and
this
is
good.
This
is
helpful,
but
we'd
go
probably
a
lot
further
in
helping
people
understand
what
we're,
what
we're
trying
to
accomplish
and
welcoming
them
to
collaborate.
If
we
just
had
a
small
like,
maybe
like
a
single
page
static
website,
maybe
there
will
be
a
couple
of
pages
if
we
get
a
couple
blog
post
going
or
what
have
you?
A
30
or
more
repos,
I
guess
about
33,
which
is
great,
but
there's
some
disparity
between
how
each
of
these
repositories
is
set
up,
and
so
there's
a
bit
of
legwork
to
be
done
about
making
sure
that
they
have
consistency
in
terms
of
the
type
of
labels
that
they
have:
the
github
labels,
the
workflows,
the
github
actions
and
workflows.
The
read
means
the
contributor
guides
and
those
kinds
of
things
I'm
across
each
of
the
repositories,
and
so
muskan
was
gonna
Moscone.
A
E
So,
as
means
like,
we
have
other
BOTS,
we
can
have
a
port
for
the
general
challenge,
general
channel,
as
well
as
a
machine
channel
like
if
a
new
user
comes
up,
then
we
both
can
show
up
our
welcome
message
as
well
as
share
the
welcome
fact
that
we
generally
share
with
each
of
them.
So
that
will
be
a
handy
thing.
For
the
newcomers
is
some
of
the
times.
It
happens
that
a
few
of
the
members
take
sometimes
or
don't
typically
see
you're.
The
user
gets
a
late
reply
for
someone.
A
This
is
actually
a
very
timely
question
for
probably
for
Ronald
I
don't
mean
to
put
you
on
the
spot,
but
your
use
you'd
recently
joined
the
slack
and
you
probably
got
hopefully
a
warm
welcome
from
different
people
in
the
community,
but
you
probably
also
got
maybe
one
message
from
a
great,
but
did
that
even
hit
your
radar
or
was
it
with
a
kind
of
useless
or
did?
Did
it
help
in
terms
of
pointing
you
to
the
newcomers?
Welcome
guide.
A
He
did
get
the
greet
pot
notification,
but
didn't
you
know,
wasn't
really
it
wasn't
presented
a
newcomers
guide
and
so
yeah.
This
is
bothersome
kind
of
tend
to
kill.
His
point
that,
like
the
the
Welcome
guide,
has,
is
a
great
index
of
resources
for
people
to
self-serve
on
to
like
get
access
to
and
kind
of,
you
know
peruse.
E
A
Cruise
on
down
to
an
app
section,
if
there's
a
few
there's
like
you
know,
11,
10
or
11
apps
that
are
here
in
our
free
slack
that
you're
most
welcome
to
use.
As
a
matter
of
fact,
maybe
we
should
try
to
get
rid
of
one
so
that
in
case
someone
has
a
better
idea
for
an
app,
but
anyway
the
one
that
we're
using
right.
Now,
this
greet
pot
is
configured
to
do
this.
If
I,
if
I,
say
slash
Greek,
we
make
the
screen
a
bit
bigger,
I,
say
slash,
greet.
A
A
Anyway,
Nikhil,
if
you
would
like,
if
you're
looking
at
this,
if
you
can
try
to
reconfigure
the
Greek
bot,
if
you
don't
have
those
permissions,
you
know,
let
me
know,
and
if
he
can
accomplish,
you
know
if
it
can
accomplish
well
letting
there's
a
community
management
channel
that,
where
there's
a
collection
of
individuals,
some
of
the
individuals
that
are
on
this
call,
spend
time
trying
to
make
sure
that
everyone
feels
welcomed
and
has
the
right
resources.
It
would
be
great
if
that
greet
Bob
sent
them
as
a
message
there
as
well.
A
A
A
E
So
currently
we
are
having
a
page
when,
when
the
user
clicks
on
the
management
option
in
the
diamond
on
the
website,
it
gets
redirected
to
a
page
with
the
button
in
the
middle
that
the
conversation
read
that
we
are
having
that
we
were
having
so
I
just
wanted
to
clarify
it.
If
we
want
to
use
a
snack
bar
on
that
page
itself,
which.
A
E
E
E
There
we
can
configure
the
adopters
so
I'm
running
it
on
the
local
3004.
So
if
we
take
a
bit
of
time
as
its
P,
so
it
will
be
related
to
the
settings
page
under
the
service
mesh
tab.
So
I
just
wanted
to
try
package
India
where
they
use
XPS
means
a
slide
bar
with
an
with
the
clickable
snack
bar
or
the
beach,
with
a
button
to
redact
things.
E
A
For
discovery,
it's
in
part
because
it's
kinda
the
same
reason
that
we
put
the
adapter
UI
chips
into
the
or,
even
though
there
isn't
the
connection
it's
like
well
until
we
build
a
better
dashboard
people,
if
we
don't
show
them
the
fact
that
there
are
unconnected
adapters,
they
may
not
realize
that
that's
a
task
they
need
to
perform.
So
it's
it's
not
a
great
experience,
but
it's
kind
of
the
best
that
we
can
get
for
this
point
in
time.
A
Yeah,
because
if
you
imagine
that
we
collapse
it
like
the
management
like
conceptually,
even
though
you
can't
tell
there's
two
tiers
of
navigation
in
the
left-hand
side,
nav
or
there's
two
high
level
links,
one
is
called
performance
and
the
other
one
is
called
management
results
that
are
under
performance.
That's
actually
a
sub
sub
menu
item
of
performance,
each
of
the
six
names
of
the
service
meshes.
Those
are
sub
menu
items
of
the
management
menu.
A
If
yeah
I
mean
in
one
respect,
if
we
didn't
show
those
service
meshes,
it
would
be.
My
Cherie
would
look
really
tiny
when
they're
not
connected
right.
You
want
to
enable
control
for
this
for
users
to
hide
things
half
after
the
fact.
So
anyway,
going
back
to
the
kills
question
to
kill
it.
If
you
could
maybe
take
it
from
the
top
we'll
run
people
through
one
more
time
to
make
sure
that
they
understand.
E
A
E
E
C
E
A
Wait
yeah,
if
you
would
yeah,
if
you
go
here
so
so,
just
you
can't
take
everyone
through
it
from
the
top
that
the
majority
of
the
time
that
someone
goes
to
bring
up
by
Sheree
I'm,
hopefully
the
majority
of
time.
They
don't
actually
see
the
UI.
Just
like
this,
with
all
those
green
measuring
icons
on
the
right
hand,
side,
hopefully
most
the
time
mastery
should
be
automatically
connecting
to
its
own
adapters,
but
it
will
be
the
case
that
sometimes
they'll
come
in
and
measure
EES
adapters.
A
A
A
If
you
click
on
one
of
those
so
just
sort
of
by
discovery,
people
will
be
like.
Oh
okay,
couldn't
ping
the
adapter
and
it
sort
of
repeats
itself
could
not
pick
adapter
adapter
could
not
be
pinged.
Okay
and
Tim
Achillas
point
they're
like
well
so
I
guess:
something's
broken
like
what
am
I
supposed
to
do,
and
there's
nothing
in
that
snack
bar
to
cook
on
to
help
them
remediate
the
issue:
oh,
not
the
best
user
experience.
A
First
of
all,
I
would
say
getting
snack
bars
in
general,
not
the
best
user
experience,
especially
red
ones,
I
feel
like
I'm,
getting
slapped
on
slapped
on
the
wrist
every
time
I
get
one
of
those
or
I
feel
embarrassed.
It
like
there's
a
bug
off,
there's
a
bug.
So
that's
part
of
the
experience.
The
kill
is
highlighting
that
okay.
Well,
if
a
user
navigates
over
to
the
like
the
console
link.
A
Yep
yep
that
they
click
and
then
all
of
a
sudden
they
start
rage
clicking
what
the
heck
is
going
on.
This
thing
sucks
I,
can't
this
tool
is
just
you
know,
crap,
and
then
they
and
they
walk
away
and
they
tweet
about
it.
No
I
just
get
they
know
and
so
well,
geez
I
don't
does
this
tool
even
work,
okay
and
so
what
okay?
So
that's
part
of
the
experience
if
they
click
on
management,
assuming
that
they
wanted
to
they'll
get
this
experience.
A
It
says
well,
actually
what
this
is
telling
them
without
actually
verbalizing
it
there's
only
one
thing
to
do
so:
they're
kind
of
driven
to
do
one
thing:
what's
this
is
telling
them?
Is
you
don't
have
your
adapters
configured
they're
not
connected,
so
the
task
here
is
to
click
the
only
button
you
can
click
and
yeah.
If
you
would
make
it
they
get
taken
to
the
settings
page
now,
there's
a
small
improvement
that
needs
to
happen
that
when
they
get
taken
to
the
settings
page
right
now,
they're
landing
on
that
first
environment
tab.
A
They
should
be
on
that
second
tab.
The
service
meshes
tab,
so
yeah,
and
here
this
is
where
they
perform
the
task
of
connecting
the
measure
II
server
to
the
measure,
II
adapters.
So
if
you
click
the
drop
down
list,
you'll
see
basically
the
same
list
of
adapter
names
that
we
were
seeing
in
the
UI
chips
on
the
dashboard
and
if
you
try
to
submit
it's
gonna,
not
work
I,
don't
think,
and
the
same
kind
of
things
like
well
I
get
this
tool
sucks.
A
We
need
to
just
make
up
our
list
of
our
own
unique
identifiers
for
error
code
2008,
you
know,
I'm.
Sorry,
that's
a
bad
that
sounds
like
a
year
error
code,
you
know
13:07
and
they
have
a
code
unique
identifier
that
says
adapter
could
not
be
pinged
and
then
they
should
have
a
button
that
says
you
know,
clicks
gear
to
fix
or
or
whatever
they're
supposed
to
do,
like
The
Killers
showing
which
actually
drops
them
right
into
the
area
where
they
should
be
able
to
fix
this,
and
that's
a
better
experience
than
what
we
have
today.
A
That's
good.
The
question
is
that
the
kills
getting
to
is
well.
Is
there
okay
of
that
improve?
That's
an
improvement
in
the
experience,
there's
an
alternative
way
to
also
improve
the
experience,
and
this
is
kind
of
the
question
that
Nikhil
is
presenting
is
like
Nikhil.
If
you
go
back
to
the
dashboard.
A
And
the
user
is
here,
maybe
there
on
the
left-hand
side
kind
of
rage
clicking
on
you
know.
One
of
these.
You
know
like.
Why?
Don't
why
don't
these
go
anywhere?
The
the
proposal
part
of
the
proposal
is
that
when
they
click
on
any
one
of
those
service
mesh
names
that,
if
you
click
on
management,
to
kill
that
they
would
be
taken
to
this
very
same
page.
That
basically
says
you
know
you're
the
console
adapter
is
not
connected
or
the
sto
adapter
is
not
connected.
Click
configure
settings
to
connect
your
adapter
bait.
A
You
know,
like
there's,
probably
a
little
more
verbage
that
needs
to
be
on
this
page,
but
that
they
would
have
that
experience.
So
I'll
pause
there.
The
question
one
question
is:
does
everyone
agree
that
it's
a
better
experience
when
someone
clicks
on
a
service
mesh
name
that
doesn't
have
a
connected
adapter
that
they're
taken
to
a
this
intermediate
page
that
says
configure
settings.
A
Okay,
okay,
very
good
and
then
there's
another
question
in
here
to
kill.
If
you
go
back,
says
that
I
totally
agree
guys,
yeah
and
by
the
way
and
Ankita
and
Ronald,
keep
calling
you
guys
out
specifically
because
I
want
you
to
feel
welcomed
and
encouraged
to
jump
in
like
this
is
one
of
those
things
like
everyone
is
entitled
to
opinion
opinion
because
everyone
uses
it
and
so
okay,
good
and
so,
like
your
opinion,
is
just
your
user
I'm,
a
user.
A
A
Basically,
it
should
say
couldn't
ping,
you
know,
click
here
to
configure
settings
or
what
you
might
click
here
to
basically
take
him
to
that
same
page
like
that
would
be
our
you
know,
I
just
that
would
be
an
improvement,
I'm
saying
it
as
a
factual
statement.
I
guess,
that's
a
more
of
a
question
and.
A
I
guess
it's
part
of
what
Dhruv
was
saying
earlier
is,
like
you
know,
putting
words
in
his
mouth,
but,
like
you,
drew
of
you're,
saying
okay,
that
this
is
an
improvement,
that
you
would
have
that
second
info
snack
bar,
but
gosh
I,
wonder
if
getting
you
know
getting
one
of
those
in
your
face,
maybe
well
Dhruv.
Would
you
say
it
like
this
that,
because
this
is
actually
the
question
like
getting
one
of
those
in
your
face
is
kind
of
bad
enough,
but
then
like
getting,
two
of
them
is
even
worse.
C
A
D
Like,
rather
than
having
to
snack
bars
or
a
no
clickable
notification
link,
we
can
give
a
pop
up
or
a
model
like
which
can
be
more
detailed.
If
this
is
doctors
successfully
pain,
then
it
can
show
the
status
that
it
was
successfully
pregnant.
If
it
is
not
available
to
connect,
then
we
can
give
some
instruction
in
the
problem.
I.
A
Hey
this
whole,
so
there's
a
bigger
question
here,
which
is
the
the
paradigm
of
user
interaction
that
we're
having
here
where
someone
clicks
a
chip
and
they
get
either
a
green,
blue
or
red
snack
bar
he's
actually
probably
not
like,
like
the
whole
interaction
paradigm,
probably
needs
to
change
so
Nikhil.
For
me,
like
my
feedback,
is
I,
do
consider
that
there
are
two
immediate
improvements
that
would
be
welcomed
and
helpful.
A
Basically,
here's
a
link
to
configure
settings,
those
would
be
an
improvement
and
that
I
agree
with,
or
my
my
opinion
is
that
that
we
wouldn't
want
to
have
to
snack
bars
that
day
and
we
were
basically
repeating
ourselves
and
the
first
one.
We
may
as
well
be
more
helpful
and
tell
them
how
to
fix
it
by
my
third
perspective
is
in
part,
what
was
you
saying,
which
is.
A
Software-
and
this
project
in
particular,
is
a
continual
improvement
and
one
of
the
area's
that's
in
need
of
improvement.
Is
this
whole
interaction.
Around
chips
and
snack
bars
like
snack
bars,
are
not
what
a
user
needs
when
they
are
sitting
there.
Real-Time
synchronously
having
something
happen:
they
don't
need
an
asynchronous.
You
like
notification,
that
some
background
tasks
occurred
or
didn't
occurred.
No,
no!
That's
a
foreground
task!
You're
sitting
right
here.
A
They,
the
snack
bars,
are
best
used
when
there's
some
long-lived
job
or
process
that
they
invoke,
and
it's
gonna
take
like
a
minute
two
minutes
whatever,
and
so
they
go
over
and
they
navigate
somewhere
else.
You
know
they're
doing
something
else
and
all
of
a
sudden
that
other
thing
gets
done
you
then
then
they
can
either
get
a
little
notification
up
in
that
Bell
right
by
it
kills
avatar
or
they
can
get
a
snack
bar
if
it's
appropriate
and
so
for
those
of
you
on
the
call
that
are
interested
I'd,
be
I'm.
A
This
interaction,
alt,
like
maybe
all,
together
and
and
cush,
gave
one
as
an
example
of
a
modal
that
that
could
that
can
work
so
long
as
the
modal's
like
super
easy
to
dismiss,
and
by
that
I
mean
you,
don't
have
to
hit
the
X,
you
don't
have
to
hit
the
okay,
you
can
click
anywhere
and
it
goes
away
because
modal's
are
pretty
bad
as
well
like
they're,
pretty
in
your
face.
Annoying
they
take
over
your
whole.
A
Damn
screen
your
whole
focus
and
imagine
if
you're
sitting
there
clicking
on
something
to
test
it
and
all
of
a
sudden
it
takes
over
your
whole
screen
and
says
like
oh,
this
is
the
most
important
thing
you
have
to.
This
has
to
take
away
your
attention
for
everything
else.
You
have
to
pay
attention
to
this
and
and
guess
what
yes
I
could
ping
your
adapter
like
what
like
you
need
to
take
over
my
whole
screen,
just
to
tell
him
that
my
adapters
doing
okay,
yeah,
okay,
so
I
think
there's
probably
a
better.