►
From YouTube: Town Hall #59 - June 8, 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
Sweet
okay
cool,
so
this
is
just
a
quick
hiring
update
from
me
today.
We're
like
really
excited.
We've
just
found
an
author
handle
it
for
our
senior
product
design,
architect
role,
so
we're
currently
finalizing
contracts
with
him
and
I
should
be
able
to
give
you
a
new
announcement
on
the
next
town
hall.
So
watch
this
space
just
highlighted
here
in
green.
B
We
have
just
kicked
off
the
hiring
process
for
a
brand
new
finance
manager,
and
this
is
a
new
role
that
will
sit
alongside
Danny
and
Jason,
and
the
idea
is
that
this
person
works
on
things
like
financial
analysis,
controlling
accounting.
This
isn't
in
a
really
popular
job
post
we've
had
hundreds
of
applications,
so
I'm
really
busy
just
screening
these
right
now
with
Jason
and
we're
doing
the
first
round
of
interviews
this
week
on
the
research
side,
as
ever
like
our
search
for
both
the
protocol
engineer
and
distributed
networking
engineer
to
work
on
vac
ongoing.
B
B
In
the
near
future,
is
that
we're
looking
to
maybe
highest
sand
legal
support
for
the
team,
and
we
currently
make
use
of
external
legal
vendors
for
advice,
but
I
think
the
time
is
looking
right
to
get
someone
on
the
team
that
can
really
help
us
advise
on
day-to-day
things,
like
legal
considerations
for
new
product
launches,
like
navigating
app
store
terms
and
conditions,
those
kind
of
things,
so
that's
still
TBC,
but
we'll
let
you
know
as
soon
as
that
search
gets
going
and
that's
really
it
for
me
yep.
Thank
you.
Thank.
A
C
Good
morning,
everyone
so
last
couple
weeks,
we
finally
got
a
release,
cut
done
for
a
key
card
integration.
We
know
you've
all
been
excited
to
get
key
card
on
your
hands
and
and
it'll
it'll
be
coming
very
very
very
soon.
The
QA
team
is
very
happy
with
with
what
we're
shipping
and
so
are.
We
so
watch
this
space.
As
for
as
for
planned
releases,
one
point
four
key
cards
and
notifications
both
are
and
ours
only
I
believe.
We've
talked
about
publicly
why
that
is
but
I'm
happy
to
answer
any
questions
about
it
later.
C
D
Yeah,
let
me
go
ahead
and
move
to
what's
what's
next
at
a
bit
more
of
a
high-level
as
I
think
it
explains
a
bit
more
about
our
rationale
for
the
order
of
releasing
features.
If
you
want
to
that
stay
tuned.
There's
a
weekly
post
on
this
bus
on
product
planning
updates
that
gives
you
the
latest
on
what
the
road
map
looks
like
based
on
like
extra
activity
going
on
in
github.
D
D
D
Notifications
are
key
to
improving
retention.
If
you
open
the
Oconee
app,
that's
not
the
end
of
your
experience
or,
if
you
close
the
app
after
we
want
to
be
able
to
at
least
let
you
know
that
something
is
happening
whenever
you
receive
a
message
and
also
make
that
experience
worthwhile.
This
is
why
we're
also
looking
into
sound
effects,
and
things
like
that,
for
when
you
get
a
notification,
we
also
when
you
have
exhibitors
going
on
in
the
app
and
then
like
a
third
pillar.
I
would
say
so.
D
Maybe
set
is
like
normal
on
par
with
other
messengers,
making
sure
that
you
get
notifications
when
you're
offline
not
using
actively
using
the
app
and
then
the
third
aspect,
there
is
making
it
easier
and
more
appealing
to
join
status,
and
in
that
regard,
you
should
think
of
a
referral
program
which
we
are
simply
working
on,
but
also
things
like
a
starter
pack.
How
do
you
get
your
first
script,
oh
and
ways
of
doing
that
through
a
referral
program?
D
How
do
you
invite
people
into
an
existing
or
from
an
existing
group,
chat
on
another
messaging
platform
into
a
group
chat
on
status?
So
those
are
things
we're
like
looking
at
in
these
like
three
buckets
and
then
aside
from
that
there's
more
when
I
would
consider
baseline
features,
which
is
like
making
said
it's
like
all
par,
would
either
mission
to
yours,
but
a
little
bit
more,
let's
say
yeah
yeah
beyond
beyond
that,
that's
called,
but
still
in
line
with
other
messengers,
so
URL
handling.
D
How
do
you
and
how
do
we
inform
people
that
they
are
leaving
status
and
what
the
security
risks
are
related
to?
That
sounds
something
I
mentioned,
but
also
sending
audio
messages,
disappearing
messages,
anonymous
messages,
there's
a
lot
more
feature.
Work
coming
out
in
the
future.
Near-Term
I
would
say
that
we're
focusing
on
now.
A
E
The
only
truck
sure
this
time
around
curry
isn't
available
so
some
new
fleets
up.
So
we
have
a
new
name,
waka
fleet,
which
is
supposed
to
be
testing
the
implementation
of
worker
protocol
and
them
should
be
interesting.
Is
it
possibly
a
replacement
for
the
current
status
go
nodes
in
the
future?
We
have
a
bare-metal
host
for
Nimbus,
become
now
the
benchmarks,
because
any
virtual
machines
or
instances
in
the
cloud
usually
would
be
affected
by
other
of
the
same
host.
So
you
need
a
parameter
one.
E
E
So,
if
you're
interested
that
there
is
a
video
and
the
PDF
and
there's
also
going
to
be
a
blog
post,
essentially
giving
you
an
intro
into
that
and
linking
as
well
there's
been
some
updates
in
the
documentation
in
addition
to
to
the
presentations
some
improvements
in
node
modules
and
resolving
of
maven
dependencies.
Even
further.
E
The
we're
also
working
on
collecting,
more
advanced
metrics
on
how
many
users
are
retained
and
they
don't
just
install
the
app
and
disappear
and
I've
been
doing
some
work
on
the
backend
of
our
elasticsearch
to
essentially
collect
data
on
PR
IDs,
which
are
anonymous.
They
just
are
essentially
identifiers
of
the
unique
installations
of
the
app
and
we
don't
correlate
them
with
anything
like
a
piece,
but
they
should
give
us
at
least
an
idea
of
how
many
people
after
I
started
up.
They
keep
using
at
the
end
for
how
long
to
give
some
retention
graphs
going.
E
F
Zachary
had
a
great
art
interview
with
one
of
the
coin:
Telegraph
reporters
about
Nimbus
and
yosik
as
well.
So
it's
great
to
see
our
coverage
being
picked
up
quite
a
bit
next
slide,
please
some
upcoming
campaigns.
Let's
just
give
you
a
sense
of
what
the
team
is
working
on
right
now,
so
working
on
a
1.4
plus
key
card
launch,
it's
pretty
big
campaign
looking
forward
to
getting
that
out
the
door
so
as
soon
as
the
product
is
released,
we'll
get
that
going
and
I'll
run
through
in
the
next
slide.
F
So
we've
done
a
bunch
of
market
research
over
the
past
few
weeks.
We're
defining
strategies
aligning
partners
in
the
area
and
really
excited
for
that.
So
so
a
lot
to
come
on
that
one
so
stay
tuned
and
next
slide
and
just
so
the
product
team.
You
all
have
been
working
very,
very
fast,
pushing
out
features
at
a
crazy
rate.
So
I
just
wanted
to
give
you
guys
a
bit
of
an
an
overview
as
to
what
the
marketing
team
does
to
try
and
keep
up
with
you
and
then,
and
also
trying
to
explain
why?
F
Just
because
a
feature
is
ready,
it
may
not
be
ready
to
launch
or
go
into
a
release.
So
look
at
what
we
do.
First
and
foremost,
the
first
phase
is
obviously
planning
so
recently
we're
working
with
Andre
and
Hester
just
to
stay
up
to
date
on
what
features
already
what
features
are
in
the
pipeline
and
then
which
release
they'll
be
in
and
we're
starting
to
I
guess
cherry-pick
which
features
go
into
those
release.
F
Just
because
they're
ready
once
again
doesn't
mean
that
they'll
go
into
the
release
in
alt,
explain
why
so,
then
we
will
scale
the
release
and
I,
don't
really
like
this
term,
but
we
will
define
the
marketability
of
certain
features
and
the
impact
they'll
have
to
on
the
campaign
itself.
So
what
we're
doing
now
is
we're
tearing
our
campaign
so
to
speak.
So
a
Tier
one
campaign,
for
example,
will
include
everything
it's
kind
of
like
our
go-to-market
strategy
in
Argentina,
which
will
coincide
with
the
referral
program,
and
this
is
you
know,
PR,
both
mainstream
and
industry.
F
Press
coverage,
localized
communications
for
region,
specific
marketing
will
have
global
campaigns.
For
you
know,
our
global
target
will
produce
social
material
for
social
campaign
more
with
Alec
and
Simon
on
our
programmatic
will
have
boots
on
the
ground.
Local
local
work
will
activate
our
ambassadors
and
because
of
the
scale
of
this,
we
typically
do
2
to
3
per
year,
and
the
lead
time
is
around
3
to
4
months
of
planning
and
production
done.
A
tier
2
campaign
is
slightly
scaled
back.
We
do
want
to
gain
as
much
coverage
so
PR.
F
Both
mainstream
and
industry,
will
typically
roll
out
global
communication
and
social
programmatic
and
ambassadors.
So
I
guess
like
the
localized
work.
It
is
not
as
prevalent
here
because
it
just
takes
a
bit
longer
to
its
activate,
and
these
are,
you
know,
will
do
more,
like
maybe
once
a
quarter,
maybe
more
so
four
to
five
and
then
will
typically
need
two
to
three
months
planning
and
then
a
Tier
three
is
slightly
smaller.
So
this
is
will
be
like
the
1.5
release.
We
still
will
work
with.
F
F
F
Look
like
how
do
we
position
this
to
to
best
target
to
best
explain
the
feature
to
our
audience,
so
I
yeah
to
find
the
product
positioning
once
we've
got
that,
then
we
will
move
into
production
of
our
bill
of
materials,
so
that
influences
our
social
content.
You
know
any
landing,
page
material
or
landing
page
content.
We
need
to
create
material
for
ads
and
programmatic
ads.
F
Then
we'll
write
the
press
release
in
conjunction
with
our
PR
team
and
then
we'll
produce
a
suite
of
materials
for
our
community
to
use
and
then
finally-
and
this
is
why
we
typically
won't
just
just
because
once
again
just
because
the
features
already,
we
won't
just
put
it
in
the
next
release
and
just
because
it's
ready,
we
can't
just
launch
it
right
away,
is
because
we
typically
need
one
one
and
a
half
weeks
minimum
to
pitch
media.
Once
again.
F
Journalists
are
extremely
interested
in
everything
we're
doing,
especially
now
with
at
the
momentum
we've
gotten,
so
they
want
to
cover
us.
However,
they
need
at
least
a
week
and
a
half
to
fit
it
into
their
editorial
schedule.
So
that's
once
again,
we
just
ask
that
once
you
guys
have
a
feature
ready
and
we
have
our
building
materials
ready.
Then
we
ask
at
least
a
week
and
a
half,
so
we
can
pitch
media
so
once
so
yeah,
that's
it
and
yeah
great
job
to
everyone.
You
guys
are
moving
extremely
fast
and
we're
trying
to
keep
up.
A
B
Sure
so
yeah
I
mean
Alex
you're,
absolutely
right.
There
is
a
lawsuit,
of
course,
but
beyond
that
I'm
sure
it's
not
a
surprise
that
we
can't
really
say
much
about
it.
I'm
sure
you
can
imagine,
because
it's
an
open
legal
matter
we're
pretty
limited
in
what
we
can
share.
You
know
we're
a
transparent
project
right
and
we
aim
to
put
as
much
of
what
we
do
out
there
in
the
public
domain.
But
our
hands
are
kind
of
tied
on
this.
B
It
does
involve
courts
so
once
we
can
will
definitely
show
you
more
information
on
this,
but
these
things
move
really
slowly.
So
I
would
really
expect
it
to
be
quite
some
time
before
you
hear
from
us
again
on
this,
but
you
know
as
ever
feel
free
to
DM
me.
If
you
have
any
questions
and
I'm
happy
to
answer
them
directly,.
A
G
So
I
want
to
explain
what
his
status
pay
and
then
answer
the
question
status
based
the
name
of
this
project.
We
are
starting
now
to
build
the
layer,
2
infrastructure,
that's
gonna,
do
a
couple
of
things:
it's
gonna
provide
scalability
and
speed
for
payments.
It's
some!
It's
an
infrastructure,
that's
going
to
be
open
and
inclusive,
and
it's
going
to
facilitate
key
card
payments
with
the
tap
in
physical
setups
and
it's
gonna
allow
to
use
status
app
as
a
point
of
sale
status.
G
Pay
is
something
that's
going
to
be
eventually
integrated
in
the
status
application,
allowing
users
to
access
the
status
by
wallet
so
to
fund
it
to
manage
it
to
control
its
settings
and
its
security
and
payments.
You
users
will
be
able
to
do
them
with
key
card,
as
said
or
with
their
phone.
Only.
So
that's
something
we're
thinking
kicking
out
now
and
to
answer
precisely
the
question
with
regards
to
how
the
gas
payments
will
be
endured
in
this
architecture.
We
are
still
discus
discussing
that.
A
D
Yes
and
Errol,
thanks
for
thanks
for
flaring
this
and
somewhere.
This
is
something
we
should
be
doing
attitude
to
to
planning,
not
hundred
priests,
chance
you're
on
the
exact
timeline,
but
we'll
definitely
work
on
that
as
soon
as
there's.
Flexibility
also
like
in
case
of
any
any
features
like
this
I
do
consider
it
a
feature
to
remove
the
metadata,
feel
free
to
post
a
discuss,
post
or
share
and
discuss
post
in
the
feature
request,
section:
that'll,
move
it
up
to
priority
list
as
well.
D
A
Cool.
Thank
you.
Alright
question
for
our
metallic
elephant
asked
needs
usernames,
so
good,
just
to
drop
a
question
or
sittin
sorry
just
to
drop
a
suggestion.
I
don't
know
if
it's
just
me,
but
it
would
be
good
to
see
a
counter
against
how
many
new
messages
posted
each
thread
similar
to
telegram
addictive,
seeing
any
messages,
as
we
know,
highlighted
with
a
dot
but
then
disappointing
to
discover
that
only
one
single
emoji
slash
sticker
was
posted.
I
guess
Hester
will
be
answering
this
as
well.
Yeah.
D
D
A
D
Good
question,
essentially,
the
answer
is,
is
no,
we
don't
sell
data.
We
have
no
inclination
of
facilitating
a
selling
of
data.
That
said,
there's
probably
more
to
it
than
than
what
I
can
address
now.
So
in
this
case,
I'd
suggest
ya,
share
a
feature
request,
suppose
the
feature
requests
on
discuss
and
let's
have
a
conversation
there
about
what
it.
What
is
exactly
that
you're
looking
to
do
on
the
streamer
marketplace?
D
A
Question
six
two-part
question
asked
by
her
majestic
Iceland
goal
are
most
probably
prominent
question
asker
for
a
while
Part
A
will
be
answered
by
URI
and
Part.
B
will
be
answered
by
aster.
Oh
I
should
probably
say
the
question,
but
a
teller
market.
Can
you
give
an
update
and
the
community
would
like
to
see
this
implemented
and
Part
B
tribute
to
talk?
Can
you
give
an
update
on
tribute
to
talk
and
explain
why
it's
in
the
long-term
pipeline
of
the
status
roadmap
so.
H
On
the
part,
a
question
the
tunnel
network
has
in
fact
been
implemented
and
it's
wedding
deployment
by
the
the
community.
It
can
be
found
at
the
teller
data
exchange
for
some
description,
as
well
as
how
to
view
the
source,
and
then
the
source
has
full
instructions
and
how
to
deploy
it
to
to
main
that.
D
Right
and
yeah
about
tribute
to
talk
so
question:
B
tribute
to
talk
was,
was
implemented
and
then
we
ran
into
architectural
changes.
It
was
already
implemented
actually
last
year,
but
that
means
we
because
of
these
changes
we
need
to
reemployment.
The
feature
that
work
is
is
planned
for
August
timelines
are
are
always
pending,
like.
E
D
Kind
of
challenges
we
run
into
but
plant
plant
for
August
and
to
keep
an
eye
on
like
the
currents
or
latest
planning
I
would
say,
take
note
of
the
product
planning
updates,
I'll
discuss
these
are
updated
weekly
and
they
give
you
a
good
idea
of
what's
what's
going
on,
moving
away
from
Trello
for
the
time
being
in
favor
of
tools
that
have
a
better
integration
with
github
and
allow
us
to
give
a
more
a
more
accurate
reflection
of
current
activity.
So
that's
why
I
definitely
check
out
product
planning
updates.
A
Awesome,
ok.
Last
question
by
python.
My
question
is
related
to
a
user
requested
feature
which
is
already
in
the
near-term
pipeline.
Push
an
education
for
Android.
Is
this
being
implemented
through
Google's
proprietary
FCM
platform?
If,
yes,
then
there
is
a
concern
of
metadata
protection,
the
same
thing
recently
implemented
by
another.
The
same
thing
was
recently
implemented
by
another
newly
launched
app
called
session
from
Loki
project,
but
they
have
offered
the
choice
between
using
FCM
and
background
polling.
A
What
do
you
guys
think
a
new
project
called
Android
open
push,
which
was
sponsored
by
the
German
Federal
Ministry
of
Federal
Ministry
of
Education
research
through
the
type
research
I
prototype,
fun
program?
I,
remember
this
question:
that's
been
asked
I
guess
at
least
210
miles
ago,
so
I
guess
it's
coming
back
and
this
will
be
answered
by
Hester
yeah.
D
Very
fair
question:
sonoda
current
implementation
does
not
use
firebase
cloud
messaging.
This
is
actually
one
of
the
reasons
why
we
removed
a
past
implementation
of
notifications
because
it
was
using
firebase.
The
current
implementation
involves
a
foreground
stir
servers
that
makes
it
so
that
the
app
stays
in
the
background
and
a
local
notification
is
displayed
when
something
happens
which,
like
a
concern,
there
would
be.
D
What
does
that
do
for
battery
consumption
we
tested
that
out
and
that
all
seems
quite
quite
minimal,
which
is
why
we're
favoring
this
look
local
notification
service
and
then,
with
regards
to
Android
open
push
it.
It
actually
becomes
irrelevant
to
us,
because
we
use
this
local
notification
service
actually
got
some
input
from
our
core
contributor
on
this.
Who
can
who
can
explain
a
lot
more
about
it?