►
From YouTube: Status Townhall #33 - Monday April 29, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
A
B
B
B
We
have
we've
created,
what's
called
our
critical
path
to
launch
inside,
for
everyone
who
is
using
rocky,
you
can
see
it.
It's
very
hard
to
actually
I
haven't
figured
out
how
to
kind
of
export
this
into
something,
that's
visual,
but
this
is
the
best
that
I
could
do
for
now.
So
you
can
see
what
these
are.
The
these
are
the
swarms
or
major
kind
of
features
that
are
blocking
the
critical
path,
there's
still
stuff
to
add.
So
keep
your
eye
on
this
or
you
can
star
it
and
be
kind
of.
B
You
can
see
the
exclamation
mark
next
to
the
title,
which
means
that
it's
higher
priority
and
basically
this
will
get
updated
and
regularly
dependencies
will
be
added
and
we'll
see
how
we're
progressing
to
hit
this
goal
by
the
end
of
the
quarter
next
slide,
and
so,
as
we
saw
on
the
last
screen,
Reich
is
now
kind
of
ready
for
us
to
use.
We
finished
our
trial,
we've
decided
to
go
ahead
with
it,
and
we've
got
50
C
license,
which
pretty
much
four
means
for
everyone
on
the
team.
There's
a
license
to
use
it.
B
If
it's
something
that
you
want
to
use
is
an
example
of
it
in
use
with
Oscar,
Dean
and
Jarrett
have
been
for
the
some
of
the
protocol
work,
so
it
just
kind
of
helps
get
like
a
visual
of
things
that
have
been
things
that
have
been
worked
on.
What
the
critical
path
path
looks
like
what
are
some
milestones
and
things
like
that?
As
I
said,
it's
not
mandatory
to
use
it's
just
a
helpful
tool
there.
If
you
need
it,
and
the
janitors
will
be
updating
this
for
the
majority
of
the
swarms.
B
On
on
the
kind
of
shifting
gears
swarm
budgets,
a
lot
of
it,
accenting
utilities
forms
that
were
planning
to
ship
at
the
end
of
q2.
Sorry,
at
the
end
of
q1,
have
now
slipped
into
q2
things
like
tribute
talk
telling
at
work.
So
please
update
the
complete
estimated
completion
times
in
github
in
the
ideas
repo
just
so
that
we
can
then
figure
out
exactly
what
the
swarm
budgets
should
end
up.
B
Looking
like
so
right
now,
a
lot
of
the
swarms
that
were
meant
to
launch
31st
of
March
and
a
shift
to
the
30th
of
June
I.
Think
if
there
is
some
sort
of
realistic
estimates
of
when
these,
when
the
first
versions
will
go
out
the
door,
that
would
be
great
to
get
updated.
So
if
you
are
slowly,
please
make
sure
that
that
happens
and
finally,
some
really
exciting
news,
and
we
believe
this
is
the
first
revenue
that
status
has
generated.
So
it's
super
exciting
amazing
work
to
the
entire
key
card
team
for
making
this
happen.
B
We
just
ticked
over
as
of
yesterday
thousand
euros
in
sales,
which
it's
not
a
lot,
but
it's
definitely
a
significant
milestone
and
hopefully
we
can
see
that
grow
into
its
10
and
100x
that
amount,
but
it's
really
exciting
to
have
it
happen,
so
huge
kudos
to
the
entire
key
car
team.
Amazing
work
and
that's
it
for
me.
C
Next
likelies,
so
here
here's
a
priorities
list
for
2019
and
you
can
jump
into
the
notes
stock
there,
but
just
a
quick
recap:
our
priorities
for
the
year
right
now,
our
increased
community
developer
contribution,
whether
that's
the
bounties
are
just
through
issues
in
github:
increased,
increased
non-developer
contributions,
so
writing
design
spreading
the
word
meetups
things
like
that.
We
want
to
then
raise
awareness
and
build
a
reputation
within
the
security
community.
C
Obviously
its
position
status,
the
application
and
everything
we're
doing
as
a
secure
and
private
messenger
communication
tool
and
then
finally,
to
increase
awareness
and
use
of
SNT
utility
features
and
with
the
priority
on
the
teller
network.
So
you
can
jump
in
to
that
note
stock
and
there's
some
more
details
and
scope
and
and
and
build
materials
and
stuff
like
that
around
that.
So
next
slide.
C
So
the
past
couple
months
has
been
spent
on
an
updated
website.
It
was
pushed
live
on
Friday.
So
thanks
to
everyone
who
helped
with
that
from
reviewing
copy
design,
Jakob
and
Anna
for
being
amazing
towards
the
end,
but
have
a
look
through
it's
it's
fresh,
its
new
and
yeah,
so
phase
2
is
is
starting.
Now
we're
working
on
content
around
all
the
research
initiatives,
SNT
utility
the
features,
and
then
you
know
optimizations,
so
things
like
animations
design,
updates
and
little
updates
here
and
there
next
said
for
q2
and
q3.
C
To
add
to
that
and
then
finally,
looking
into
security
events,
security
minded
events
to
try
and
just
break
out
of
this
kind
of
etherium
space
and
introduce
status
to
the
security
community,
Coris
we're
trying
to
kind
of
hero
Cori
on
various
podcasts
and
then,
whether
it's
through
paid
content
or
third-party
content,
but
just
try
and
amplify
our
message
around
security
through
through
third
parties.
Next
slide.
C
So
linking
out
to
the
workbook
that
Barry
stone
or
books
that
Barry's
done
and
then
we've
got
a
series
of
blog
posts
from
Corey,
highlighting
those
the
workbooks
and
then
there's
really
raising
awareness
around
the
research,
we're
doing
around
token
economics
and
then
what
we
may
try
and
do.
What
we're
going
to
try
and
do
is
approach
various
economics
professors
to
have
them
critique
and
review
it.
Because
once
again,
this
work
is
very
much
research
and
we
want
to
validate
critique
review
just
get
as
many
eyes
on
it
as
possible.
So
potentially
approach.
C
C
C
C
It'll,
potentially
look
at
that
like
translate
about
status
time
where
we
can
then
track
the
progress
of
the
of
the
translations
and
then
also
allow
anyone
from
any
language
to
to
the
translate
status
into
their
own
language,
and
a
really
cool
example
of
that
is
is
react.
Translated
bien,
I
should
drop
a
link
in
here.
I'll
share
it,
but
its
just
a
cool
open-source
way
of
translating
everything
so
I'm
keeping
a
lookout
for
about
next
line,
and
here's
just
a
list
of
other
projects
that
we've
got
going
on.
C
It
still
allows
away
a
long
way,
but
want
to
start
planning
for
that.
Now.
The
teller
network
brand
and
planning
go
to
market
so
in
the
bill
obviously
mentioned
to
go
to
market
strategy.
So
we're
thinking
about
that.
Obviously,
thinking
about
global
campaigns
and
global
comms,
but
then
also
figuring
out
specific
markets
and
regions
that
we
want
to
target
Korea
being
one
of
those
so
we're
just
kind
of
doing
some
market
sizing,
now's
and
initial
research
on
the
audience
and
was
actually
a
really
helpful
report
that
came
out
a
couple
weeks
ago.
C
So
that's
it's
looking
like
Korea
is.
There
is
a
really
good
market
for
us
to
target
for
that.
So
research
setting
goals
and
kpi's
will
then
think
about
positioning
and
branding
to
tell
a
network.
Is
it's
a
status
product?
Is
it
do
we
want
to
kind
of
branded
it
on
its
own
like
key
card
and
embark,
or
is
it
kind
of
a
hybrid?
So
a
lot
of
the
research
we're
doing
now
will
inform
that
that
decision
and
then
obviously
moving
into
production
and
then
well.
C
We
want
to
really
clean
up
and
kind
of
push
the
developer,
onboarding
experience
through
documents
and
through
Docs
and
content,
so
we're
defining
user
journeys
now
Posadas
helped
out
with
that,
and
then
we
want
to
start
with
a
very
small
scope
of
ones,
very,
very
specific
user
journey.
Whether
that's
you
know
the
first
touch
point
someone
has
with
our
documentation
or
if
it's
something
specific,
like
extensions,
probably
do
not
know,
but
you
know
something
like
that.
C
We
wanted
to
find
a
very
small
scope
and
then
really
really
perfect
it
through
content
through
channel
strategy
and
all
of
that
stuff.
So
we're
working
on
that
now
and
then
finally,
working
with
the
embark
team,
there's
a
series
of
content
that
we're
gonna
push
out.
Pascal
has
been
amazing
with
that
via
Twitter,
and
we
also
want
to
pilot
like
a
contributor
Welcome
package
to
know
so
when
we
noticed
someone
using
embark
and
is
taking
an
active
role
in
their
channels.
C
We
just
want
to
want
to
send
like
a
surprising
to
like
my
thing,
like
a
little
Welcome
package
with
some
swag
and
some
t-shirts,
maybe
a
little
bit
of
SMT.
We
don't
know
we're
trying
to
find
that
exactly
what
that
is
now,
but
just
a
welcome
package
for
anyone
and
then,
of
course,
the
event
strategy.
So
the
EM,
our
team,
will
be
at
the
surge
hackathon
in
Bangkok
and
then
also
you
know,
there's
so
many
meetups
and
hackathons
throughout
the
year
that
we
just
really
want
to
position
embark
well
there.
A
D
D
Cool
yeah,
so
quick,
a
couple
things
regards
to
security,
this
one's,
not
super
security
but
definitely
is
speaks
to
the
resiliency
of
status
and
our
user
base.
When
we
start
onboarding
or
much
of
people.
We
currently
rely
on
a
cluster
that
basically
routes
all
messages
and
if
that
were
to
fail,
as
we
saw
during
chaos
unicorn
day,
the
usability
and
resiliency
of
the
status
network
is
quite
low.
D
So,
in
order
to
combat
that,
I
came
up
with
an
idea
of
eating
our
own
cluster
and
that's
basically
a
way
in
which
we
could
remove
our
dependency
on
the
cluster,
while
also
allowing
our
core
contributors
to
learn
how
to
educate
those
to
do
the
same.
It's
initiated
by
discuss
posters.
You
could
find
there,
but
the
too
long
didn't
read
there
is
that
all
core
contributors
are
in
a
status
node.
D
Right
guides
fix,
whatever
infrastructure
needs
to
be
fixed
so
that
it's
easier
to
deploy
and
run
a
node
at
home,
and
then
we
move
on
to
the
the
last
tranche,
which
is
the
non-technical
folks
at
status,
the
core
contributors
who
weren't
running
code,
who
aren't
doing
things,
that's
super
technical
and
once
we
onboard
them
and
teach
them
how
to
do
it
by
that
time.
If
we
do,
if
we
do
this
successfully,
then
everyone
in
the
company
is
running
a
node
which
offsets
a
tremendous
amount
of
a
cost.
We
currently
eat
to
run
status
nodes.
D
It
just
distributes
the
amount
of
work
or
to
monitor
the
cluster
as
opposed
to
putting
it
on
a
few
people
who
understand
how
we
run
this
infrastructure.
It
drastically
increases
the
resiliency
and
reliability
of
the
network
itself
and
when
we
start
getting
new
users,
we
have
as
opposed
to
maybe
five
or
six
people
who
know
how
to
teach
someone
how
to
run
a
node.
We
have
over
60.
D
So
all
of
these
things
can
can
make
a
big
difference
in
not
only
the
backend
resiliency
of
how
the
status
network
runs,
but
the
ability
to
make
that
grow
as
well
as
potentially
reducing
the
number.
A
tional
costs
of
running
that
network
on
status
itself.
So
kind
of
excited
about
this
I
think
it's
a
great
way
for
us
to
not
only
make
status
stronger
but
help
make
the
CRO
quickly
and
hopefully
in
a
cost-effective
way.
D
So
we
need
to
do
some
more
planning
in
terms
of
how
much
that's
gonna
cost
and
the
associated
time
it's
gonna
take
from
people
not
doing
their
their
the
work
they're
already
doing,
because
we
don't
want
up.
You
don't
want
to
like
stop
production
altogether
in
order
to
get
this
done,
it
needs
to
be
done
in
a
good
way.
So
that's
that
I'll
have
more
stuff
I.
D
Think
my
next
Town
Hall
I
should
have
a
roadmap
based
on
what
this
is
going
to
look
like
and
if
we're
capable
of
doing
it
soon
it's
for
security
we
have.
If
you
didn't
know,
we
have
a
retainer,
a
security
retainer
with
trailer
bits.
That
is
basically
a
way
for
us
to
do
security
related
overview
of
projects
within
the
status.
So
anytime
we
have
a
product
product.
We
can
ping
them
to
have
them
check
it
out.
D
If
there's
any
fishy,
pull
requests
or
things
that
are
in
question,
we
can
always
bring
them
in
to
have
a
quick
assessment
or
throw
their
weight
from
a
security
lens
perspective.
I
also
do
organizational
process
check
and
consultation
with
me
to
make
sure
that
the
organization
of
status
is
running
appropriately
and
we're
not
doing
anything,
that's
out
of
the
ordinary
or
not
or
not
best
practices.
D
So
if
I
have
questions
or
someone
does,
we
can
always
ping
them
for
that
type
of
stuff,
and
we're
also
doing
a
lot
of
work
to
integrate
a
lot
of
the
trailer
bits
tooling
into
Embarq,
as
well
as
our
github
repos.
That
will
help
us
improve
the
security
process
of
developing
smart
contracts
as
well
as
automation.
D
D
One
is
when
they're
starting
a
new
swarm
project,
and
so
they
ping
security
check
at
status
with
the
idea
of
what
they're
doing
and
answers
to
a
list
of
questions
which
you
can
find
at
the
bottom
that
try
and
help
guide
you
on
making
sure
that
you're
answering
and
looking
at
some
pivotal
aspects
of
what
your
project
is
supposed
to
do
and
why
it
works
and
how
it
fits
in
within
the
within
the
ecosystem,
so
that
it's
easier
for
us
to
assess
risk
and
overall
complexity
of
what
you're
doing.
So.
D
We
know
how
to
move
forward
and
looking
at
the
security
implications
of
your
project,
and
when
that's
done
so,
we
you
know,
have
an
idea
of
what's
going
on.
Will
you
the
ping
us
again
when
you're
winding
down
a
project
which
by
then
you
should
be
continuing
answering
a
lot
of
initial
questions
that
you
you
started
with,
but
then
have
a
second
series
of
questions
that
make
sure
you've
checked
off
all
the
things
you
should
have
looked
at.
So
when
you
do
that.
D
Basically,
what
I'm
hoping
is
that
you've
created
in
the
process
of
answering
these
questions?
You
have
created
a
spec
sheet
as
well
as
done
all
of
the
final
checks
and
balances
that
would
be
required
if
we
were
to
just
hand
it
off
into
an
audit.
So,
basically,
by
the
time
you
do
you're
winding
down
we're
going
down
the
project
and
you
start
to
ping
security
check.
D
The
questions
below
I've,
guided
you
to
the
point
where
it's
just
ready
to
be
shipped
off
for
an
audit,
and
it's
a
way
that
then
auditor
would
like
to
see
it
so
for
more
information
on
what
those
questions
are
and
what
you
wish
should
be.
Pinging
security
check
with
you
can
find
those
two
notes:
documents
that
help
help
guide
that
and
if
you
have
any
questions
or
feedback,
I'm
more
than
happy
to
take
that
in
and
iterate
on
those
documents
to
make
them
easier
for
you
and
that's
it.
For
me,.
A
F
E
Hello,
so,
regarding
tribute
to
talk,
we
are
now
in
testing.
I
would
expect
it
to
go
over
the
course
of
this
week,
so
it
will
be
a
bit
of
back
and
forth.
So,
regarding
the
swarm
chat
swarm,
we
are
going
to
work
on
other
things
and
as
soon
as
we
get
feedback
from
testing,
we
will
fix
the
bugs
and
so
on.
E
There
will
also
be
an
update
like
a
blog
post,
updating
on
which
decisions
we've
made,
what
the
future
will
look
like
and
how
we
see
it
evolve
in
the
future
and
regarding
the
deployment
of
the
feature
it
might
depend
on
some
decisions
that
we
still
have
to
take
regarding
whether
we
deploy
main
net
or
test
that
first
so
yeah,
there
will
be
probably
some
of
these
decisions
we
made
by
the
time
we
make
the
update,
but
it's
yeah
it's
soon
soon
to
be
available.
That's
it
for
TRADOC.
Thank
you
great.
G
G
What
saying
was
about
like
running
the
note
and
especially
non-technical
people,
to
be
able
to
run
a
note
because
well
have
it
a
nice
UI
is
always
better
than
having
console
if
you're,
not
technical
person,
and
then
we
also
did
another
part.
A
country
I
did
the
first
working
draft.
He
made
it
national
PR.
To
start
us,
go
that
where
you
can
like
register
your
notes
in
a
smart
contract
and
promote
this
notes
with
the
consensus
and
also
pay
there
they're
on
the
only
test
net.
So
again
it's
it's.
H
Right
so
we
did
with
R&D
on
the
on
scaling
with
status
state
channels
we
implemented
most
of
it.
We
just
run
into
some
limitations
with
those
channels
that
were
looking
for
alternative
solutions
and
we're
gonna
look
at
multiple
solution.
At
the
same
time,
I'm
going
to
look
at
those
side
chains
at
the
possible
scalable
solutions,
we
did
some
pre
security
review.
Basically,
we
found
some
issues
that
were
fixed.
We
still
have
more
to
do
with
we're
gonna
experiment
with
the
other
tools
term
and
we
implemented
the
disciplines
arbiter
and
max
sorry.
H
I
Ok,
I
last
since
last
week
the
research
on
on
the
delegation
I
started
to
talk
with
Aragon
to
see
if
they
they
also
research,
wicked
democracy.
So
we
can
probably
have
some
collaboration
together
or
the
use
of
a
convention
like
a
similar
interface.
So
if
there
is
a
interoperability
regarding
the
development,
the
immigrated
to
the
material
UI-
and
there
is
an
our
factory
for
creating
new
delegations
and
another
UI
for
setting
and
viewing
your
delegation
and
that
that's
it
for
now,.
G
So,
basically
why
the
installation
was
a
little
bit
dumb.
Paradise
is
to
ramp
up
something
and
core
improvements.
So,
and
actually
we
have
like
fine,
like
making
a
final
test
for
the
new
release
zero
to
zero,
and
also
we
have
a
hotfix
planned
after
that,
because
yeah
there
are
so
many
things
we
want
to
fill
in,
but
we
want.
We
don't
want
to
make
it
like
never-ending.
G
So
a
few
things
there
were
tons
of
bugs
fix
their
inclusion
like
for
the
ones
that
were
were
fixed
by
non
core
contributors,
which
is
very
cool
so
and
then
one
more
thing
is
like
focus
on
message:
reliability
and
improvements.
Was
it
collect
message,
gaps
that
I
showed
like
two
weeks
ago?
I
guess
the
screenshot,
when
you
actually,
when
we
know
that
you
didn't
receive
a
history
for
a
certain
period
of
time,
because
it
was
outside
the
typical
window
we
receive.
G
We
actually
show
it
to
you
right
now
and
you
can
download
more
messages
and
what
we
are
working
on
right
now
is
that
using
the
same
mechanics
with
these
gaps,
you
will
be
able
to
retrieve
much
more
history
into
in
there.
Any
channel
it's
like
up
to
a
month
or
something
instead
of
just
up
to
a
day
like
right
now
also
what
we're
working
on
is
like
performance
improvements
from
another
side
from
the
mail
server
perspective
and
I
guess
Andrea
is
doing
a
very
good
job
there.
G
We
found
one
of
the
reasons
why
sometimes
mail
servers
have
been
slow,
so
I
guess
we're
trying
to
address
it.
But
it's
it's
not
a
small
thing.
It
doesn't
fit
into
two
weeks.
So
it's
working
progress
right
now.
Also
one
more
performance
improvement
that
we
are
doing
and
also
a
simplification
of
our
code
base
is
to
move
the
protocol
code
to
standards
go
sack
again.
G
It
was
a
didn't
start
like
right
now
it
was
there
for
quite
a
while,
but
I
hope
that
maybe
by
the
next
town
hall,
we'll
have
some
fruits
of
this
already
done
and
yeah.
We
are
testing
a
slightly
more
reliable
way
to
get
messages
from
mail
servers.
I
mean
that's.
If
you
have
a
spotted
connection,
you
will
still
should
be
able
to
sooner
or
later
retrieve
your
messages
not
like
right
now.
We
repeat
it
over
and
over
again,
but
again
yeah
that
soon
your
release
is
coming
pretty
soon
so
yeah,
that's
it
from
my
side.
G
F
So
we've
been
continuing
to
document
the
current
protocol.
We've
been
working
on
the
reference
client
a
bit
as
well
as
the
status
improvement
protocols.
Then
Oscar
started
working
on
minimum
viable
data.
Sync
requirements,
we've
been
continuing
to
spec
out
the
Minimum
Viable
Data
Sync
and
we're
working
on
an
implementation
there
which
we're
going
to
implement
into
the
reference
client
as
well,
and
we
continue
to
have
our
bi-weekly
calls
with
the
web.
3
foundation
validity
labs
named
swarm
to
talk
about
web
3
messaging.
A
Cool
thanks,
Dean,
all
right
and
I,
believe
that's
it
for
our
swarm
updates.
Now
we're
gonna
jump
into
Q
&
A.
These
were
questions
that
were
submitted
from
the
town
hall
questions,
so
the
first
one
is
a
chat
interface.
Currently,
the
status
chats
page
layout
reflects
that
of
telegram.
I
know
there
was
work
going
on
to
a
separate
group
chats
but
wondered
if
there
were
any
current
or
future
plans
to
make
the
chat
UI
more
akin
to
most
guys
Wow
similar
to
how
discord
functions.
I
feel
a
status
gross.
A
F
F
So,
hopefully,
one
day
in
the
future
we'll
have
much
better
filtering
rules
and
different
ways
that
you
can
create
your
own
kind
of
customized,
subcategories
or
customized
groups.
Based
on
these
filtration
rules,
there
will
have
to
be
things
like
tagging
systems
and
yeah.
So
so
it
wouldn't
be
like
it
wouldn't
be
like
what
currently
exists
in
discord.
It
would
be
basically
a
more
unique
way
to
manage,
like
tabs
in
a
browser,
for
example,
when
there
will
be
done.
Who
knows
maybe
never,
because
we
might
even
find
a
better
solution
than
that.
I
Regarding
this,
in
future,
we
expect
you
have
many
parts
of
the
clients
that
have
different
shots
interface,
so
we
can
actually
have
for
a
specific
demographic
that
likes
a
specific
way
of
grouping
their
their
their
information.
We
can
have
a
fart
for
that
and
I
see
that
in
future
status
is.
We
were
also
decouple
the
this
chat
feature
as
a
specific
death,
so
we
can
have
multiple
interfaces
for
that.
I
So,
of
course,
that
there
is
a
lot
of
road
to
go
to
implement
this
separation
and
account
and
a
wallet
in
in
the
database
of
chats
but
yeah
in
future.
We
want
you
to
have,
because
everyone
have
a
different
taste
on
these
things
and
I.
Think
it's
a
valid
point
of
researching
on
what's
the
best
for
general
and
having
these
specific
Forks
for,
for
example,
a
discard
like
status.
Currently,
we
have
a
fork
that
is
something
like
a
gator
or
like
another
made
by
status
gjs
but
yeah.
I
F
A
All
right,
fantastic
jumping
into
the
next
question:
it
is
messaging
research
with
the
research
into
alternative
messaging
protocol.
Other
than
whisper
currently
being
undertaken
is
the
aim
to
have
this
new
messenger
protocol
implemented
within
status
before
I
main
version.
One
release
given
whisper
drawbacks.
G
D
Want
to
add
that
we're
doing
a
lot
of
research
into
other
messaging
protocols
into
this,
as
well
as
a
Data
Sync
layer
which
will
allow
you
to
swap
the
underlying
message
passing
protocol
relatively
painlessly,
without
affecting
everything
above
that
layers,
so
like
the
user
won't
experiencing
much
different
from
from
like
a
end
user
perspective.
But
the
way
the
messages
are
routed
will
change
drastically.
So
that's
kind
of
the
approach
is
to
introduce
the
data
stink
layer
and
then
continue
really
so
much
for
the
research
on
the
way
those
messages
are
passed
below.
I
That
we
also
have
a
great
time
of
using
whisper
like
the
research
of
messaging.
It's
not
like
we're
going
to
change
suddenly,
because
we
had
this
discussion
in
the
car.
Dev
calls
about
changing
the
protocol
rules
and,
and
that's
not
something
that
we
are
going
to
just
throw
away
the
old
clients
and
change
to
something
new.
So
of
course
they
were
so
she
is
for
now
it's
just
a
research,
so
we
just
I
see
that
Whisperer
is
long-living
this
year,
yet
I
don't
see
it
like
being
replaced.
It's
so
fast.