►
Description
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/uM4ZWDjNfK
or say hello on Telegram https://t.me/tecommons
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: https://twitter.com/tecmns
Learn more http://tecommons.org/
A
Okay,
let's,
let's
go
welcome
everyone.
A
A
None
of
the
developers
even
near
the
server,
so
we
have
still
haven't
been
able
to
figure
out
what
happened,
but
we
assumed
that
we
assume
that
the
best
hypothesis
is
that
the
server
security,
the
server,
wasn't
secure
enough
and
then
somehow
some
like
one,
automated
internet
bot,
looking
for
open
ports
or
whatever
found
an
open
port
and
somehow
got
snuck
in
and
did
some
damage.
A
We
have
the
the
new
praise
board
is
up
and
running,
so
we
can
do
a
short
demo
of
it.
The
the
demo
that
we
weren't
able
to
really
complete
last
week-
and
I
and
me
and
nebs
maybe,
can
talk
a
little
about
what
we
have
been
up
to
in
the
praise,
backing
and
front
end
and
we
have
continued
quant
preparation,
so
a
trial
quant
preparations,
and
we
can.
A
We
also
should
talk
about
the
first
real
quant
preparations
like
scheduling
this
source
credit
ram
sessions
that
you
highlighted
in
the
chat
and
as
well
as
maybe
not
setting
a
date
for
the
first
real
quant,
but
at
least
starting
to
talk
about
it
yeah
and
we
sort
of
started
a
new
work
stream
noggin
and
ms
and
me
called
the
the
praise
revision
where
we
look
over
clean
up
the
praise
data
from
from
discord,
because
some
huanka,
for
instance,
has
his
phrase-
has
hasn't
been
registered
by
the
bot.
A
B
Yeah
sure,
first
of
all
I
do
have
a
question:
can
we
use
the
current
deployed
version
or.
B
So
the
new
players
bot
uses
these
things
called
slash
commands
which
give
you
this
neat
ui
when
typing
command,
which
are
slightly
more
user
friendly
than
the
previous
text.
And
you
know
these
have
some
form
of
separation
of
concerns
because
the
fields
are
separated
because,
like
what
used
to
happen
previously
was
people
could
do
write
messages
and
they
can
mention
anyone
anywhere
and
they
would
get
praise
like
something
like
this
random
stuff.
B
And
you
know
this
is
really
hard
to
pass
and
sometimes
they'll
say
for
reason,
and
sometimes
they
wouldn't
put
the
four
in
there.
So
this
was
really
hard
to
parse
and
clean
up,
and
you
know
if
you
look
at
the
generated
csv
files
that
we
had.
Some
of
them
still
had
issues,
and
you
know
there's
there
was
some
missing
stuff.
B
There
was
some
weird
formatting
going
on
and
like
if
we
had
that
in
our
place,
ui
that
would
just
look
weird
and
wouldn't
be
as
clean-cut
as
it
is
right
now,
so
this
has
separated
it
out
now.
This
is
this:
is
a
receiver's
field.
B
It
says
mention
the
users
you
would
like
to
send
this
place
to.
So
I
just
place
christopher
and
I'll
praise
nebs.
That's
here,
never
mind
and
yeah
I'll
give
to
give
a
reason
for
stuff.
That's
the
reason.
B
A
B
Isn't
activated,
I
can't
place
anyone.
I
need
to
use
the
press
activate
command.
Okay,
let's
use
that
command
this
activates
your
place,
accounting
links
for
each
address.
Okay,
there
you
go
okay.
This
is
just
a
link
that
I
click
and
you
I
get
addicted
to
the
ui
for
it.
But
one
thing
is
that
this
is
a
private
message.
B
No
one
else
in
the
server
would
be
able
to
see
this,
so
this
link
is
secure
and
this
link
isn't
in
dms,
which
is
an
added
benefit,
like
usually
people
don't
like.
If
the
bot
randomly
dm
someone,
people
have
a
tendency
of
not
noticing
but
yeah
that
you
can
you
get
the
link
instantly
and
it's
private.
No
one
else
can
cricket
and
let
me
just
turn
this
message.
A
B
The
place
was
registered
and
christopher
would
have
got
a
dm
saying.
You
have
received
praise.
One
thing
that
I'd
like
to
highlight
is:
you
know.
Usually
people
had
a
tendency
of
you
know.
They'd
mention
a
couple
of
people.
B
And
they
eventually
they'll
do
this
and
there's
someone's
name
written
there,
but
it's
not
actually
a
mention,
and
this
usually
happens
when
someone
is
not
present
in
our
discord.
Previously,
this
used
to
cause
some
issues
with
the
you
know
reason
and
it
looked
weird.
The
text
looked
weird
because
then
the
reason
would
have
this
mentioned
and
then
whoever's
quantifying
the
place
has
to
lick
up.
If
this
person
has
something
to
do
with
the
reason
given
here.
B
But
the
current
version
just
lags
it
out.
You
can't
see
it
right
now,
but
in
the
back
end
it's
flagging
it
out.
So,
for
example,
instead
of
mentioning
someone
who's
valid
I'll,
just
do
this
and
write
some
random
reason.
This
would
get
flagged
and
it'll
say
the
command
requires
at
least
one
valid
receiver
to
be
mentioned,
and
that's
undefined
receivers
in
future.
This
would
have
like
more
sophisticated
logs
inside
the
server
so
that
we
get
like
updated.
B
You
know
whoever
is
like
the
guide
or
whoever's
the
who
are
the
people
managing
the
reward
system,
for
whichever
group
would
have
an
eye
on
things
like
they
would
be.
It
would
be
more
accessible
to
look
up
logs
and
yeah.
That's
the
plan.
B
Yeah
yeah,
so,
okay,
we
send
it
as
a
personal
message
in
their
dm.
That's
what
you're
talking
to
right.
C
B
C
B
A
B
One
thing
we
could
do
is,
I
think
the
the
president
version
is
slightly
extensive.
It
doesn't
need
to
be
that
long.
B
So
what
we'll
do
is
like
make
it
more
brief
to
the
point
saying
what
what
went
wrong
and
what
was
the
message
you
typed,
and
this
the
more
detailed
message
would
go
to
the
actual
bot
logs
instead
of
in
here,
so
that
that
would
like
ensure
that
it
doesn't
clutter
up
the
channel,
but
also
everyone
would
be
aware
that
what
what
was
the
issue
there
and
anyone
could
help
them
out
fix
it
get
submitted.
A
Yeah,
we'll,
let's
massage
these
messages
until
they,
they
look
and
feel
feel
right.
So
there
I
guess
there
is
some
balance
there,
not
making
the
messages
too
big,
because
that
if
a
lot
of
people
have
they,
everyone
needs
to
activate
their
account
before
the
first
time
they
praise.
So
my
guess,
it
would
be
that
that
would
would
be
quite
a
lot
of
you
haven't
activated
your
account
messages,
clogging
up
the
channel,
but
we'll
we'll
see,
and
these
things
are
easy
to
modify
as
we
as
we
go
along.
C
Yeah,
this
looks
incredible
why
those
are
issues
that
I
didn't
even
dream
that
they
would
ever
be
solved.
It
just
felt
like
the
types
of
things
that
we
would
always
have
to
deal
with,
especially
that
message
for
inviting
people
for
the
orientation
call
and
saying
that
they
should
reach
out
to
a
steward.
I
think
that's
super
helpful.
A
Yeah,
and
also
now
we
have
a
bi-directional
setup,
so
the
the
the
the
bot
can
can
react
to
stuff
happening
in
the
in
the
back
end
in
the
in
the
price
server.
So,
for
instance,
we
one
thing
that
came
up
with
this
is
not
implemented
yet,
but
it's
a
it's
a
candidate
absolutely
for
for
a
feature,
good
candidate
for
a
new
feature
which
would
be
to
if
either
flag
a
message.
A
Two
would
be
flag
it
as
vegan
ask
for
a
clarification
and
the
bot
would
reach
out
to
the
original
praise
giver
saying
you
need
to
clarify
this
praise,
please
reply
to
this
message
and
and
that
that
reply
would
be
connected
to
the
original
praise
amended
to
it
so
helping
the
quantifier
to
do
a
good
quantification.
A
B
I
think
we
can
move
on
to
place
something
back
and
if
anyone
has
any
specific
comments
about
changing
the
content
of
the
messenger,
adding
more
detail
feel
free
to
like
send
send
a
message
in
the
reward
system
chat
channel
so
that
I
can
customize
those
things.
B
That's
for
sending
place
you
need
to
activate
for
sending
place,
but
I
don't
think
we
need
anyone
to
be
activated
to
receive.
A
We
want
to
have
the
ability
to
praise
people
that
that
are
only
loosely
connected
to
the
tec.
They
have
to
be
in
the
on
the
on
the
server
and
so
that
that
rule
is
the
same
as
before.
You
need
to
be
on
the
discord
server
so
that
we
can
praise
you,
but
you
don't
have
to
have
your
account
activated
or
anything,
but
you
will
get
notified
that
you
have.
You
have
received
praise
and
in
order
for
you
to
receive
your
your
your
token
payouts.
A
A
Yeah
sort
of
partly
that
and
and
we
also
need
everyone
to
sort
of-
we
need
to
get
them
into
the
the
pray
system.
So
we
can,
we
can
do
the
payouts.
Finally,
and
and
if
you
could
praise
without
having
your
account
con
connect,
then
we
would
have
to
have
some
other
kind
of
system
in
place
to
remind
people,
maybe
after
a
quantification,
don't
remember,
don't
forget
to
activate
your
account,
but
why?
If
you
want
to
get
payouts,
we
have
to
do
that
for
for
everyone
that
receives
praise
but
yeah.
It.
A
I
have
been
working
on
fixing
a
few
of
the
bugs
that
we
identified
during
the
trial
quant,
so
that
was
some
stuff
that
is
not
visible
now,
because
it's
fixed,
mostly
the
the
the
the
tables,
became
too
wide.
The
text
became
wider
than
the
the
sort
of
the
box
around
them.
That
is
fixed
and
we
have
new
quantifications
sliders
that
work
work
really
well
and
look.
A
A
Yeah,
so,
let's
feel
feel
this
out
a
bit
and
see
what
we
like
the
the
new
sliders
and
they-
and
this
also,
the
the
horizontal
navigation
between
pages
between
receivers,
now
work.
Well,
so
the
sliders
update
and
overall,
I
think
it
feels
really
smooth
and
nice
now
what
else
in
the
front
end.
A
I
think
that
is
the
the
major
thing
done
in
the
front
end
nebs,
can
you
say
so
a
few
words
about
back
end
work.
D
A
So
the
general
idea
for
the
back
end
and
the
front
and
just
now
is
to
to
turn
this
alpha
version
into
a
sort
of
a
stable
beta
version.
So
we
we
try
to
add
as
little
new
functionality
as
possible
so,
for
instance,
the
the
the
setting
page
that
looks
a
bit
half
baked.
It
will
still
remain
half
baked
because
that
is
not
vital
for
us
to
continue
doing
trial,
quants
or
real
quants.
A
For
that
matter,
it's
mostly
a
question
of
looks,
and
instead
we
will
focus
on
on
making
the
system
stable
so
that
we
can
as
start
using
it
basically
and
and
then
the
main
big
feature
that
we
would
like
to
add
before
in
offering
the
system
to
to
giveth
and
common
stack
as
well
would
be
the
the
praise
by
proxy
feature,
but
other
than
that
which
will
be
mostly
polishing
stability,
stuff
and
making
sure
it's
we'll
have
a
look
over
the
whole
server
installation
so
that
the
whole
package
is
like
really
works,
solid
and
runs
smoothly.
A
E
I
mean
I
was
gonna
set
it
up
today
to
put
out
another
test
quant.
I
think
there's
like
what
seven
or
eight
people
that
have
signed
up
for
it,
so
we
might
have
to
play
around
with
the
settings,
but
it'll
be
cool.
I
think
I'll
do
it
after
this
call,
if
it
sounds
all
right
and
then
just
leave
it
open
for
the
rest
of
the
week.
E
A
Cool
and
if
we
talk
a
little
bit
about
prep
for
for
the
next,
like
the
the
first
real
quant,
we
need
to
schedule
the
the
source
cred
or
the
the
shortcut
and
praise
params
setting
session.
D
Hey
guys
hi,
there
is
no
broker.
I
think
that
we
should
decide
a
time
to
meet
and
basically
we
would
be
doing
the
same
that
we
did
last
year
among
the
people
in
the
committee,
so
I
would
explain
we
can
use
the
same
post
like
before.
People
will
read
it.
I
would
like
show
the
interface
and
kind
of
explain
what
those
number
means,
because
they
can
be
a
little
bit
tough
to
understand
at
first
and
after
that
we
should.
D
We
just
like
be
picking
a
certain
numbers
and
if
anyone
has
like
no,
we
should
be
doing
this
number
a
little
bit
larger
or
shorter.
That's
that's
going
to
be
like
the
big
debate
that
that
was
what
happened
last
year.
Essentially,
and
this
time
it
would
be
a
little
bit
longer
because
we
are
adding
discord
to
the
to
the
parry.
So
last
time
we
only
use
this
course
and
on
github
so
yeah.
I
think
that's
it
it's
it's
only
about
gathering
all
the
people
and
I'm
making
that
debate.
D
A
Count
discord,
interactions
or.
A
B
Yeah,
though
we
would
still
need
the
plugin
to
be
installed
and
running,
we
would
we
just
wouldn't
count
any
of
the
messages
or
write
anything
any
great,
but
we,
the
plugin,
would
be
existing
because
we
need.
We
need
the
identities
to
be
managed
by
that
plugin
instead
of
our
plugin.
A
And
it
it
seems
like
the
like,
has
set
the
parameters
for
for
that.
For
for
us
he
he
made
some
changes,
if
I
recall
correctly
to
he,
he
said,
set
all
all
values
that
could
be
set
to
zero
to
zero.
So
basically
it
doesn't
count
any
score.
A
But
mateo-
and
I
guess
this
would
be
an
invite
that
goes
out
to
the
whole
reward
board.
A
Yeah,
perhaps
it's
would
be
best
to
do
a
what's.
It
called
the
doodle
and
suggests
like
a
few,
a
few
dates
so
that
it's
we
allow
everyone
to
participate
or
as
many
as
possible.
Could
you
could
you
do
the
invite.
D
No,
I
think
it
was
3
p.m.
Europe
time.
C
E
Yeah,
I
I
think
they're
all
here,
zep
just
asked
me
now
and
I'm
trying
to
remember
whose
name
is
what
address.
A
Would
we
need
or
want
to
do
this
as
some
sort
of
formal
can
we
do
do
reward
board
votes.
C
C
C
A
We
were
discussing
if,
if
we
should
try
to
have
get
someone
from
from
source
credit
to
join
in
on
this
meeting,
or
do
you
feel
confident
that
you
have
the
knowledge
required
to
to
guide
us
through
setting
the
parameters.
D
Yeah,
I
think
I
can
do
it,
but
I
also
would
like
to
talk
with
the
same
people
that
helped
me
last
time,
so
maybe
they
have
like
new
advices
or
something
to
that.
We
should
know
because
it's
been
a
while
it's
been
like
a
long
time
for
now
and
they
they
should
have
more
knowledge
now.
D
So
if
we
can
have
someone
that
that
would
be
amazing,
but
it's
not
needed.
I
just
can't
contact
anybody
else.
A
But
then
it
feels
like
to
to
schedule
it,
for
tomorrow
feels
a
little
bit
too
too
short
notice
for
you
to
be
able
to
talk
to
some
some
source
credit
people.
Maybe
we
should
schedule
for
for
next
thursday.
Instead
that
time,
yeah.
D
Oh
wait
no,
never
mind
if
we
can
change
the
hour.
That
would
work
for
me.
D
A
Make
a
doodle
for
for
like
yeah
for
thursday,
thursday
friday
next
week,
then
perfect.
A
E
A
A
We
don't
need
to
set
the
source
credit
premise
for
for
us
to
do
the
first
page
quant,
but
we
need
to
do
this.
This
run
of
this
trial,
quant
again
and
hopefully
nothing
big
comes
up.
So
then
we
could
say
that
the
system
is
good
enough
to
to
use,
because,
as
long
as
we
have
up
backups
on
on
the
quant
data
that
we
do,
then
the
data
is
good,
even
if
like
ui
bugs
and
other
stuff
would
would
appear.
A
A
But
the
general
perception
of
doing
that
the
first,
the
this
first
failed.
The
trial
quant,
I
think,
was
that
that
quantifying
a
full
month
birth
of
data
that
went
fairly
quickly.
Wouldn't
you
say
so,
would
it
be?
A
It
all
depends
on
how
many
how
many
quantifiers
we
think
that
we
can
on
board
for
for
a
a
real
quant.
If
we
believe
that
we
can
on
board,
have
30
quantifiers
for
for
the
real
quantification
as
well,
then,
if
it
would
be
the
double
amount,
then
each
quantifier
would
have
to
quantify
somewhere
around
400
place.
A
A
E
No,
I
was
saying
like
I
was
curious
because
I
quote
we
quoted
saying
it
would
take
one
to
two
hours
bi-weekly
for
for
regular,
regular
quantification,
so
I
even
think
like
it,
wouldn't
take
people
four
hours
to
do
a
month's
worth
of
worth
of
praise.
I
think
it
would
take
less
than
that,
so
I
go
ahead.
Libby.
C
E
Well,
we
can
always
modify
some
stuff
like,
however,
many
quantifiers
need
to
quantify
each
praise
set,
and
you
know
we
can
always
onboard
more
quantifiers
if
we
need
to
like.
Maybe
we
need
40
or
50
in
the
end,
but
I
think,
based
on
what
we
saw
like
that
was
all
of
november,
that
we
did,
and
I
think
you
could
push
it
out
on
the
cnn
or
yeah.
A
Either
way
we
we
we
planned
this.
However,
we
planned
this.
A
We
still
have
eight
months
worth
of
praise
to
to
work
our
way
through
until
we
get
back
to
to
present
day
and-
and
that
is
that
it's
a
lot
of
praise
and
if
we
so,
if
we
were
to
quantify
a
month
worth
of
praise
every
two
weeks,
it
would
take
us
16
weeks
to
to
get
back
to
the
present
day
if
time
stopped,
and
it
doesn't
so,
then
we
will
also
that,
because
that
is
also
for
four
months,
so
it
would
take
us
like
a
half
a
year
or
something
to
get
back
to
present
day.
F
I'm
for
larger
batches
of
the
beginning.
I
think
it's
since
we're
starting
the
system.
There
will
be
probably
more
motivation
and
we
can
get
through
through
that
quickly
and
test
the
system
with
that
and
then
once
we
have
catched
up
it
will
ask
significantly
less
time
of
people,
because
I
don't
think
we
have
so
much
praise
into
in
14
days.
C
B
Like
I
don't
know,
it
just
feels
a
bit
weird
the
way
putting
it
forward
that
you
know
we
have
this
excess
phrase
and
the
first
batch
gets
reviewed
by
people
that
are
being
paid
by
the
common
stack
and
that's
the
incentive.
So,
like
current
people
want
to
sign
up
for
that
and
quickly
be
done
with
it,
and
you.
A
F
I
think
if
it,
if
it's
necessary,
I
do
think
it's
a
good.
It's
a
good
chance
to
like
kind
of
dog
food,
our
system
through
this
backlog
and
and
try
to
use
the
system
how
we
designed
it
and
see
what
what
works
and
what
not,
instead
of
just
you
know,
setting
something
apart
and
doing
having
a
small
group
of
people
quantifying
everything
again,
which
was
an
issue
in
the
past.
Just
you
know,
do
what
we
are
designing
and
if
it
takes
a
bit
longer,
then
it
takes
one
extra
month.
A
Yeah
we're
taking
the
opposite
route,
so
sort
of
to
try
to
onboard
as
many
quantifiers
as
possible,
and
you
know
make
it
a
wide
community
effort
and
like
now,
everyone
needs
to
help
out
and
yeah,
because
then
the
the
results
would
be.
It
would
be
hard
to
question
the
results
in
that
in
if
we
had
a
really
a
lot
of
quantifiers
involved.
B
F
A
Yeah,
that's
true,
you
get
you
get
paid
for
quantifying.
It
won't
be
a
huge
amount.
I
guess,
but
but.
A
Okay,
so
that
maybe
we
should
close
this
discussion
for
now.
We
won't
don't
need
to
make
us
so
hard
decision
here
here
now,
but
I'll
have
we'll
look
at
recording
and
make
sure
some
some
notes
and
then
we'll
I
will.
A
F
Yeah,
well,
it
seems
huanka
brought
up
the
the
issue
that
some
of
his
praise
wasn't
getting.
F
So
I'm
going
to
look
into
it
and
yeah
try
to
figure
out
what
happened
if
it
has
happened
more
times
at
the
first
glance,
it
doesn't
seem
to
be
something
that
has
happened
a
lot
but
we'll
yeah
we'll
try
to
we'll
just
pull
all
the
discord,
chat,
history
and
kind
of
compare
it
to
the
the
excel
file
we
have
from
the
from
the
bot
and
see
if
there
are,
if
there's
something
missing
and
yeah,
and
probably
also
do
some
formatting
changes,
because
some
usernames
would
get
picked
in
as
the
reason
if
the
username
has
a
space
in
it,
it
stayed
inside
the
reason
and
not
just
as
the
as
the
crazy,
even
though
the
praise
got
correctly
quantified
or
saved
so
yeah.
F
We
immediately
just
ordered
the
data
and
clean
it
up
a
bit
to
prepare
it
for
the
for
the
quantification
and
we'll
do
that
in
a
separate
repo
where
we'll
have
like
as
transparent
as
possible,
like
this
is
original
data.
This
is
the
raw
info
from
the
discord.
These
are
the
differences.
A
Thanks,
no,
I
I
think
it
will
be
great
for
for
transparency
and
and
to
avoid
a
new
praise
magette
and
to
really
have
focus
for
focusing
on
transparency,
showing
people
that
you
here
you
have
all
the
source
data
here.
Clearly
in
this
github
repository,
it
cannot
be
tampered
with
without
seeing
it
and
etc.
A
D
A
Yeah,
let's
try
to
find
a
new
time
and,
and
then
the
the
remaining
work
streams
are
mostly
put
on
pause,
the
source
credit,
the
meeting
tracker,
but
it's
a
little
bit
on
pause
now.
I'd
say
since
vivab
works
on
the
the
prey
spot
and
it
that
feels
more
important.
A
B
Mostly
on
play
spot
but
I'll
try
to
squeeze
squeeze
it
in
because
mostly
it's
set
up
stuff
that
should
be
done
and
testing
it
out,
but
but
yeah
I
had
a
sync
with
has,
and
I
do
know
what
to
do
now
so
like
I
could.
Maybe
if
I
had
time
I
can
just
mess
around
with
it
and
see
if
it
works
and
yeah,
then
I'll.
B
Maybe
contact
has
and
get
all
the
things
figured
out
that
if
the,
if
there's
any
errors
inside
source
chris
internals
with
what
I'm
doing
or
is
it
like,
writing
the
great
prop
properly
and
after
that,
I
think
it
would
be
good
to
go.
C
C
D
C
Enough,
that's
so
weird,
okay,
I'll
post
this
document
in
the
chat
and
maybe.
C
C
I
was
thinking
just
this
quite
the
session
that
we'll
have,
after
the
quantification,
for
tweaking
the
praise
and
just
having
insights
in
general,
so
always
having
a
note
taker
in
the
beginning.
So
we
can
share
all
of
this
in
the
forum
every
time
and
then
this
would
be
more
or
less
the
structure
to
start
with
questions
and
then
open
the
dashboard
and
compare
results,
especially
looking
for
extremes.
So
if
one
per
like,
if
if
three
people
quantified
the
same
person
and
one
person
gave
like
zero
to
something
that
another
person
gave
144
like-
why?
C
C
So
we
were
thinking
in
the
research
group
of
how
it
would
be
amazing
to
have
the
tea
flower
being
categories
for
where
contributions
fill
in.
So
we
would
have
an
understanding
of
what
types
of
expertise
are
in
the
community
and
we
could
attach
subject
matter
experts
based
on
the
contributions
they
have.
C
But
that's
a
another
point
that
can
be
discussed
more
like
it
would
require
some
time
it
would.
It
would
be
for
the
v2,
but
we
could
start
implementing
something
in
this
sessions
for
people
to
like
intuitively.
Think
of
like
what
categories
did
you
perceive
and
the
praise
that
you
sorted,
that
you
can
tell
out
of
your
mind
and
then
keep
track
of
them
and
sense
making
and
tweaking.
C
A
The
the
initial
plan
is
that
we
we
make
an
export
after
the
quantification
and
then
pull
all
that
data
into
a
google
spreadsheet,
and
then
we
make
the
the
the
changes
and
the
comments
in
in
that
spreadsheet
before
before
exporting
it
to
again
exporting
it
for
for
distribution
and
to
the
analysis
to
the
red
dashboard,
so
that
that
is
like
absolutely
a
candidate
for
for
the
for
a
future
version
that
you
could
do.
Post
quant
changes
when
you
have
the
full
data
set,
but
it'll
be.
C
C
And,
of
course,
if
there
are
members
of
the
board
for
quantifiers
and
then
sharing
learnings
and
then
I
started
to
think
of
some
questions,
so
this
maybe
to
open
the
session.
How
comfortable
did
you
feel
with
your
quantification
from
one
to
five?
So
one
being
I
didn't
understand
what
most
of
the
contributions
meant
and
it
was
difficult
to
access
the
value.
So
my
quant
is
closed
to
random
and
five
being.
C
I
think
I
could
gauge
well
the
value
of
most
contributions
and
felt
like
I
had
enough
context
to
quantify
even
the
ones
I
wasn't
familiar
with.
So
maybe
this
is
good
for
us
to
keep
track
of
how
quantifiers
are
doing
and
how
they're
feeling
and
if
the
system
is
working
at
all,
because
if
most
people
feel
like
they're
giving
random
numbers,
then
we
need
to
like
reassess
everything
and
was
it
easy
to
sort
out
the
duplicates
any
questions
about
a
specific
one.
C
I
feel
like
this
will
bring
a
lot
of
confusion,
just
as
it
did
in
that.
Like
short
call,
we
had,
and
was
there
one
or
two
phrases
that
especially
caught
your
attention,
and
why
and
then
I
think
here
we
would
go
more
deeply
into
like
insights,
that
people
have
without
being
too
much
of
a
broad
question
that
would
like
make
people
just
like.
Oh
I
liked
I
didn't
like.
A
Yeah
this
this
looks
great.
It
will
be
so
so
amazing,
seeing
this
process
evolve
over
time
like
doing
this,
the
first
time
and
it
will
be
really
clunky
and
everyone
will
be
really
it's
not
going
to
feel
awkward.
But
but
you
know
people
will
be
really
fresh
doing
this
and
then,
after
after
doing
this
10
times,
I
think
the
the
quality
of
the
praise
will
be
increased
because
we
will
give
people
feedback
for
for
how
they
praise
and
so
that
we
get
better
praise.
We
can
do
better
analysis
and
and
yeah.
A
Nice
work.
Sorry,
if
I,
if
I
hadn't
seen
these
other
topics,
I
would
have
reserved
some
more
time
at
the
end
for
for
them.
C
B
C
The
categories
thing
I
think
I
can
write
something
down.
Maybe
it's
confusing
to
talk
about
it.
A
C
Well:
okay,
really
quick!
The
idea
was
to
attach
emojis
to
each
one
of
the
paddles
and
start
to
like
brainwash
people
with
those
emojis.
You
know
like
it's
very
easy
for
them
to
relate
that
emoji
with
that
pedal,
and
then
we
add
a
layer
of
emojis
to
the
quantification.
C
You
know
to
each
phrase:
there's
just
those
emojis
there
and
then
the
people
can
like
pick
the
emoji
that
that
belongs
to,
and
that
would
be
a
way
of
categorizing
and
then,
in
the
end,
for
the
analysis
we
would
have
like
we
could
have
a
graph
that
is
this
pedal
and
how
many
contributions
are
going
to
each
paddle
according
to
the
emojis
and
then
seeing
if
there
is
any
like.
Oh,
maybe,
strawberry
was
mistaken
for
grape,
and
we
could
see
that
in
the
in
this
analysis
part.