►
From YouTube: Status Townhall - July 16th, 2018
Description
General
00:11 - Intro
Non-Tech Updates
01:13 - Welcome new Core Contributors
02:25 - People Update
05:44 - Security summit in Basel
12:57 - Q3 Experimental OKRs
Marketing
14:20 - Marketing Update
16:52 - Meme Competition - Submissions
18:40 - Content and Channel Report
19:58 - Top Tweets
20:21 - Top Posts
21:05 - Site
UX/UXR
22:27 - Product Content Strategy
Core Swarms
27:49 - Core Goal: Beta Launched
Mobile App
29:11 - #83-energy-efficient
Infra & Tooling
30:24 - Infrastructure Automation
32:15 - Canaries via Icinga 2
32:30 - #280-disc-mail-servers
Chat
33:55 - #core-chat
Wallet & Account
35:59 - #151-ens-usernames
38:03 - #170-wallet-improvements
DApps & Developers
39:12 - DApps & Developers
Research
41:29 - #67-nimbus
Dekstop
45:12 - Desktop update
Q&A
48:08 - Q&A
Slides can be found here - https://bit.ly/status-th13
A
You
okay:
let's
begin
welcome
to
13th
Town
Hall
on
the
16th
of
July
2018.
Today
we're
coming
at
you
from
the
global
blockchain
conference
in
Johannesburg,
South
Africa
spread
around
the
world
as
always,
though,
with
all
of
our
contributors.
So
without
any
further
ado,
let's
dive
right
in
certs,
we've
got
a
lot
to
get
through.
The
first
thing
that
we
wanted
sort
of
detail
is
some
key
takeaways
from
our
security
summit
in
Basel
that
we
had
last
week
and
I
believe
that
Carl
is
going
to
be
giving
the
updates
on
this.
B
C
Hey,
can
you
hear
me
yep
Oh
awesome:
oh
okay,
hi
everyone!
So
in
two
weeks
we'll
be
welcoming
for
people
and
my
bad
for
not
having
found
a
good
photo
of
Dustin
he
starting
today
so
I
think
him,
but
because
he's
dazed,
you
know
another
time
when
we
didn't
have
time
to
send
it
to
me
and
I
shall
Sebastian.
We
have
actually
the
joy
in
those
the
last
week
as
the
head
of
state,
the
studio
Michael
as
a
social
media
manager
and
Jonathan
was
joining
us
today,
specifically
my
team.
C
As
the
director
of
people,
ops
and
talent
combined,
we
still
have
22
over
Rossum
and
we'd
love
to
close
the
design
agency
in
the
incubator
system
as
possible,
so
useful.
Anyone
who's
tuned
into
this
Town
Hall
has
anybody
minded
would
be
a
great
addition
to
those
two
teams.
Specifically,
please
let
us
know
and
also
remember
that
with
that
you
can
get
up
a
bonus
of
$5,000
in
theme.
C
This
next
slide
and
thank
you
because
in
the
last
couple
of
weeks
we
had
discussion
around
the
day,
okay,
our
so
for
this
quarter
we
scored
them.
We
sell
finalized
them
and
we
realize
that
we
still
have
several
basics
to
get
better
at
mainly
on
board
in
which
is
still
a
very
big
focus
area
for
us.
We
want
to
improve
it
not
only
on
a
technical
level,
but
by
making
available
integrated
learning
opportunities
at
the
appropriate
level,
for
everyone
joins
the
organization.
C
There's
going
to
be
a
lot
of
work
in
that
sense,
and
the
talent
started
experimenting
with,
as
I
just
mentioned,
that
the
Basel
meetup,
which
we
didn't
hear
about
yet
but
would
come
later.
There
was
a
set
of
principles
that
came
out
of
that
together
that
we
are
going
to
try
to
use
to
inform
everything
that
we
do
and
talented
a
helps
after
that,
and
now
they're
already
used
in
ways
to
score
and
scan
for
those
values
while
very
early
in
the
recruitment
process.
C
During
interviews
during
tests
and
integration
tasks,
we
also
wanted
to
become
even
more
transparent
about
what
we
do
so
we're
going
to
make
an
effort
to
use,
discuss.
Most
I
have
more
regularly
to
brainstorm
projects
and
ideas
that
are
related
to
people
operations,
and
we
would
love
everyone's
interest
in
contributions.
Also
there
another
thing
that
we're
going
to
be
doing
is
like
Teddy
and
I
are
thinking
to
split
in
the
Ginza,
so
that
everyone
will
have
one
person
dedicated
to
them
as
people
of
support.
C
If
anyone
seems
that's,
not
a
good
idea,
let
us
know
otherwise
we're
gonna
proceed
and
try
to
speed
the
teams
together
and
like
announce
the
next
steps.
During
this
week,
we've
been
working
on
a
blog
post
with
marketing
about
the
excitement
and
the
challenges
and
the
joys
of
doing
people
operations
in
our
context,
and
also
not
known
directly
technical
talk
that
we
are
planning
for
this
Friday
afternoon.
Again
we
carry,
and
yes
in,
did
one
last
week
as
an
introduction
to
crypto
transactions.
C
It
was
very
successful.
People
loved
it.
We
have
we're
still
discussing
what's
going
to
happen
next,
whether
we
are
going
to
be
published
in
that
record
then
or
prepare
a
series
of
similar
ones
and
so
stay
tuned
on
our
Channel
and,
as
you
probably
know,
or
have
received,
even
by
now
we
shipped
everyone
at
the
core
contributor
alleged
Nano
a
couple
of
weeks
ago
and
as
a
fan
of
the
cognition
for
the
efforts
that
everyone
put
recently
and
hard
work.
C
If
you
haven't
received
it
yet,
please
let
us
know
so
that
we
should
be
able
to
find
out
where
it
is
I
think
there's
our
customs
problem
for
now.
That's
everything
we're
going
to
have
a
meet-up
next
week,
also
Switzerland
with
finally
going
to
be
all
together
under
the
same
roof
and
work
a
bit
more
on
consolidating
what
it
is
we
want
to
do
next
and
no
splitting
so
give
it
up.
We
let
you
know
that
yep.
A
D
Then
we
went
on
to
trying
to
identify
like
why
these
items
were
concerning
so
I'll
give
a
few
specific
examples,
so
one
would
be.
You
know
we
have
no
perfect
forward
secrecy
implemented.
Yet
status
is
predicated
on
creating
secure
communication
systems,
so
this
is
an
example
of
something
that
on
fixing
will
bring
us
close
for
that
goal.
Another
would
be
that
we
currently
depend
on
Fuhrer,
yet
the
whole
idea
of
status
is
to
be
as
decentralized
as
possible,
and
so
this
is
a
breach
fell
police.
D
D
They
overlap
with
some
of
the
assisting
mark
and
if
you
have
comments
or
thoughts
or
things
we've
missed
like
please,
please
add
them
in
on
the
by
no
means
finalized,
so
the
first
of
which
was
Liberty
like
we
believe
in
the
right
of
individuals
to
have
autonomy
and
responsibility
of
a
his
or
her
life.
We
aim
to
maximize
social,
political
and
economic
freedoms.
The
status
as
an
agnostic
platform,
censorship
resistance.
We
aim
to
avoid
the
suppression
of
information.
D
No
content
is
under
surveillance,
one
of
the
design
goals
of
etherium
is
to
be
censorship
resistant,
and
we
should
provide
the
same
guarantees
across
status
security.
We
don't
compromise
on
security
when
building
features
where
you
started
out.
Research
and
new
security
methods
to
make
strong
security
guarantees.
D
Privacy
privacy
is
the
power
to
selectively
reveal
oneself
to
the
world.
This
means
you
need
to
protect
privacy
and
communications
and
transit
and
transactions,
as
well
as
the
right
to
total
anonymity
transparency.
We
strive
for
a
complete
openness
and
symmetry
of
information
and
have
no
more
border
between
our
core
contributors
and
our
community.
We'll
be
frank
about
our
faults,
especially
when
making
short-term
trade-offs
and
service
of
our
long-term
goals.
D
Free
culture.
The
software
we
create
is
a
public
good.
It
will
be
made
available
by
a
via
free
and
open-source
license,
for
anyone
to
share,
modify
and
benefit
from
decentralization
will
minimize
centralization
across
both
the
software
and
the
organization,
inclusive
'ti.
We
believe
in
fire
and
widespread
access
to
our
software,
with
an
emphasis
on
ease
of
use.
This
also
extends
to
circle
inclusivity,
inviting
participation
in
the
organization
and
investing
in
educational
efforts,
and,
lastly,
we
had
continuance.
D
What
constitutes
success
for
each
principle,
both
in
terms
of
the
software
in
the
organization
and
then,
lastly,
like
I,
believe
very
deeply
in
each
of
these
principles,
and
hopefully
a
flavor
and
listening
will?
But
if
you
don't
I
think
it's
worth
asking,
why,
like?
Maybe
we
can
help
to
provide
educational
information
and
resources
and
so
yeah?
That's
that's
it
for
me
like.
A
Yeah,
thank
you
so
much
cop
there's
really
there's
a
lot
of
stuff
to
go
through
and
there
a
lot
of
things
to
be
thought
about,
and
a
lot
of
discussions
to
be
had
so
I
really
encourage
everybody
to
take
part
actively.
You
know
the
whole
points
of
being
a
part
of
a
decentralized
community
of
people
is
that
we
each
get
to
define
the
direction
that
we
take
as
an
organization
by
our
acts
of
contributions
and
participation,
and
that
goes
for
both
core
contributors
and
anybody
in
the
community.
A
A
It
also
brings
me
back
to
just
highlight
briefly
again
the
fact
that
we
have
22
open
roles,
particularly
within
the
design
agency
and
incubates,
which
are
again
both
premise
on
making
sure
that
we
can
make
technology
inclusive
and
accessible
to
as
many
people
as
we
possibly
can,
which
is
a
core
part
of
the
principles
that
Carl
outlined,
and
we
really
are.
You
know
keen
to
try
and
find
the
best
people
in
the
world
to
push
forward
those
two
parts
of
the
puzzle.
A
In
particular,
we've
got
some
amazing
people
that
have
come
on
board
you'll
hear
from
OB
in
a
moments.
Ned
is
doing
an
amazing
job
already
in
terms
of
trying
to
come
up
with
a
design
philosophy,
and
the
projects
that
are
coming
out
of
incubates
are
really
fantastic.
To
see.
Crypto
strikers
has
been
an
amazing
success,
I
dread
speaking
to
Julia
and
Eric
mammy,
and
our
other
French
contributors
in
status.
B
So,
moving
on
from
the
past
fortnight,
where
we
basically
tried
to
create
this
open,
ok,
our
voting
process
is
taken.
It's
a
little
bit
longer
to
get
things
ready
and
we've
had
a
couple
of
contributions.
So
far
right
now,
where
we
are
as
of
this
morning,
is
we
have
the
twelve
twelve
proposals
there?
If
you
has
to
vote,
got
status,
thought
I
am
inside
of
status
or
any
web
3
browser.
You
can
then
see
and
then
using
S&T
in
your
account,
you
can
vote
on
specific
ideas,
so
there's
12
ideas
there.
B
Their
proposed,
please
give
your
input
in
the
next
say,
48
hours
and
then
we'll
go
ahead
and
basically
start
working
on
on
those
things
so
check
it
out.
You
know,
there's
a
lot
that
we've
learned
going
through
this
process
and
hopefully
affordably
much
smoother.
So
thanks
for
everyone
for
getting
involved.
A
F
Is
Joanie
I'm
actually
gonna?
Kick
it
off?
Okay
for
me,
yep
cool!
So
before
we
get
into
some
of
our
like
the
metrics
know,
what
we've
been
doing,
it's
gonna
go
through
some
of
the
ongoing
projects
we're
still
hosting
these
Tech
Talks.
So
if
you
want
are
interested
in
in
hosting
one,
please
contact
area
myself
and
we
can
help,
arrange
it
and
then
there's
also
some
content
campaigns
going
on
so
around
each
release.
We're
looking
to
highlight
one
of
the
insights
around
that
specific
release.
F
Just
to
you
know,
educate
people
around
the
key
update
in
that
release,
we're
also
conducting
or
in
production,
on
a
campaigner
on
the
whisperer
protocol
right
now,
along
with
UX
design,
and
then
also
people
up
once
again,
just
really
trying
to
highlight
the
amazing
work,
that's
being
done
by
the
team
status
projects.
There's
some
interesting
things
going
on
as
well.
So
three
point
one
is
to
come
out
and
then
to
accompany
that.
F
We're
working
on
some
tutorials
and
some
some
quick
light
touch:
videos
blip
hearing
the
team
which
we're
gonna
call
bursts,
which
is
exciting
and
then
also
working
with
the
M
team.
Once
again,
to
really
like
highlight
the
work
that
they're
doing
as
well
and
really
just
announce,
you
know
it's
everyone,
what
we're
really
doing
with
NIMH
and
Nimbus.
F
It's
it's
really
exciting
and
there's
also
some
well
there's
a
lot
of
events
coming
up,
DAP,
Cohn
and
Berlin,
and
then
the
F
global
events
will
be
in
India
in
August
and
then
will
also
be
in
Berlin
or
working
with
Maria
and
the
team
with
the
for
with
the
8th
Berlin
team
to
integrate
status
as
much
as
we
can
at
the
actual
event.
So
some
really
exciting
things
happening
there.
F
F
You
know
brilliant
people
in
Prague
at
the
time
and
really
just
trying
to
encourage
the
community
to
come
together
and
and
to
build
some
really
really
awesome
things
and
there's
more
details
coming
out
regarding
the
hackathon
with
the
theme
and
what
we're
going
for
this
week.
So
stay
tuned,
it's
really
exciting
and
then
once
again
will
be
since
we'll
be
in
Prague
the
weekend
before,
for
our
hackathon
will
obviously
be
at
DEFCON
as
well,
so
really
exciting
stuff
all
around
and
I'll
kick
it
over
to
Kim.
G
Thanks
Johnny,
so
can
you
jump
back
Andy,
real,
quick
to
the
previous
slide,
yeah
just
running
through
campaign
and
community
really
quickly?
One
of
the
things
to
call
out
is:
we
did
launch
our
Spanish
channels
last
week,
so
yay
Eduardo
I
mean
there's
a
link
there.
If
you
want
to
read
the
blog
post
about
it
and
we
now
have
dedicated
Spanish,
Facebook
and
Twitter
channels,
as
well
as
obviously
the
in-app
public
chat.
So
that
was
a
really
big
win
for
that
community.
So
congratulations,
Eduardo!
Okay!
You
can
go
ahead
now.
Andy
thanks.
G
The
meme
competition
hutch
has
been
working
round
the
clock
driving
this
competition
doing
a
great
job,
so
thanks
to
everyone,
who's
helped
with
those
brave
new
memes,
especially
the
status
community
as
a
whole,
really
showing
a
full
force.
We've
had
some
amazing
and
trees
and
some
great
community
buzz
around
this
over
500
mentions
and
over
200
meme
submissions,
which
we're
really
thrilled
to
see
extremely
creative
ones
or
some
examples.
They're
one
of
our
aetherium
artists
did
a
series
taking
our
logo
and
basically
hacking
our
logo
and
so
there's
a
lot
of
different
varieties
of
that.
G
That
have
been
really
fun
to
see
and
also
a
big
thanks
to
flex
tabs
for
building
on
our
mean
site,
which
you
can
see
over
on
the
right
and
there's
a
link
there.
You
can
check
out
the
meme
leaderboard
and
then
a
special
things,
of
course,
Maria
MP,
our
main
powerhouse
for
curating
and
judging
all
the
submissions
and
just
a
reminder.
There's
one
day
left
for
submissions
I
believe
ends
tomorrow.
12
p.m.
Eastern
Time.
G
So,
let's
save
our
content
and
channel
this
covers
Facebook
and
Twitter.
A
really
great
strong
number
is
our
total
engagement
grew
by
39%
since
the
last
fortnight.
This
is
awesome
and
primarily
driven
by
brave
new
memes
and
all
the
mentions
around
that,
and
it's
also
I
think
worth
calling
out.
This
39
percent
increase
is
on
top
of
the
last
fortnight
reporting
period,
which
was
where
we
have
announced
beta.
So
this
is
really
strong
on
top
of
numbers
that
were
already
strong
from
the
last
reporting
period.
G
G
We
were
thrilled
and
so
overall
we're
up
on
every
metric,
which
is
pretty
amazing
and
so
I
think
it's
gonna
be
a
real
challenge
in
two
weeks
when
we
do
have
to
go
back
and
report
on
this
again
to
see
where
we
are
because
it's
gonna
be
very
hard
to
improve
on
these
numbers,
but
we're
definitely
moving
in
the
right
direction.
Next
slide.
G
These
are
our
top
tweets
from
the
last
two
weeks.
These
are
sorted
by
clicks,
but
you
can
see
other
metrics
there
as
well
like
a
reach
to
response
total
responses
and
retweets.
Obviously
they
need
to
go.
Announcement
was
our
strongest
feat
by
far
followed
by
some
of
just
sort
of
the
beta
reminder.
Tweets
next
slide.
G
Our
top
two
blog
posts
over
the
last
few
weeks,
obviously
years
ago,
really
was
our
best
performers.
By
far
the
strongest
followed
by
our
state
of
US
announcement,
which
sort
of
explained
the
backstory
on
the
naming
of
status
and
what
state
of
us
means-
and
we
had
be
sharing
an
amazing
infographic
with
the
community-
there's
links
to
both
blog
posts
there
in
the
doc,
as
well
as
a
link
to
the
infographic,
which
you
should
definitely
check
out
and
explore
because
there's
a
lot
to
it,
there's
dozens
of
ways.
G
You
can
contribute
to
building
status
for
both
text
and
context
alike,
and
you
can
actually
download
the
infographic
share.
It
there's
a
link
for
that
as
well.
There
and
the
last
two
slides
cover
our
site
engagement.
So
this
first
one
new
visitor
sessions
by
source
which
looks
very
healthy,
driven
by
organic
email,
social
and
direct
traffic,
which
is
very
strong,
but
on
the
next
slide,
it's
a
bit
of
a
womp-womp,
because
you
can
see
that
our
bounce
rate
is
incredibly
high,
and
this
is
one
case
where
the
higher
number
is
actually
not.
G
What
you
want
to
see.
You
want
to
see
a
lower
number.
This
is
basically
someone
coming
to
our
site
and
the
percentage
of
people
that
visit
one
page
briefly
and
then
leave
our
site.
So
I
think
that
this
is
probably
attributable
to
beta
downloads
of
people
going
to
the
site
to
confirm
their
email
or
request
access
to
beta
and
then
leaving,
which
is
obviously
not
what
we
want
to
see.
A
Thank
you
so
much
Kim,
there's
some
really
exciting
stuff
in
there
and
again
huge
kudos
to
Hatchin
to
keep
you
on
the
brink
new
memes
competition.
The
site
might
break
your
computer
if
you
spent
too
long
in
it,
but
I'm
told
reliably
that
that's
exactly
the
point,
sir.
So
we
move
into
UX
and
UX
are
I'm
really
excited
about
this
one,
because
we
have
one
of
our
new
contributors
o
be
presenting
the
product
content
strategy.
A
H
So
that's
all
of
the
words
that
you
see
within
the
app
you
know
from
the
little
guidance
messages
in
onboarding
or
when
you're
sending
your
transaction
down
to
like
the
words
that
you
see
on
the
buttons
you
know,
and
so
you
know
no,
this
is
UX.
Writing
some
people,
call
it
micro
copy.
So
that
would
be
one
of
my
main
focus.
Another
thing
I'll
be
contributing
is
information
architecture.
So
this
is
the
organization
of
how
the
information
is
presented
within
the
app
and
the
entry
and
exit
points
to
the
app.
H
So
this
will
include
things
like
whether
or
not
we'll
include
links
out
to
further
resources,
and
this
becomes
really
important
in
athletic
status,
because
you
know,
as
it's
been
said
before,
we're
not
just
onboarding
people
into
our
abra
onboarding
people
onto
the
blockchain.
So
there's
a
lot
of
Education
and
support
that
we
need
to
give
users
and
finally,
a
style
guide
is
something
I'll
be
working
on,
and
this
is
something
that
will
be
sort
of
like
an
editorial
guideline.
H
That
makes
sure
that
the
words
that
we
see
within
the
app
are
consistent
across
the
board,
so
I'll
be
using
that
every
time
I
added
something,
and
it
also
be
something
that
I
can
distribute
to
other
contributors
into
the
community
so
that
you
know
I,
don't
become
a.
You
know,
a
bottleneck
when
somebody
needs
to
contribute
a
little
piece
of
text.
They
can
all
consult
with
this
dog
and
see
if
it
if
it
goes
along
with
what
we've
established
there.
H
So
you
know
working
on
all
of
these
things,
obviously
so
that
users
can
feel
competent
within
the
app
and
that
they
establishes
a
sense
of
trust
and
it's
a
very
collaborative
process,
so
I'm
embedded
within
the
UX,
our
team.
So
of
course,
I'll
be
incorporating
the
insights
that
they
get
from
these
or
testing
I
work
very
closely
with
designers
to
make
sure
that
the
copy'
within
the
app
it
looks.
H
It
looks
right
and
it
goes
along
with
how
we
want
to
be
presenting
that
product
managers
will
give
guidance
for
to
make
sure
that
the
the
words
within
an
app
make
sure
that
they
are
in
line
with
our
business
and
product
goals.
I'll,
definitely
be
consulting
with
developers
and
other
tech
team
members.
Who
will
make
sure
that
everything
that
we
write
within
the
app
is
technically
accurate
and
then,
of
course,
collaborating
with
marketing
and
branding
to
make
sure
that
the
the
tone
of
voice
within
the
app
is
is
on
message.
H
So
you
know
that's
it's
obviously
a
very
collaborative
effort,
and
anybody
who
wants
to
get
my
attention
can
mention
or
assign
me
a
Toby
20/20
on
github.
And
if
you
go
to
the
next
slide,
you
see
just
a
really
quick
example
here
of
sort
of
the
process
of
editing
something
in
apps.
So
here
we
got
some
feedback
that
this
first
screen
on
the
left
here
was
confusing.
We
got
this
feedback
from
a
community
member
and
even
internally
it
was
something
that
had
been
flagged.
So
I
rewrote
it.
H
A
You
so
much
yeah,
it's
really
great
to
see
the
sort
of
progress
in
particular
and
to
see
such
careful
and
critical
thinking
around
exactly
what
kind
of
language
it
is
that
we
use
to
frame
what
we're
doing
as
a
lot
of
people
and
that's
called
no.
It's
sort
of
my
one
of
my
biggest
interests
in
life
and
I
was
having
this
conversation
with
Ned
the
other
day
about
the
fact
that
what
we're
really
doing
when
we
design
is
entering
into
a
dialogue
with
the
tools
that
we
make.
That
then
make
us
back.
A
It's
the
design
is
constantly
this
dialogue
with
the
world
and
with
the
tools
that
we
use
to
interact
with
that
world
and
it's
especially
better
at
status,
because
what
we're
really
doing
is
we're
using
this
dialogic
tool
called
design
to
design
spaces
in
which
people
can
have
safe
and
secure
dialogues,
which
is
pretty
neat,
I.
Think
and
there's
a
whole
world
to
be
explored
in
there
in
terms
of
how
we
can
best
explain
to
people
what
is
difference,
unique
and
really
inspiring
about
using
a
product
like
status.
E
Yeah
I
think
sandy,
and
this
title
this
slides
a
little
bit
out
of
date
now
but
yep,
so
we
released
a
beta
version,
0.9
point
two
to
two
weeks
ago
on
the
fifth,
and
in
that
version
we
added
support
for
three
collectibles
to
the
wallets.
A
Farsi
public
chat,
a
very
basic
mechanism
for
spam
moderation
and
also
senior
doubts.
Of
course,
we
also
downgraded
our
version
of
react
native
to
reduce
battery
consumption.
E
Last
week
we
did
not
have
a
release,
and
the
reason
for
that
is
that
we
were
low
on
testers
and
the
new
PRQ
was
pretty
long,
so
ana
suggested
that
we
skip
the
release
last
week
and
instead
of
spending
our
time
testing
one
work
on
all
of
those
new
PRS.
So
we
did
make
good
progress
against
that
list
and
we're
back
on
track
to
make
a
release
cut
this
Wednesday,
which
will
hopefully
become
available
to
usual
channels,
testify
and
the
Play
Store
on
Monday.
E
Something
to
note
about
that
one.
We
have
a
PR
in
to
remove
mix
panel,
so
the
goal
that
we
set
to
get
rid
of
product
tracking
should
be
met
in
this
next
release
and
yeah
from
there.
We
should
be
back
to
our
usual
weekly
cadence
and
continuing
to
learn
from
these
beta
releases
as
much
as
we
can.
So
we
can
improve
the
app
for
an
eventual
public
launch.
I
Hi,
yes,
results.
We
found
out
this
battery
drain
issue
on
the
Android,
so
what
we
did
today,
yeah
we
switched
on
react
Ida,
funk
we
downgraded
for
the
zero
922
to
the
old
one.
So
it
gives
us
more
time
to
actually
find
an
ignition.
Then
Roman
actually
detected
and
fix
the
issue,
and
then
we
found
out
that
it
was
actually
fixing
the
new
3x
negative
0:56
zero.
So
we
didn't
submit
any
PR
there.
I
J
Hi,
so
there
are
two
weeks:
we've
added
any
single
set
up
for
calories
from
wintering,
publicly
available
services,
and
that
allows
to
winter
not
only
just
public
website
or
but
also
internal
services,
that
we
use
like
console
and
and
Ravana,
and
you
should
do
that.
I'm
currently
setting
up
monitoring
with
the
help
from
Pedro
of
our
mail
servers.
I
wish
for
my
servers
and
if
you
are
also
always
per
notes,
just
to
be
always
just
always
know
whether
they
are
public
or
not.
J
In
other
news,
we've
other
limits
for
CPU
and
memory
on
for
our
status
go
containers
in
order
to
avoid
losing
visibility
when
they
get
overloaded
and
still
having
all
the
metrics
and
logs
that
we
might
need
for
debugging.
There's
also
been
out
of
work
on
continuous
integration
for
various
more
certain
parts
of
status
like
the
exporter,
which
is
just
for
metrics,
for
status,
D
and
also
just
like
Doc
status.
J
In
addition,
that
will
also
have
switched
our
alerts
measure
for
metrics
related
dollars
into
a
cluster
mode
for,
however,
other
availability
and
also
added
oil,
each
who
buys
the
wealth-
and
we
also
have
a
core
set
up
for
disco
stops,
and
so
we
can
embed,
discuss
comments,
sections
into
blogs
and,
and
so
on.
We've
got
another
slide.
We
can
see
an
example
of
we
have
initially
set
up
for
icinga
for
monitoring
our
websites,
the
next
slide,
and
that
will
soon
add
mentoring
of
all
of
our
theorem
notes
and
that
make
how
the
app
works
possible.
A
Need
so
much
more
incredible
to
see
the
amount
of
work
that
you
get
through
in
two
weeks.
That's
that's
pretty
much
all
younger
than
I
can
say,
particularly
from
a
documentation
and
content
of
the
relations
perspective.
Thank
you
and
kudos
for
the
for
the
ducks
that
status,
continuous
integration.
It's
gonna
make
my
life
in
particular
lab
easier.
So
we
move
on
to
discover
email
servers,
and
this
is
Adam.
K
Hello
yeah,
so
we
are
continuing
working
on
that
and
the
last
thing
that
the
done
they
were
chips
in
the
last
two
weeks
is
backward
compatible
for
symmetric
encryption
of
messages.
Message
requests
so
right
now
we
are
gonna
support
both
symmetric
and
asymmetric.
That's
required
for,
like
yeah,
for
backward
compatibility
and
in
the
future.
We
probably
gonna
just
use
the
symmetric
encryption
up
for
those
requests.
K
The
next
one
is
pier
pool
for
my
servers,
and
that
is
go
so
Adriana
immersed
the
pre
quest
that
implements
that
so
it's
possible
to
to
find
made
servers
using
discovery
version
5.
The
next
step
is
to
integrate
all
those
all
this
work
into
stands
react
and
you
have
pretty
much
get
rid
of
the
hard-coded
main
servers.
My
server
addresses
yeah
and
that's
the
spreadsheet.
A
L
L
L
Then
there
will
be
later
today.
Gasps
threads,
so
that
we
can
all
you
know,
look
into
what
this
will
bring
us.
You
know
in
terms
of
performance
security,
so
hoping
to
get
everyone's
participation
on
that
and
we're
also
starting
to
work
on
implementing
the
PFS
perfect
forward
secrecy
and
by
starting
with
a
double
ratchet
algorithm.
That's
it
cool.
A
M
Yeah
so
I
guess
over
the
past
two
weeks,
there's
actually
some
exciting
progress.
So
thanks
to
Andre
and
Julian
for
the
work
they've
done
in
terms
of
being
able
to
expose
the
status
API,
so
that'll
allow
the
DAP
to
allow
the
user
to
effectively
grab
and
associate
their
status
status
at
key
with
the
username
in
a
very
seamless
manner.
M
A
N
Everyone
sorry
be
quick.
Basically,
the
all
the
progress
we
made
in
envelope
is
focused
either
on
bug,
fixing
or
refactoring,
mostly
around
new
command
API.
So
we
plan
to
continue
doing
that
most
specifically
bug
fixing
until
they
are
not
no
bugs
left
and
we
plan
to
continue
refactoring
until
there
are
no
more
opportunities
for
bugs
left.
So
that's
that's
pretty
much
it.
The
overall
goal
is
to
reach
a
point
where
wallet
is
our
like
most
stable
and
trustworthy
and
all
that
part
of
yep
something
we'll
be
proud
of.
So
that's
pretty
much
it.
A
E
Y'all
presume
+1
so
I'm
happy
to
say
that
the
focus
for
our
team
has
shifted
away
from
fixes
and
small
improvements
for
now
toward
developer
tools
at
last
so
highlights,
or
a
developer
work
on
the
status
side
for
contributors
for
people
who
want
to
build
status.
We
fixed
a
bunch
of
issues
with
dependencies
in
the
set
up,
and
we
also
added
yarn
support
so
that
building
status
is
not
only
possible
but
a
bit
easier
and
faster
as
well.
E
On
the
DAP
developer
side,
where
your
incompletion,
almost
sort
of
generic
status
internal
will
hook
for
extensions
which
will
provide
access
to
basic
things
like
videos,
contact
list
or
whisper
ID
for
any
extension
use
case
in
the
future
and,
as
Barry
mentioned,
we'll
be
our
own
first
user.
For
that,
because
this
variety
can
really
improve,
you
need
registration,
a
lot.
We
also
began
work
on.
Oh
sorry,
I
just
mentioned
the
API
will
be
the
thing
that
will
help
us
with
user
name
registration,
but
it's
also
going
to
offer
things
like
wall
address.
E
Contacts
kind
of
anything
to
do.
That's
like
core
data
for
user
we're
also
going
to
be
working.
On
a
permission
flow
for
that,
so
we
will
never
give
away.
These
are
data
by
default.
We're
always
going
to
let
these
our
control,
whether
they
want
to
share
these
things
with
a
particular
website,
and
we
also
made
a
big
fix
to
UX
bug
that
was
a
partial
blocker
to
core
flows
in
the
status
app.
That
was
an
issue
with
the
keyboard
that
was
instructing
certain
input
fields.
E
E
The
next
two
weeks
will
focus
on
having
some
demos
ready
of
the
WebDAV
API
and
status
cook,
we're,
of
course,
prioritizing
security
issues
that
are
relevant
to
our
team
as
well.
So
things
like
browser
security,
third-party
dependencies
user
data
exposure
to
web.
The
objects
in
particular
all
need
to
be
and
will
be
addressed
by
our
team,
and
that's
it
for
me.
A
O
I
guess
currently
on
vacation
provide
a
update,
perfect
all
right.
The
first
thing
we
did
this
week
was
to
set
up
our
goals
for
the
next
quarter
and
the
goals
of
the
research
department
in
general
a
bit
wider,
but
here
I
would
just
focus
the
goals
of
the
Nimbus
team.
In
the
next
three
months,
we
will
try
to
deliver
a
fully
working
flight
path.
This
would
be
our
main
goal
and
our
secondary
goal
would
be
to
stay
very
close
to
the
research
of
the
new
sharding
design
that
was
presented
in
Berlin.
O
This
means
all
kind
of
mobile
devices
and
embedded
system
on
a
chip
platforms,
and
as
for
the
progress
that
we've
done
in
the
last
two
weeks,
we
started
doing
some
research
from
the
sharding.
Already
we
identified
some
components:
many
critical
of
cryptographic
primitives
that
can
be
implemented
right
now,
so
we've
already
done
some
work
on
implementing
some
of
these
primitives.
O
Our
work
on
meeting
our
previous
ball
from
the
previous
quarter
is
still
ongoing.
We
aim
to
have
compatibility
with
the
existing
etholon
1.0
ecosystem
and,
to
this
end,
we
continue
to
improve
the
space
more
and
more
tests
from
the
ATO
IBM
tests
suit,
and
we
are
currently
improving
the
JSON
RPC
interface
of
Nimbus,
so
it
can
be
used
with
existing
tools
that
managed
to
deter
implants
or
test
environments.
That.
O
So
we
now
we
have
released
a
set
of
tools
that
can
help
me
in
the
workers,
publish
smart
contracts
in
webassembly
that
will
be
used
in
the
future,
and
our
goals
continues
to
be
reaching
because
most
of
the
components
of
the
virtual
machine
are
already
in
place.
The
remaining
work
work
is
fixing
bugs
and
issues,
so
we
can
reach
100%
success
rate
under
you,
get
tested
and
hopefully
be
able
to
sync
with
the
blockchain
slow
and
that's
it.
A
N
Also,
there
have
been
some
things
like
moral
support
and
hyperlinks
support
that
have
been
added
to
react.
Native
on
the
core
app
side.
There
have
been
updates
to
the
basically
to
all
of
the
main
views
of
the
app
to
make
them
in
sync
with
they
will
be
designs.
Like
the
profile
view,
the
chat
view
the
chat,
lists,
chat,
address
and
such
stuff.
Also,
one
of
the
more
recent
updates
is
push
notification
support.
N
N
This
has
to
be
investigated
as
well
and
on
the
UI
side
seems
that
we
have
covered
most
of
the
stuff
that
has
been
originally
intended
either
covered
completely
or
it's
in
theory,
and
it's
in
progress
except
for
message:
delivery
notifications
like
deliberate
and
Santos
small,
by
both
appearing
in
chats
and
also
the
the
global
connectivity
status
notifications.
We
that
we
are
still
lacking
like
so
that
users
know
whether
they
are
connected
to
the
blockchain
or
not,
and
the
last
remaining
long-standing
item
that
is
PR
is
already
in
review.
N
But
this
will
require
a
bit
more
work
because
it's
complicated
in
itself
is
the
desktop
in
to
develop
branch
merch.
The
final
objective
is
being
able
to
build
both
desktop
and
mobile
versions
from
the
same
source
code,
and
it
presents
a
particular
kind
of
problems,
because
even
the
dependencies,
the
packages
and
stuff
is
different,
so
this
mobile
most
likely
will
require
some
kind
of
preliminary
project
setup
steps
some
parameterization
or
stuff
like
that.
Oh
hopefully
that
will
be
done
quick.
A
A
If
there
are
any
questions,
as
always,
we
have
an
open
channel
in
our
riots,
which
you
can
join
a
chat
status
that
I
am
and
feel
free
to
reach
us,
either
there
or
on
Twitter,
very
one
of
our
various
social
channels,
including
our
newly
launched
Spanish
social
channels,
which
are
already
pumping
and
we'll
be
sure
to
get
back
to
you
other
than
that
I'm
a
fantastic
week.
Everybody
thank
you
for
all
of
the
amazing
work
consistently
blows
my
mind
to
see
how
much
gets
done
in
this
organization
every
two
weeks.