►
From YouTube: Status Town Hall - Monday September 30, 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
B
A
C
Think
JB
was
having
issues
with
the
link,
so
I'll
just
talk
quickly
about
the
kudos.
We
wanted
to
put
the
leaderboard
top
5
here,
just
to
kind
of
recognize
everyone.
The
leaderboard
is
pretty
hidden
in
the
DAP,
so
maybe
you
haven't
seen
it
but
check
it
out
and
yeah
just
it
was
really
cool
to
see
people
getting
so
many
different
like
praises
and
kudos.
So
just
a
massive
shout
out
to
the
people.
There
we've
got
Eric
Jacob,
Andre,
Johnny
and
Hester
and
do
be
assuming
you're
not
here,
but
quickly
on
the
hiring.
C
We've
got
a
bunch
of
hiring
going
on
like
here's,
a
list
of
the
roles
like
ever.
If
you
know
anyone
just
let
us
know,
there's
a
referral
bonus
available
and
if
you
have
any
questions
and
each
of
those
posts
should
have
like
its
own
discuss
thread
where
you
can
take
a
look
and
then
ask
questions
or
weigh
in
or
the
process
yeah
and
that's
it.
D
So
in
the
weeks
before
Istanbul
we
managed
to
get
out
our
iOS
hotfix,
which
announces
some
of
the
breaking
changes
that
will
be
happening
with
version
1,
and
you
can
read
about
those
in
the
blog
post
if
you
haven't
already,
but
the
top
line
is
for
users.
Make
sure
that
you
have
your
12
word:
c3
release
ready
to
go
to
recovery
when
version
1
comes
out,
because
otherwise
you
could
lose
access
to
get
that
particular
size
law
on
your
device
and
the
fund
event
if
you
haven't
already
used
it
in
other
wallets.
D
So,
oh
there's
that,
as
for
progress
towards
the
actual
d1
release-
and
it's
really
coming
along
also
before
Istanbul,
the
guys
fixed
the
massive
64-bit
issue-
we've
been
doing
with
Android,
it
was
constants
your
upgrade
to
react
native
version,
0.6
zero
and
a
new
Hermes
and
Jane,
so
huge
kudos
to
pager
in
verse,
44
I'm,
trying
to
merging
that
the
status
codes
has
protocol
go
issues
that
we
had
open
for.
D
V1
audit
are
complete,
so
are
all
of
the
security
issues
reported
in
our
private
repo
and
leave
Andre
and
Andre
I
tackled,
though
before
happiness.
Well,
we
do
have
one
last
open
issue
that
I
believe
is
just
on
status
right
outside
that's
biometric
login.
This
is
something
that
was
a
bit
of
a
Hail
Mary
that
we
decided
to
try
to
fit
in
before
this
code,
freeze,
which
is
meant
to
happen
today
on
13
September
today,
yep
I
mean
so.
D
D
Anyways
in
the
next
few
weeks,
I'll
be
putting
a
timeline
together
for
the
v1
release
again
on
it
is
meant
to
take
off
today,
starting
on
the
Status
go,
and
it's
meant
to
take
about
three
weeks.
I
believe
Cora
can
probably
give
us
more
later
on,
but
I'll
be
putting
together
timeline
for
the
release
itself,
as
the
team
has
just
finished.
Estimates
towards
our
v1
backlog,
the
backlog
is
mostly
along
the
sir
bugs
you
can
find
it
on
github.
D
If
you
just
look
at
the
v1
release
label,
but
I've
also
linked
a
high-level
overview
of
the
changes
that
that
we
need
to
make
so
for
the
release.
There
are
a
few
new
features
and
builds
on
new
features
that
we
need
to
complete
before
we
can
release
version
one.
So
one
of
those
things
is
eNOS
verification
and
the
ability
to
change
a
whisper
I
do
DNS
switch
Eric
and
Pedro
worth
working
on
so
I
mean
yes,
you
change
in
discuss
in
the
coming
weeks.
B
E
Right
now
is,
of
course,
the
security
audit
that
starts
today,
together
with
the
code
freeze,
done
by
trail
bits,
and
this
security
audit
will
be
focusing
mostly
on
the
core
components
of
the
application,
so
the
protocol
and
how
we
store
information
about
the
users
and
what
is
sure
to
the
protocol
and
we'll
be
getting
weekly
update.
So
we
can
all
the
fly
fix
whatever
you
should
pop
up,
and
you
can
read
more
about
that
on
the
discussed
post.
E
And
in
terms
of
infrastructure,
for
example,
the
cool
thing
that
happened
recently
is
now
we
have
bridging
between
status,
chats
and
Kitter
and
discord.
There
are
other
ones
coming
so
proudly
telegram
which
I'm
staring
at
right.
Now,
it's
not
all
chats.
It's
only
ones
that
I've
configured,
but
it's
most
of
the
ones
that
we
use
currently
for
by
most
developers,
that's
up
already
and
still
use
improvement.
But
it's
getting
here.
E
We
also
have
some
cool
things
in
terms
of
analytics,
so
we
have
fathom
analytics
for
our
main
site,
which
is
this
open
source
and
Attucks
ocean
that
does
a
lot
of
hashing
and
salting
of
the
data.
So
it's
fully
your.
It
fully
respects
the
privacy
of
our
users.
So
we
we
only
collect
quantity
information
and
nothing
about
individual
users.
I
also
have
source
spread
which
collects
information
about
the
contributors
and
how
much
they
put
in
on
different
repos
and
that's
going
to
expand
as
I
as
I,
add,
more
organizations
and
private
repos
and
so
on.
E
But
you
can
already
check
out
at
the
URL
they're
also
tested
out.
I
saw
wasn't
bit
water
for
further
secrets,
but
said
against
that.
There's
also
a
lot
of
work
going
on
in
terms
of
builds
first
status
reactor
come
you
have
to
do
release
so,
for
example,
we
will
have
our
architecture
apks,
which
will
reduce
the
size
to
about
20
megabytes
instead
of
more
of
a
40
megabyte
size.
So
that's
nice
for
users
and
we're
also
getting
ready
because
of
great
work
by
Baldomir
to
get
new
builds
for
us
desktop.
E
B
B
B
So
this
payment
network,
we
want
to
choose
and
use
the
right,
scalable
layer,
2
technology,
to
further
the
transactions,
the
state's
contracts
management's.
We
want
this
payment
network
to
fulfill
all
Taylor
Network
needs,
and
this
payment
network
I
mean
in
this
payment
network.
Account
is
going
to
be
integrated,
which
means
that
it's
going
to
be
easy
to
on
board
for
a
merchant
key
card
tap
payments,
and
for
this
we
are
going
to
lose
that
to
be
easy
to
set
up
point-of-sale
and
we
laugh
some
fraud
limitation
built-in
mechanisms.
B
A
Good
thanks,
QE,
okay,
that
is
actually
all
of
our
updates
for
today,
I'm
just
a
quick
town
hall.
For
you
guys,
we
do
have
one
QA
that
was
submitted
through
town
hall
questions
on
status,
so
the
question
was:
what
is
status
is
plan
after
the
one
launch
and
does
anybody
want
to
take
a
quick
stab
at
this
answer?.
D
D
So,
okay
yeah!
So
for
regrets
the
core
product
alone,
just
the
status
application
on
October
15th
we're
going
to
be
having
an
Road
mapping
session
where
we
discuss
what
our
priorities
are
in
q4
and
q1
of
2020,
and
we
are
currently
working
to
set
up
like
a
simple
analytics
dashboard
where
you
can
begin
to
start
looking
at
the
actual
usage
that
we're
seeing
on
with
them
on
by
tucking
the
key
IDs,
and
we
can
begin
to
venues
that
sort
of
the
baseline
for
for
a
user
base
and
begin
to
measure
engagement.
D
F
Just
to
be
more
specific
about
a
noise
complaint,
just
for
example,
most
of
the
things
that
we
are
launching
on
v1
are
very
how
I
would
say
bare-bones,
for
example,
the
sticker
market
is
it
just
people
can
only
buy,
they
cannot
cannot
register
new
stickers
there.
So
after
the
v1,
we
are
working
on,
for
example,
in
this
sticker
market.
For
the
artists,
the
same
thing
about
about
the
tribute
to
talk,
so
it's
a
real.
The
first
version
is
just
a
simple
spoon
protection.
F
So
if,
after
the
v1,
we
want
to
make
it
that
that
there
is
more
tools
there
for
people
uses
on
table
to
talk
that
are
in
the
white
paper,
for
example,
for
people
selling
services
like
consultants
and
so
on.
So
just
two
examples,
but
this
would
would
be
to
everything
that
we
are
building.
They
are
counting
sis
and
the
multi
accounts.
So
in
future
we
are
also
going
to
support
more
adversity,
account
systems,
the
identity,
C's
systems
that
currently
are
being
used
by
other
depths.
F
A
Cool
thanks.
No
anybody
else
want
to
jump
in
here,
alright
cool,
so
I'm,
just
flying
too
quickly.
That
was
more
front
like
a
public
hearing,
a
I'm
gonna
stop
our
livestream
and
we're
gonna
have
more
of
like
an
internal
Qi.
So
thanks
everybody
who
submitted
them
publicly.
Everyone
just
quickly
stay
here
for
one
sec.