►
From YouTube: Status Town Hall - March 26, 2018
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).
B
A
Awesome
all
right
so
sorry
for
technical
difficulties
were
testing
out
zoom
now,
because
zoom
integrates
directly
into
YouTube.
So
now
we
can
launch
from
it
instead
of
recording
in
and
uploading
it
later
welcome
everyone
to
our
fifth
Town
Hall
will
be
increasing
the
cadence
of
our
town
holes
to
every
two
weeks
so
that
we
get,
you
know,
foster
a
duration
of
updates
and
things
like
that.
So
we'll
kick
it
off,
because
we
have
a
pretty
detailed
listing
to
get
to
to
get
into.
A
First
thing
is
just
wanted
to
chat
to
our
talks:
open
bounty
contributors,
so
we've
got
food.
Bang,
Boyka
and
alex
kohler
with
new
kind
of
top
are
listed
number
of
bounties
and
we'll
be
doing
this
as
well,
every
two
weeks,
whether
its
top
contributors
or
new
contributors,
and
we
have
two
who
really
helped
build
a
design
and
build
a
website
for
our
f
prize,
and
I
don't
even
want
to
try
and
say
the
first
one
in
CS
76,
so
special
thanks
everyone
for
getting
involved.
B
A
Next,
there's
a
there's,
a
channel
on
riot
and
slack
called
study
fundamentals,
and
it's
basically
started
by
Ricardo.
We
highlighting
what
are
the
most
I
guess,
important
things
for
you
to
learn
whether
it's
newbies
or
people
trying
to
understand
what
we're
trying
to
what
status
is
trying
to
achieve
and
build.
So
here
are
some
highlights,
and
this
section
is
basically
going
to
be.
Here
are
three
things
you
should
check
out
in
the
next
two
weeks.
If
there's
nothing
else
that
you
can
follow
along.
A
So
this,
as
I
said
this
will
be
shared
around
so
check
out
the
links
and
then,
if
you
really
want
to
engage
more,
you
can
go
check
to
Ricardo
Randy
in
the
study
fundamentals
channel
alright
and
that
basically
the
the
intro
part
we
are
gonna,
go
through
three
sets
of
okay,
ours
that
we
planned
all
together
in
starting
off
in
Bangkok,
Chad
Irish
and
got
sick,
we'll
be
giving
an
update
on
that
and
then
afterwards,
we'll
get
in
an
overview
of
how
swarms
are
gonna.
Stop
operating
an
Oscar
will
give
us
an
update.
A
C
D
A
D
So
this
is
a
test
I'm
doing
okay
odds
for
Court.
It
was
pretty
gnarly
in
Bangkok
there
was
a
huge
group
of
us.
We
had
to
get
into
different
groups,
and
it
was
the
first
time
that
we
were
doing
it
so
before
I
get
into
the
okay
ours.
I
just
wanted
to
share
us
very
quick,
so
they
I
did,
which
is
about
how
we
feel
about
the
okay
house.
We
send
another
48
people
and
the
first
question
was:
you
feel
confident
we
can
achieve
these
okay,
Arts
Inc
uses
43%
of
us
said.
D
Yes,
six
percent
said
no,
and
51
percent
said
not
sure.
So
that's
actually
a
half
good
thing
about
okay
house.
We
do
want
to
be
ambitious,
so
I
think
we
should
always
be
reaching
just
above
our
comfort
level
and
speaking
of
some
people,
I
think
that
the
first
rounds
has
been
a
hard
because
we
haven't
had
a
benchmark.
D
So
we
can
measure-
and
that's
specifics
and
I-
think
that's
an
ongoing
process.
We'll
definitely
do
that
better
in
q3.
Is
this?
Okay?
All
this
complete
most
of
us
said.
Yes,
some
of
us
said
it
needs
more.
Some
of
this.
That
means
less
again,
I
think
a
work
in
progress,
but
70
percent
said
yes,
I.
Think
we've
done
pretty
good
for
the
first
time
and
here's
what
some
people
said.
This
needs
more
and
less.
D
D
D
A
good
inherit
to
and
Bangkok
so
I
think
next
time
we'll
have
some
more
times.
I
accept
the
okay,
our
foundations
and
some
comments
are
very
open
process.
Ideas
solicited
well
and
both
enable
participation,
even
those
without
strong
ideas,
opinions
some
of
the
said
process,
not
clear
enough
and
I
think
we
could
do
with
a
bit
more
direction,
but
not
much.
It's
important
people
are
encouraged
to
use
tools
in
a
way
they
themselves
fine,
appropriate.
So
I
think
that's.
D
If
you
can
reach
out
to
me
and
give
me
a
feedback,
this
survey
was
anonymous,
so
I'm
not
sure
who
posted
that,
hopefully
we
can
address
those
hands
and
I
just
wanted
to
put
a
salaryman
give
your
neck
and
a
comment
was
it's
very
helpful
to
have
a
central
point
of
consensus
on
what
should
be
prioritized
and
worked
on.
It's
not
a
perfect
process,
but
it's
definitely
better
than
not
having
one
I
think.
D
Up
the
okay
on
us,
so
with
that
background,
I'll
dive
into
the
okay,
ours
and
all
the
okay
ours
we've
set
on
a
priority
from
p
0
to
P
4
P
Zero
is
a
top
priority.
We
really
need
to
do
it
down
to
three
down
through
to
P,
for
that.
It's
okay,
if
it
slips
so
the
core.
Ok
ours
for
q2,
are
as
follows:
top
priority
really
important.
We
do
this
messaging
is
reliable.
D
Next
p1
priority
beta
is
launched
successfully.
We
really
want
to
get
the
beater
out
and
most
people
vote.
I
should
say
that
these
priorities
came
from
voting.
Most
people
like
about
40
or
50
people
in
the
okay.
Our
core
group
voted
on
these.
So
that's
where
the
priorities
are
coming
from
p2
priority.
S&Amp;T
is
a
powerful
utility
in
status.
D
P3
priority
status
is
used
every
day
internally,
p4
priority
performance
significantly
improves
and
another
p4
implement
continuous
delivery.
So
there
are
core
objectives.
The
key
results
for
those
the
key
results
for
messaging
is
reliable.
We
need
to
make
sure
the
send
delivered
ratio
is
greater
than
99%.
That's
something
that's
essential.
Another
essential
priority
is
that
more
than
95%
of
people
surveyed
trust
status
for
messaging
and
zero
message,
reliability,
insta
bug
reports,
we've
had
a
few
instable
reports
come
up
and
we
want
to
get
that
number
down
to
zero.
D
The
next
objective
successfully
launched
the
beta
main
priority.
We
want
to
have
5000
daily
active
users,
and
that
should
be
obtained
of
link
you
to
p1
key
result.
More
than
80%
of
users
retained
seven
days
after
recovering
an
account
and
Kosta
can
handle
500
concurrent
users
p3
priority
more
than
20%
of
users,
send
a
transaction
and
20%
well,
at
least
more
than
20%
open
at
least
one
dad
and
a
p4
priority
is
that
we
want
to
have
more
than
99%
cost
off
time.
D
D
D
E
Cool,
can
you
guys
hear
me?
Yep
awesome,
hey
everyone,
so
these
are
the
open,
beta.
Okay,
so
same
thing
goes.
As
Chad
said,
these
were
defined
at
bangkok
by
the
swarm
and
prioritized
by
this
form
as
well
and
again.
These
are
work
in
progress,
and
I
think
we
will
be
able
to
further
define
them
as
we
continue
in
this
quarter
and
then
into
next
quarter.
So
just
quickly
running
through
these
the
objectives
for
open
bounty,
the
main
priority
was
really
to
improve
our
onboarding
and
I'll
go
through
what
each
of
these
mean.
E
When
we
talk
about
the
key
results,
p1
was
to
increase
the
platform.
Usage
p2
was
to
make
up
and
bounty
productive
tool
to
create
and
manage
bounties
for
everyone.
That's
using
it
and
p3
was
something
kind
of
new
that
came
out,
which
was
this
concept
of
swarm
experimentation
that
we
wanted
to
really
try
around
and
and
see
how
we
can
extend
the
current
bounty
platform
to
really
work
across
the
end-to-end
ecosystem
of
create
creating
applications
in
a
decentralized
environment.
So
we
can
go
through
that
a
little
bit
more
ok,
so
just
next
slide
cool.
E
So
on
improve
onboarding,
our
key
results
were,
and
some
of
these
are
so
removing
our
white
listing
requirements
are
currently
anyone
that
wants
to
use
the
platform
has
to
go
through
a
whitelist
process,
which
is
a
little
bit
cumbersome.
Our
p1
is
to
launch
an
improved
onboarding
workflow
to
reduce
the
complexity
and
really
reduce
time,
so
we'll
do
some
metrics
around
how
long
it
takes
to
post
and
solve
your
first
bounty,
and
the
idea
is
to
reduce
that
to
be
a
really
manageable
number,
p2
identify
and
prioritize
and
plan
to
quick
fixes
a
week.
E
So
these
are
kind
of
small
you
like
changes
and
that
we
get
feedback
from
the
community
on.
We
want
to
really
have
a
quick
turnaround
on
getting
some
of
those
quick
fixes
in
and
p3
was
against
some
questions
that
came
at
her
on
how
to
better
utilize.
Our
platform
and
I
can
be
done
through
some
quick
wins
through
a
fake
use
and
how-to
videos.
E
E
And
so
we
want
to
get
more
and
more
people
on
boarded
using
the
platform
and
contributing
to
our
code
base.
Obviously,
and
then
really
p2
is
just
in
terms
of
getting
more
traction
through
to
up
and
bounty,
so
we're
currently
our
flea
just
over
7,000
in
terms
of
unique
monthly
visitors,
and
we
want
to
get
that
to
about
10,000
okay.
E
So
the
P
Zero
was
organization,
dashboard
MVP
has
been
shipped,
and
this
this
has
been
a
request
that
has
come
through,
which
is
around
helping
repository,
maintainer
z'
and
those
the
post
bounties
be
able
to
manage
track
their
spending
and
as
well
as
the
number
of
bounties
and
who's
been
working
on
them.
So
that's,
hopefully
something
we
want
to
ship.
This
quarter
track
progressive
bounties,
so
that's
again
around.
Where
is
the
bounty
at
who's
been
working
on
it?
When
is
it
completes
and
be
able
to
manage
each
bounty
a
little
bit
better?
E
Then
this
is
the
next
one.
P2
is
around
our
new
support
contract
integration
that
we're
working
with
consents
is
on.
So
we
want
to
really
implement
this
Marc
contract
to
really
help
the
entire
ecosystem
of
Bounty's
collaborate
a
little
bit
better
and
when
p3
was
around
metrics
that
we
want
to
be
able
to
track
and
monitor
okay
and
the
next
one.
E
Okay.
So
swarm
experimentation,
as
I
said,
is
around
this
concept
of
exploring
different
mechanics
and
different
compensation
models
that
we
can
operate
in
in
teams
and
swarms.
When
we
do
our
work,
so
we
want
to
run
for
experimental
swarms,
exploring
different
mechanisms
for
compensation
and
at
least
at
the
beginning.
E
This
will
be
essentially
on
paper
and
spreadsheets
that
we'll
use
to
monitor
and
track
how
we
progress
and
once
we're
kind
of
comfortable
with
it,
will
look
at
some
swarms
to
actually
put
it
in
practice
and
hopefully,
by
the
end
of
this
quarter,
we'll
be
able
to
come
up
with
a
solid
mechanism
to
move
forward.
I
mean,
obviously,
when
a
document
and
prototype
this
and
with
the
end
result
in
in
and
the
following
quarter,
to
be
able
to
actually
put
it
in
in
practice
and
then
the
last
one
I
think
that
was
the
last
one.
E
F
Should
be
here,
everybody
can
hear
me
then
I'm
here,
but
it
was
I'm,
not
yeah,
alright
cool,
so
research
we're
doing
the
same
thing.
It's
an
ongoing
project
to
make
up
these
okay,
ours
and
there's
still
some
discussion
about
what
should
go
into
them
and
which
key
results
can
be
measured
and
which
are
slightly
harder
to
measure.
But
by
and
large
the
picture
is
should
be
pretty
clear.
We
have
a
big
chunk
of
work
to
do
on
on
on
implementing
stuff,
that's
already
in
the
pipeline,
so
to
speak.
F
So
we
can
start
by
looking
at
some
of
the
ongoing
research
projects.
Next
slide,
please
all
right
cool,
a
big
chunk
of
it
is
obviously
Nimbus
our
very
own.
If
your
own
client,
we
have
an
ambitious
goal
there
to
pass
the
entire
ETH
blockchain
through
it
and
by
the
end
of
it
that
should
provide
a
stable
base
for
us
to
build
upon,
and
it's
going
to
be
sort
of
the
starting
point
where
we
were
we
can
implement.
Some
of
them
were
experimental.
F
Things
on
on
the
theorems
horizon,
which
include
stuff
like
might
be,
proto
stake
might
be,
sharding
might
be
the
new
execution
engine
based
on
a
wesen
and
so
on
and
so
forth,
but
before
we
can
even
start
at
work,
there's
a
fair
bit
of
ground
work
to
do
other
than
that
guess
which
we're
relying
upon
today
is
getting
developed
in
cooperation
with
the
foundation.
Here
we
have
things
like
ultralight
clients
and
the
service
model
in
order
to
encourage
people
to
provide
light,
client
services
to
others,
it's
being
developed.
F
Nimbus
itself
is
written
in
a
language
called
NIM
and
that
language
is
still
in
development
and
being
a
major
contributor
or
a
remainder
user
of
that
language.
It's
important
that
we
create
an
ecosystem
community
driving
a
thriving
place
for
the
language
itself
to
be
such
that
we
can,
in
the
future,
hire
more
competent
developers
and
sort
of
leverage
on
how
grading
them
is.
F
There
are
some
things
which
are
still
being
developed
on
the
whisper
side.
I
recently
also
met
with
some
of
the
developers
and
Paraty
they've
been
making
other
improvements
to
whisper
soon,
while
some
things
we
already
know
like
whisper
v6
from
Bangkok
I,
expect
there
be
more
improvements
coming
our
way
that
still
need
a
little
bit
of
research
work
before
we
deploy
them
and
finally,
Viper
jack
is
working
on
getting
the
bed
out.
This
is
contingent
upon
the
foundation
passing
an
audit
for
it,
but
pretty
exciting
all
over
onwards
to
the
test
benchmark.
I.
F
Met
with
some
of
the
other,
it's
theorem
client
developers,
and
they
couldn't
stress
enough
how
important
it
is
that
that
we're
we're
good
on
the
testing
side,
because
the
sort
of
them
adversarial
nature
of
Assyrian
really
stresses
clients
and
and
people
trying
to
break
them
in
various
ways.
So
once
we
discover
vulnerabilities
or
once
we
discover
bugs
and
so
on,
it's
extremely
important
that
the
test
bench
is
there
on
the
more
practical
side
gets
itself
is
being
tested
from
from
that
point
of
view.
F
F
Those
might
be
both
positive
research
results
where
something
works,
but
obviously
also
and
when
something
didn't
work
out,
so
that
we
don't
have
to
try
it
again,
we'll
be
documenting
this
through
the
wiki
through
the
blog's,
we'll
be
providing
updates
on
ongoing
projects
in
the
town
hall
and
and
at
some
point
will,
will
have
to
gather
and
see
what
the
future
would
look
like
and
get
get
sort
of
a
directional
document
done
as
well.
On
that
points.
F
F
So
we
have
some
time
to
sort
of
work
out
what
charting
is
going
to
look
like,
but
nonetheless
the
first
phase
is
coming
from
the
foundation
and
from
the
other
client
implementers,
and
the
other
concern
I've
heard
when,
when
talking
to
a
lot
of
people
is,
is
whether
whisper
itself
will
be
viable
as
a
as
a
communications
protocol.
Once
we
start
scaling
seriously
and
by
seriously
we're
talking
about
millions
of
users,
whisper
itself
is
a
caustic
protocol
that
has
obvious
downsides
on
the
efficiency
front.
A
A
So
you
should
check
them
out,
leave
comments
and
then,
if
you
want
to
see
things
on
the
on
the
people,
oppression,
side
of
things
and
hiring
then
obviously
check
out
the
last
one
as
well
and
then
finally,
what
our
next
steps
here
and
the
okay
ours
once
they
get
basically
in
a
final
state,
we're
like
the
20-somethings.
So
in
the
next
few
days
you
should
polish
them
up,
put
them
on
github
or
an
open
dog,
whatever
its
easiest,
and
then
people
should
start
creating
personal
again.
A
So
what
are
you
going
to
work
on
that
relates
to
or
that's
part
of
the
the
core
team
and
the
research
team
are
open
bounty?
The
design
team
has
already
kicked
this
off.
There's
a
bunch
of
you
know
personal
okay,
ours
and
if
you
prefer
that
to
be
in
a
dog
or
on
github,
whatever
is
easiest
and
open.
So
that's
what's
happening
next
on
that
front
and
alright,
we,
if
we
won't,
do
QA
around
this,
we'll
do
it
at
the
end.
So
let's
move
on
now
to
swarms
Oscar.
Are
you
on
the
line.
G
Cool
yes,
talk
about
the
swarm,
slash
idea
process,
it's
similar
to
what
we've
done
before.
We
try
to
sort
of
tighten
it
up
a
bit
and
formalize
it
and
make
it
work
with
procures
and
so
on
and
next
slide,
so
we're
pretty
Gators
of
a
swarm
annual.
That's
look
based
on
a
lot
of
feedback
and
also
a
bunch
of
unconference
sessions
that
happened
during
bangkok
and
it
essentially
about
sort
of
formalizing.
G
In
part
of
solar
festival
mentioned,
we
are
increasing
the
cadence
of
these
town
halls.
We're
also
going
to
have
in
order
to
learn
to
not
have
so
give
orphaned
as
forms
but
sort
of
doesn't
live
on
forever.
We
can
essentially
just
mark
swarms
as
sort
of
being
not
being
in
progress
every
every
other
week
and
then,
if
this
will
work
to
be
done
and
so
on,
it's
sort
of
reopened.
G
So
you
refer
to
riously
later
it's
a
great
opportunity
for
teams
to
demo
I,
also
link
to
videos,
and
so
on
about
things
that
have
been
done
and
coming
soon
is
also
gonna,
be
some
experimentation
with
rush
talked
about
in
Vermont,
in
terms
of
having
like
a
budget
for
for
Banta,
fication
and
and
maybe
some
extra
bonus
for
achieving
old
cars
and
so
on.
We
also
work
on
improving
the
tooling
around
swung
an
idea
management
in
general.
G
So
if
you
have
an
idea
that
welcome
to
drop
them
in
swarm
leads
slack
channel,
you
can
read
more
about
the
investor
emmanuel
and
next
please.
So.
This
is
just
like
a
very
brief
example
of
what
it
might
look
like.
This
is
obviously
not
real.
Yet
on
your
right,
ears
have
a
swamp
summary,
which
is
essentially
those
teal.
They
are
what
this
form
is
even
about
because,
as
we
scale,
we
have
more
and
more
efforts
and
it's
hard
to
get
no
view.
So,
just
like
an
overview.
G
People
have
no
idea
what's
going
on
next
secretary,
essentially
just
at
what
point
will
this
form
finish
and
then
success?
Metrics
is
sort
of
how
it's
essentially
it
could
be
okay
or
something,
maybe
even
more
general
than
that,
and
just
knowing
what
success
looks
like
and
who's
participating
and
I'm
sort
of
the
left
side
is
more
about.
A
A
H
Okay,
okay,
so
I
can
just
give
you
a
quick
update,
yeah.
So
the
last
two
weeks,
first
of
all,
we
uncivilized
new
Minard
cluster.
It's
you
know
like
called
to
death
minded
cluster,
but
it's
totally
symbolized
and
managed
by
a
single
iBook
and
rolls
so
it's
easier
to
change.
We
finished
status
ago
changes.
So
there
was
a
couple
of
things
that
we
needed
to
adjust
to
support
my
night,
but
it's
done.
H
We
had
pre
of
coal
we've
abu
security
company,
that's
gonna
start
our
audit
orb
of
status
gone
status,
react
starting
today,
I
guess
so
so
yeah!
That's
that's!
What's
happened
in
the
last
two
weeks
for
the
next
two
weeks
we
have
mostly
testing,
so
we
basically
want
to
run
mine
it
on
the
physical
devices
and
simulators
involve
the
test
team
into
into
this
work
and
make
sure
that
main
it
works
just
fine.
At
the
same
time,
we're
gonna
have
the
quickly
cause
with
the
security
audit
company.
H
You
get
more
details,
how
they
are
going
and
what
they
actually
found
so
and
also
lesson
learned
yeah.
We
need
DevOps,
because
we
noticed
that
there's
a
problem
of
managing
color
servers.
We
had
a
lot
of
different
vendors
right
now,
like
digitalocean
scale
away,
and
we
just
need
someone
who
can
help
to
manage
this
because
right
now,
it's
like
end
of
many
people
and
it's
just
getting
click
in
different
ways,
so
yeah
so
yeah.
This
is
search,
I,
guess.
A
G
Yeah
yeah,
so
this
one
we're
gonna
bought
this
one,
because
this
essentially
no
clear
end
to
it.
There's
no
execute
here
so
instead
we're
gonna
keep
doing
leases
just
like
we
are
doing
all
the
other
week,
but
this
what
it
won't
be
in
the
form
of
this
one
in
terms
of
updates.
Last
two
weeks
we
erased,
sir
9:15
I
also
made
some
progress
on
integrating
fast
lane
for
better
builds,
no
specific
goals
for
this
next
two
weeks
since
this
one's
getting
a
bullet,
but
there's
some
some
work
being
done.
G
We
just
saw
them
working
on
SEO
916
and
it's
also
potentially
going
to
be
some
swarms
around
automated
testing
and
these
kinds
of
things
they're
still
to
be
determined.
Lessons
learned
well,
one
meta
thing
that
we
just
learned
earlier
on
swarms
is
that
they
should
have
some
sort
of
end,
because
otherwise
it's
easy
to
get
demotivated.
Then
it's
sort
of
this
just
yeah,
there's
no
clear
goal
with
a
specific
form,
which
probably
should
be
also
some
still
some
issues
around
build
release
pipeline
not
being
conversant
there.
Yet,
but
it's
it's
it's
getting
there.
G
Automation
matters
a
lot
here,
and
the
main
thing
here
is
just
fast
lane,
which
we
are
close
to
achieving
and
also
DevOps
resource
will
be
helpful
here
and
also
the
fact
that
we
release
cutting
as
interim
Sparky
polishing
a
release
on
fixing
all
the
questions
and,
like
all
these
things,
they're
sort
of
a
separate
activity
from
all
this
more
investment
work
that
goes
into
automated
tests
and
build
and
so
on.
That's
it
I'm
58.
D
Hey
Chad
here
again,
so
quick
update.
The
last
two
weeks
had
a
lot
of
progress
on
our
second
iteration,
adding
in
Mixpanel
events
and
so
now
like,
if
you
go
into
the
app
and
you
tap
around
we're
recording
events
for
like
the
main
taps.
We've
also
been
building
a
dashboard
and
mix
panel.
So
you
can
see
analysis
in
the
next
two
weeks.
We've
got
a
few
issues,
we're
adding
I'm,
including
an
opt-out,
setting
a
recovery
flow,
opt-in
and
adding
events
to
the
new
onboarding
screens,
as
well
as
creating
wiki
page
and
upgrading
into
the
both.
D
A
lesson
we've
learned
so
far
is
that,
rather
than
having
one
person
responsible
for
metrics
updates
be
great.
If
this
knowledge
is
disseminated
in
two
swarms
and
it's
made
part
of
the
swarm
kickoff,
likewise,
one
will
check
that
they
have
the
metrics
they
need
in
Mixpanel
and,
if
not
that
add
it
and
we're
very
close
to
wrapping
up,
we
have
mix
panel
installed.
We
have
instrumentation
and
dashboards.
We
just
have
a
few
more
issues
to
do
and
a
big
success
metric
will
be
allowing
other
swarms
to
have
like
to
use
these
call
metrics
in
there.
D
Okay,
our
evaluation
and
success
evaluation
and
I've
got
a
very
quick
demo
of
what
this
looks
like.
So,
if
you
haven't
seen
it
on
the
Left
when
you're
creating
a
new
account,
there's
an
opt-in
screen
during
signup
and
it
asked
to
help
improve
status
by
sharing
usage
data
and
we're
going
to
improve
this
screen
to
let
users
know
that
it's
anonymous,
we
don't
collect
personal
information
and
we're
gonna
have
a
link
to
a
wiki
page
on
the
right
is
what
the
actual
event
code
looks
like.
D
D
We
picked
with
39
daily
active
users,
but
we
only
had
one
user
that
used
the
depth
and
for
users
that
sent
a
transaction,
whereas
we
had
22
that
sent
a
message
so
like
this,
you
can
see
where
people
are
using
the
app
and
how
they're
using
it
next
and
also,
we
can
see
how
many
messages
their
new
accounts.
We've
got
funnels
setup
for
opening
gaps
and
sending
messages
and
lots
more
than
example
and
I
think
we've
got
one
more
screen,
yeah.
Here's
an
example
of
a
funnel.
D
This
is
sending
a
message,
so
31
percent
of
the
users
that
created
an
account
on
Friday
ended
up
sending
a
message
and
we
can
log
each
individual
step.
So
this
is
a
start.
We'll
have
a
lot
more
info,
but
it's
only
going
to
get
better
to
understand
how
people
using
status.
Thank
you.
Oh
sorry,
one
more
chart
you
guys
might
remember
during
Oscars
Bangkok
presentation
he
showed
a
survival
chart.
D
C
I
think
it's
more
Eugene,
but
I
can
talk
about
because
there
is
two
sides
to
this:
there
is
the
growth
side,
the
cooler
side
and
the
cooler
side.
We
developed
a
new
protocol
for
communications
in
status
that
uses
less
pips
that
is
smaller
with
smaller
payloads
and
doing
a
bunch
of
improvements
in
the
code
to
make
it
faster
and
yeah,
and
and
that's
basically
it
and
we
are
like
right
now.
We
are
done
with
the
main
functionalities
and
we
are
going
to
move
to
QA
now
and
yeah.
C
A
B
Hi
everyone.
Can
you
hear
me
yep,
quick
update
on
this
one,
so
in
the
recent
recent
time
we
hear
that
reef
in
tunics
library,
which
allows
us
to
debug
reframe
events
and
view
and
subscriptions
timings,
so
it
will
be
big
improvement
on
the
measuring
side
of
things
for
the
next
two
weeks
we
gonna
measure
our
performance
UI
performance
against
new
message
protocol
where
Eric
and
Janna
doing
some
work.
Hopefully
this
week
come
in
the
next
week
about
exit
criteria.
B
So
we
have
some
number
of
performance
user
stories
which
I
mostly
based
on
offline
messaging
performance
or
once
we
get
a
lot
of
messages
up
become
unresponsive.
So
the
main
like
ultimate
goal,
to
fix
all
this
user
stories
so
for
success
metric,
we
decided
to
go
with
user
tap
interaction
time
so
any
time
user
taps
on
something
in
the
app.
B
This
reaction
should
be
less
than
100
millisecond,
so
maybe
we're
gonna
use
end-to-end
tests
to
measure
it
an
automatic
way,
but
this
is
actually
hard
task
to
so
non-trivial
task
to
to
do
this
during
optimizing
testing.
But
we
think
about
this,
how
we
can
measure
FPS
during
of
thematic
test,
fit
Ron?
C
Hey
Hugh
me
yeah,
so
for
doing
burning,
it's
been
put
on
hold
since
the
iteration
one
has
ended.
The
only
thing
that
is
currently
going
on
is
the
copy
updates.
We
kicked
off
that
camera
with
the
marketing
team
I'm
currently,
and
this
isn't
in
progress
and
the
what
are
we
doing
now
with
the
onboarding
swarmers,
creating
a
list
of
what
should
be
done
for
the
iteration.
There's
been
a
lot
of
ideas
and
insights
during
the
test
sessions.
It's
it's
a
long
list.
C
So
the
currently
the
hard
thing
to
do
is
to
define
which
one
of
those
should
go
to
iteration.
What's
the
exit
criteria
and
we
so
basically
it's
all
about
alternative
rubric
verification
to
sign
the
transaction
or
login
improve
the
invite
friends
flow
which
might
be
considered
to
exist
in
a
separate
form
so
yeah,
it's
all
about
structuring
the
the
upcoming
work
and
defining
the
exit
criteria.
G
I
said
Oscar
eager
is
on
vacation
as
soon
as
meeting
yeah
right.
So
this
is
mostly
about
battery
efficiency
and
so
on
and
I
guess
was
what's
been
down.
There's
been
a
how
to
that.
Lucas
wrote
for
Android
ng
testing
and
then
also
Igor
and
Eugene
worked
on
a
proof.
Concept
for
saving
battery
when
Android
is
in
background
and
ability
was
also
another
notice
sort
of
concept
that
was
done,
but
hopefully
both
of
these
things.
G
So
property
result
so
far,
and
hopefully
they
will
both
meet
the
success
metrics,
which
means
that
the
the
sort
of
swamp
could
and
essentially
and
success
metric
is
about
getting
a
foreground
and
background
and
consumption
to
Ballpark.
What
it's
a
similar
class
of
application
is
that
so
a
messenger
like
telegram
or
whatsapp
or
whatever
that's.
H
So
we
just
have
started
working
on
this
I
think
most
work
has
been
done
by
Dmitry
yeah.
It's
basically
about
discovery
version,
5
research,
so
we
want
to
first
of
all
figured
out
how
discovery
version
5
exactly
works
and
how
it
can
be
useful
to
build
some
kind
of
a
dynamic
clusters,
because
right
now
our
costs
are
static.
Now,
so,
basically,
we
need
to
put
like
hard
code
IP,
some
hordes
and
no
IDs
into
the
into
the
app.
So
the
the
thing
here
is
to
move
to
discovery
and
use
regular
boots.
H
B
So
this
form
is
that
we
didn't
have
too
much
progress
last
week,
so
we
kind
of
have
scope
for
the
consideration,
which
is
mostly
related,
our
sent
status,
which
actually
doesn't
mean
anything
right
now
in
application,
and
it's
confusing
those
two
time
stamps
which
we
don't
have
and
that's
it.
So
actually
what
we
need
to
do
is
to
verify
other
items
for
our
product
description
and
like
to
find
participants
for
this
form.
A
A
B
Amid
hello,
Lou,
hemming,
yep,
perfect,
oh
okay,
cool!
Thank
you
yeah
for
a
creative
cute.
In
the
last
week's
we
were
updating
their
rank
native,
desktop
Fork
of
status,
electron
project.
We
managed
to
get
the
quite
reliable,
chatty
and
reliable
I
mean
not
in
terms
of
like
reliability,
but
reliability
in
the
site
of
recommending
tests
of
implementation.
B
So
we
are
receiving
and
sending
messages,
and
also
it
was
created,
a
distribution
package
for
wounded
and
for
the
next
two
weeks
we
will
move
a
bit
from
the
status
electron
form
to
a
new
code
and
we
put
all
his
desktop
related
code
to
the
status
track.
So
now
we
have
like
one
more
platform
in
the
code
of
status,
our
desktop
platform
and
in
next
two
weeks,
we'll
touch
our
native
implementation
to
it
and
we'll
fix
the
usual
bugs
that
we
have
kind
of
fixing
up
our
plants
and
so
on.
A
Okay,
awesome
all
right
thanks.
Everyone
I
think
that
wraps
up
the
Town
Hall.
Now,
hopefully
you
know
people
enjoyed
the
top
dated
swarm
format
for
giving
updates-
and
you
know
will
continue
to
scream
like
this
streamline
this,
to
make
it
more
efficient,
more
effective,
so
that
people
can
maximize
this
power.