►
Description
Discussing design for an MVC to create polls within GitLab issues/MRs.
Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/415232
A
B
No,
not
really
in
fact
well
I,
suppose
I
I
do
and
it's
the
it's
ASCII.
If
that's
the
right
term,
albeit
that
it's
it's
like,
obviously
not
a
very
good
job,
but
just
for,
like
the
so
on
this
issue,
specifically
that
we're
hopefully
going
to
bounce
more
ideas
around
but
I
started
with
or
early
it's
like
Richard
started
with,
because
we
were
set
together,
but
just
just
kind
of
dump
in
like
for
the
tables.
B
A
A
Well,
yeah
I
think
that's
helpful,
I
mean
I.
Think
you
know.
Writing
things
down
in
any
format
is
always
really
clarifying
for
me
in
terms
of
understanding
the
thought
process,
so
whether
Eve,
whether
it's
like
in
a
sentence
or
a
bullet
point
or
in
a
table
like
this,
it's
definitely
a
good
place
to
start
but
I'm
happy
to
to
do
you
want
to
talk
us
through
the
other
thing.
That's
great
is
rubber
ducking
right.
Talking.
B
Absolutely
that'd
be
amazing.
Thank
you.
So
I'll
I'll
give
you
a
tiny
little
bit
on
on
Richard,
because
it
is
his
kind
of
like
his
seed
that
hopefully
he
might
end
up
kind
of
being
able
to
to
build
out.
So
at
the
moment
he
has
like
some
bespoke
bot
type
tall
thing
that
his
organization
have
built,
which
allows
them
to
do
I.
Think
I'd
basically
call
it
like
the
waiting,
like
almost
plan
in
poker
type
situation,
where
it
says
right.
B
C
B
That's
taken,
hopefully,
there's
a
link
to
it
somewhere
on
here,
but
that's
taken
from
another
issue
which
I
think
he's
a
bit
more
a
bit
more
focused
on
the
visualization
aspect
of
the
poll,
whereas,
like
at
the
moment,
we're
not
really
sort
of
too
interested
or
fast
in
that.
But
there's
definitely
this
thought
process
about.
Can
we
extend
scale
whatever
you
want
to
call
it
emojis
in
some
way
to
to
kind
of
become
a
bit
more
of
a
an
official
structured
whatever
you
want
to
call
it
polling
system.
B
A
C
A
I
agree
with
you
that
polls
I
find
myself
doing
polls
in
kitlab
all
the
time
we
were
just
trying
to
organize
the
Meetup
and
people
were
doing.
You
know
it's
a
good
example
yeah
yeah
like
when
what
dates
work
for
you,
what
location
and
the
the
current
mechanisms
we
have
for
that
are
are
kind
of
challenging.
You
just
have
to
usually
comment
and
say,
or-
or
you
can
say
you
know,
reuse.
This
reaction
Emoji
to
mean
this
or
this
reaction.
B
So
you,
it
sounds
like
you've
got
a
bit
of
a
gut,
feel
that
that
may
be
like
emojis
and
reactions
aren't
the
way
to
to
go
okay.
Well,
that
that's
that's
good,
because
it's
on
the
same,
like
the
I
I,
think
I
think
that's
a
really
good
like
driving
into
this
one
of
the
specifics
there,
the
fact
that
we've
only
got
a
subset
over
a
limited
set
of
emojis-
and
you
know
even
just
the
the
I-
don't
know
what
you
want
to
call
it
mental
gym
last.
B
B
The
the
other
kind
of
big
thing
that
I'm
conscious
of,
although
I
know
it
shouldn't,
really
be
one
of
the
top
of
the
list,
but
is
that
you
know
from
my
understanding
I
think:
we've
got
a
table
award
Emoji
in
the
database
and
it's
I
think
it's
got
probably
something
like
the
awardable
type
and
the
awardable
ID.
So
that
can
be
maybe
an
issue,
an
epic,
a
merge
request
or
a
note,
maybe
some
other
things
like
a
snippet
and
then
the
snippet
ID.
B
Now,
if
you
think
of
the
size
of
gitlab.com,
the
number
of
groups
and
projects,
issuables,
awardables,
essentially
I'm,
pretty
sure,
there's
going
to
be
tens
of
millions,
I
mean
if,
if
I
wasn't
too
lazy,
I'd
run
a
quick
query
to
see
how
many
records
there
are
in
that
table.
But
you
know
the
size
of
it
is
going
to
make
it
fairly
unsuitable
to
extend
that
table
in
a
reasonably
simple
way.
So
I've
talked
to
myself
and
hopefully
some
others
away
from
that
idea.
But
yeah
sound,
sound.
Okay,
so
far,.
B
Actually,
you
know
if
we
want
to
do
this,
we
kind
of
really
need
to
move
it
away
from
there.
So
my
gut
feel
is
to
to
step
back
and
kind
of
say.
Well
if
we
were
building
this
from
scratch,
what
would
it
look
like?
Which
kind
of
then
takes
us
to
this
very
poor
ASCII
table
diagram
that
you've
got
in
front
of
you
there
and-
and
you
know
me,
Richard-
were
kind
of
bouncing
the
ideas
around
and
realistically,
as
a
first
iteration
in
my
head.
B
I
feel
that
all
you
really
need
is
I,
don't
know
if
you
call
it
an
entity
or
a
model
or
whatever,
but
this
this
kind
of
whole
object.
That
says
this
is
a
power
it
needs.
It
needs
an
identifier
and
potentially
a
name.
A
description
like
in
future
we'd
like
to
have
like
when
it
opens
when
it
closes.
You
know
all
sorts
of
other
stuff,
but
you
always
need
this
kind
of
entity.
B
Let's
call
it
this
model
now
I've
heard
a
no
ID
on
there,
but
I
I,
don't
know
I,
don't
know
whether
that's
quite
quite
right.
My
thinking
initially
was
well.
If,
if
you
can
add
a
poll
to
a
note,
then
you
can
add
it
to
an
issue.
You
can
add
it
to
a
epic.
You
know
to
a
merge
request,
any
work
item
snip
it.
You
know
pretty
much
the
world
to
your
oyster
there.
B
So
that's
that's
kind
of
just
creating
a
poll
like
forget
about
any
functionality,
but
just
it's
it's
an
object.
I've
created
it
and
it's
attached
to
something.
It's
got
an
identifier,
then
I
feel
like
again
the
simplest,
then
for
the
voting
side
of
things.
The
simplest
thing
would
be
to
oh
yeah
yeah,
let's
just
talk
about
the
table
and
then
we'll
talk
about
the
the
kind
of
quick
actions
or,
however,
we're
going
to
interact
with
that,
but
then
yeah
to
I
think
it
would
be
simplest
to
actually
allow
I.
B
Don't
know
if
you
call
it
like
an
open-ended
poll
like
you
can
you
can
vote
with
whatever
you
want,
so
you
can
say:
Hello
Goodbye,
yes,
no
apple
whatever,
so
it's
it's
not
like
here
are
a
set
of
options.
Choose
one
of
those
options.
It's
open
architecturally.
It
feels
like
the
simplest
solution.
So
you
know,
then,
all
of
a
sudden.
You
need
a
second
table
just
to
link
here's
a
poll
and
then
for
that
poll.
B
This
is
the
vote
and
this
is
who
the
vote
was
from
and
when
the
vote
was
again
can't
immediately.
Think
of
any
but
but
all
of
a
sudden
magically
from
two
tables
you
seem
to,
or
in
my
head
you've
got.
You
know
structurally
what
you
need
to
have
a
poll
submit,
votes
and
and
sort
of
view
those
results.
C
C
B
A
B
If
it
was
I'm
trying
to
think
what
it
would
actually
take,
you
know
what
I
mean,
what
would
it
take
care
of
and
what
would
it
avoid
us
having
to
because,
like
obviously,
we
need
somewhere
to
store
the
data,
so
we're
going
to
need
to
build
the
tables
right,
regardless
of
whether
we
leverage
a
gem
or
am
I
wrong?
Is
there
some
way
that
a
gem
might
avoid
us
needing
to
even
build
out
the
data
store.
C
B
C
A
B
A
Yeah
well,
that's
interesting,
though,
because
there
is
a
world
in
which
we
use
an
external
service.
We
would,
of
course,
have
to
get
approval
to
do
this,
but
maybe
we'd
have
an
API
key
in
that
all
the
poll
data
lives
and
pull
everywhere.
As
an
example,
I
don't
know
if
this
would
be
a
good
choice,
but
and
basically
what
we're
doing
is
we're
just
sending
API
requests
to
pull
everywhere
they're
generating
a
poll.
Maybe
we
just
linked,
maybe
the
MVC
of
that
approach
would
be.
B
Yeah,
that
is,
that
is
an
interest
in
and
I
think
again
that
was
kind
of
not
not
exactly
discussed
on
the
old
issue,
but
the
I
think
again
the
old
issue
was
about
visualization,
so
there
was
an
idea
that
we
might
be
able
to
use
I
struggled
to
think
of
the
name
of
the
things.
Have
you
do?
Have
you
used
Shields
I?
Think
it's
shields.io.
Let
me
just
check.
C
B
Shields.Io,
have
you
used
anything
like
that
before?
No,
so,
essentially,
you
can
put
together
like
a
query
string
and
it
will
just
generate
you
a
badge
so
I.
It's
used
to
generate
things.
You
know
you
know
like.
We've
got
our
pipeline
status
and
our
code
coverage
and
things
like
that.
You
can
use
shields.io
to
generate
those
kind
of
badges,
but
the
cool
thing
is,
you
can
embed
it.
So
let's
say
yeah
I've
got
my
website
on
my
my
git
lab.
Read
me:
I.
B
Can
reference
something
and
I
I,
don't
have
to
kind
of
create
the
image
or
keep
updating
the
image
or
write
any
code
to
do
that
myself
because
there's
a
an
external
service,
so
you
know,
like
you
say,
with
an
API.
We
might
even
just
be
able
to
say
right.
Here's
the
award
Emoji
data,
and
can
you
render
that
into
a
pretty
good
graph
for
me
just
by
sending
using
a
special
URL
but
I
like
I
I?
B
Think,
with
all
these
things,
the
challenge
is
I
I,
suppose
I
could
see
them
as
mvcs,
but
I
don't
know
that
we
could
then
iterate
on
those
without
kind
of
basically
being
like
right
now
blow
throw
this
away
and
now
build
something
in
gitlab.
If
that
makes
it
like,
or
you
know,
throw
this
away
and
now
stop
bastardizing
award
emojis
or
you.
B
C
C
A
A
Would
there
be
a
world
where
and
I'll
just
try
to
show
you
through
a
comment
where
we
created
slash
trans,
it's
like
create
poll
yeah
and
then
the
first
argument
is
like
this
is
my
title.
This
is
my
description
and
then
the
options
are
one
two,
three
four
and
then
what
this
does.
Rather
than
creating
a
pull
object
with
this
these
attributes,
it
actually
outputs
a
new
comment
from
me.
It's
just
a
comment,
object
and
it
just
says:
Like
Jesse
is
creating
creating
a
new
poll.
A
This
is
just
example
of
it
could
be
anything
if
you
and
marks
your
opinion.
Please
vote
for
one
two,
three
or
four
by
responding
to
this
comment
with
wrote,
One
or
whatever
right,
yep,
and
then
what
that
would
do
is
that
would
that
would
leverage
our
existing?
That
would
basically
do
an
emoji
reaction.
A
Now,
how
would
you
map
the
vote
to
an
emoji
that
I
don't
know
so
how
to
map
vote
to
Emoji,
but
the
benefit
of
this
is
just
that
there
would
be
no
additional,
basically
you're,
just
hooking
up
a
slash
command
to
create
comments
for
you
now
you
could
argue
that
is
this
really
saving
us?
Is
this
doing
anything
interesting.
B
Nice,
it's
nice
to
come
up
with
these
ideas
so
and
that
that's
what's
really
interesting.
Is
that
kind
of
describes
pretty
much
how
we
envisage
this
feature,
but
just
in
avoid
not
piggybacking
off
of
the
existing
like
Emoji
structure
table
Etc
I
I
haven't
seen
too
much
resistance
in
the
past
to
kind
of
creating
new
new
tables,
so
I
I,
don't
think
there'd
be
a
big
concern.
B
I
don't
know
all
the
all
the
quick
actions
but
I
think
that
like
create
poll
and
then
maybe
with
like
one
option
like
a
title
or
a
description
or
or
maybe
even
a
sort
of
suggested
list
of
responses
or
something
like
that
is,
is
cool
I.
Think.
Once
you
get
to
multiple
arguments,
you
start
getting
a
little
bit
to
I,
don't
know
what
you
want
to
call
it,
but
you
know
risky
or
or
whatever
you
know
like
spend
times
the
only
one
I
can
think
of
off
the
top
of
my
head.
B
A
B
B
So
you've
really
put
a
message
in
this.
This
is
the
only
argument.
I
guess
I'd
have
that
you
could
write
your
own
message,
so
it
might
not
be
necessary,
but
I
was
thinking
that
yeah.
That
would
convert
it
into
what's
just
below,
which
is
kind
of.
Like
your
your
comment,
your
note,
but
then
just
with
with
kind
of
some
placeholder
that
just
kind
of
says
poll
no
votes
or
you
know.
A
B
And
this
is
this
is
interesting.
Some
people
love
it.
Some
people
hate
it,
but
the
my
thinking
is
that
at
the
moment,
all
we
have
is
multiple
choice.
Yeah
we've
awarded
80s,
essentially
like
that's
the
only
option
you
have
now
in
the
new
world.
We
want
both.
We
want
to
have
open,
but
we
also
want
multiple
choice,
but
the
the
smaller
iteration
is
is
the
open-ended
option
the
to
to
make
it
multiple
choice
like
we're?
B
Gonna
have
to
have
another
table
which
will
store
the
possible
values
and
a
way
to
then
validate
against
that,
and
you
know,
there's
more
complexity.
So
in
my
head,
I'm
thinking
this,
the
simple
initial
stat
is
an
open-ended
one
that
just
kind
of
right.
Okay,
we've
now
got
a
poll
object,
an
entity,
a
model
whatever
you
want
to
call
it,
but
we've
got
no
votes.
Now.
People
can
start
to
use
Quick
actions
to
vote
on
that
poll.
C
C
C
A
B
B
Exactly
and
then
what
I
would
see
like,
so
if
we
want
to
fast
forward
like
a
year
two
years
or
whatever,
then
okay,
first
of
all,
you
can
do
multiple
choice
or,
if
you
want
it
open,
but
you
want
to
avoid
this
issue,
then,
obviously,
once
you've
got
your
power,
there's
obviously
a
UI.
So
once
people
have
started
to
vote,
you
can
see
the
existing
votes
and
you
can
click
on
them
or
there's
there's
an
easier
way.
So
you
know
quick
actions.
B
A
A
C
B
B
B
B
B
But
quick
actions
are
using.
Let's
say
they
use
the
notes.
Api,
it's
not
really
an
API,
it's
the
internal,
the
notes
controller,
essentially
to
send
the
note
and
then
there's
a
service
that
then
processes
those
quick
captions.
Essentially,
so
it
bypasses
the
need
for
like
a
an
API
as
I'm
sure
you,
you
know,
it's
kind
of
has
to
be
well
defined
and
then
versions.
B
You
can
you
can't
just,
whereas
with
these
internal
like
services,
we
can
do
whatever
we
want
with
it,
because
we're
the
only
ones
that
are
kind
of
using
it
and
consuming
it.
It
also
means
actually
that,
if
somebody
wanted
to
build
their
own
front
end
for
this
boat
in
then
they
could,
because
all
they
would
have
to
do
is
create
notes
with
the
quick
action,
if
that
makes
sense.
So.
C
B
They
don't
need
to
use
a
polls
API,
they
can
just
use
our
notes,
API
and
I've
seen
a
tweet
or
something
about
this
recently
like
big
enough,
our
quick
actions
so
much
because
it's
so
powerful
allowing
us
to
you
know,
do
almost
anything
just
by
using
the
notes.
Api
rather
than
having
to
oh
I,
want
to
merge
a
merge
request.
I
need
to
use
this
complex,
API
call
and
I
need
to
understand
it
or
it's
like
well.
No
just
use
slash,
merge
you.
B
We
wouldn't
wouldn't
need
an
I
mean,
don't
don't
get
me
wrong.
I
love,
apis
and
I'm.
Sure
we'd
want
to
build
it
again
fairly
soon
down
the
line,
but
I
see
an
MVC
has
been
possible
with
two
tables
that
I
mentioned
above
and
probably
just
the
two
quick
actions,
one
to
start
the
poll,
one
to
vote
and
a
guess
just
it's
just
how
we
do
visualize
as
I
am
expecting
it
to
be
quite
Rough
Around
the
Edges,
maybe
just
like
in
the
original
note,
that's
created
the
poll.
C
B
Them
as
many
options
as
they
want,
because
what
we
might
do,
based
on
that
suggestion
of
just
having
two
options,
I
think
what
what
the
the
Temptation
would
be
would
be
to
store
those
two
options
in
the
poll
table
and
then
you
wouldn't
that
wouldn't
scale
if
we
were
just
having
right.
Okay,
here's
our
poll,
ID
is:
if
we
wanted
a
title
or
description
I,
don't
think
we
really
need
it
initially,
but.
C
B
Oh
okay,
sorry
yeah,
okay,
so
it
should
just
say
right:
okay,
yeah,
but
but
then
ultimately
I
guess
that's
down
to
the
the
person
crying.
The
pole
can
say
whatever
they
want.
If
they
want
to
say
you
know,
oh,
please
I
have
a
vote
Yes
or
no
or
please
no
either
bowling
or
golf
or
please
vote
with
what,
however,
big
you
think
this
piece
of
work's
gonna.
C
B
B
That
being
said,
my
my
slight
counter
argument
to
that
is
that
if
this
is
done
by
a
quick
action,
then
whoever
kind
of
adds
that
no
can
write
whatever
they
want
in
there
at
the
end
of
the
day.
So
you
know
Jesse
you're
your
example
earlier
here,
perfect
yeah,
so
Jesse
is
creating.
A
new
poll
wants
your
opinion.
C
A
Very
interesting
to
see
one
question
I
had
Lee
in
terms
of
the
implementation
here
is
I
assume
that
when
I
respond
with
Slash
vote
per
like
here,
that's
gonna
update
I.
Just
you
saw
me,
as
you
heard
I
added
this
to
the
comment,
so
is:
would
that
be
the
plan
that
we
would
use
the
current
users
kind
of
session
to
update
the
original
comment
created
by
the
pool
Creator?
So.
B
So
this
this
is
I'm
really
glad
you
asked,
because
I
probably
would
have
forgotten
about
this
bit,
but
the
the
kind
of
maybe
the
hardest
decision
but
I
could
be
completely
wrong.
So
we've
got
two
simple
tables:
we've
got
two
simple,
quick
actions
and
the
only
thing
where
they're
missing
is
actually
rendering
something
right.
So
how
do
we
render
it?
So
my
I've
got
a
couple
of
ideas
in
my
head
and
I
probably
need
to
have
a
bit
more
of
a
look
at
how
we
currently
what
references
look
like.
B
B
Is
it
called
like
Banzai
or
Bonsai,
or
something
that
the
the
engine
will
just
when
it
renders
when
it
passes
the
the
no,
it
will
see
the
reference
and
it
will
then
explode
it
if
that
makes
sense,
and
it
will
say.
Oh,
this
is
pole,
one
two
three
four
five
go
and
grab
the
results
for
that
pole
and
and
render
that
text.
So
we
never
actually
need
to
update
the
Note.
A
B
Right,
but
even
that
is
being
rendered
magically
right
because
you
typed
in
the
URL
and
it's
not
just
rendering
the
URL,
it's
actually
rendering
the
reference
I
think
we
call
it
is
that
yeah
exactly
so,
that's
still
being
passed
so
yeah
exactly
and
I've
I've
not
really
dug
into
that.
But
I
hope
that
that's
a
fairly
extendable.
The
fact
that
we
already
allow
references
to
Milestones
to
epics
to
issues
merge,
there's
a
lot
of
different
referenceables.
B
See
them
I
see
the
most
flexible
being
able
to
attach
it
to
and
no,
but
that
being
said,
I
don't
know
if,
if,
if
you
make
it
a
sort
of
a
I,
don't
know
what
you
call
it
like
a
markdown,
a
bonsai,
a
Banzai
thing.
It
might
be
that
it
can
be
in
a
note
or
a
description
because
they
all
use
the
same
password
the
same
renderer.
B
So
maybe
it
doesn't
matter,
but
my
yeah,
my
thinking
was
that
you
could
have
a
lot
of
friends
on
a
merger
Quest
or
an
issue
and
like
like,
for
example,
this
issue
that
we're
talking
about
today,
right
I,
might
ask
you
to
vote
on.
Should
we
have
multiple
choice
as
the
first
iteration,
or
should
we
have
like
open-ended
is
the
first
iteration
that
might
be
one
poll,
but
then
I
might
have
another
poll.
That's
like!
Oh
should
you
know
you
know,
is
quick
actions,
an
acceptable
first
step
or
or
do
we
need
to?
B
So
it's
very
horrible
and
messy
to
try
and
understand
whether
an
issue
is
related
to
a
merge
request
and
vice
versa,
because
you
have
to
use
this
Bonsai
rendering
thing
to
basically
pass
text.
So
that's
like
in
my
head,
I
think.
Maybe
I
want
to
try
and
make
sure
there's
some
easy
mechanism
of
actually
relating
the
the
the
poll
to
a
note
or
an
issue
or
or
something
even
if
we
don't
need
it.
B
C
That's
okay:
it's
actually
I'm
a
bit
confused
here.
I,
don't
I
mean
I'm,
not
even
it's
getting
difficult
for
me
to
imagine
how
it
will
work.
It's
like
in
an
issue
in
a
comment.
We
would
try
and
use
a
quick
action
and
create
a
poll
with
the
text.
As
a
reply,
I
can
vote
to
that
particular
comment.
As
Slash
vote,
I
can
reply
and
the
my
vote
will
be
recorded.
B
C
B
B
So
if
you
vote
and
there's
already
a
record
in
there,
we
can
maybe
use
upset
or
something
like
that.
So
it
would
insert
a
new
record
if
you
haven't
voted,
but
if
you
have
already
voted
it
would
update
your
vote.
So
again
we
could
almost
get
that
for
free
without
having
to
kind
of
build
this
specific
new
mechanism
to
update
votes.
We
could
just
say
well
if
someone
votes
and
they've
already
voted,
let's
just
update
their
vote.
C
A
One
question
I
had
and
I:
don't
know
if
any
of
us
know
the
answer
to
this,
but
in
terms
of
I,
think
it's
very
clever.
The
idea
of
using
Bonsai
to
expand
basically
there's
an
object
somewhere
in
the
database,
we're
going
to
use
this
tool.
We
already
have
called
Bonsai
to
expand
the
reference
to
that
to
just
kind
of
render
it
visually
I'm,
not
aware
of
any
other
resources
that
we
referenced.
That
don't
have
like
a
view
like
a
like
a
that
aren't
URLs
right.
So
this
wouldn't
be
a
hyperlink.
A
B
C
B
You
don't
have
to
put
a
hyperlink
in
the
the
the
the
the
Bonsai
or
whatever
it
is,
is
intelligent
enough
to
say.
Oh
something
with
a
hash
at
the
beginning
is
a
reference
to
an
issue.
Something
with
an
exclamation
mark
is
a
reference
to
a
merge
request.
Something
with
an
ampersand
is
an
epic
and
we've
actually
I
didn't
realize
how
many
of
these
we've
got,
but
we've
pretty
much
run
out
of
special
characters.
Now
so
really.
B
A
A
B
B
C
B
B
That's
that's
definitely
so
I
I
kind
of
I
got
distracted
halfway
through
giving
Richard's
use
case.
So
Richard's
got
this.
This
bot
that
they've
built
in
some
other
like
chat
platform.
That
does
a
couple
of
things
so,
first
of
all,
yeah
they
start
about
I
think
they
can
set
the
end
time
from
the
beginning.
B
B
C
C
B
It
would
have
a
closed
date
and
if
the
closed
date
has
passed
or
if
it's
now
or
something,
then
it
would
render
the
power.
If
it
was
in
the
future,
then
it
it
would
just
render
a
placeholder
to
sort
of
say
you
know
whole
still
open
or
whatever.
But
again
that's
I
I
think
that
I
I
really
see
a
nice
small,
easy
two
tables.
Two
quick
actions
looks
a
little
bit
messy
very
rough
around
the
edges,
but
does
the
job.
And
then
it's
like
right.
B
B
Maybe
even
you
know
what
you
were
kind
of
alluding
to
there
Jesse
about
holes
needing
links
or
not
sorry
about
references
normally
having
a
hyperlink,
maybe
even
in
some
World
there
will
be
a
a
place
in
the
system
where
you
can
go
to
polls
and
it
will
kind
of
link
you
to
the
poll
and
the
poll
like
the
comment
or
the
the
issue
of
all
or
whatever
you
know,
whatever
The
Works,
your
oyster
right.
Once
you
build
the
first.
C
A
A
I
was
the
abuse
board
is
more
just
like.
Are
people
just
gonna
pop
in
and
like
vote
on
whatever
and
kind
of
leave,
because
the
voting
in
this
MVC
and,
of
course,
maybe
we
shouldn't
worry
about
abuse
for
mvcs,
but
it
like.
If,
if
the
vote,
it's
a
person
who
plays
the
vote
is
somewhat
invisible
in
this
MVC.
B
So
yeah,
that's
that's
interesting!
So
almost
like
we
need
to
because
when
you
sorry
someone
gets
blocked
or
abuse,
then
all
of
that
like
comments
and
issues
and
other
things
all
kind
of
I,
don't
know
if
they
get
deleted
or
they're,
just
invisible
or
maybe
probably
get
deleted.
So
we
should
sort
of
try
and
tie
into
whatever
mechanism
is
behind
the
scenes
there.
C
B
B
B
A
B
A
A
Exactly
native
definitely
feels
better
like
when
I
did
that
with
some
friends
we
were
trying
to
do.
You
know
the
Doodle
for
coming
up
with
a
shared
date
to
do
something.
Oh
yeah
I
use
that
I
use
that
yeah
yeah.
Absolutely
I
worked
on
a
version,
something
very
similar
to
that
like
10
years
ago
for
Microsoft,
so
terrible,
sorry
Microsoft,
it
was
just
it
was.
It
was
an
example
app.
They
were
trying
to
show
like
what
cool
things
you
could
do
by
using
Yammer
oauth.
A
B
So
I
I
I
didn't
immediately
know
what
the
Twitter
spouse
look
like
so
I,
just
Googled
and
yeah.
It's
quite
a
nice
simple.
You
know
bar
graphy
type
thing
right,
the
the
word
overlaid
on
the
what's
it
and
then
the
percentage,
the
only
thing
I've
seen
and
it's
good,
because
we've
got
the
existing
issue.
B
The
old
one
from
six
years
ago
he's
very
much
talking
about
the
visuals,
so
I
think
we've
got
like
quite
a
lot
of
that
conversation
captured
there's,
there's
a
definite
fun
and
games
that
someone's
gonna
have
when
they
come
to
do
that
because
of
like.
Oh,
if
something's
like
got
very
few
votes
and
the
text
doesn't
fit
inside
the
bar
and
all
those
kind
of,
but
hopefully.
A
A
B
Something
well
again,
I
really
like
the
idea
of
flexibility.
You
know
like
let's
extend
this
and
you
know.
One
thing
you
can
have
is
that
a
pole
is
complete.
It
will
always
remain
anonymous.
You
know
that
you
can't
see
who's
voted
on
what,
unless
someone
self-hosted
and
looks
in
the
database,
you
know
but
yeah
I
I,
that's
what
I
I
like
about
this.
You
know
I
I,
don't
see
any
kind
of
like
oh
well.
We
wouldn't
be
able
to
do
that.
Well,
yeah,
but
eventually
you
know.
B
If
someone
wants
that
hard
enough,
then
hopefully
they
can
bring
it
to
the
table.
One
of
one
of
the
challenges
I
see
I,
think
this
all
living
in
in
Gabe's
Kingdom,
so
I've
already
ping
Gabe,
like
it
just
feels
kind
of
plan-ish,
but
sometimes
these
things
are
a
bit
like.
Well,
you
know
a
poll
is
just
as
valid
on
a
merger
Quest,
so
you
know
it
sometimes
would
be
hard
to
find
like
dris
and
owners,
and
but
you
know,
from
working
with
Gabe
in
the
past.
A
C
A
B
Yeah
yeah,
no,
no
you're
right,
there's
definite
yeah
that
I
guess
one
of
the
things
and
yeah.
Forgive
me
because
I
know
we
do
need
to
drop
in
a
second,
but
one
of
the
challenges
might
be
actually
that
we've
then
got
almost
two
ways
of
of
voting
and
like
do.
We
want
to
try
and
move
people
away
from
using
reaction.
Do
you
know
what
I
mean
like
yeah.
B
No,
no
I,
guess
I!
Guess
it's
it's
kind
of
trying
to
be
like
right.
Okay,
remember
what
emojis
were
originally
for:
okay,
they,
they
were
for
kind
of
expressing
a
reaction
right.
Okay.
This
makes
me
happy.
This
makes
me
sad,
like
I
love.
This,
like
I'm,
excited
about
like
yeah,
a
reaction
as
opposed
to
like
do
you
want
option,
one
two
or
three
so
I
think
like
a
thumbs
up
or
thumbs
down
on
like
a
feature
request
or
something
like
that
or
a
plus
one,
maybe
to
be
like,
oh
yeah.
B
This
affects
me
as
well
like
those
kind
of
things
good,
but
when
you
start
stretching
it
a
bit
bit
further
yeah
that
that
I
I
feel
like
there
might
be
this
weird
transitional
kind
of
get
like
how
do
we
tell
people
that
this
feature
exists
and
how
do
they
choose
to
use
this
feature
rather
than
just
using
the
Emojis
instead
kind
of
thing?
Okay,.
A
B
Now,
obviously,
it's
always
interesting,
say
other
implementations
and
I
guess
they're
not
as
open
as
we
are
so
I
wouldn't
be
able
to
see
how
it
works
behind
the
scenes,
how
the
data
structured
Etc
but
yeah.
Although
saying
that,
if
it
uses
a
third-party
tool,
then
maybe
that
information
would
be
available.