►
From YouTube: April 13, 2020 Town Hall #55
Description
The 55th Status Town Hall, held fortnightly
B
B
C
Piece
trying
to
highlight
illustration
of
the
border
vision
then
go
over
to
like
a
sort
of
a
bird's-eye
view
of
the
organization,
as
well
as
outline
any
changes
and
followed
by
kudos
and
just
highlighting
different
people
within
the
organization
and
showing
our
appreciation
for
going
above
and
beyond,
and
then
just
a
feedback
and
further
reading
last
slide.
Next
slide,
please
cool!
So
so,
basically,
you
probably
all
know
that
you
know
I'm
quite
sympathetic
towards
the
the
kachins.
C
C
C
Unfortunately,
the
reality
is
that
this
never
really
came
to
fruition,
that
this
federation
or
union
of
these
different
states
has
never
really
material
and
and
really
really
suffers
from
this
resource
curve.
They're.
Actually,
the
largest
natural
resource
reserve
in
you
know
they
have
the
largest
jade
gold
amber
timber
iron
and
hydroelectric
energy,
so
they
built
dams
back
in
the
60s
and
what's
actually
caused.
C
I
like
we
were
supposed
to
do
a
face
to
face
with
one
of
the
the
generals
there,
because
what
they're
trying
to
do
is
they're
trying
to
bolster
their
nation-building
efforts
and
one
of
the
pieces
there
is
that
they
require
their
own
currency,
they're,
currently
classified
as
autonomous
region,
and
they
have
no
currency.
They
use
all
the
currencies
of
like
that
are
around
them.
So
you
know
india,
china
and
and
myanmar.
C
So
unfortunately
yeah
the
face-to-face
is
cancelled,
but
I
will
be
working
on
and
submitting
a
proposal
for
a
national
digital
currency
for
them
and
they
have
some
plans
in
terms
of
getting
adoption
on
this.
They
want
to
build
these
hospitals
that
will
accept
this
current,
so
it
is
very
slow
moving.
It
may
never
come
to
fruition,
but
what
this
technology
is
really
good
for
is
supporting
sovereign
communities,
and
this
is
just
one
piece
of
many
that
could
fulfill
a
very
similar
narrative
next
slide.
Please.
C
C
This
isn't
about
time-driven
development.
This
is
more
about
just
kind
of
understanding
where
we're
going
and
that's
essentially
it,
but
this
doesn't
change
the
strategy.
The
strategy
this
year
is
still
currently
the
focus
on
user
growth
and
fundraising
to
fuel
growth
and
support
the
pdp
infrastructure
requirements.
C
Now
we've
had
a
lot
of
turbulence
this
year
with
with
the
coronavirus
and
and
the
economy,
so
we
have
been
planning
this
year
to
to
not
expect
raising
and
how
we,
how
go
about
that
is,
is
still
not
fully
settled,
but
we're
still
going
to
try
anyway,
because
it's
worth
trying,
but
we're
certainly
not
planning
for
for
that.
This
year
there
has
been
some
rather
large
changes
in
the
organization.
C
Rachel
would
be
leaving
us
she's
gonna
head
out
on
her
own
and
and
try
out
some
new
things,
and
we
support
that.
I
think
that's
a
fantastic
move
for
her,
but,
yes,
she
will
be
sorely
missed,
rachel's
been
the
head
of
product
and
has
really
kept
everybody
to
together
and
fulfilling
a
lot
of
a
lot
of
strategic
needs
in
the
organization,
and
so
we
we
have
some
big
shoes
to
fill
it
looks
like
this
is
unofficial.
C
This
is
an
opportunity
actually
to
to
get
more
community
involvement
and
it's
kind
of
good
timing
from
a
certain
respect,
because
we
are
moving
the
application
into
the
public
and
we've
got
the
state
platform.
So
this
what
better
moment
to
actually
get
the
which
might
potentially
lead
to
a
better
product.
C
So
you
know
this
doesn't
mean
the
this
is
the
end
of
a
buck
or
anything
like
this.
It's
it's
basically
been
put
on
pause
and,
what's
actually
kind
of
good
about
doing
desktop.
Is
that
then
it
gives
us
a
platform
to
kind
of
integrate
embark
into
it
and
allows
us
to
to
pave
the
way
for
reintroducing
extensions
with
the
embark
team
understanding
the
application
on
a
much
more
intimate
level.
C
I
also
want
to
say
that
you
know
the
embark
team
of
absolute
rock
stars.
I
am
a
little
sorry
that
I
have
to
ask
this
of
you,
but
it
seems
like
it's
the
the
best
play
forward
to
keep
everyone
on
board
and
definitely
don't
worry
about
productivity.
Of
course,
there's
going
to
be
a
hit
while
everyone
trains
and
understands
you
know
and
settles
down
into
the
into
the
new
roles
so
yeah
I
mean
and
you're
probably
taking
a
glance
on
on
the
right.
C
The
yeah,
I
think
I
covered
most
of
the
things
there
next
slide.
Please
yeah
so
so
kudos
is
a
is
a
is
a
dap
that
we
made
a
while
back
and,
quite
frankly,
I've
had
a
terrible
participation
record
in
in
it,
but
I
will
be
making
a
concerted
effort
to
participate
in
kodas
and
encourage
everyone
else
to
do
the
same
I'll,
be
giving
kudos
based
on
feedback
from
from
anyone
of
course,
but
especially
team
leads.
C
So
if
you
can,
let
me
know
team
leads
that
would
be
if
anyone's
been
doing
above
and
beyond.
Please
let
me
know,
there's
a
couple
of
here:
that's
a
long
overdue
gravity.
Blast
identified
a
security
issue
issue
many
months
ago.
That
was,
I
think,
was
missed
by
some
one
of
the
audits
and
absolute
lifesaver.
I
really
appreciate
the
the
efforts
there.
Gender
has
just
done
a
major
mega
education
session
with
embark,
helping
them
get
up
to
speed
with
the
application
architecture,
took
him
a
few
hours.
C
I
think,
and
I
really
appreciate
everyone
being
involved
in
that
and
gender
for
putting
that
together
and,
of
course,
hester
she's,
bringing
a
lot
of
structure
and
communication
and
relevance
to
what
we
do.
She
seems
to
be
everywhere,
and
I
really
appreciate
that
then
then
all
the
people
involved
in
the
the
wacko
design,
implementation
and
rollout.
I
I
think
that
couldn't
have
gone
more
smoothly.
C
I
think
that
that
was
a
really
really
impressive
effort-
yeah,
that's
great
and,
of
course,
rachel
for
being
the
the
ultimate
cat,
herder
and
keeping
everyone
together,
and
I
said
product
on
chat,
but
I
meant
a
product
on
track,
yeah
next
slide,
yeah
and
yeah.
I
also
wanted
to
create
anonymous
form
here.
So
if
you
have
any
feedback
at
all
on
these
slides
or
anything,
that's
on
your
mind
definitely
hit
me
up.
I
don't
need
to
sign
in
with
google
or
anything
like
that.
C
B
A
Yeah,
that's
me
cool.
I'm
really
excited
to
see
kudos
on
this
by
the
way
yeah
I'll
be
giving
out
some
more
snt
later
this
week.
So
you
can
give
out
your
kudos
to
your
favorite
peoples.
So,
okay,
peter
pops,
update
we've
got
one
new
core
contributor,
I'm
very
excited
about
this
one.
This
is
terry
who's
joining
our
team
as
an
hr
operations
coordinator
and
she'll
be
on
board
from
tomorrow.
A
It's
a
warm
welcome
to
terry,
it's
nice
to
have
you
here
next
up,
just
a
quick,
recurring
update.
Not
much
has
changed
since
last
week,
but
I
have
highlighted
in
green
the
two
new
roles
that
we're
kind
of
putting
onto
the
market,
so
the
technical
copywriter
for
marketing
is
something
that
we
started
recruiting
for
a
while
back,
but
was
de-prioritized.
A
Now
we
would
like
to
reactivate
that
search
so
we'll
be
getting
back
to.
I
think
we
still
have
some
candidates
in
the
pipeline
for
that
one
so
expect
to
have
from
us
pretty
soon
and
then
on
the
research
side,
working
with
oscar
and
dean,
we're
looking
for
a
protocol
engineer
to
help
us
solve
the
problem
of
decentralized
communication,
and
that's
it.
You
can
also
see
as
well
that
we
had
another
protocol,
engineer
role
which
was
working
with
dimitri
on
cache.
A
D
So
I'm
the
new
tech
writer
on
the
nimbus
team
and
I've
joined
status
for
in
my
first
month
and
last
month,
I've
wrote,
I
mainly
focus
on
name
the
p2p,
and
I
wrote
three
tutorial
articles
for
beginners
to
get
started
using
a
direct
check
example,
and
also
my
work
has
involved
some
sample
code
refactoring,
because
previously
the
code
was
a
bit
messy.
For
example,
the
function
name
is
is
not
that
intuitive
and
also
I
simplify
a
lot
of
things
in
the
sample
code
and
I've.
D
B
E
Hey
yeah,
so,
first
of
all,
thank
you
jared
for
the
shout
out
today
go
stop
saying
that
I'm
really
really
going
to
miss
working
with
you
guys,
but
I
will
be
cheering
for
you
and
you'll.
See
me
around
no
doubt
so
updates
for
core.
Today,
real
quick,
we
released
version
1.2
with
waku
mail
servers
on
april,
8th,
which
I
believe
was
shortly
after
the
last
town
hall.
E
I
have
to
update
the
install
data
for
ios,
I'm
so
sorry.
I
wasn't
able
to
grab
that.
I
didn't
ping
andre
early
enough
on
friday,
but
we
did
see
like
this
is
a
this
is
a
an
uptake
of
like
more
than
a
thousand
new
users
on
android,
I
believe
so
close
to
10k,
active
users
or
active
installs.
Sorry,
I
shouldn't
say
users
active
installs
on
android
as
of
today.
E
E
E
For
from
code
perspective,
we
have
a
new
webview
implementation
that
will
be
integrated
for
the
browser
in
1.3
and
with
this
new
implementation,
we
are
able
to
drop
two
outdated
libraries,
we're
staying
more
in
sync
with
the
react
native
webview
community
and
will
be
benefiting
from
upstream
fixes
to
that
implementation.
So,
oh,
and
we
also
spent
a
good
portion
of
last
week,
fixing
bugs
as
we
as
we
had
determined
to
do
on
the
past,
the
previous
town
hall.
So
a
bunch
of
bug
fixes
to
be
included
as
well
and
I'll
detail.
E
Some
of
those
in
the
release
notes
for
1.3.
After
that,
the
the
scope
for
the
following
release.
1.4
is
quite
tentative,
but
given
where
things
stand,
I
do
anticipate
being
able
to
release
push
notifications
for
direct
messages,
and
this
is
again
for
android
only
because
we
have
great
limitations
on
ios
that
prohibit
us
from
releasing
push
notifications
in
a
decentralized
manner.
E
I'd
also
really
like
to
prioritize
testing
of
the
key
card
integration
within
the
status
client
once
1.3
is
released,
so
I
can't
say
for
certain
whether
it
will
be
included
in
1.4.
It
really
depends
on
what
comes
up
in
qa
of
key
card,
but
that
is
going
to
be
next
on
the
docket,
I
hope
for
the
qa
team
so
that
we
can
officially
launch
key
card
which
will
be
very
exciting
beyond
that.
E
Our
roadmap
we've
got
loads
of
we've,
got
loads
of
great
feature
requests
in
the
community,
which
I
really
appreciate
and
have
been
integrating
onto
the
trello
roadmap,
so
that
they're
visible
to
all.
But
wednesday
of
this
week,
we'll
be
having
a
product
planning
session
which
again
will
take
a
bottoms-up
approach
where
everybody
is
invited
to
share
their
thoughts,
their
feedback,
their
concerns
and
their
requests
with
us,
and
if
you'd
like
to
get
more
vocal
about
that,
you
can
do
so
on
the
relevant,
discuss
post,
which
is
linked
on
this
slide.
E
We
would
love
to
hear
from
you
definitely
taking
opinions
from
the
core
team
and
we
will
be
using
the
wednesday
synchronous
call
to
just
sort
of
filter
through
and
prioritize.
What's
come
up,
so
that
should
be
a
good
preview
for
the
product
planning.
That's
to
come
as
we
move
to
a
more
more
community-led
product
planning
process
yeah.
E
Lastly,
like
image
sending
in
chat
that
feature
has
a
tiny
bit
of
work
left,
but
can
be
finished
soon,
so
it
should
also
be
included
in
upcoming
release
and,
unfortunately,
the
status
starter
pack
which
we're
really
excited
about.
I
don't
have
any
word
on
whether
we
have
the
administrative
clearance
that
we
require
from
the
app
store
to
move
forward
on
that
feature.
E
B
F
What's
up
henry
thanks
security
stuff
not
too
much
to
discuss
today,
we'll
have
a
lot
more
coming
up
soon,
though,
a
few
more
tutorials
on
what
I'm
going
to
talk
about
status
app,
we
had
the
audit
done
on
the
starter
pack
service.
That's
been
finished,
we're
working
on
addressing
some
of
the
issues,
nothing
too
major
to
concerned
about
we're
pretty
happy
with
how
it
went
out
just
doing
some
final
touches
and
addressing
all
the
issues
that
were
brought
up
I'll,
be
releasing
that
into
a
public
repository.
F
So
people
can
read
not
not
only
the
report
that
was
done
and
all
of
the
assets
that
were
created
during
the
audit,
but
also
kind
of
how
we
mitigated
the
issues
and
so
on
and
so
forth.
If
you're
interested
outside
of
that,
actually
as
a
part
of
the
starter
product
service,
some
threat
modeling
was
done,
and
I
really
liked
the
way
it
was
done
for
this
particular
project.
So
I'm
building
out
process
that
reflects
that
and
a
bit
more
as
a
trying
to
build
a
standard
process
for
threat
modeling
across
status.
F
We
tried
this
previously,
but
it
didn't
quite
catch.
Probably
due
to
me
not
following
through,
but
we'll
be,
building
examples
and
kind
of
a
walk
through
on
what
needs
to
be
done
at
status
security.
The
skeleton
of
that
is
already
there.
If
you
want
to
go,
take
a
look
at
it
through
the
link
once
that's
completed,
I'll,
be
walking
through
and
trying
to
get
people
to
do,
threat,
modeling
on
all
the
old
current
and
future
products
or
protocols
of
status.
F
F
I
have
examples
on
what
on
how
you
can
do
that
and
then
from
there
you
do
a
threat
modeling
session
like
stride
or
dread,
or
something
like
that
which
I'll
have
examples
of
based
on
that
diagram
and
they
it
iterate
on
each
other
until
everyone
has
an
agreement
and
last
but
not
least,
we'll
be
moving
from
zoom
for
status,
town
halls
or
any
other
kind
of
peripheral
communications.
We
don't
use
zoom
much,
but
when
we
do
we'll
be
moving
away
from
it
for
security
concerns,
I'm
reviewing
options.
F
Let's
expect
to
be
on
something
else.
Next
time
you
can
go
next
slide
for
infrastructure,
so
a
lot
of
stuff
here
jacob
made
it
all
he's
not
here
to
talk
about
it.
So
I'm
just
going
to
read
it
while
you
read
it
as
well
sites.
We've
got
this.
We
got
deploy
starter
pack
on
the
test,
hosts
making
some
docker
images
for
for
starter
pack.
So,
as
you
can
see,
there's
a
lot
of
work
around
making
sure
starter
pack
works,
easy
to
use
and
so
on
and
so
forth.
F
For
the
app
fixed,
mig,
filter,
nyx
reduced,
builds,
let's
see,
fix,
missing
asset
images
and
status
apps
to
make
sure
those
show
up
when
they're
supposed
to
got
some
more
metrics,
we
can
actually
see
better
whisper
envelope.
Archive
metrics
across
the
network,
which
is
really
great
to
see
by
us,
helps
us
figure
out.
What's
going
on
and
maybe
track
users
a
little
bit
better
in
terms
of
how
much
usage
in
the
network
is
actually
happening,
let's
see
switch
to
mongodb,
thank
god.
F
Let's
see
fixed
deployment
process
for
simpledap,
that's
going
to
be
better
for
testing
as
we
implement
more
and
more
projects.
Universal
links
are
getting
a
lot
more
work
done
thanks
to
jacob
and
people
working
on
that,
it's
gonna
make
it
easier
for
you
to
click
on
things
and
get
to
status
or
people
quicker
or
share
your
share.
F
Your
your
profile
with
people
adapt
discoveries
get
quite
a
bit
of
work,
really
enjoying
seeing
that
get
get
better
and
better
and
we've
archived
the
embark
server
as
they've
moved
over
to
the
core
contributor
disc
discord,
so
that
people
can
still
maintain
all
the
history
from
there
and
that's
being
exposed
through
oauth.
So
you
have
to
log
in
make
sure
you
have
access
to
it.
That's
it
for
us.
B
G
G
G
They
have
translated
status
and
our
website
into
their
languages
or
produced
some
awesome
content,
such
as
blog
posts
introducing
status.
Also,
we've
recently
received
applications
from
hong
kong,
ukraine
and
poland,
so
the
ambassador
program
is
getting
more
diverse
than
ever
next
slide.
Please
in
q1,
we
had
seven
more
completed
tasks
than
q4
2019.
G
G
I
planned
to
support
a
couple
of
meetups
in
march
and
april,
but
everything
was
cancelled
due
to
the
coronavirus
and
the
good
thing
is:
we've
got
awesome
technical
content
from
ambassadors
such
as
building
numbers
on
android
from
android,
which
was
one
of
the
most
popular
technical
blog
posts
in
q1.
So
thank
you
andrew
again.
G
G
Aside
from
the
translation
from
the
ambassadors,
there
were
some
open
source
translators
as
well.
For
example,
status
status
status
was
100
translated
into
traditional
chinese
by
an
open
source
translators.
Recently,
his
translation
was
reviewed
by
tina,
as
she
said
before,
and
the
quality
of
the
translation
was
really
great.
G
We
serve,
we
support
nine
languages,
other
than
english
for
status
and
five
languages
are
in
progress
or
under
review
for
your
information.
Russian
was
translated
by
the
localized
team
recently
as
for
our
requests,
but
all
the
other
languages
have
been
translated
by
the
ambassadors
or
open
source
translators
on
top
of
the
mobile
application.
Mobile
app
translation,
the
status.im
website
also
supports
9
languages
as
well,
thanks
to
the
translators
next
slide.
Please.
G
G
B
H
Yeah
hi
everyone,
so
this
will
be
pretty
quick,
two
main
points.
I
I
wanted
to
first
answer
the
question
about:
when
will
keycard
be
available
to
status
users?
I
can
give
a
super
precise
answer,
but
I
wanted
to
highlight
the
the
dependencies
we
have
to
to
release
the
key
card,
so
we
have
three
things.
First,
the
production
of
cards.
This
is
the
this
is
well
we
we
are
suffering
from
the
coronavirus
here.
Obviously
it
was
planned
to
be
manufactured
mid
this
week.
H
So
in
two
days
from
now,
we
had
some
issues
with
the
the
the
personalization
scripts
on
the
the
factory
line
working
on
that
we're
a
bit
slowed
down,
because
the
samples
are
traveling
from
countries
to
countries
and
yeah
dhl
is
pretty
slow,
so
we're
gonna
have
some
delay
and
the
cards
will
get
them
by
end
of
april.
So
that's
one
thing
production.
The
second
thing
is:
is
the
integration
with
status
as
outlined
by
rachel?
H
We're
gonna
go
through
some
keycard
qa
and
the
plan
is
to
have
keycard
integrated
in
android
on
1.4.
The
exact
date
is
not
clear
for
now,
but
yeah.
Once
we
have
that
the
main
priority
after
will
be
ios
integration
and
the
third
dependencies
is
something
pretty
basic,
but
it's
the
shipping
of
cards
from
the
factory,
because
just
last
week,
dhl
just
did
stop
the
service
we're
using
to
ship
the
cards
since
we're
using
a
pretty
convenient
service
which
ships
worldwide
for
for
for
for
a
fixed
cost,
and
they
stopped
that.
H
So
we
can't
ship
the
key
cards
anymore.
So
we
have
these
three
dependencies.
Some
uncertainties
on
when
integration
and
shipping
will
be
ready
again.
Overall.
This
means
that
the
keycards
won't
be
available
in
april
and
we'll
come
back
on
more
detail
whether
for
a
more
precise
day,
but
that's
the
current.
I
mean
status
of
the
our
planning
two,
two
quick
updates
about
what
we're
working
on
from
a
product
ecosystem
standpoint.
H
We
had
last
week
some
pretty
interesting
discussion,
both
internally
with
the
marketing
team,
especially
especially
johnny,
and
ian
rudy,
about
how
to
pitch
in
keycard
in
our
pitches
to
partners
and
dabs.
Especially
that's
pretty
positive,
and
the
other
thing
is
that
we're
working
on
the
possibility
and
the
proposal
to
use
key
card
and
maybe
status
for
attendees
at
next
defcon,
so
stay
tuned.
But
this
is
pretty
exciting
and
ongoing
discussions
and
that's
what
I
wanted
to
update
yeah.
B
All
right,
thank
you
very
much,
so
the
last
update
will
be
community
update
for
me.
Actually
so,
let's
start
okay,
so
we're
gonna
be
starting
something
called
the
status
by
weekly
update,
I'm
getting
I'm
going
to
be
working
on
this
with
ken
who's,
just
an
ambassador
for
status,
so
the
bible
key
update,
mainly
contains
information
about
everything.
B
That's
going
on
around
the
status
network,
for
you
know
two
weeks,
so
this
will
include
updates
about
the
mobile
app
events
blog,
shout
outs,
nimbus,
keycard,
teller,
down
alls,
like
just
covering
everything
around
status
network,
so
we're
also
gonna
be
recording
an
audio
version
of
this
update
that
a
podcast
episode.
I
need
to
be
uploaded
on
the
everything
status
podcast.
So
if
you
want
to
check
that,
you
can
just
go
to
media.statusnetwork.com
to
listen
to
the
update,
so
we're
going
to
be
having
the
test
version
of
the
update,
written
and
uploaded
on
discuss.
B
B
All
right
so
status
by
weekly,
update,
that's
down
all
2.0,
so
this
is
just
an
idea
that
I
came
up
with,
along
with
ken,
so
we're
just
trying
to
break
up
something
that
we
could
use
as
an
alternate
to
town
oil.
So
so
the
idea
is
to
create
an
alternate
version
to
the
current
version
of
town.
Also,
it
worked
as
a
compliment,
so
it's
been
an
audio
version
of
tunnels
and
we'll
be
using
the
everton
status
podcast
to
implement
these
and
we'll
be
having
two
different
catch-up
sessions.
B
So
the
first
one
is
the
bible
catch
up
with
the
team,
while
the
second
one
is,
the
bible,
click
catch
up
with
ambassadors.
So
sorry,
let's
type
this
yeah,
so
the
bi-weekly
catch-up
with
the
team
will
be
a
first-class
episode
where
a
member
of
the
saddles
team
will
come
on
and
join
us
and
then
we'll
discuss
about
the
things
the
team
has
been
working
on
for
the
past
two
weeks
and
we're
going
to
create
a
discus
thread
every
two
weeks
where
people
can,
you
know,
add
questions.
B
So
if
you
have
any
questions
that
you
would
like
to
ask
any
of
the
team
members
to
discuss
and
explain
over
the
podcast,
then
you
can
submit
it
on
that
discuss
thread.
So,
while
the
biblical
casualty
ambassadors
is
a
podcast
episode,
ambassador
we're
going
to
be
talking
about
what
the
ambassador
has
been
working
and
how
he
has
been
contributing
to
that
status
network.
So
if
you
have
any
questions,
if
you're
not
an
ambassador
or
you
would
like
to
come
on
the
podcast
services
and
discuss,
you
can
just
bring
me
my
enzyme
stats.
B
So
you
can
just
message
me
and
or
join
the
everything
status
channel
on
discord
or
status.
So
the
next
update
I
have
is
the
niger
crypto
community?
So,
okay,
can
you
please
move
to
the
next
slide?
Yeah,
oh
great!
Thank
you.
So
this
is
just
for
our
nigerian
friends.
I
actually
wrote
these
in
pidgin,
so
you
know
just
for
them
to
read
it
so
we're
starting
the
nigerian
community
on
status
up.
If
you
want
to
join,
you
can
type
in
ice
status,
niger
and
join
there.
We're
going
to
be
discussing
and
we've
started.