►
From YouTube: Town Hall #62 - July 20, 2020
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
Hey
yep,
this
couple,
quick
slides
from
us,
this
town
hall,
so
a
huge
warm
welcome
to
diana
who's
joining
core
team.
As
a
junior
qa
engineer,
diana
we're
really
excited
to
have
you
on
board
and
it's
really
great
already
to
have
some
much
needed
additional
qa
support.
So
thank
you
so
much
for
coming
to
the
team.
B
B
Yeah
we
found
a
distributed
networking
engineer,
they'll
be
announced
next
week
and
the
search
for
protocol
engineer
continues
on
the
nimbus
slide.
We're
also
really
pleased
to
have
our
tech,
writer
and
again
we'll
we'll
share
the
name
with
you
in
the
next
town
hall
legal
council.
We're
still
searching
for
that.
We've
also
put
up
a
job
ad
for
a
recruiter
on
the
people,
ops
team,
to
cover
peppa's
maternity
leave
on
marketing.
B
D
All
thanks
terry
right,
so
the
last
week's
release
1.4.1
came
out
with
already
some
really
nice.
Ui
improvements
have
a
look
at
the
icons
in
that
release
next
to
next
to
some
other
improvements,
so
we
did
not
give
too
much
of
of
a
loud
voice
to
that
release
as
it's,
it's
mainly
fixing
and
introducing
smaller,
smaller
improvements.
D
Those
are
pretty
much
finalized
by
now.
I
believe,
there's
there's
one
pull
request
open
to
resolve
some
some
outstanding
issues,
but
it
will
make
a
great
improvement
to
how
the
app
looks
and
feels
for
sure,
so
pre
planned
releases
actually
see
that
release.
1.4.1
is
still
mentioned
there
that
one's
out
version
1.5
is
coming
out
shortly.
I
realize
there's
also
a
question
on
when
it's
coming
out
so
I'll
save
that,
but
that
would
include
images,
emoji
reactions
and
and
audio
messages.
D
After
that,
we'll
release
the
referral
program
and
all
that
that
entails
it's,
it's
been
quite
a
big
project
to
to
get
that
on
its
feet
and
then
release
1.7
will
be
similar
to
what
we
did
with
1.4
kind
of
making
sure
that
we
reduce
any
debt
that
we're
building
up
and
fix
any
issues
that
come
out
of
the
let's
say,
feature
feature
releases:
what's
next,
so
stopping
with
plant
releases
at
1.7
for
version
1.8
and
beyond.
The
next
step
is
to
scope
out
the
work.
D
There
have
definitely
been
a
lot
of
discussions
around
like
how
can
we
best
drive
your
attention?
We
do
want
to
increase
retention.
I
believe
there's
no
update
on
our
numbers
this
time
around,
but
you
can
surely
find
them
on
discuss
where
oscar's
been
posting
weekly
updates.
We
also
have
a
dashboard
for
that.
D
What
is
next
to
plan
for
this
work
is
to
understand
what
what
we
all
agree
on
that
can
potentially
drive
retention.
It'll,
be
very
tough
for
us
to
vote
on
features.
If
we
don't
know
or
don't
have
consensus
on
whether
or
not
they
will
impact
our
tension,
so
that's
something
that
we're
looking
to
do.
Tentative
plan
is
early
next
week.
A
E
Hey
everybody,
a
few
things,
mostly
it's
kind
of
outward
announcements
that
you
may
have
missed
if
you're,
not
following
along
on
the
status
that
I
am
big
movement
last
few
weeks
is
we
kicked
off
the
the
nimbus
beacon
chain,
audit
or
assessment
full
announcement.
Article
can
be
found
in
that
link.
We
did
a
few
different
different
things
to
the
process
of
doing
a
security
assessment
to
try
and
redesign
it
to
make
it
more
open,
transparent,
encourage
the
long-lasting
security
relationships
as
opposed
to
kind
of
a
short
time.
E
Boxed
focused
security
assessment
where
they
they
work
for
a
little
while
and
we
try
to
fix
everything
and
then
announcement
and
say
hey.
We
got
a
security
audit
everything's
good.
The
process
we've
designed
here
is
really
a
highly
collaborative
effort
to
get
the
security
community
to
have
long,
lasting
relationships
and
focus
on
very
important
code
bases
that
kind
of
are
the
infrastructure
for
ethereum
and
ethereum.
Two.
E
This
particular
one
this
this
phase
phase
zero,
is
a
multi-vendor
audit,
with
consensus,
trailer
bits
and
mcc
spread
across
all
of
the
beacon
chain,
repositories
and
code
bases,
it's
long
as
opposed
to
other
security
assessments
that
are
relatively
short.
This
is
a
four-month
effort
just
for
f2
phase
zero,
so
we'll
be
doing
something
similar
for
the
latter
phases.
E
This
is
only
for
looking
at
the
security
implications
of
phase
zero,
we'll
be
sharing
summary
reports
and
lessons
to
learn
periodically
so
that
other
implementations
can
learn
from
the
things
that
we
learn
if
you're
really
into
it,
you
can
just
follow
the
github
issues.
That'll
be
posted
as
thing
as
as
the
assessors
find
things
because
we're
doing
it
as
it
stands
all
in
our
github
repertoires
that
are
public
and
open.
E
Rajiv
wrote
an
article
on
the
android
notification
security
overview
and
how
status
implements
android
notifications,
specifically
in
order
to
protect
your
privacy
and
why
centralized
notifications
kind
of
steal
some
of
that,
and
so
you
can
be
a
little
more
informed
on
what
you're
giving
up
whenever
you
get
centralized
notifications
from
all
your
other
applications
and
and
as
always
back
up
your
sheet
phrase.
Remember
your
password
or
get
a
key
card
and
get
a
key
card.
So
that's
all
for
me.
C
Thanks
hi,
so
there's
been
this
big
push
around
metrics,
specifically
about
around
retention
metrics,
and
for
that
I've
deployed
reduction
stance
through
which
will
be
combining
metrics
regarding
both
attention
and
other
services
like,
for
example,
the
upcoming
referral
service,
there's
also
retention
of
satellite.
If
I
want
to
look
at
those
metrics
they're
pretty
bad
right
now,
but
I
mean
we
need
them
to
see
if
we're
actually
doing
something
right
or
wrong
so
check
that
out,
and
so
some
other
work
in
terms
of
exporting
pure
data.
C
So
we
can
more
effectively
generate
their
attention,
which
is
actually
pretty
complex.
There's
still
ongoing
work
on
upgrading
all
of
our
fleets
to
the
newest,
long-term
support
release
of
ubuntu,
and
I
was
kind
of
blocked
by
fred
stuck
not
having
support
for
2004,
but
they
released
that
last
week.
So
so
it's
started
off
again.
C
I've
also
implemented
pr
builds
for
a
desktop
client
which
are
essentially
a
mirror
of
what
status
react
ripple
has
so
that
should
improve
testing
and
developing
experience,
and
we
also
have
some
updates
to
to
logic
for
uploading
builds
for
states.
React
there's
also
ongoing
work
on
the
referral
service
that
will
be
used
in
the
1.6,
and
we
already
have
a
test
in
the
production
environment,
but
this
environment
is
up
is
being
used,
I
believe,
by
george,
to
implement
usage
of
reverse
services
in
the
application.
C
I
researched
bridging
whatsapp
with
status
for
marketing
purposes
and
it's
doable,
but
a
real
pain
ds,
so
we
probably
won't
do
it,
but
we'll
see
I'll,
see
oh
yeah
and
there's
also
referrals
service
support
for
deep
links,
which
is
partially
out
mostly
for
testing
purposes,
and
also
I've
been
fighting
with
ios
code
signing
as
always
made
an
improvement
to
fast
lane
which
might
get
into
masters.
We'll
see
that's
most
of
it.
Thank
you.
F
F
We
can
have
a
bit
more
like
granular
visibility
into
the
effectiveness
of
specific
campaigns
without
like
granular
data
in
the
app
it's
extremely
difficult
for
us
to
measure
campaigns
that
are
simultaneously
running,
so
we're
working
on
some
ways
to
just
do
that
now,
while
I
don't
have
the
exact
retention
metrics,
I
do
have
some
vanity
metrics
for
us
to
look
at
today.
Just
wanted
to
call
out
that
output
on
social
and,
like
general
content
on
our
status,
has
been
increased
significantly.
F
F
And
so
upcoming,
the
latin
america
work
is
still
in
progress.
We've
started
with
some
instagram
live
sessions
in
both
brazil
and
argentina,
and
we're
starting
to
see
a
little
bit
of
adoption
there
slowly
growing
the
communities
each
week
and
the
big
the
next
big
effort.
There
are
influencer
negotiations,
so
we
found
some
crypto
and
like
tech
influencers
who
love
status
and
are
really
interested
to
start
promoting
the
work
we're
just
in
procurement
and
final
contract
negotiations
there
and
then
yeah
as
hester
mentioned,
so
we're
working
on
1.5.
F
That's
it's
a
pretty
content
heavy
campaign,
but
then
also
have
like
a
brand
component
to
that,
in
which
we'll
be
doing
a
lot
of
outreach
to
like
partner
projects
and
stuff
like
that.
So
and
the
big
thing
for
1.5
is
that
we're
going
to
time
box
it
into
a
three
week
campaign.
So
we
can
have
much
more.
F
I
guess
detailed.
I
guess
metrics
on
the
on
that
three
week
window
and
then
we
can.
You
know,
alter
that
how
we
measure
for
1.6
in
future
campaigns
and
the
final
element
to
1.5
is
well.
Another
element
is
ambassadors,
so
we're
recruiting
pretty
heavily
for
new
ambassadors
right
now
and
jin
has
been
doing
a
great
job
of
intake.
I
think
I
think
last
week
there
was
like
11
applications.
F
While
we
have
multiple
campaigns,
running
that's
been,
the
trickiest
part
for
us
right
now
is
to
pinpoint
which
campaigns
are
effective
versus
which
ones
aren't,
and
I
guess
the
further
down
the
funnel
you
go
into
the
application,
the
less
visibility
we
have
just
because
of
our
security
and
privacy
measures.
So
thinking
around
things
to
do
there
and
then
the
last
thing
I'll
say
is
working
on
like
audience
and
persona
slides,
as
we
start
to
you
know,
define
product
roadmap
and
marketing
efforts.
A
D
D
I
was
reading
through
an
update
a
little
bit
earlier
today.
It's
it's
looking
good,
but
we've
deliberately
not
planned
ios
notifications
against
any
timeline,
which
is
something
we
try
to
avoid
in
general,
because
it
has
a
lot
of
unknown
unknowns,
a
lot
of
complexity
to
it.
That
said,
it
is
surely
coming
it's
being
worked
on.
I'd
rather
not
commit
to
a
specific
release
because
it,
it
is
a
high
complexity,
feature
but
stay
tuned,
I'll.
D
A
D
Yeah
thanks
terry
and
thank
you
ken
yeah,
thanks
for
asking,
we
had
planned
1.5
to
be
ready
for
release
cut
testing
which
is
not
necessarily
released.
It
just
means
that
we
have
all
features
that
we
want
to
release
compiled
into
one
branch
that
can
then
be
extensively
tested
and
to
end
by
the
by
the
qa
team.
That
is
something
that
we're
still
looking
to
do
this
week.
D
So
if
anything
has
priority,
this
is
what
the
team
is
working
on
right
now
to
make
that
happen,
I'm
cautious
of
giving
an
exact
eta,
because
I
do
not
know
the
absolute
latest
on
this.
I
would
say
if
you
want
to
check
on
the
continuous
progress
best
is
to
go
to
the
github
repository
check.
The
pull
request
take
take
a
look
at
what's
still
open.
It's
definitely
like
an
hour
by
hour.
Update
right
now,
so
best
is
to
keep
an
eye
on
that.