►
From YouTube: Community Governance Call #1
Description
Discussing:
1. Fathom Analytics
2. Discord as IM and community access to Discord
A
B
I'll
get
started
so
this.
This
is
the
first
of
I
guess
many.
Our
future
community
government
governance
calls
just
trying
to
give
the
community
a
bit
more
of
a
voice
and
SNT
stakeholders,
particularly
a
voice
in
the
direction
some
of
the
decisions
that
are
made
within
status.
So
this
is
entirely
an
experiment
and
will
evolve
the
process
as
we
go,
but
just
figured.
We
start
it
and
and
learn
so
I
guess
we'll
just
get
started.
I'm
gonna
share
my
screen
and
walk
through
the
first
proposal
and
then
I'll
kick
it
over
to
JB.
B
Who
will
walk
you
in
a
second?
Can
you
guys
see
yeah
yeah
cool,
so
the
first
proposal
is
to
introduce
fathom
analytics
on
our
marketing
web
properties.
Fathom
analytics
is
a
privacy-preserving
analytics
tool
that
a
few
people
have
I
guess
proposed
in
the
past
and
with
the
launch
of
e1
coming
up.
We
just
simply
need
a
way
to
monitor
our
success
of
contents,
page
views
and
just
kind
of
give
us
a
better
indicator
of
what's
working.
B
What's
not
so
a
little
background
back
in
2017
or
early
2018,
we
removed
Google
Analytics
from
our
websites
as
as
an
adherence
to
the
principles.
Google
Analytics
takes
a
lot
of
data
from
your
users,
implements
cookie
tracking
and
since
we're
building
tools
to
actually
you
know
prevent
this.
It
was
a
bit
hypocritical
to
use
GA,
so
we
removed
GA
and
leveraged
only
social
metrics.
B
So
like
Twitter
likes,
Twitter
engagement
discussed
post
likes
certain
metrics
from
github
Facebook
and
that
and
so
we
had
some
high-level
overview
of
what
was
working,
but
it
really
gave
us
nothing
in
terms
of
referral
traffic
website,
successful
pages
and
things
like
that.
So
it's
been
very
tricky
and
it's
too
becomes
very
hard
to
measure
success
and
set
proper
KPIs
for
any
marketing
work
and
so
I
know
Jakob
and
I
think
even.
B
B
So
that's
that's
not
so
we
use
it
on
all
of
our
blog
content
as
well.
So
we
can
see
what
blog
content
is
working
well
and
what's
not,
and
we
can
infer
a
little
bit
more
about
our
user.
Our
sorry,
our
audience
as
well,
whether
you
know
more
technical
content,
working
or
more
branded
kind
of
visionary
contents
working
and
then
just
scale
it
up
from
there.
B
Next,
we
can
monitor
link
clicks
over
a
period
of
time.
So
when
we
do
get
into
v1-
and
we
have
you
know
CTAs
for
install
IRF,
iOS
or
Android-
we
can
actually
see
we
can
monitor
and
measure
how
many
people
are
clicking
on
that.
And
then
what
is
the
actual
conversion
to
actually
the
actual
conversion
to
install
it
on
their
phones?
Because
we
will
have
the
the
Play
Store
and
App
Store
or
store
data
as
well.
B
Once
again,
yeah
we'll
use
it
on
on
specific
blog
articles.
I've
already
mentioned
that
and
we
connect
so
if
Adam
also
provides
referrals.
So
if
we
run
well,
we
can
see
where
people
are
coming
from.
If
it's
social,
if
it's
more
technical
blogs,
if
it's
more,
you
know
security
and
privacy
focused
blogs
and
websites,
we
can.
You
can
just
see
where
people
are
coming
from
and
then
we
can.
B
This
is
only
for
our
marketing
web
properties
just
to
help
us
out
with
with
KPI
planning,
so
Jakob
and
I
met
with
the
Fadem
team,
just
to
get
a
little
bit
more
information
of
how
it
works
and
Jakob
then
took
that
and
set
up
a
self-hosted
version,
which
is
what
we'll
use
and
there's
a
demo
up
and
running
for
anyone
who
wants
to
see
it.
So
we
will
host
this
ourselves
just
making
it
even
more
I
guess
securing
it
in
our
control.
B
C
One
thing
two
out
if
I
can
sure
just
just
just
to
add
to
that.
This
is
something
that
realistically,
it
is
that's
something
we
need,
especially
going
into
v1
with
the
amount
of
content
that
we
want
to
be
putting
out
and
stuff
to
attract.
You
know,
developers
and
contributors
that
session
to
the
follow.
We
really
do
need
analytics
like
the
stuff
that
flavin
provides.
You
know
to
go
with
the
new
content
that
we're
going
to
be
pushing
out,
and
you
kind
of
develop
a
stuff
that
we're
going
to
be
pushing
out.
So
this.
C
B
Yeah
definitely
so
jumping
back
into
how
fathom
specifically
works.
It's
listed
out
here,
the
data
is
collected,
yeah
yeah,
embedding
an
image
that
image
is
then
downloaded
from
their
servers
hosted
on
Heroku
for
auto-scaling
and
Jakob
feel
free
to
jump
in
at
any
points,
because
you
kind
of
know
more
than
I
do
on
this.
But
when
a
request
is
made
to
the
servers,
the
process
of
handling
hashes
insults
the
data.
So
then
that
data
is
not
stored
anywhere.
It's
not
it's
not
maintained
in
the
server.
It's
it's
kind
of
cleaned.
B
B
So
so,
essentially,
the
only
information
stored
are
what
they
claim
to
collect
on
their
web
sites
right.
So
paths
refers
in
times
of
requests,
there's
absolutely
no
cookie
associated
to
users,
which
is
obviously
issuance
using
Google
Analytics.
So
in
essentially
it
really
is
its
privacy,
preserving
it
respects
the
users
data
and
it
doesn't
track
or
store
any
of
their
information
anywhere.
E
D
Way
it
works.
Is
it
just
has
a
this
one,
pixel
image
that
is
loaded
every
time
and
that
just
collects
on
the
server
the
things
like
the
paths
and
the
timings
and
so
on.
Everything
else
is
hashed
I,
one
thing
that
I
might
add
here.
It
says
hostile
Heroku.
In
our
case,
it's
just
hosted
on
the
ocean
a
host
and
the
thing
is,
it
doesn't
have
to
scale
because
so
hosted
ones,
don't
run
out
of
skills.
So
this
one
disadvantage
of
that
is.
We
just
have
to
keep
it
on
a
decently
sized
horse.
D
F
D
Yes,
so
since
this
is
hosted,
we
are
the
upgrades
are
manual
so
I
guess
we
can
just
hold
it
whenever
we
upgrade
to
see
if
they
are
there.
I
think
the
other
thing
is
as
the
good,
the
community
of
states,
all
the
data
goes
to
Redis
and
we
can
just
directly
ourselves
look
up
what
the
stored
in
Redis
and
that,
as
far
as
I
can
tell
it's
accurate.
Everything
is
hashed
except
things
like
paths,
so
there
are
descriptions
like
you.
It.
E
D
F
B
How
would
be,
how
would
we
be
informing
people
about
this
tracking?
So
obviously,
this
process
is
intended
to
help
people
understand
what
we're
doing
gaming,
a
the
stakeholders
and
community
of
voice
in
whether
we
do
this
or
not,
and
before
we
implement
this.
There
will
be
a
series
of
communications
that
comes
out
whether
it's
no
it
will
be
a
blog
post
and
update
to
this
discuss
and
I
guess.
A
I'm
curious
to
what
extent
your
average
visitor
is
familiar
with
father
like
if
they
Saudis
claim
and
I
agree,
that's
the
right
thing
to
do
if
they
saw
a
disclaimer
saying
that
this
and
tracking
like
would
they
understand
how
anonymous
it
is,
or
might
it
kind
of
be
a
bit
scary
thinking?
Okay,
it's
just
like
Google
Analytics.
G
I'd
say:
there's
a
myriad
of
people
with
various
things.
One
is
the
people
who
don't
care,
won't
care.
The
people
who
do
care
and
don't
understand,
can
google
it
and
that
and
how
much
they're
willing
to
google.
It
is
probably
going
to
be
detention
upon
the
like
the
copy.
We
use
to
inform
that
we're
doing
this
type
of
thing
and
the
people
that
do
care
and
know
will
will
understand.
Also.
H
B
I
D
J
Suggest
even
positioning
it
as
initiative
like
in
order
to
provide
web
services
with
privacy.
You
have
to
take
these
kinds
of
steps,
and
so
it's
not
just
that
we're
falling
back
on
this
because
we
can't
do
GA,
but
rather
it's
a
proactive
measure
and
we're
excited
about
doing
this
because
we
we
want
to
be
able
to
reach
people
to
to
do
it
needs
to
be
done,
but
at
the
same
time
we
want
to
preserve
privacy.
Here's
that
compromise
talk
them
up
a
little
bit.
J
B
Think
it's
it's
mostly
just
respecting
our
audience
and
and
kind
of
just
adhering
to
the
principles
as
much.
We
can
I
think
we're
not
we're
not
taking
you
know
personal
PII
from
our
users
and
also
we
are.
This
is
also
like
a
branding
piece
right
like
we
can
promote
and
and
be
proud
of,
the
fact
that
we're
using
this
instead
of
GA
and
and
publicize
this
to
everyone
and
actually
kind
of
start
potentially
even
start
like
a
movement
in
people
doing
this
because
I
know
there's
a
lot
of
other
projects
and
it's
pretty
obvious.
B
You
know
they're
building
the
tools
for
security
and
privacy
and
then
you
go
to
their
website
and
you
get
the
the
cookie
tracking
GPR
notification,
which
is
a
bit
hypocritical.
I,
think
it's!
It's
definitely
for
us
to
stake,
claim
and
what
we're
doing
I
mean
they
were
protecting
our
users
by
not
taking
their
data.
B
G
At
the
same
time
like
okay,
we
don't
want
to
shoot
ourselves
in
the
foot
and
the
process
of
trying
to
reach
our
audience
and
get
the
product
at
the
people
who
would
care
about
it
by
not
doing
anything,
and
so
this
is
one
of
the
best
situations
of
not
like
upholding
the
principles,
not
taking
this
information,
but
getting
what
information
is
currently
available.
That
is
aligned
with
our
principles
and
using
them
absolutely.
B
So
quickly,
just
to
rehash
kind
of
the
pros
and
cons,
the
pros
is
pretty
much
how
we
will
use
it
right,
enable
us
to
more
effectively
measure
campaigns
and
content,
success
and-
and
we
will
allow
the
marketing
team
to
just
be
a
bit
more
KPI
driven
and
hold
us
a
bit
more
accountable
right
now.
We're
basing
our
the
success
of
our
campaigns
on
on
social
metrics,
and
you
know,
attendance
to
things
and
the
more
we
get
into
acquisition.
The
more
we
simply
just
need.
B
B
And
also
makes
yeah
we
use
ghosts
and
we
use
other
tools
that
are
once
again
that
we
simply
need
to
use
that
are
collecting
more
information
than
men.
Adam
does
ghosts,
I,
don't
well,
because
our
ghost
is
a
self-hosted
Jakob.
They
probably
we
don't
have
GA,
but
I
mean
Twitter,
Twitter
and
Facebook,
and
even
github
is
collecting
more
information
that
that
then
we
do,
but
we
suppose.
B
So
once
again,
we
can
be
more
KPI
driven.
We
can
learn
more
about
our
audience,
not
through
direct
data,
but
just
through
like
inference
and
information
that
we
collect
over
time,
and
we
can
incentivize
acquisition
campaigns
through
third
parties
with
SNT
specifically
that
work
drives
further
acquisition
and
then
we
can
finally
start
to
leverage
tools
and
platforms
such
as
code
fund,
which
is
get
coins,
privacy,
add
platform.
They
simply
need
some
sort
of
metric
or
some
sort
of
like
it's,
not
a
cookie.
B
But
it's
it's
data
on
our
website
that
tracks
clicks
and
we
can
actually
start
to
run
those
ads
across
there.
An
ad
network
on
the
cons
once
again
it
some
people
could
argue
that
this
is
in
opposition
to
privacy
into
our
principles
and
that's
why
we're
hosting
this
vote
just
to
see
what
people
think
and
then
also
into
Hester's
question
if
they
do
push
an
update
it,
it
is
more
work
on
our
side
to
audit
it
and
make
sure
that
you
know
there's
nothing
negative,
that
we're
implementing.
B
So
the
information
that
we
have.
That's
the
proposal
which
we'll
be
voting
on
so
next
step
is
Monday.
Next
Monday
October
28th
we're
gonna,
kick
off
a
vote
in
the
S&T
voting
that
for
now
I
know,
Ricardo
is
potentially
working
on
some
stuff
with
a
topic
democracy
which
we
may
leverage
instead,
but
either
way
there
will
be
a
simple
vote
or
SMT
holders.
Stakeholders
can
can
vote
on
yes
or
no
to
this
proposal,
and
once
the
book
closes
on
Friday
we'll
have
our
our
results
and
we
either
will
implement
or
we
will
not.
B
B
H
H
Hadn't
really
fulfilled
some
of
the
voids
left
by
slack
and
the
people
who
were
feeling
you
know
a
bit
isolated
or
finding
collaboration
a
bit
difficult,
and
so
in
Istanbul
we
talked
about
a
proposal
to
test
discord
for
kind
of
the
rest
of
the
year
and
see
if
that
increased
the
communication
and
collaboration
across
core
contributors.
So
the
the
initial
solution
was
to
a
problem
that
core
contributors
mainly
faced,
which
was
kind
of
data
they
collaboration
during
our
day,
job
status.
H
So
most
people
it
looks
like
joins
discord.
We've
not
we've
not
really
been
tracking,
but
it
looks
like
most
core
contributors
are
in
there
and
yeah
Bob's,
obviously
bridged
a
lot
off
the
channels.
We
see
lots
of
traffic
coming
through
and
maybe
being
like
a
successful.
It
seems
like
community
members
have
now
asked
to
join
their
discord
as
well
and
so
I
guess
there
are
pros
and
cons.
Obviously,
our
principles
around
openness
and
transparency
probably
dictate
that
opening
up
this
chord
is
something
we
should
do,
or
at
least
seriously
think
about.
H
So
this
was
a
temporary
stopgap
to
try
to
score
to
see
if
it
works
and
see
if
it
improves
our
collaboration
as
a
group,
and
so
you
know
we
don't
we
I
guess
we
don't
have
a
long
term
plan
right.
There
is
no
guarantee
that
we'll
consider
using
this
according
q1.
If,
if
this
doesn't
work
with
other
get
better
and
so
moving
a
community
over
to
discord,
may
actually
not
be
the
smartest
idea
if
we
would
move
them
away
from
it
or
close
it
down.
D
I,
for
one
think
it's
good
I
mean
it
allowed
me
to
be
more
productive
because
I
don't
struggle
with
communications
as
I
used
to
and
the
fact
that
we're
we're
explicit
about
it
being
temporary
until
we,
for
example,
get
back
to
making
desktop.
Actually
usable
I
think
it's
perfectly
sensible.
There's
I,
don't
see
a
point
of
of
making
it
harder
on
ourselves
to
do
the
actual
thing
that
we
made
ourselves.
Do
we
just
make
the
app
just
because,
oh
we
should
struggle
with
this
broken
software.
G
I
think
I
would
I
would
personally,
second,
that
I
felt
it
easier
to
communicate
with
people
to
get
things
done
and
figure
out.
What's
going
on,
since
the
switch
based
on
everyone
being
in
the
same
place,
the
bridge
has
allowed
me
to
communicate
with
the
outside
was
like
the
Status
channel
and
people
asking
questions
in
status
and
as
status
gets
better
with
the
features
if
it's
maintained
some
feature
parity
with
what
we
want
to
do
in
terms
of
using
as
a
collaboration
tool
that
can
be
a
graceful
switch
back
over
to
status.
G
One-On-Ones,
like
DNS
with
it
with
people,
so
we'll
have
to
develop
a
better
culture
around
where
that
should
go
first,
and
maybe
second
or
emergency
type
stuff,
but
it
we
should
be
focused
on
getting
being
efficient.
First,
using
things
like
this
that
tie
back
to
what
we're
trying
to
get
to
they've
been
allow
for
graceful
changes
back
to
status.
In
my
opinion,
and.
G
Channels
that
need
to
be
private
remain.
Private
I
have
a
slight
worry
that
we
lose
say.
For
instance,
we
push
v1,
we
gain
a
bunch
of
users
and
then
they
span
the
channel
and
we're
back
to
square
one
and
where
we
were
in
beforehand.
So
we
need
we
need.
If
we
do
that,
we
need
to
make
sure
that
the
channels
that
are
open
to
community
members
don't
inhibit
the
core
contributors
team
and
those,
maybe
even
slightly
outside-
of
core
contributors
to
get
work
done
and
not
just
have
a
bunch
of
spam.
D
D
G
B
C
On
this
principle,
in
the
sense
that
I
love
the
idea
of
having
community
members
in
our
discord,
but
only
in
kind
of
community,
open
channels
right
so,
for
instance,
like
the
marketing
channel,
I,
often
post
unfinished,
like
articles
and
stuff
for
proofreading
and
stuff
like
that-
that
wouldn't
really
be
appropriate
for
anyone
other
than
people
on
the
team
to
read
so
are
we
saying
you
know
that
we
can
invite
community
members
into
specific
channels
specially
made
for
them?
Or
you
know,
are
we
saying
open
up
kind
of
most
channels
to
them?.
H
H
Yeah
because
I
haven't
cow,
I
think
we're
kind
of
running
kind
of
25
plus
channels.
At
this
point
right,
we
Dardis
cause
been
so
successful.
We
keep
on
adding
channels,
and
it's
probably
getting
already
noisy
with
within
just
the
core
crunch
pieces
in
Johnny
in
Chin
Ho.
Do
you
have
like
any
feedback
for
the
community
on
exactly
what
it
is
they
they're
kind
of
missing,
although
they
would
like
to
have
access
to?
Is
it
just
this
great.
B
B
I
think
well,
our
community
and
the
people
who
chat
in
the
channels.
Now
it's
it's
significantly
smaller
than
where
it
was
primarily
because
you
know
like
Cory's
point,
there
are
barriers
to
entry
to
getting
status
and
it's
just
it's
not
the
most
reliable
tool
right.
So
these
people
want
just
a
more
reliable
tool
and
something
that
they
could
just
easily
chat
with
us
chat
with
us
on.
That's
been
the
feedback
so
far
and
I
think
other
otherwise,
just
looking
at
it.
It's
it's.
H
Would
it
work
if
we
set
up
a
separate?
You
know
server
disk
disk
called
server
for
community
members
that
we
also,
rather
than
invite
them
to
the
existing
one?
We
have
where
people
that
I
guess
concerned
about
the
confidential
information
or
kind
of
the
unfinished
work
for
they.
Don't
they
don't
want
to
share?
But
if
we
had
a
separate
discord,
do
we
invited
everyone
so
and
then,
because
it's
quite
easy,
I
think
to
manage
the
different
servers
in
discord
once
you're
once
you
into
this
gold?
Could.
B
Do
that
I
mean
whatever's
easiest
or
just
create
those
private?
Just
just
have
private
channels
for
the
team.
I
think
we
just
need
to
think
about
what
the
ultimate
goal
of
this
is
it's
to
interact
with
our
community
and
are
much
more
open
and
like
seamless
way
and
give
our
community
members
like
a
simple
way
to
contact
us
and
into
comment
to
communicate
with
each
other.
Whatever
works
best,
there
I
mean
I'm
open
to
it.
Yeah.
B
Last
thing
from
from
my
side
is
you
know
when
we
do
who
want
to
be
one
like?
We
have
a
lot
of
plans
and
there's
a
lot
of
traffic.
That's
gonna
be
driven
to
our
site
and
to
install
the
app,
and
we
really
do
need
to
make
it
make
it
as
easy
for
people
to
troubleshoot
as
possible,
and
discord
is
just
easier
to
get
into
right.
Now
then,
status
desktop,
so
I
would
hate
to
miss
out
on
the
opportunity
to
get
those
people
bring
them
into
our
community
support
them
call
like
cultivate
those
relationships.
B
D
E
E
Coming
to
status
like
on
the
website
and
I
think
it's
kind
of
cool
how
this
cord
is
there.
You
can
kind
of
from
the
website,
see
what's
going
on
and
then
sign
up
pretty
easily
I
like
what
someone
said
just
how
it
is
now.
People
can
communicate,
but
maybe
had
some
channels,
private
and
then
kind
of
invite
people,
maybe,
as
a
per
case
basis,
on
more
sensitive
channels.
H
A
Was
chatting
today
with
URI
because
URI
Craver
wrong,
but
like
embark
team
already
has
their
own
separate
server
on
discord
like?
How
is
it,
and
you
also
have
community
members
on
that
server
right
like
how
has
that
been,
because
what
we
were
discussing
was
what
does
it
make
sense
to
migrators
embark
channels
now
to
the
status
discord
and
with
it
the
community
members
that
are
there,
because
it
feels
like
there's
two
different
kind
of
modes
like
one
server
has
community
members,
the
other
dozen.
L
It's
too
ok.
We
also
have
private
channels
which
we
we
manage
with
the
roads.
So
we
can
also
discuss
like
a
more
more
sensitive
part
and
I,
just
like
nimbletoes
of
graduate
to
together
and
to
stare
at
itself.
So
sometimes
people
will.
They
will
actually
not
be
on
this
core
they'll
be
on
Gator
and
talk
from
and
talk
from
there
I
mean
I,
don't
really
see
as
an
issue.
I
think
issue
is
ready
for
the
more
private
channels,
the
more
sensitive
stuff,
but
that's
it
that's
kept
private.
L
H
And
it's
just
just
knowing
where,
if
we
do
migrate
communities
into
discord,
that's
you
know.
We
don't
really
want
that
to
be
like
a
short-term
solutions.
It's
a
pain
to
move
everyone
out
right
as
a
group.
Do
we
do
we
rate
discord
enough,
so
you
know
continue
using
it
into
next
year.
I
haven't
some
had
anything,
it's
a
very
negative
about,
like
our
discord
trial
so
far,.
J
Hey
this
is
an
Andy
I
just
want
to
provide
one
counterpoint
which
I'm
not
sure
if
you
guys
have
talked
about,
but
you
know
having
a
product
that
is
a
messaging
platform
and
using
a
different
messaging
platform
is
something
that
we
should
just
be
aware
of,
and
will
probably
face
criticism
for
that
somewhere
that
the
reality
is,
and
it
sounds
like
from
everybody.
You
guys
have
used
these
for
a
lot
longer
and
productivity
is
incredibly
important,
but
we
need
to
be
prepared
for
that.
The
perception
of
that
as
well.
K
That
was
the
main
reason
we
let
go
of
slack
like
dog,
feeding
eating
own
food.
So
but,
as
someone
said,
we
need
to
ship
few
on
then
concentrate
on
desktop,
I
guess
and
for
I.
Think
four
I'm
back
team
as
well,
but
for
four
I
said
Nimbus,
is
the
main
draw
of
slack
was
threaded
communication,
because
sometimes
we
had
conversation
going
like
one
with
talking
about
networking.
Another
one
is
talking
about.
I,
don't
know,
prefer
steak,
and
it
makes
very
hard
to
follow
on
the
current
status
up.
L
L
G
I
guess,
echoing
on
that
slack
is
popular
for
a
reason,
and
that's
because
they've
optimized
for
teams,
and
not
necessarily
chatting
we've,
had
chat
apps
for
a
long
long
period
of
time
and
if
they
were
doing
the
job
appropriately
for
teams,
then
black
would
not
be
popular
or
discord
for
that
matter.
Just
that
the
UI
has
a
big
big,
big
part
of
how
efficient
you
are
in
the
process
of
doing
teamwork.
I'm,
sorry,
how's,
your
good!
No.
F
I
mean
mostly
echoing
the
same
points
like,
which
is
why
I
think
we
will
not
be
moving
like
for
like
office
productivity
or
as
a
work
tool.
I,
don't
think
we'll
be
moving
back
to
set
us
any
time
soon,
because
it's
just
a
very
different
use
case
and
what
the
core
app
is
developing
for
at
the
moment.
I
guess
I
just
wanted
to
say
I'm
I'm,
not
entirely
sure
on
the
problem
that
we're
trying
to
solve
like
I,
totally
understand.
We
want
to
optimize
for
community
engagement,
I,
don't
think,
there's
there's
any
about
that.
F
Like
Beyonc,
let's
say
the
bridging
that
we
already
have
in
place
if
I'm
trying
to
imagine
if
there's
a
bigger
demand
for
understanding
what
the
teams
are
working
on,
there
might
be
a
whole
different
direction,
which
is
like
more
frequent
updates.
I'll
discuss
a
more
comprehensive
timeline
of
what's
coming
down
the
road,
whether
it's
like
set
in
stone
or
not
so
I
mean
I,
guess
I'm
not
entirely
clear
what
we.
K
One
thing
is
that
when
you
do
a
blog
post
or
discuss
well,
especially
blog
posts,
there
is
less
personal
touch
that
someone
that
is
really
a
contributor
involved
in
the
project.
Just
reply
like
one
minute
after
you
ask
a
question
and
you
feel
how
most
people
are
really
accessible
and
we're
not
like.
We
are
not
behind
a
wall,
and
we
need
to
go
through
some
kind
of
broad
critique
procedures
to
talk
to
them.
F
Yeah,
that's
so
that
yeah
yeah
I
understand
that
point
I'm,
just
not
sure.
To
what
extent
it's
the
case
now
that,
like
people
write
on
discuss,
are
not
a
core
contributor
and
let's
say
like
wait
four
days
for
someone
to
reply.
If
that's
the
case,
maybe
we
should
be
more
proactive
in
engaging
with
with
contributors
I'm
looking
to
connect
another.
K
F
A
Could
also
be
just
a
signaling
thing,
like
you
know,
wearing
this
app,
you
stay
in
that
app.
It
kind
of
puts
like
a
perceived
wall,
even
if
effectively
like
the
communication,
is
bridged
perfectly
between
the
two
you
know
like
in
one
app.
You
can
see
some
nails
and
gifts
and
whatever
and
then
the
other
you
can't
it
may
be
just
as
like
a
signal
of
how
we
value
and
include
people.
That's
kinda,
saying:
okay
got
it
I,
don't
know
if
people
perceive
that,
but
that
would
be
my
guess.
I
think.
B
That
is
a
perception
at
the
moment
right.
So
when
we're
messaging
in
discord
and
it's
bridge
to
status,
it
says
you
know
my
username
and
then
like
bought
discord
and
then
as
soon
as
what
the
community
member
sees
that
they're
like
hey.
How
come
I
can't
get
into
discord?
Oh
god!
Well,
maybe
soon
sorry
got.
M
B
H
B
H
H
So
it's
not
so
I
guess
one
point:
it's
not
like
all
the
up,
so
all
the
other
channels
that
we
have
in
discord
right
now,
which
people
can't
see
there
I
guess
they're
the
bits
that
I
hear
like
the
we
value.
It's
that
ability
to
collaborate
as
a
group
and
I
think
a
few
people
kind
of
voiced
concerns
that
they'd
be
worried
that
that
work
might
get
swamped
with
messages
or
spam
or
just
the
noise
in
general
would
reduced
their
collaboration
or
their
their
productivity.
H
H
Because
I
guess,
the
other
thing
right
is
the
the
number
of
channels.
So
we
currently
the
number
of
channels
is
growing
and
if
community
members
claim
along
and
wanted
to
create
more
channels
that
I
guess
adding
in
another
ten
or
fifteen
channels
may
actually
further,
like
tax
collaboration
and
just
being
able
to
find
information
in
discord.
So
we'd
have
to
come
up
with
a
set
of
like
community
guidelines
for
how
we
manage
the
discord
and
different
Commission's
on
creating
new
channels
and
managing
them.
K
Maybe
we
can
have
like
a
status
discord
and
status
community
discord,
which
would
be
managed
mainly
like
with
community
channels,
so
that
the
community
can
grow
as
they
wish
because
like
if
we
automatically
set
a
set
up
channel
for
each
languages,
we
have
community
members
in.
We
automatically
have
like
20
or
40
more
channels.
H
Yeah
so
I
guess
I
guess
for
me,
we
can
put
this
to
the
like
a
community
vote
as
well
next
week
and
it
sounds
like
they
were
probably
like
three
or
potentially
four
different
options.
The
first
is
which
I
don't
hear
really
any
support
for.
It's
like,
let's
not
add
community
members.
That's
all
the
middle
ground
seems
to
be
like
creating
a
separate
discord
for
community
members
that
we
would
join.
H
Third
option
would
be
adding
allowing
anyone
to
join
our
discord
and
then
using
permissions
and
roles
as
a
way
of
like
I,
guess,
walling
access
to
different
things
and
the
fourth
option
being
just
having
everyone
in
anyone
who
wants
access,
so
anything
can
have
it.
Then
we
could
kind
of
define
those
four
options
and
let
people
vote.
H
M
M
M
D
M
Yeah,
the
other
thing
I
was
I,
was
gonna.
It
was
just
kind
of
going
through
my
mind,
was
listening
to
everyone.
Talk
is
I,
you
know
now
we're
talking
about.
You
know
how
we're
migrating
all
this
communication
to
discord
versus.
You
know
why
we
brought
it
back
compared
to
when
we
were
purely
on
status
things.
These
thing.
These
features
that
people
are
bringing
up
now
like
having
threaded
conversations
or
you
know
some
of
the
features
that
you
get
and
things
like
slack
in
discord.
M
I
never
saw
anyone
actually
voice
an
opinion
saying
we
want
to
have
these
things
in
status.
Let's
build
them,
it's
not
even
a
matter
of
we
didn't
like
we
what
we
tried,
but
we
weren't
able
to
build
them.
We
just
didn't
even
it
seems
like
people
didn't
want
to
focus
on
building
those
things
we
people
just
I,
guess
want
something
out
of
the
box
where
it's
that
that
thinking
has
been
done
for
them
and
then
it's
already
kind
of
here
you
go
use
this
design,
that's
built
for
this
purpose.
D
K
Another
thing
is
that,
before
moving
away
from
slack,
there
was
fred
in
slack
about
what
we
will
miss
from
slack
and
I'm,
pretty
sure
Fred.
That
conversation
got
a
lot
of
vote,
but
obviously
we
don't
have
the
logs
anymore
or
maybe
we
have
them,
but
not
in
a
proper
consumable
format,
and
we
didn't
have
discussed
at
the
time
as
well.
So
we
couldn't
save
them
for
posterity.
D
D
Oh
yes,
I
do
recall
people
mentioning
that
they
will
miss,
mentions
and
group
chats
and
and
stuff
like
that.
I,
don't
think
that
was
taken
craft
I
think
that
the
point
was
to
make
a
public
thing
out
of
switching,
even
if
it
wasn't
fully
thought
through,
but
I
guess
I
made
this
partially.
It's
helped
us
realize
that
desktop
is
trash,
but
that
didn't
change
anything
because
the
stuff
is
still
most
mostly
trash
or
even
unusable,
but
at
least
we
realize
that
whispers
trash
fully.
So
I
guess
that's
a
benefit,
but
I
made
everything
else
worse.
D
M
D
G
D
F
D
H
M
H
I
guess
maybe
at
some
point
some
of
these
features
get
implemented
into
the
desktop,
and
so,
if
there
was
I
guess,
there's
like
a
minimum
threshold
for
whether
it's
I
don't
know
threading
or
at
mentions
or
reactions.
But
at
some
point,
if
the
state
says
death
for
app
has
some
form
of
parity
with
the
features
we
won,
then
we
might
consider
moving
from
discord
to
status
test,
though.
A
G
D
M
I
mean
I
would
say,
though
the
same
desktop
doesn't
work,
I'm
sure
something
some
things
about
it
are
off,
but
I
mean
it.
It
doesn't
work
in
the
sense
that
you
know
you
can
message
and
it
sort
of
has
that
functionality,
but
I
think
you
know
the
reason
it
feels
clunky
to
all
US.
Is
it
just
lacks
so
much
of
the
functionality
we've
grown
accustomed
to
that
we
expect.
Out
of
you,
know
like
a
desktop
messenger,
so
ok,
I
guess
it
doesn't
run
Linux,
but
it
the
reason.
I
said
you
know
six
months
from
now.
M
You
know
why
would
you
reconsider?
This
is
because
I
don't
see
a
like.
If
you
look
on
discus
or
anywhere,
you
don't
see
much
of
an
impetus.
You
don't
see
much
of
people
asking
for
these
features
in
desktop.
You
don't
you
know,
I
understand,
there's,
there's
some
bugs
they
could
be
fixed.
You
know
some.
It
could
probably
be
more
memory
efficient
and
things
like
that
for
sure,
but
I
think
in
some
cases
maybe
people
would
rather
have
some
of
these
features
implemented
or
not.
M
A
One
thing
to
mention,
as
well
just
from
my
recollection
is
like
I
feel
that,
like
in
the
last
two
engagement
surveys,
we
did
where
we
asked
everyone
what
they
thought,
like
the
communication
tool
came
up
like
quite
strongly
across
the
last
two
quarters
is
something
that
like
people
were
feeling
like,
it
was
impeding
work,
or
there
was
a
sense
of
like
isolation,
because
that
connectivity
with
other
people
wasn't
there
so
I,
don't
know
if
it
spoke
about
specific
features,
but
it
did
like
strongly
kind
of
imply.
It
was
something
on
a
lot
of
people's
minds.
H
H
So
it
sounds
like
there's
not
really
like
a
perfect
consensus
on
how
we
move
forward
to
join
Evan.
If
we
wanna
give
her
community
for
a
while
and
see,
maybe
we
can
come
up
with
different
options
rather
than
a
straight
yes
or
no,
because
I
think
it's
a
various
point.
No
one's
gonna
vote.
No,
but
we
keep
yeah,
sorry,
okay,
yeah,
so
we
can
describe
with
some
different
options
on
how
we,
you
know,
try
and
integrate
the
community
into
into
discord.
Yeah.
B
I
would
say
they
found
like.
There
are
a
few
different
options
we
can
take
and
then
within
the
vote
just
add
the
pros
and
cons
of
each
and
then
and
then
we
can
vote
within
the
within
the
voting
gap.
We
don't
it
doesn't
have
to
be
yes
or
no
and
we
can
have
options
cool
great
thanks.
Everyone
will
capture
this
write
up
some
those
shared
and
discuss,
and
then
you
know
publish
this
recording,
so
people
can
view
it
listen
in
kind
of
formulate
their
own
opinions
and
then
we'll
kick
off
the
vote.