►
From YouTube: Status Town Hall - May 21st, 2018
Description
General
2:19 - Welcome
2:41 - Status organizational catalysts - Jarrad H.
26:45 - Core contributors / Hiring
27:45 - Marketing update
Core Swarms
36:57 - Beta update
42:12 - Core goal: Beta
Infra & Tooling
43:22 - Infrastructure update
44:19 - #167-extended-automated-testing
46:58 - #92-discovery-v5-research
48:08 - #58-mainnet
Mobile App
49:48 - #84-energy-effecient
54:07 - #142-wallet-compatibility
54:58 - #170-wallet-improvements
DApps & Developers
57:22 - #154-support-web3
58:32 - #101-extensions
59:34 - Swarm summit conf.
1:07:04 - #67-nimbus
Desktop
1:11:05 - #034-react-native-qt
1:12:00 - #desktop
Q&A
1:14:33 - Questions and Answers
Slides: https://docs.google.com/presentation/d/16Buex63S_mPd_9haiS05lqr2vdIpSrtr9gNi_lK4ayA/edit?usp=sharing
- Bi-Weekly Town Hall livestream
- Q&A Sessions will be held at the end of each livestream if you missed out and would like to ask any questions about the content please leave a comment!
- This week we heard a very inspiring talk from Jarrad about Status' catalysts, updates on beta, desktop and more!
Any other questions please leave a comment or join our chat - https://chat.status.im
A
A
A
B
C
D
E
Why
the?
Why
they're
important?
Why
it's
important
to
set
us
and
throw
out
some
ideas
there
and
if
they're
interesting
to
you,
I'd
love
to
talk
to
you,
and
maybe
we
can
work
together
to
make
this
division
come
come
to
life,
and
it's
really
about
the
sort
of
mentality
of
decentralization
that
we
need
the
people
who
want
to
join
on
and
participate
in,
but
they're,
not
just
my
my
ideas.
E
These
are
ideas
that
very
prominent
people
and
many
other
people
have
been
looking
at
and
researching
so
I
try
to
compile
a
list
of
books
which
will
be
at
the
end
for
you
to
peruse
and
we're
happy
to
get
them
for
you
if
you're
not
give
them
a
read.
But
if
you
had
to
read
one
of
them,
I
think
one
of
them
is
great.
To
start
with
is
the
the
starfish
and
the
spider,
and
the
analogy
is
essentially
between
centralized
organizations
versus
decentralized
organizations
and
why
face
value
they
often
appear
to
look
the
same.
E
E
But
then,
if
you
cut
off
the
head,
the
entire
thing
stops
working,
whereas
if
you
have
a
starfish,
if
you
cut
it
in
half
all
of
a
sudden,
you
have
two
starfish
to
deal
with
and
that's
largely
because
a
lot
of
its
core
organize
organize
our
organism
and,
of
course,
we're
an
organization,
not
an
animal.
Having
that
said,
organizations
are
something
like
a
super
organism
made
up
of
humans,
so
that's
kind
of
the
sort
of
underlying
analogy
there.
I
I
am
recruiting
status
catalysts.
E
E
F
E
I
certainly
looks
like
it's
the
sort
of
technology
to
do
this
sort
of
stuff,
but
with
this
it
does
come
with
a
shift
in
mindset
or
in
thinking,
and
that's
really
about
this
network
thinking,
whereas
no
longer
the
value
is,
is
entirely
within
the
product
and
then
you're
giving
us
to
users,
but
instead
it's
in
within
the
social
relationships
that
we
form
around
it.
So
you
can
imagine
status.
E
The
software
is
actually
more
an
expression
or
a
catalyst
of
this
mission
that
were
all
wrong
on
together,
but
the
real
value
lies
in
our
relationships
with
each
other
and
with
the
greater
greater
people
around
this
who
are
also
participating
in
aetherium,
for
example,
the
ethereum
network
had
actually
given
rise
to
the
status
network
without
ethereum
we
wouldn't
exist
and
without
Bitcoin
a
very
improbably
wouldn't
exist
either.
So,
there's
all
these
sort
of
internal
organizational
communities
out
there,
and
that
is
where
the
real
value
really
lies.
E
So
it's
great
to
take
our
expertise
and
how
we
create
these
products.
We
certainly
need
to
learn
how
to
enhance
that
to
start
include
being
more
inclusive
and
bringing
more
people
in
next
slide,
yeah
and
so
like.
If
you
have
to
remember
just
one
thing
out
of
all
of
this,
it's
it's
a
simple
matter
of
changing.
One
word:
instead
of
building
false
are
building
for
somebody
you're
building
with
them.
Everyone
we
interact
with.
We
talk
to
is
a
potential
contributor
to
status.
It's
not
like.
They
are
just
a
user
of
status
or
S&T
holder.
E
Our
job
is
really
to
take
these
S&T
holders
and
bring
them
all
the
way
to
being
active
contributors,
and
this
isn't
just
within
software.
This
can
be
within
marketing,
but
in
design
with
evangelism
anywhere
we
can
get
an
extra
spare
our
hands
to
be
involved.
We
can
strengthen
the
network,
we
can
strengthen
aetherium
Network
and
we
can
all
rise
together.
E
And
it
looks
like
like
I
said:
some
of
this
may
not
be
apparent
to
many
of
the
contributors
that
have
come
on
board
recently,
since
we
have
grown
so
quickly,
but
there's
been
a
couple
of
other
events
along
the
way
that
I
think
is
worth
sharing
with
you
just
so.
You
know
a
lot
of
these
decentralized
organization.
Ideas
were
were
there
from
day
one.
E
E
Unfortunately,
our
community
wasn't
big
enough
to
and
handle
that
amount
of
interest,
and
it
got
somewhat
diluted
during
that
process
and
because
it
goes
so
large,
we
ended
up
attracting
a
lunch
of
scammers
and
fishers,
and
this
sort
of
thing
there
was
no
moderation
tools
in
slack,
so
so
any
remnants
of
that
kind
of
got
blown
away,
and
then
the
community
got
somewhat
splits.
We
put
everyone
into
it
to
riot
and
we
built
up
essentially
a
bit
of
a
wall
with
slack.
E
Unfortunately,
this
is
something
we
need
to
get
away
from
in
the
future,
but
it
was
certainly
necessary
at
that
time
just
to
find
some
semblance
of
sanity,
and
this
is
very
different
from
the
sort
of
some
of
the
conversations
that
we
see
today.
You
know
like
we
have
a
little
consumer
based
or
investor
base
conversations
and
and
they're
valid
people,
but
we
need
to
figure
out
how
we
can.
We
can
take
them
from
that
that
point
in
mindset
and
how
we
can
actually
to
be
a
participant
in
in
in
what
we're
doing.
E
E
So
this
might
all
sound
like
great
ideas,
you
know,
but
maybe
they're
a
little
too
pie-in-the-sky.
Maybe
you
don't
see
the
actual
relevance
so
how
to
bring
this
back
to
reality
and
I.
Think
that's
a
perfectly
valid
position
to
take.
It
is
very,
very
hard
to
look
at
these
sort
of
organizational
designs
and
see
how
the
different
or
how
things
could
be
done
in
a
different
way,
particularly
when
you
we
already
have
a
certain
worldview
and
we've
been
working
in
a
particular
fashion.
E
E
Things
like
our
program
or
public
watch,
James
perfectly
suited
for
hostile
environments,
and
what
do
I
mean
by
that?
Well
I
mean
the
the
independent
activists
of
Catalan,
for
example,
are
facing
the
Spanish
states
and
they
need
a
means
of
creating
a
new
society
on
top
of
a
blockchain.
Are
they
need
a
means
of
communicating
with
each
other,
then
in
a
separate
mesh
network,
separate
infrastructure,
and
they
need
applications
that
actually
connect
to
peer
to
peer,
so
they
can't
be
unencumbered
or
they
can't
be
overruled.
E
Some
other
interest
has
come
from
Rajavi,
which
is
a
democratic,
so
it
was
a
democratic
Confederacy
out
in
Syria
and
they
have
the
same
issue
in
fact
they're
getting
bombed
by
Turkey
right
now
and
of
course
these
are
extreme
examples,
but
what
they
do
bring
up
is
how
it
does
bring
up
the
question
on
how
status
as
legal
entities
could
potentially
be
attacked.
Just
recently,
I
think
it
was
like
two
or
three
weeks
ago.
E
Maybe
even
a
month
ago,
we
saw
the
attack
on
on
telegram,
and
that
was
largely
on
the
the
underlying
infrastructure,
because
that's
easy
and
cheap
to
attack
us
being
a
peer-to-peer
application.
We
raise
those
costs
to
do
that
substantially,
and
so
another
attack
vector
is
the
bootstrap
legal
entity
that
we're
currently
working
with
that
could
be
taken
down
and
we
need
the
status
organization
to
be
able
to
survive.
It's
legal
entities
being
attacked
and
for
this
software
to
continue
and.
E
This
brings
up
this
idea
of
the
decentralized
autonomous
organization
now
or
in
short,
a
dhow.
Now,
what
is
it
doubt?
Well,
a
dhow
is
essentially
a
set
of
smart
contracts
that
are
on
top
of
a
program
or
block
chain
like
ethereum
that'll.
Allow
us
to
socially
coordinate
we're
talking
about
things
like
voting
systems,
new
ways
of
allocating
funds
and
doing
governance
in
general,
and
ultimately
this
is
our
goal.
E
We
want
to
ascend
into
the
blockchain
essentially
and
dissolve
any
aspect
of
legal
entities
that,
except
for
what's
the
bare
minimum,
and
this
will
actually
allow
us
to
do
something
that
hasn't
really
been
able
to
be
done
before,
but
something
like
what's
called
like
a
hybrid
organization,
and
this
is
also
in
the
starfish
and
severe
spider,
where
we
try
and
take
some
of
the
efficiencies
of
the
centralized
organization,
while
also
maintaining
a
large
decentralized
aspect
of
it.
And
so
this
is
one
of
the
the
core
reasons
and
I
hope.
That's
pretty
clear.
Yeah.
E
The
other
one
is
open:
source
is
actually
our
ultimate
competitive
advantage
and
I.
Don't
think,
there's
actually
many
open
source
projects
that
really
this
it
it's
not
about
putting
your
code
out
there
and
letting
it
being
publicly
viewed
on
its
own
I
think
this
is
a
great
first
step,
but
there's
so
much
more
to
that.
We
can
actually
be
building
a
community
around
open
source
software
that
actually
has
the
end
goal
to
build
it
out.
They,
it's
there's
a
certain
level
of
trust
that
you
get
just
by
putting
it
out
in
open
source.
E
It's
a
whole
other
level
to
start
actually
cultivating
people
to
come
around
and
actually
work
on
it
around
those.
We
can
actually
take
this
a
step
further,
where
it's
not
just
about
working
on
the
code
or
itself
on
the
client
itself,
but
we
actually
can
open
source
all
the
things
we
can
open
source.
The
way
we
do
marketing,
we
can
do
the
design-
and
these
are
very
new
concepts-
I,
don't
think,
there's
any
real
sort
of
models
or
templates
that
we
can
really
borrow
from.
E
So
we
have
to
do
some
experimenting
here,
because
if
we
do
this,
then
we
build
the
strongest
community.
We
build
the
strongest
decentralized
organization,
the
strongest
social
network,
around
status
status
no
longer
becomes
the
software,
it
becomes
this
network
and,
more
importantly,
you
get
very
impassioned
people
doing
this.
When
you
start
moving
this
idea
to
to
the
people
in
the
relationships
that
are
around
you
I
find
and
you
give
them
a
mission
or
give
them
all
they
see
some
meaning
in
in
the
work
themselves.
Then
you
can
be
self-directed,
you
can
have
a
purpose.
E
So
this
is
directly
lifted
from
the
book.
I
think
you
can
find
it
in
the
starfish
and
spider
wiki
wiki
pedia
summary.
But
these
are
some
of
the
trace
of
catalyst.
You
know
you
have
some
genuine
interest
in
others.
You
firm
your
form
lots
of
loose
connections
rather
than
a
small
number
of
close
connections.
E
This
allows
you
to
distribute
your
influence
throughout
the
network
having
more
skill
with
social
mapping,
I
desire
a
genuine
desire
to
actually
help
people
that
you
meet
and
then
also
becoming
somewhat
of
a
leader,
giving
people
the
tools
to
not
only
help
themselves
but
also
help
other
people
there's
our
emotional
intelligence.
This
trust
in
others,
obviously
inspiration
tolerance
for
ambiguity.
I
think
this
is
kind
of
important.
Sometimes
what
we
do
have
to
let
go
a
little
bit
and
that's
some
somewhat
scary.
E
Sometimes,
of
course,
this
is
balanced
against
again
trying
to
to
reach
certain
goals
that
we've
set
for
ourselves
as
long
as
we
see
them
to
set
them
together
and
it's
been
a
joint
or
by
consensus
and
that's
a
very
important
distinction,
even
though
it's
kind
of
subtle,
yeah
and
Sam
again
having
this
hands-off
approach
and
ability
to
get,
let
go
they're
all
kind
of
personal
at
those
last
three,
and
these
are
ten
rules
that
the
book
outlines
for
the
organization.
This
idea
of
just
diseconomy
is
a
scale.
E
You
actually
don't
need
too
many
people
in
the
core
in
the
core
organization.
You
need
a
bit
of
structure,
but
really
they
they
are
called
coordinators
or
connectors
and
they're,
bringing
people
together
so
you're
kind
of
externalizing,
a
lot
of
processes
and
you're
trying
to
embed
a
lot
of
what
we're
doing
in
the
people
around
you
and
they
might
not
necessarily
be
considered
core
contributors,
even
though
they're
very
much
part
of
status,
you're,
building
up
the
network
effects.
This
is
incredibly
powerful
and
it's
even
more
so
good.
E
We
have
a
token
we
can
actually
tokenize
our
network
and
I.
Don't
think
any
of
us
have
really
seen
this.
We
saw
a
glimpse
of
this
when
we
had
the
status
Genesis
tokens
we're
giving
this
out.
It
was
absolutely
phenomenal
to
see-
and
it's
exactly
what
took
us
from
3,000
contributors
or
community
members
to
16,000
people,
and
when
you
see
this,
it's
going
to
be
mind-blowing.
I,
really
can't
wait
to
show
it
to
you.
I
got
this
power
of
chaos.
We
need
to
learn
how
to
thrive
in
this
sort
of
somewhat
drunken
style
of
organization.
E
It's
somewhat
unorganized
to
to
delay
I,
but
there
is
actually
some
structure
underneath
it.
The
knowledge
is
in
the
edge,
you
know
like
the
people
who
are
developing
the
people
who
are
working
doing
the
marketing
they're,
the
ones
who
know
these
sort
of
things.
They
actually
have
a
lot
of
ideas
and
that
they
understand
things
that,
if
you
have
some
hierarchies
and
managers,
they
might
actually
be
just
divorced
from
the
front
lines,
so
they
don't
necessarily
have
all
the
knowledge
it's
important
to
realize
this
and
then
take
advantage
of
it.
E
Now
this
realize
that
everyone,
if
you
can,
if
you
can
build
a
structure
out
like
this
and
you
can
build
a
way
of
bringing
people
into
it,
you'll
find
that
people
actually
want
to
contribute.
Now
there
might
not
be
the
best
people,
but
the
fact
that
you
can
the
fact
that
they
can
that's
Commission
list
and
trustless
to
do,
and
we
give
them
the
tools
to
do
that.
It's
ten
times,
if
not
a
hundred
times
better
than
just
having
a
loyal
customer.
This
is
a
this
is
a
real
evangelist.
This
is
a
real
believer.
E
It's
it
they're,
essentially
activist
again
this
this
Hydra
response,
something
like
a
starfish.
If
we're
attacked
the
organization
can
perpetuate
itself,
because
it's
now
multiple
different
cells
or
groups
of
people
achieving
the
same
goal,
even
though
the
central
entity
has
been
removed,
we
need
to
inspire
people
to
action.
We
need
to
inspire
people
to
work
on
the
organization.
E
The
the
really
the
binding
force
of
the
glue
are
our
values
and
our
ideology
now
hasn't
really
been
set
in
stone.
You
know,
Johnny
Steph
Ali
are
all
working
together
to
make
this
happen.
They're
doing
a
fantastic
job
and
I'll
talk
a
little
bit
about
that
in
a
moment.
The
other
thing
is
measuring
and
monitoring
and
managing
it,
and
this
is
what
Newbill
does
a
great
job
of
it
and
is
working
on
as
well
is
how
come
particularly
with
the
ok
house
is.
E
Anyway,
that's
it
for
me
again,
like
I,
mean,
if
becoming
a
catalyst
or
working
on
this
sort
of
stuff
interests.
You
please
message
me
we're
gonna,
do
training
on
this
we're
gonna,
we're
gonna,
build
this
out
and
treat
this
really
seriously
we're
going
to
be
working
towards
this
decentralized
autonomous
organization.
In
fact,
status,
open
bounty
was
kind
of
like
a
precursor
or
playing
this
on
paper,
and
all
of
these
books
here,
I
think,
will
give
you
a
really
good
idea
of
where
I'm
coming
from
or
where
these
ideas
rely,
and
they
can
articulate
it
way.
E
Better.
I
can
but
definitely
start
with
the
starfish
and
the
spider,
and
the
very
foundation
is
actually
pushing
that
radical
markets
book
as
well.
I
actually
had
a
chance
to
read
that
yet
to
its
entirety,
but
definitely
give
them
those
two
at
least
a
check
out
and
we'll
definitely
get
them
for
you.
That's
it
from
me.
Thanks.
D
G
D
Okay,
all
right
we'll
leave
QA
as
well
at
the
end,
but
just
in
case
people
have
further
thoughts.
At
least
it's
super
interesting
to
hear
that
and
to
think
about
what
it
was
like
at
day.
One
back
when
there
was
you
know,
seven
people
and
a
huge
community
of
world
engaging
so
I
think
and
every
single.
E
D
E
D
In
the
past
two
weeks,
you've
had
three
people
who
joined
us
as
core
contributors
on
the
team
and
Shawn
who's
heading
up.
Our
engagement
work
he'll
be
spending
a
lot
of
time.
Thinking
about
this
evangelism
part
and
helping
to
engage
the
community
further.
We
have
Barry
who's,
a
smart
contract,
developer
who's
joined
us
recently
and
Kerry
who's
First
Aiders.
H
Yes,
so
there's
a
lot
going
on
right
now,
one
of
the
major
the
main
things
were
working
on
is
the
state
of
us
campaign
really
designed
to
encourage
active
participation,
so
we're
working
closely
with
Chad
and
everyone
from
the
product
teams
to
just
effectively
communicate
the
state
of
the
product
and
how
we
can
you
know,
encourage
people
to
get
in
and
test
and
use
it
as
much
as
possible
we're
using
the
the
brand
platform
state
of
us.
It
really
has
an
all-encompassing
campaign
platform.
H
Just
to
really
you
know,
encourage
people
to
get
out
and
become
part
of
this
community
that
we're
building
some
of
the
activations.
Some
of
the
initiatives
were
we're
launching,
as
part
of
us,
is
a
podcast
series.
Andy's
recorded
a
couple
and
those
are
coming
out
really
nice
we're
working
on
a
60-second
video,
really
inspirational
piece
explaining
what
we're
doing
and
how
people
can
get
involved
and
a
lot
of
information,
so
we're
creating
an
infographic
on
how
to
contribute.
H
H
Hutch
is
planning
out
another
community
competition
and
then
a
series
of
competitions,
so
so
stay
tuned
for
those
they're
really
exciting
and
then
finally,
onboarding
flows
via
email
and
via
social.
So
you
know
where
people
know
exactly
how
to
use
the
product
and
they
can
get
involved
and
ask
questions
effectively
and
then
finally,
we'll
be
running
a
paid
pilot
in
the
background
and
then
so
we
had
a
excuse
me.
H
We
had
a
marketing
summit,
a
small
marketing
summit
in
New,
York,
Sean
and
Ally
came
to
New
York
to
plan
out
the
next
few
months
and
really
what
what
we
noticed
was
and
tying
back
into
what
Jared
was
just
speaking
about
is
how
can
we
effectively
open
this
up
and
open
up
the
process
for
campaign
creation,
community
involvement
and
essentially
evangelism?
So
we
came
up
with
a
few
things.
One
of
them
is
a
campaign
tearing
system,
a
tier
1
at
tier
2
and
a
tier
3
where
we
can
identify
the
the
livers.
H
We
can
pull
the
resources
we
need
and
how
to
engage
the
community
in
each
one
of
those
campaigns.
So
we're
documenting
that
now
so
stay
tuned
for
a
document
on
that,
so
you
can
see
exactly
what
happened
and
the
other
thing
we
did
was
we
identified
some
some
quote
unquote
play
books
that
we
can
use
as
tools
to
to
try
and
open
this
up
to
everyone.
So
anyone
can
get
involved
right,
so
we
can
document
how
to
host
an
event.
So
it
doesn't.
H
You
know
there
is
no
single
point
of
failure,
a
central
point
of
contact
that
has
to
organize
that
anyone
essentially
can
do
it
a
community
event
toolkit
so
making
assets,
resources,
information
available
to
anyone
and
then
the
same
thing
for
Tech
Talks.
So
we've
had
this
really
awesome
series
of
technical
conversations,
but
right
now,
just
to
you
know,
get
the
ball
rolling.
There's
been,
you
know
one
or
two
people
that
have
been
organizing
it.
We
want
to
open
this
up
so
we're
putting
together
a
playbook.
H
So
we're
documenting
this
at
stay
tuned
for
that
moving
over
there's
a
ton
of
content
in
the
works,
which
is
great,
we've
got
a
series
of
tech
talks
on
drea
Yegor
Jared
have
given
great
ones.
Frank
will
be
speaking.
This
Friday
and
Alex
is
working
with
us
to
write
out
blog
posts
to
accompany
those
which
is
fantastic
and
he's
writing
a
series
of
more
inspirational.
Why
decentralization
content
to
appeal
to
everyone?
H
So
we're
currently
performing
a
site
audit
we're
going
to
be
putting
together
a
site
map
and
some
wireframes
just
because
the
website
at
this
point
has
grown
into
something
bigger
than
I.
Think
we
all
expected
it
to
with
the
inclusion
of
projects
Andres
design
site,
which
is
great,
so
we
just
want
to
basically
clean
it
up
and
make
it
much
more
approachable
for
everyone.
H
Finally,
there's
a
ton
of
events
going
on,
which
is
great,
Beth
point
Osiris.
The
hackathon
in
BA
is
happening
this
weekend,
so
Eduardo,
Andy,
Richard,
Ricardo
and
I.
Think
that's
it
we'll
all
be
in
Buenos
Aires.
Working
with
up
to
you
know,
500
developers
down
there,
yosik
has
been
organizing
an
athenian,
clean
up,
client
Meetup
stay
tuned
for
more
details
on
that.
It's
a
really
exciting
initiative:
F
Berlin,
it's
happening,
September
7th,
so
we'll
be
involved
in
that
one
and
we're
looking
to
really
have
a
strong
presence
there.
H
The
the
details
around
are
the
details
around
that
are
still
being
finalized,
but
it's
really
exciting
and
hopefully,
as
many
of
us
can
be
involved
in
a
many
as
many
of
the
community
community
members
can
be
involved,
so
so
stay
tuned
and
then
finally,
Def
Con
is
end
of
October
early
November
and
we'll
definitely
be
there.
So
stay
tuned
for
details
on
that
one
as
well.
Once
again,
this
is
all
early
early
days
and
then
finally,
an
update
on
the
status
projects
working
with
URI
and
his
team.
H
H
The
naming
is
still
TBD,
but
we're
putting
together
requirements
documents
for
that
now
and
we'll
be
working
with
Jared
and
team
and
really
would
love
feedback
from
everyone
on
how
we
can
really
kick
this
off
just
need
to
identify
the
the
initial
requirements,
and
that
is
an
initiative
to
really
encourage
development
and
promotion
of
the
decentralized
ecosystem
through
that
development
through
pretty
much
anything.
We
want
to
essentially
recreate
these
very
centralized
services
using
a
theme
so
so
stay
tuned
for
more
details
on
that.
It's
going
to
be
really
exciting.
H
So
we
hit
a
hundred
thousand
Twitter
followers.
We
typically
don't
we're,
not
one
for
for
vanity
metrics,
and
this
is
a
vanity
metric,
but
I
just
wanted
to
call
this
out,
because
it
is
a
pretty
big
milestone
and
it
shows
the
growth
that
we've
seen
over
the
course
of
the
past
few
months,
and
you
know
it's
it's
an
just
want
to
say
this
is
from
the
work
that
everyone
does.
You
know
from
the
Status
core
contributors
to
the
community
members
thanks
to
everyone.
H
We
have
seen
a
shift
to
towards
that
more
I
guess
you
know
kind
of
like
the
early
days
that
jared
was
talking
about
where
people
were
genuinely
interested
in
the
project
and
wanted
to
get
involved,
and
you
know
so
thanks
to
everyone
who's
in
riot
and
is
kind
of
making
a
shift
back
towards
that
mentality
and
we'll
be
working
with
everyone
to
really
foster
that
and
encourage
active
contribution.
So
so,
thanks
to
everyone
thanks.
D
Jenny,
oh
thanks,
all
right
we're
mid
mid-may,
so
we
are
halfway
through
q2,
ok
hours,
there's
been
a
lot
of
progress
on
some
of
our
core
okrs,
specifically
around
messaging
reliability.
So
it's
really
awesome
to
see
I
don't
want
to
go
into
too
much
detail.
So,
if
people,
if
teams
specifically
want
to
jump
in
and
measure
how
they've
gone
so
far
in
in
q2
go
ahead
and
do
it
create
like
a
meter,
okay
or
a
check-in,
and
then
about
a
month's
time,
we'll
start
and
see
what
q3
looks
like.
D
I
Cool,
so
I
just
want
to
talk
briefly
about
a
better.
So
far,
it's
really
cool
to
see
everyone
coming
together.
These
last
few
weeks
and
really
focusing
on
the
critical
path
and
I
think
we've
seen
a
kind
of
a
big
difference
in
mindset
and
everyone
working
toward
the
same
goal
instead
of
thinking
in
terms
of
their
swarms
being
pre,
better
or
post
better.
I
To
do
this,
we
have
had
to
do
some
trade
offs,
some
concessions,
so
our
nodes
are
still
single
point
of
failure.
If
a
cluster
goes
down
uses
contractor,
we
still
lack
proper
incentive
mechanisms
around
identity,
spam
management,
we're
still
hosting
all
the
mail
server
ourselves.
We
have
seen
partial
team
civilization.
We
don't
have
performed
secrecy.
We
don't
support
group
chat,
we
don't
use
on
device
node
by
default.
I
We
still
have
issues
with
performance
and
so
on,
but
all
that
said
it's
important
to
remember
avaricious,
a
stepping
stone,
an
anchor
this
quote
by
program
on
shipping
software
and
sort
of
highlight
the
importance
of
getting
something
in
front
of
users
that
it
can
actually
use.
In
this
case,
this
means
having
a
version
of
the
app
where
our
users
can
transact
on
main
it,
because
it
will
tell
us
a
lot
once
they
have
actually
real
users
who
use
it
on
a
daily
basis
and
inform
what
we
built
and
next
slide.
Please.
I
So
one
of
the
challenges
with
drumming
sort
of
distributed
organization
is
that
this
little
implicit
context
and
as
Jared
mentioned
a
lot
of
the
context
from
decisions
are
sort
of
at
the
edges.
So
to
help
with
this
trying
to
document
decisions-
and
this
is
something
called
honor-
textured
decision
records
and
ideas,
essentially
that
you
capture
the
context,
decision
and
consequences
and
in
our
case
we're
capturing
it
in
the
state
public
get
repository.
I
So
it's
a
form
of
open
decision,
that's
part
of
the
public
record
and
it
helps
to
spread
knowledge,
and
you
can
refer
back
to
it
later.
So
some
examples
of
things,
decisions
that
we
made
and
documented
for
the
better
one
is
rounds
of
the
DEF
node.
We
are
relying
on
upstream
for
better,
but
you
can
enable
a
custom
one
if
you're
on
your
own
off
to
the
better,
we'll
work
towards
getting,
you
know,
see
MEP,
that's
an
option
to
up
as
soon
as
possible
and
possibly
also
work
on
improving
less.
I
At
the
same
time,
we
disabling
group
Chet
for
a
better
and
simply
it's
simply
too
buggy
right
now,
and
instead
of
focusing
on
one-on-one
and
public
chat,
we're
using
a
new
discovery
version
five
protocol,
which
allows
us
to
discover
new
peers
from
that
and
also
scale
peers
in
the
cluster
independently
and
we've
seen
some
really
cool
stuff
with
world
compatibility
as
we're
changing
a
change,
the
key
generation
to
be
compatible
with
other
bullets.
So
if
you
have
a
wallet
in
meta
mask,
you
can
use
it
status.
I
I
How
can
we
encourage
uses
as
stakeholders
and
a
thriving
ecosystem
of
contributors
and
some
example
of
litmus
tests
in
Oscar
Schultz?
So
if
all
our
service
disappear
tomorrow,
how
could
status
still
operate?
What
about,
if
all
all
Jupiter's
here
we
disappeared,
Constanta
still
operate
after
a
user's
point
of
view,
would
Snowden
or
a
future
whistle
blow
yourselves?
Why
or
why?
Not?
I
I
J
I'll
just
give
a
quick
update
on
the
dates
here,
and
so
our
goal
for
this
week
is
to
release
version.
Point
nine
point:
one
nine.
We
had
tried
to
release
last
week
but
ran
into
a
few
blockers.
We
seem
to
be
on
target
for
this
week
and
that
is
to
include
the
much-anticipated
option
of
main
net
because
of
the
timing
and
the
fact
that
it
is
now
the
end
of
May
point
nine
point:
one
nine
will
also
be
tested
for
beta
Candidate.
J
I
It's
alright
I,
give
a
brief
one,
so
we've
seen
so
what
we're
doing
is
essentially
rebuilding
our
custard.
This
has
been
a
bit
janky,
so
essentially
the
goals
are
on
high
availability
and
being
able
to
do
dynamic,
Skype
scaling
and
also
making
sure
we
have
sort
of
monitoring
and
logging,
and
a
lot
of
things
that
are
currently
missing.
I
Some
things
are
happened.
Is
that
we're
setting
up
sort
of
basic
tooling
for
this
so
terraform
for
the
point
hosts
console
for
dynamic
hosted
imagery,
so
we
can
put
push
up
a
lot
of
wispy
notes
and
so
on,
unstable
for
management
configuration
and
using
docker
for
senior
services,
and
also
some
additional
things
around
how
we
do
deal
with
credentials.
K
High
OH,
so
basically
we
reached
it's
a
coverage
of
80%
of
tomato
test
for
nightly
the
street
and
we've
introduced.
The
new
way
of
testing
currently
builds.
It
works
pretty
great.
Basically,
the
most
work
is
done,
but
I
made
the
test
and
like
20,
even
less
like
15
percent
of
tests
are
done
manually
like
faster,
but
it
doesn't
mean
that
we
are
not
testing
for
Milan.
It
means
that
we
are
focusing
on
different
tricky
scenarios,
flaws
which
are
not
optimal,
that
II
in
which
were
not
found
yet.
K
So
it
gives
us
a
lot
of
time
and
effort
for
during
investigation
to
find
all
possible
scenarios
which
can
predict
our
future
goals
is
to
increase
coverage.
First
of
all,
we
are
going
to
add
separate
test
my
social
ideology,
science,
it's
our
p0
and
also
we
are
going
to
cover
all
critical
regression
issues
which
happens
at
least
twice
in
the
episode
box
which
reproduced
from
time
to
time,
and
we
are
going
to
switch
the
extended
test
suite
to
run
against
each
PR
and
also
to
run
against
trill
its
branches.
K
Also,
we
are
going
to
decrease
execution
time
right
now.
It
takes
40
minutes
or
maybe
an
hour
it's
due
to
your
onion
cat
test,
but
instead
of
rewriting
cat
test
and
our
test,
we
are
using
several
devices
several
sessions
and,
for
example,
in
group
chat
where,
when
we
are
using
three
four
devices,
communicating
with
each
other
one
can
crash
and
we
are
not
going
to
rerun
whole
test
with
all
devices
which
are
going
to
result
in
the
session.
K
Also,
we
are
going
to
investigate
on
possibility
to
provide
public
destroy
reports
which
can
be
seen
on
next
screen
for
each
PR,
because
it's
much
better
to
understand
what
is
going
on
than
just
to
read
plain
text
comments
and
lessons
long
take
it's
and
it's
about
you
running
tests.
It
takes
too
much
time
for
your
running
to
test
instead
of
restarting
the
session,
so
we
are
going
to
focus
on
session
your
started
in
order
to
bypass
position.
That's
it.
G
So
yeah
we
did
like
huge
progress
recently
and
the
main
point
is
the
discovery
version.
5
is
available
for
networks
and
right
now
we
are
mostly
like
for
the
past
two
weeks,
we're
mostly
working
on
improving
and
the
experience.
So,
for
example,
we
created
a
custom
boot
node
which
handles
shortly
feels
better
and
it's
more
suited
for
our
way.
Using
the
discovery.
Protocol
there's
also
signal
support
from
the
status
code
status
react.
We
have
also
improved
the
p2p
server
for
different
conditions
and
we
in
the
next
in
the
next
week's
we
are
still
gonna
tweak.
G
D
G
Am
I
in
it
yep
so
two
weeks
ago
we
had
this
final
report
read
out
the
travel
security
and
they
did
not
find
new
issues
in
the
in
the
last
two
weeks,
short
readout,
so
so
yeah.
We
also
took
a
look
at
the
recommendation
of
servation.
They
had
really
good
points
that
are
not
necessarily
like
the
security
issues
right
now,
but
they
may
be
in
the
future,
so
we
transferred
them
to
issues
security
label
in
both
I
status
ago
and
status,
react
repositories
also.
G
G
B
Well,
it's
yeah,
potentially
the
energy-efficient
swamp
became
some
kind
of
overall
performance
of
the
apps
warm.
So
we
did
quite
a
good
progress.
Last
week
we
finally
getting
batching
of
the
incoming
messages
when
you
get
a
lot
of
messages,
almost
at
the
same
time,
I
thought
about
if
they
should
be
rendered
and
delivered
much
much
more
quickly,
that
QPR's
they're
very
close
to
being
merged.
That's
one
of
the
faster
message
for
their
income
tourism
that
essentially
helps
every
time
this
lease
for
itself.
B
It
doesn't
have
any
order
in
it,
so
we
received
with
their
envelopes
in
like
any
order.
So
we
need
to
reorder
them
to
keep
like
conversation
in
normal.
So
then
yeah
we
got
we
used
to
have
one
algorithm,
but
it
was
easier
for
multi
gradient
quite
quickly
with
the
number
of
messages
received.
So
we
improved
quite
a
bit
and
also
we
one
more
thing
is
that
we
also
did
an
envelope
did
a
brocation
on
the
go
side.
B
So
essentially,
when
you
receive
the
same
envelope
content,
then
we
just
ignore
and
don't
even
send
them
to
the
right
side
that
it
helps
with
what
performance
and
special
responsiveness
of
that,
because
the
thread
that
works
with
the
UI
event
is
well
visit.
So
for
the
future
know,
we
need
to
recheck
that
performance
again,
and
we
also
need
to
take
a
look
at
the
animation.
B
So
we
all
day
like
today,
we
had
a
code
where
we
decided
that
we
start
with
switching
them
off
in
the
chat
room
until
we
can
implement
a
performance
version
of
them
because
they
nakida
a
lot
and
there's
no
essentially
as
a
lesson
learned.
So
as
soon
as
we
fix
issues
with
it.
When
we
receive
messages
and
we
can
receive
them
efficiently
and
quick,
then
the
other
bottleneck
is
the
animations
when
it
feels
safe.
It's
what
you
and
yeah
essentially
devils
improve
as
much
as
we
wanted.
Yeah.
C
So,
in
the
last
two
weeks,
we
fixed
a
bunch
of
issues
that
affected
the
message:
delivery,
reliability,
you
know
stuff
like
there
was
a
problem
with
time
drifts
when
a
device
and
drifted
for
more
than
20
seconds.
Regarding
the
official
time,
then
it
would
be
kicked
off
as
a
peer.
So
there
was
some
work
to
measure
the
time
drift
regarding
the
NTP
service
and
adjust
to
that.
There
were
also
some
missing
messages.
We
start
the
counts,
so
we
fix
that
for
the
future
goals
next
weeks,
we'll
be
addressing
all
the
remaining
blockers
for
data.
C
So
Andrea
is
working
on
that
there's
also
the
mail
server
capacity
improvements
so
that
we
have
multiple
mail
servers
and
people
get
distributed
across
those
mail
servers,
and
we
don't
overload
a
single
one
and
of
course
we
will
be
integrating
the
the
performance
improvements
mentioned
and
those
in
the
last
slides
about
message
deduplication,
which
will
help
improve
the
general
usability
of
the
app.
Yes,
that's
the
lesson
so
far
is
just
that's
measuring
you
really
are
you
reliable
team?
I
A
Yeah
well
on
the
wallet
improvements
side.
The
major
update
is
that
now
we
have
unified
workflow,
unified
payment
workflow
between
chat
and
wallet.
That
means
that
you'll
get
the
same
user
experience
more
or
less
whether
you
go
to
chat
and
then
typed
accent
or
you
go
to
to
wallet
and
u.s.
wallets
sent
comment
so
that
it
doesn't
sound
like
a
big
deal,
but
that
has
been
a
major
blocker
for
an
actually
useful
feature,
that's
being
able
to
send
request
tokens
from
chat.
A
So
that's
also
our
immediate
future
goal
to
enable
tokens
being
sent
or
requested
or
sent
back
directly
from
the
chat
know
like
backslash,
send
X
and
t20
type
enter.
The
lesson
learned
so
far
is
that
we
really
need
an
internal
API,
clear,
internal
API
or
in
other
words
we
need
a
good
support
for
extensions,
because
some
things
that
sound
trivial,
like
just
sending
a
multimedia
message
about
the
payment
in
the
chat
without
you
know
an
actual
a
child
comment
and
an
actual
sentiment.
It's
exceedingly
difficult
at
the
moment.
A
There's
too
many
couple
things,
so
we
need
some
internal
decoupling.
Some
component
is
componentization
so,
which
is
you
know
and
I
think
we
need
to
look
look
at.
Do
it
so
yeah
long
story
short.
We
now
have
the
same
workflow
for
chat
and
wallet
sent,
and
the
next
thing
is
enabling
tokens
in
chats
and
comment.
That's
it
more
or
less
in
other
updates,
or
these
design.
/Ux
team
is
working
on
a
new
user
experience
based
on
your
questions,
but
that's
those
data
so
you're
here
to
hear
more
about
it.
After
the
beta
okay.
J
I
will
give
the
update
for
154
excitingly.
This
forum
was
closed
successfully
last
week,
the
last
two
big
issues
that
we
solved
or
support
for
web
3
filters
and
sync
calls,
and
this
means
that
our
exit
criteria
and
success
metrics
now
passed
means
that
every
single
gap
in
our
curated
APIs
actually
works
inside
status.
Previously
there
were
quite
a
few
broken
experiences,
but
now
you
should
be
able
to
load
all
daps
login
make
transactions
and
take
any
sort
of
critical
action
that
you
would
want
to
take
inside
a
DAP.
J
But
if
you
happen
to
run
adapt
in
the
browser
and
run
into
any
issues,
we
would
really
appreciate
it.
If
you
would
report
that,
so
that's
the
update
for
154,
we
can
move
on
101
extensions.
This
swarm
was
actually
put
on
pause
as
we
narrowed
our
focus
in
on
the
beta,
but
Julien
did
complete
the
first
half
of
an
MVP,
and
you
can
see
a
really
simple
demo
of
an
extension
being
loaded
from
ipfs
in
the
browser.
J
If
you
click
on
that
link,
I
think
I'll
go
a
little
rogue
here,
because
Julien
actually
did
help
us
make
some
serious
improvements
to
adapts
that
aren't
covered
by
this
slide
or
this
swarm.
So
there
were
firstly,
a
few
UX
improvements,
mine
our
UX
improvements,
but
also
we
fixed
a
bug
that
was
preventing
some
transactions
from
being
signed
successfully,
and
we
also
Julian
created
a
variable
that
would
allow
taps
to
identify
status
as
a
host.
J
So
that
means
that
when
a
user
is
making
a
transaction
inside,
another
depth
at
DAQ
would
be
able
to
present
a
status
logo
to
the
user
instead
of
a
meta
masked
logo,
which
is
kind
of
the
default
standard
out
there.
Today,
even
if
it's
not
accurate
and
then
last
we
were
looking
at
some
security
issues,
particularly
just
making
sure
that
we
could
gain
fusers
peace
of
mind
that
when
they
use
the
status
browser,
they
are
actually
on
secure
sites
and
that
they
are
at
risk
of
phishing
attack.
D
F
F
It
is
a
really
great
job,
not
just
great
talks,
but
also
like
a
really
warm
reception,
great
team,
fun
people,
yeah
lots
of
excitement
going
on
and
there
they're
releasing
their
POC
3,
which
contains
a
whole
bunch
of
features
which
are
interesting,
encryption,
all
kinds
of
stuff,
big
Network
rewrite
to
make
it
more
efficient
and
they're
working
on
the
PMC
for
which,
which
basically
will
mean
more
or
less
feature
completeness
in
yeah
early
next
year.
Sometime
and
I
mean
I
can
only
say
that
then,
that
I'm
really
really
excited
about
this
development.
F
F
One
conference
that
was
presented
was
an
implementation
of
the
the
source
window
framework,
basically
a
little
bit
similar
to
payment
channels,
but
what's
really
nice
about
it
is
that
it
offers
people
a
way
to
offer
service
on
a
network
and
think
you're
compensated
for
that.
Instead
of
buying
things
for
s,
you
can
provide
service,
and
this
service
in
the
case
of
swarm,
is
obviously
storage
in
the
case
of
status.
That
could
be,
for
example,
running
a
mail
server
or
maybe
running.
F
Basically,
it's
a
combo
of
their
particular
form
of
routing
and
whisper,
which
is
already
part
of
the
theorem
sort
of
protocols
and
what
we
can
buy
with
that.
One
is
a
bit
of
messaging
efficiency,
perhaps
at
a
cost
to
darkness
security,
not
really
security,
but
darkness
above
all,
and
that
is
indeed
a
variant
in
topic
of
conversation
to
have
a
future
like
how
do
we
balance
those
two
and
not
represent
into
users
swarm
itself
as
a
storage,
very
exciting
project?
F
Obviously,
there
are
also
difficult
questions
that
sumir
answering
one
point
is
in
particulars
that
you,
as
a
user,
once
you
put
data
onto
there,
there
there's
no
real
way
of
removing
it
from
there
and
so
I'm
sort
of
one
of
the
things
that
you
need
a
creative
solution.
Another
thing
is
that
the
network
is
kind
of
geared
towards
data
that
doesn't
change
that
often
or
that
doesn't
need
updating
very
often
and
frequently
updating
the
arils,
such
as,
for
example,
a
chat
log
will
also
need
some
creative
work
in
order
to
to
fit
into
that
model.
F
Well,
what
else
can
I
say
about
the
conference?
There
are
lots
of
other
projects
that
present
to
their
work,
their
mainframe
decentralized
chat
application.
Nowadays,
a
development
SDK
for
for
aetherium
depths.
It
was
ether,
get
a
way
to
put
your
git
repos
onto
swarm,
which
is
really
cool.
I
know
a
lot
of
projects
right
now.
F
Another
way
of
handling
payments
this
time,
through
kind
of
like
a
subscription
model
where
payments
basically
flow
between
projects,
instead
of
being
micro
transactions
having
and
having
the
high
overhead
of
those
new
cypher
public
kiri
encryption.
So
this
is
this-
is
this
is
a
possibility
for
for
somebody
to
delegate
the
possibility
to
re-encrypt
data
as
a
way
of
access
control.
So
if,
if
he
usually
wants
to
pass
some
data
to
somebody
else,
they
can
instead
of
negotiating
keys
there,
they
ask
a
service
to
to
be
encrypted.
They
are
using
that
users.
F
Public
key
in
this
confor
example
be
a
way
to
solve
group
chat
because
you
re
encrypted.
They
are
using
using
using
a
common
using
this,
this
real
encryption
framework
and
there
were
lots
of
other
projects,
tarik
complements
in
them
all
I,
really
encourage
you
to
check
out
their
conference
webpage
there.
They
promise
to
put
up
videos
of
all
the
talks.
A
A
A
A
Interest
is
quite
novel
and
will
probably
be
interesting
to
the
entire
name
community,
so
we
plan
to
publish
a
little
bit
more
information
about
it
in
the
future,
probably
as
their
RFC
document
in
the
github
tracker
of
name
and
finally,
we
have
started
work
on
unimproved,
a
synchronous
event
loop
for
name.
Basically,
we
aim
to
increase
the
performance
and
the
power
efficiency
of
the
a
synchronous
networking
code
in
the
coming
weeks
to
meet
our
oh
okay,
our
goals.
A
Local
database,
so
that
we
can
start
working
on
implementing
the
first
book,
changing
algorithms,
which
will
be
the
fasting
motive.
Yet
so
that's
it
for
me,
three
up
the
lesson
we
were
so
firm
is
that
with
much
everything
we
work,
we
frequently
stumble
on
some
issues
that
has
to
be
worked
and
fixed
up
streaming.
The
min
compiler
itself
for
the
status
bar
very
cool.
F
I
just
throw
in
a
quick
comment
there,
one
last
thing
and
this
one
goes
out
to
the
name
community
really,
which
is
that
we're
very
excited
right
with
them,
and
we
we're
looking
for
more
hands-on
back
there.
So
you
know
any
name
programs
out
there.
Anybody
that's
curious
about
name
and
curious
about
languages
in
general.
K
Qt
WebKit
is
used
for
beauty,
min
Joo
EE
you
Bay
is
to
chain
on
Windows
to
support,
react
native
web
components
and
future
goals
resolved
fail,
ingest
unit
tests.
This
issue
a
period
of
the
recent
upgrade
of
reality
version
and
also
provide
ongoing
support
of
state
to
Siam
desktop
application.
It's
a
so
from
us
cool
and.
D
C
Guys,
yes,
so
we've
had
a
kickoff
meeting
a
bit
less
than
two
weeks
ago,
we
had
a
quick
run
through
the
app
installed
it,
both
for
QA
and
dev,
guys
have
nailed
out
some
of
the
sharp
corners
during
the
local
dev
environment
set
up
the
huge
thanks
to
max
for
helping
this
out.
We
have
already
had
some
success
and
basically
shaping
up
what
we
want
to
do
in
the
next
six
weeks.
I
have
defined
the
use
cases,
our
QA
guys
now
stanziano.
C
We
have
quite
a
formidable
list
of
high
priority
issues
to
deal
with
that
we
have
just
began
starting
looking
into,
and
the
goal
for
the
next
two
weeks
would
be
to
finalize
a
list
of
those
use
cases
that
we
want
to
be
included
in
the
bat
up
both
use
cases
and
the
issues
that
have
to
be
fixed
till
the
end
of
q2
we'd
also
want
to
set
up
some
CI
harnesses
and
set
up
some
infrastructure
with
regards
to
Jenkins.
Ci
builds
because,
right
now
we
are
still
building
them.
C
Ad
hoc,
still
building
the
packages
for
Mac
OS
and
the
boon
to
ad
hoc
and
the
priority
for
development.
For
the
development
team
would
be
some
high
priority,
bugs
that
have
been
already
put
in
our
github
project
by
a
nasty
entity
on
ax.
This
would
be
also
dealt
with
during
the
next
two
weeks.
We've
already
had
some
successes
already.
C
Volodymyr
have
fixed
some
of
the
nailing
issues,
gnarling
issues
like
the
inability
to
copy
and
paste
the
public
key
from
from
within
the
application,
and
also
some
issues
with
regards
to
the
Enter
key,
not
working
and
the
chat
window.
So
yeah
I
think
we
have
already
kind
of
loaded
the
fuel
into
the
rocket
engines,
and
we
already
and
the.
C
D
So
yeah
the
one
thing
to
highlight,
so
the
goal
for
the
team
is
that
by
the
end
of
the
quarter,
the
entire
desktop
team
will
be
using
status
to
communicate
with
each
other
and
then
through
the
course
of
q3,
more
and
more
teams
and
with
the
goal
that,
by
the
end
of
q3,
all
of
status
and
all
our
channels,
including
riot
and
everything,
will
be
replaced
by
slack.
Let's
see
how
we
go,
but
it's
a
very
exciting
and
ambitious
target
cool
all
right.
That
wraps
us
up
we're
slightly
over
schedule,
but
that's
okay.
D
Apologies
to
other
teams
that
have
me
Zender.
The
embark
folks
are
running
15
minutes
late.
Because
of
this
there
is
one
question:
that's
come
through
and
Jared
I
don't
know
if
you
want
to
take
a
stab
at
it
around
balancing
between
quality
of
product
development
versus
community
engagement,
which
is,
in
my
opinion,
a
bit
of
a
false
dichotomy
but
I'll.
Let
Jared
kinda
answer.
E
E
E
So
so
this
idea
of
everyone
who's
involved,
already
wants
the
the
sort
of
best
outcome
rather
than
doing
things
for
for
the
lulz
I
think
this
is
great
because
it
is
the
most
flexible
and
it
allows
things
to
allows
us
to
not
take
things
entirely
so
seriously
all
the
time,
and
it
certainly
allows
you
to
fit
get
us
that
perfect,
there's
a
very
snug
if
market
fit.
It's
also
the
hardest
to
get
right,
because
social
ontology
is
more
of
an
art
than
a
science.
E
But
you
know
it's
it's
worth
to
try.
I
haven't
really
found
any
like
really
hard
resources
on
that
how
to
go
about
that?
If
it's
on
the
software
side
well,
I
mean
maintainer,
xand,
I,
still
somewhat
gatekeepers,
and
there
is
an
inherent
trust
and
reputation.
I
involved
in
that,
like
you,
know,
even
kind
of
maintainer,
unless
we
can
trust
you
with
managing
the
codebase
and
things
get
reviewed
by
them.
Of
course,
reviewing
is
quite
costly.
E
So
there
needs
to
be
some
kind
of
form
of
compensation
from
that,
and
maybe
there's
some
kind
of
multi-tiered
screening
system
to
make
sure
that
people
aren't
getting
over
encumbered
with
just
useless
quote:
quote:
unquote,
useless,
pull
requests
so
so
to
speak
and
I
mean
the
other
side.
Is
that
like
S&T
voting,
there
are
large
stakeholders,
including
the
status
organization
that
could
help
direct
and
guide
this
in
in
the
sort
of
short
term?
Of
course
we
want
to.
E
We
are
a
good
strat,
so
the
idea
is
that
we
disseminate
or
dissolve
our
our
stake
in
this,
to
give
it
over
to
the
users
themselves,
so
so
yeah
I
think
there's.
Definitely
some
things
that
you
can.
You
can
do
to
help
influence
this,
whether
or
not
it's
it's
ultimately
the
best
day.
I
guess
that's!
That's
part
of
the
fun
to
find
out.
D
So
the
the
one
of
the
last
questions
is:
was
the
goal
on
desktop
to
have
right
and
slack
channels
migrated
to
to
status
by
up
to
three
I?
Don't
want
to
speak
on
behalf
of
the
team
and
that
probably
is
a
little
bit
too
aggressive,
but
I
think
it's
definitely.
We
will
be
close
to
that.
So
by
the
end
of
the
queue
to
the
desktop
team
will
be
communicating
on
status,
that's
the
goal
and
then
as
many
teams
as
possible
and
if
not
everything
moves
on
by
the
end
of
q3.