►
From YouTube: Town Hall #60 - June 22, 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).
A
C
Absolutely
all
right
so,
first
up
just
a
quick
hiring
update
for
you.
We've
got
three
rules
that
are
active.
The
first
is
our
Finance
Manager
role
and
we've
had
it
basically
over
a
thousand
applications
in
two
weeks,
so
we
are
doing
as
much
as
we
can
to
really
speak
to
as
many
promising
candidates
as
we've
seen
so,
if
you've
applied
you've
probably
heard
from
me
to
give
you
a
holding
update
as
we're
working
our
way
through
all
the
applications.
I
know
it's
not
the
quickest.
C
We
can
only
interview
as
many
people
as
we
can
concurrently,
but
rest
assured,
like
the
job,
is
still
alive.
We're
keen
to
hire
someone
as
soon
as
we
can
so
I
will
get
back
to
you
as
soon
as
possible
and
yeah.
Just
thanks
for
the
patience
everyone
that
applied
and
then
on
the
research
side
of
things.
So
we
have
two
roles:
we're
on
the
late
stage
into
use
for
our
secure
messaging
protocol,
engineer
and
we've
seen
a
couple
of
promising
candidates.
C
So
far,
so
we
will
finish
those
out
and
hopefully
make
an
evaluation
pretty
soon
and
whether
we've
got
enough
to
move
forward
with
an
offer
and
then
on
the
distributed
file,
storage
side
of
things.
The
networking
engineer
we've
been
hoping
to
hire
has
been
a
really
long
process.
We
haven't
yet
quite
found
the
perfect
person,
so
we
keep
mining
our
network
chanting
to
potential
candidates.
C
Make
sure
that
we
get
the
decision
so
thanks
to
me
tree
for
your
patience
in
working
with
us
on
that
one
and
you'll
see
just
a
screenshot
of
our
hiring
page
on
the
right
here
and
what
you
might
notice
about
it
is
that
it's
super
buried
on
our
website
like
right.
The
way
ended,
developer
documentation,
so
I'll
be
working
with
jinho
this
week
to
refresh
the
content
and
make
it
a
bit
more
discoverable
because
I
think
right
now.
It's
not
super
obvious
two
candidates
who
drop
by
the
site
next
slide.
C
Please,
okay,
just
a
couple
of
quick
people!
Ops
updates
here
thanks
everyone
for
the
feedback
on
headspace,
it
looks
like
it's
been
useful
for
those
of
you
who
use
it
so
I'm
going
to
propose
that
we
keep
it
I.
Think
it's
a
nice
option
to
have
available
to
us.
Those
of
you
using
the
kudos
tap
you'll,
probably
have
noticed.
C
It's
been
a
bit
quiet
recently,
I've
been
making
allocations
less
infrequently,
because
gas
is
really
expensive
right
now,
so
you'll
get
some
kudos
SNT
soon,
I'll
add
some
this
week
and
I
will
distribute
a
higher
amount
than
normal
to
cover
a
few
weeks
in
one
go,
it
is
believe
it
or
not.
Q3
on
the
1st
of
July,
which
is
like
a
yeah
it's
so
the
gas
is
really
expensive.
I,
don't
even
know
why
that
is.
Does
anyone
know
it's
just
ridiculous
anyway?
C
Yeah
q3
SNT
payouts,
that's
1st
of
July,
so
you'll
get
a
letter
on
the
1st
of
July.
Basically,
with
your
wallet
address
asking
you
to
confirm
it.
So
take
a
look,
and
just
let
us
know
if
he
changes
a
few
people
have
been
asking
you
about
this
year's
off-site.
So
in
the
pre
Cova
days
we
were
going
to
plan
this
one
for
October.
However,
that
still
looks
quite
risky
and
not
super
likely
at
this
point
in
time.
C
So
it's
something
I'm
keeping
an
eye
on
and
as
soon
as
travel
is
safe
and
unrestricted
again,
we
can
definitely
revisit
it,
but
like
I,
just
wanted
to
manage
the
expectation
that
it's
just
not
looking
super
likely
for
this
year.
If
I
had
to
guess
I
know,
that's
really
disappointing
to
everyone
and
we
all
enjoy
hanging
out
and
playing
mafia
in
person.
So
I'm
really
sorry
about
that
folks,
but
yeah
I
am
keeping
an
eye
on
it.
C
So,
let's
see
and
last
point
here
is
feedback
round,
so
it's
been
a
while
since
we've
done
these
and
we're
kicking
one
off
this
week
with
the
design
team,
which
is
really
cool.
So
if
you'd
like
to
do
a
feedback
round
either
within
your
team
or
just
for
yourself
individually,
reach
out
I'm
happy
to
help
set
that
up
for
you
and
then
just
a
quick
look
here
at
our
pecan
score.
So
thanks
everyone
for
filling
these
in
I,
still
read
them.
Every
two
weeks
still
reply
to
all
your
comments.
C
So
that's
really
cool
and
really
interesting
for
me.
Even
if
you
don't
have
time
to
leave
comments,
even
the
scores
are
really
helpful
to
me
as
well.
So
thank
you
for
that,
and
just
just
actually
that
I
gather
this
information,
not
just
for
the
pops
team,
but
everyone
is
welcome
to
use
it
and
look
at
it.
So
if
you,
for
instance,
want
that
data
just
for
your
team,
let
me
know-
or
if
you
want
access
to
the
comments
they
can
also
help
you
with
that.
C
So,
on
the
left
hand,
side
here,
I,
don't
know
if
you
can
see
it,
but
I've
put
our
top
six
areas
where
we
score
the
highest
and
I
think
particularly
cool.
You
know
in
a
decentralized
organization
that
caring
rates
so
highly,
and
then
we
all
look
after
one
another,
which
is
very
nice
and
then,
on
the
right
hand,
side.
We
see
our
lowest
scoring
six
akr
areas
for
improvement,
so
for
this
week,
I
just
wanted
to
call
out
recognition
and
performance
as
the
ones
to
highlight
just
for
some
food
for
thought.
C
So
recognition
is
really
defined
as
like
whether
someone
feels
their
work
is
valued
by
the
organization
and
it's
strongly
linked
to
feedback
and
praise
they
receive,
and
then
performance
is
if
you
feel
that
your
peers
and
your
team
Reid
are
aware
of
your
contribution
to
a
degree
that
you
they
offer
constant
and
constructive
feedback.
So
I
think
these
in
part,
I'm,
hoping
to
solve
with
feedback
rounds
so
again
would
encourage
you
all
to
get
involved.
C
I
think
that's
a
nice
thing
to
do
to
kind
of
unearth
praise
and
look
at
where
we
can
help
people
grow.
Another
weaker
area
I
wanted
to
point
out
as
well
is
the
process
for
setting
strategy.
So
there
have
been
some
recent
discussions
about
how
we
make
decisions
and
how
best
we
can
be
inclusive
and
transparent
in
how
those
decisions
are
made
and
I.
Think
that
you
know
making
it
a
synchronous
as
possible
is
really
helpful.
C
C
D
Yeah
to
kick
things
off
over
the
last
week
or
weeks,
core
team
has
been
focusing
on
key
part
release
among
many
other
things,
but
we're
all
set
up
for
a
peak
art
release.
App
is
ready
to
go
as
well
as
numerous
fixes
for
a
release
that
we
call
a
fixes
release
like
a
dedicated
release
to
get
rid
of
some
technical
death.
That
should
also
go
into
like
a
separate
release
cut,
which
can
then
be
tested.
D
Better
work
experimenting
with
react,
native
used
for
a
desktop
application,
especially
for
the
fiddly
and
vladimir
did
a
lot
of
work
on
that,
and
I
could
have
sued
a
team
for
pushing
pushing
the
bar
as
to
what
could
be
could
be
done
there.
You
can
check
out
the
discuss
post
where
you
can
find
a
bundle
to
try
the
result
yourself.
D
Next,
at
chasing
a
crash
issue,
we've
been
having
an
issue
with
like
occasional
crashes,
on
some
devices
and
emulators.
It's
been
very
opaque,
but
you're
they
made
a
bit
of
a
breakthrough
there.
Last
Friday
I
believe
it
was
not
a
major
issue
because
it
didn't
come
up
often,
but
anything
that
we
don't
understand
seems
a
little
bit
risky.
So
we
we
definitely
wanted
to
dive
into
the
details
to
to
resolve
that
planned
releases
are
what's
coming
out
for
sure
key
cards
and
notifications.
D
I
know
a
lot
of
people
are
asking
about
it
and
waiting
for
it.
We're
getting
that
out
as
quickly
as
we
as
we
can,
but
fixes
coming
coming
right
after
that,
some
things
that
we
already
know
or
have
learned
in
the
meantime
after
I
already
cut
that
we
would
want
to
have
fixed
and
then
release.
1.5
is
very
much
images
they
are
coming,
and
now
we
have
a
question
on
that
later
as
well
mentions
and
we're
looking
into
an
emoji
emoji
reactions
to
the
death.
D
What's
next,
maybe
this
is
basically
to
reiterate,
as
I
also
stated
this
in
the
last
town
hall,
you
can
check
weekly
on
this
cuss
any
like
product
planning
update,
so
any
changes
to
these
releases
that
I
described
here,
but
in
like
at
a
very
high
level.
What
we
look
to
do
is
makes
that
as
like
a
normal
messaging
application,
because
that's
how
a
lot
of
people
get
invited
and
start
using
the
app.
D
If
people
have
used
the
app
and
are
like
seemingly
excited
about
it,
we
don't
want
them
to
like
never
never
open
the
app
just
because,
like
life
gets
in
the
way
and
they're
they're
not
reminded
of
having
status,
install
notifications
are
key
to
that
and
then
very
much
focus
and
priority
on
making
it
easier
and
more
appealing
to
join
status,
which
is
use
a
referral
program.
Hopefully,
you
can
share
more
about
that
soon,
as
well
as
group
chat.
D
Invites
then,
aside
from
that
there's
a
list
of
other
baseline
features
and
Rico
has
been
doing
fantastic
work
on
audio
messages.
So
thank
you
for
that.
Url
and
curling
sounds
disappearing
messages.
There's
a
lot
in
the
pipeline
that
the
team
is
discussing.
All
of
those
features
tend
to
need
a
detailed
specification
of
how
they
will
actually
be
implemented,
implemented
in
a
decentralized
and
private
manner,
so
they
do
take
time
they
are
coming
and
there
my
child
radar.
E
Cool
okay,
so
I
just
wanted
to
make
a
brief
explanation
of
how
notifications
are
working
on
Android
right
now,
it's
it's
similar
to
what
Esther
already
answered
last
Town
Hall
during
the
questions.
So
basically,
since
our
communication
protocol
has
no
central
servers
and
tries
to
hide
metadata
as
much
as
possible,
it's
pretty
hard
to,
or
even
it's
impossible
to
notify
about
anything
from
from
the
outside
of
your
device,
because
there
is
no
way
even
for
a
mail
server
to
know
if
a
message
is
actually
for
you
or
not
so
for
iOS.
E
The
current
idea
is
that
the
sender
of
a
message
would
willingly
send
a
an
extra
noted
message
through
whisper
to
a
notification
server
so
that
the
notification
can
be
sent
so
so
there
is
metadata
associated
with
that
in
the
case
of
Android.
There
is
absolutely
nothing
because
what
we
do
for
Android
is
to
start
a
service
on
the
device
that
basically
makes
the
app
runs
in
the
background
which
we
test
it
for
battery
consumption,
which
is
very
limited.
So
so
on
that
and
it's
fine,
and
that
means
that
Android
doesn't
have
push
notifications.
E
It
has
local
notifications
which,
which
means
that,
besides
what
well
it's
already
coming
out
and
coming
in
to
your
phone
in
terms
of
data
enabling
notifications
doesn't
add
anything,
it's
it's
it's
already.
It's
just
the
messages
that
you
already
received,
because
the
app
runs
in
the
background.
It's
able
to
notify
you
when
there
is
a
to
look
at
or
or
in
the
future,
we
can
extend
that
and
notify
you
about
more
than
just
one-to-one
messages,
but
also
maybe
wallet
events
or
or
mentions
all
that
kind
of
things.
E
F
So
I've
just
joined
status
and
I
was
asked
to
give
a
brief
introduction
to
what
I'm
going
to
be
doing
here
and
so
I'm
working
on
product
design,
architecture,
and
you
know
some
people
kind
of
ask.
Well
what
does
that
mean?
What
does
that
really
involve
so
that
it's
the
design
of
user
facing
functional
architecture?
Basically,
so
this
kind
of
distills
out
to
kind
of
requirements,
use
cases,
activity,
diagrams
low
fidelity,
mocks,
etc.
F
So,
in
my
first
week,
I've
already
discovered
that
a
lot
of
really
great
engineering
research
work
has
been
done.
That
opens
the
door
to
lots
of
new
user
interaction
possibilities.
So
part
of
my
job
is
to
take
kind
of
what
engineering
have
made
possible
and
from
this
distill
and
craft,
and
hopefully
intuitive
an
engaging
user
flows
and
experiences.
F
Yeah.
My
background
prior
to
this
I
used
to
work
at
Microsoft
before
that
I
was
at
canonical
working
on
the
bun
too,
and
I've
been
a
passionate
blockchain
enthusiast
for
many
years,
so
I'm
really
excited
to
actually
start
contributing
to
the
blockchain
space
as
well
as
watching
it
as
a
community
member.
A
G
Hey
there
are
things
so
yeah
folks,
I
want
to
give
you
a
quick
you
updated
on
what
has
been
happening
on
the
security
side
of
things,
we're
currently
screening
several
code
paths
that
could
potentially
expose
user
data
and
review
what
we
have
implemented
there.
We
do
that
in
an
effort
to
simplify
our
privacy.
Note
where
we
kinda
want
to
reflect
all
our
ongoing
efforts
to
avoid
data
and
and
the
ways
where
we
implement
the
data
economy.
G
Then
we
also
institutionalize
one
ability
handling.
The
idea
is
that
the
security
and
the
core
team
have
committed
to
a
time
to
fix
of
30
days,
which
is,
in
my
opinion,
a
quite
ambitious
goal.
30
days
were
kind
of
the
gold
standard
back
in
the
90s,
when
X
was
still
really
really
impatient
people.
The
first
impression
of
this
has
been
pretty
good.
G
We
have
seen
time
to
fix
us
from
three
hours
over
two
days
to
a
maximum
of
36
days,
for
one
very
subtle
bug,
yeah
and
that
particular
bug
is
also
life
and
one
major
social
network
where
we
can
informed
the
vendor
but
didn't
receive
a
response.
Yet
so
I
guess
we're
in
a
good
track.
Here
we
also
encoded
a
clear
incentive
for
everyone
and
every
contributor
to
increase
security
and
privacy
as
contributions
to
privacy
and
security
issues
will
be
rewarded
by
the
status
quo
program
by
default.
G
Basically,
so,
whenever
there
are,
someone
is
working
on
a
fix.
They
will
basically
have
a
direct
incentive
to
to
work
on
that
yeah.
Also,
we
received
a
bunch
of
reports
through
a
variety
of
side
channels,
which
is
cool
and
yeah.
When
I
use
the
occasion
to
encourage
the
community
to
review
our
code
base,
umpire
led
work,
we'll
play
with
it.
Try
it
out
yeah
and
reach
out
to
security
tips.
That'll
stop
him
in
case
you
find
something
or
identify
something
that
we
might
have
missed.
G
H
Hello,
so
we've
created
a
new
fleet
for
members
to
do
additional
research
into
the
PTP.
We
also
have
a
new
website
called
tutorials
that
stuff's
network.com
made
by
gene
hall,
which
is
it
will
be
kind
of
a
central
point
for
all
the
very
own
content
targeted
developers,
essentially
where
it's
on
some
analytics
to
the
key
card
site
and
that
in
advance
of
the
worldwide
two
key
card
lunch
and
in
terms
of
the
app
I've
improved
garbage
collection.
H
Vnx
in
cities,
react
there's
been
some
additional
error
handling
for
maven
resolution.
We've
moved
API
tokens
and
separated
them
in
CI,
so
we
use
different
tokens
for
dev
builds
for
it
to
end
build
and
release
builds,
which
should
give
us
more
clearer
idea
of
how
much
we
are
actually
using
in
Fura
in
comparison
to
just
development
purposes.
H
Wells
found
a
new
issue
with
knixwear
tags
that
you
used
to
add
dependencies
have
to
be
regular
attacks
rather
than
annotated
tags.
It's
actually
not
a
major
issue.
It
just
pops
up
here
in
there
from
time
to
time,
but
if
you're
make,
if
you're
working
on
dependency
for
status
react
just
make
a
normal
type,
not
another
annotated,
one
that
would
be
beneficial
to
all
of
us.
We
also
have
a
new
service
for
pinning
sticker
packs
to
ipfs.
H
It's
been
tested
on
on
a
tested,
but
when
we
get
a
new
a
new
park
on
for
maintenance,
I'm
going
to
verify
that
it
works
properly
for
formuoli
others,
because
we
don't
get
new
park
stuff
frequently,
which
is
a
shame
we
do
need
some
new
ones,
especially
some
pepper
ones.
I'll
be
great.
Some
security
improvements
for
Universal
links,
the
deep-linking
for
Android
and
iOS,
and
some
provements
for
against
the
protection
against
DDoS,
because
we've
been
having
some
scripted
is
attacking
us.
H
I
Thanks,
oh
yeah
next
slide
once
we've
gotten
some
good
coverage
over
the
past
couple
weeks,
Cory
sat
down
with
the
reporter
from
Forbes
and
there's
a
really
nice
write-up
about
what
we're
doing
both
you
know
at
the
product
level
and
you
know
from
principles
perspective.
So
you
better
read
if
you
haven't,
he
also
wrote
an
op-ed
around
open-source.
It
was
picked
up
in
e27
online
magazine,
which
is
great
so
kudos
to
Cory.
So
then
also
Simon
and
Alec
have
been
working
on
a
pilot
for
our
search
and
display.
I
Well,
we've
been
working
with
get
coin
on
the
latest
hackathon
we've
got
three
bounties
up
all
from
keycard
integrations
with
the
key
card
and
then
also
a
call
for
new
API,
our
SDKs
and
I
think
there's
already
like
13
people
who
are
contributing
to
our
projects,
which
is
fantastic
to
see
so
basically
keep
card
team
and
everyone
hoping
off
that
next
line
and
then
also
yeah,
so
key
card
launch.
That
should
be
going
live
tomorrow,
coordinating
with
journalists.
We've
got
some
really
good
coverage
lined
up,
so
I'm
really
excited
about
that.
Along
with
some.
I
I
I
So
it's
just
status
that
I
am
just
looking
at
specifically
Brazil,
which
is
the
second-highest
penetrate
second
highest
penetration
rates
in
the
world,
just
behind
the
US
for
Instagram,
so
we're
rolling
out
a
channel
there
and
that's
actually
going
live
today
and
that's
being
driven
by
Andy
and
Alex,
a
nice
book
there
and
then
finally,
we've
got.
We've
got
like
a
developer
activation
and
retention
idea
that
Robyn's
driving,
so
he's
got
a
discus
list
up
here.
I
We're
basically
going
to
be
creating
some
developer
challenges
that
explore
our
tech
stack
along
with
a
range
of
other
ideas
and
topics
and
I
see.
Barian
has
to
have
already
contributed
some
ideas
to
that.
So
if
anyone
has
any
other
ideas
for
little
developer
challenges,
that
Robyn
can
then
write
up,
put
some
trades
of
tutorials
and
then
it's
up
on
our
channels.
That'd
be
great
check
those
out
and
discuss
and
yeah.
That's
it
for
me.
J
So
so
you
know
key
card
is
here.
Finally,
it's
part
of
status,
V
1.4,
there's
gonna
be
released
this
week,
so
it's
pretty
huge
actually
because
there's
been
a
lot
of
work
and
I'm,
not
talking
only
about
the
work
that
we've
done
in
the
past
weeks
to
finalize
this
lounge,
but
this
work
I
started
was
some
more
than
two
years
ago,
so
this
is
huge
work.
J
Everyone
in
space
has
contributed
to
that.
So
I
already
believe
that's
an
important
milestone
for
all
of
us
and
yeah
really
really
happy
about
that
and
full
of
gratitude
for
all
the
work
that
everyone's
been
doing
so
huge
kudos
to
Rico
contributors
or
ambassadors
and,
of
course,
to
kick
our
team
so
yeah.
This
is
great
and
yeah.
I
also
wanted
to
mention
that
the
marketing
team
and
technical
writers
have
done
an
incredible
work.
The
past
week
for
this
lounge
we've
got
new
websites
for
the
tech
side
of
things
with
cada
tech
website.
J
We've
got
a
new
website
for
status
users.
Looking
for
what
to
understand
how
he
consecrates
with
status
and
there's
lots
and
lots
of
material,
that's
going
to
be
released
and
planned
for
the
coming
weeks
and
even
month
we
have
a
food
plan,
a
blog
post
for
several
weeks,
both
for
users
and
some
more
technical
stuff
for
developers.
There's
a
social
media
plan.
There's
a
press
release.
There
are
new
videos.
J
J
What
we
do,
countries
we
don't
deliver
are
not
delivered
because
of
the
kavita
yet
so
I
hope
this
will
get
better
and
better.
We
are
not
covering
a
lot
of
countries
that
are
small
or
medium
islands,
not
not
covering
lots
of
African
countries.
Still
there
are
several
South
American
countries
that
are
not
delivered
yet
and
there's
Australia
New
Zealand,
also
so
still
working
on
that,
but
I
guess
among
the
195
countries
in
the
world
that
exist
would
probably
be
the
river
well
2/3
of
them
yeah.
Can
you
go
to
the
next
one?
J
Please
other
updates,
apart
from
this
lounge,
so
we
are
continuing
to
work
on
status,
pay
our
payment
network
designed
to
work
with
key
card.
We
are
getting
help
from
the
little
teams
on
that.
We
had
a
very
interesting
workshop
on
this.
We
are
at
the
stage
where
we
are
gathering
the
functional
requirements.
I
mean.
J
Actually,
these
functional
requirements
have
been
gathered
and
we
are
listing
the
different
issues
and
trade-offs
that
we
are
going
to
need
to
to
decide
on,
and
the
next
big
step
is
gonna
be
to
decide
on
which
type
of
infrastructure
we
go
ahead
with
with
these
requirements
in
mind,
so
we
have
optimistic
roll-ups,
zero
knowledge,
proof,
products
and
state
channels,
and
there's
gonna
be
a
new
workshop
I
think
this
week,
maybe
early
week
after
that,
thing's
gonna
be
this
week.
So,
if
you're
interested
in
this
subject,
please
check
the
status
of
this
core
channel.
J
That's
listed
here.
Did
the
help
payment
network
and
I
also
wanted
to
mention,
but
Johnny
said
it.
We've
got
this
a
C'thun
going
on
protect
privacy
from
get
current
up
to
the
end
of
first
week
of
July
and
well.
We
had
three
projects.
Four
key
card,
I
mean
three
bounties
and
the
success
has
been
I
mean
really
huge.
J
Lots
of
interest
and
I
just
counted
them.
This
morning
there
are
22
projects,
22
hackers
that
submitted
the
project
and
said
that
they
started
so
they
all
are
I,
mean
they've
all
been
shipped
a
key
card
or
we
made
sure
they
had
a
key
card
and
I
mean
that's
great.
To
see
that
key
card
is,
is
raising
so
much
interest
and
some
a
different
type
of
application.
So
really
looking
forward
to
see
what
these
hackers
develop
and
that's
it
for
our
katana
blade.
A
J
So
Lutheran
is
a
zero
knowledge,
proof,
roll-up
protocol
and
infrastructure.
So,
as
just
said,
a
part
of
our
status
pay
effort
is
to
I
mean.
The
stage
we
are
at
now
is
to
choose
the
right
type
of
technology
we
want
to
use.
So
we
are
one
step
before
being
able
to
answer
precisely
this
question.
We
first
want
to
we
our
design
stage,
not
at
the
implementation
stage,
so
we
look
at
the
frame
as
other
technologies,
but
we're
not
at
that
stage.
Yet.
A
D
C
All
right,
yeah
flex,
great
question,
so
for
those
of
you
not
sure
this
is
about
this
from
the
outset
of
the
project,
we
locked
away
29%
of
all
s
NT
minted
into
a
reserved
with
the
intention
of
keeping
that
aside.
So
really
there's
nothing
to
report
on
this.
Indeed,
that
whole
twenty-nine
percent
is
still
locked
away
in
a
multi-sig.
We
don't
have
any
plans
finalized
yet
for
what
to
do
with
it.
A
D
I'm,
hoping
I
understand
the
question
correctly,
so
please
ping
instead
of
mystic
sellers
or
support.
If,
if
you
have
further
questions
image
port
is
coming
and
release
1.5
so
think,
mid-july,
its
words
and
and
July
most
of
the
work
there
is
done.
The
weight
is
on
the
fact
that
we
do
not
want
to
release
without
thorough
into
and
and
manual
testing
of,
of
an
application
that
we
put
into
release
so
there's
always
a
gap
between
when
window
feature
is
delivered
and
when
we
actually
bring
it
in
into
production
or
release
it
into
production.
D
That's
images
in
chat,
video,
audio
versions,
I'm,
not
100%,
sure
what
is
meant
there.
There
is
an
issue
on
audio
messages,
which
is
kind
of
like
a
tap
to
hold.
Your
microphone
and
you'd
speak
into
the
microphone
to
record
a
message
and
sent
that
that
is
something
that's
actively
being
works
on
video
audio
in
terms
of
video
conference,
calling
that's
not
something
that's
planned
for
it
in
the
near
near
term.
I.
A
Have
question
for
bi,
which
has
been
presented
by
poor,
majestic
Iceland
goal,
and
this
is
about
embeddable
support
chat,
so
back
in
early
2019
stages
had
build
week,
I
believe
Richard
and
URI
came
up
with
the
embeddable
support
chat,
which
enabled
people
to
embed
a
status
chat
into
their
website
with
it
and
was
only
four
lines
of
code
to
implement
using
the
existing
libraries
with
notifications
coming
in
next
status.
Release
would
embeddable
chant,
be
a
nice
feature
again
to
complement
status
notifications
so
URI?
Would
you
be
able
to
answer
this
one?
Yes,.
K
So
so
the
question:
would
it
be
nice?
The
answer
is
yes,
but
to
put
more
context
into
this
this,
this
a
embeddable
support,
shot,
is
based
or
relies
on,
murmur
and
and
murmur.
Currently,
it
needs
a
lot
of
updates,
because
a
lot
has
changed.
Insiders
there's
been
a
lot
of
developments
and
advances
and
in
status
in
their
in
their
protocol.
K
So
memory
needs
to
be
updated
to
reflect
all
that
and
that-
and
that
takes
some
considerable
work
and
currently
are
our
priorities,
lie
elsewhere,
lying
in
a
shipping
and
desktop
and
chat
line,
continue
to
improve
the
mobile
client
and
to
implement
you
know
other
things
like
Waku
and
other
other
protocols
to
continue
to
improve
status.
So
it
is
a
priority.
It's
just
not
a
big
priority,
maybe
at
some
point
we
could
work
on
it
again.
K
A
C
It's
a
good
question,
so
I'm
gonna
say
that
we
feel
the
development
team
is
sufficiently
staffed
right
to
cover
the
volume
of
works
that
we
have
like,
particularly
now
that
we've
got
embark
team
working
on
desktop
alongside
the
core
team
working
on
the
mobile
app
and
just
in
general.
I'd
always
be
wary
of
just
like
adding
more
people
to
speed
up
development,
like
we've
all
heard
of
the
mythical
man-month
and
how
your
coordination
tax
goes
up.
C
When
you
add
people,
so
it
doesn't
necessarily
just
linearly
add
more
production
capacity
to
the
team,
so
yeah
I
think
that
the
team
size
is
right.
As
for
working
weekends,
you
know
everyone
needs
a
break.
I
had
a
figure
to
anyone
that
so
cool
with
that.
But
no
we
hear
you
and
we
also
want
this
thing
to
move
along
with
some
momentum
as
well
right.
So
very
much
like
a
lot
of
our
planning
is
around
looking
at
what
our
processes
are
and
how
to
make
those
more
efficient.