►
From YouTube: W16 Rewards WG: DEMO!!!
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
Rewards
work
group
meeting
for
2022
and
today
is
demo
day
and
status,
updates,
etc,
but
I'm
happy
to
sort
of
announce
that
we
me
and
nabs
have
been
hard
at
work
with
the
back
and
fronted
for
the
new
prey
system,
and
we
have
now
have
something
that
is
not
done,
but
but
it
works
good
enough.
A
So
I
can
show
you
and
get
some
feedback,
perhaps
or
just
happy
to
be
able
to
share
something,
and
then
we
have
a
status
updates
from
from
the
work
work
streams
as
as
regular
as
usual,
and
one
of
the
main
things
I
hope
that
we
can
set
today
is,
since
we
are
nearing
finish
of
the
mvp
version
of
the
the
price
new
prey
system
is
that
we
can
set
the
dates
for
a
trial,
quant
and
a
post
trial,
quant
analysis
session,
etc.
A
So
we
do
some
some
planning
for
that,
and
then
we
look
into
the
the
meeting
tracker,
bots
and
the
regular
stuff.
But
I
I
thought
we'll
start
I
moved.
I
moved
pace
to
the
top
of
the
agenda
because
it's
always
fun
to
start
with
the
fun
stuff.
A
So
this
is
so
the
we,
the
new
bot,
has
been
feeding
phrase
data
into
the
new
database
and
me
as
an
administrator
of
the
new
praise
system
goes
to
the
praise
dashboard
to
see
what
has
been
happening.
So
this
is
the
screen
that
greets
me
there's
a
lot
of
details
to
fix
all
over
the
place
like
sorting
this
table
etc.
A
But
the
main
screen
is
like
a
feed
of
incoming
praise
into
the
system
and,
let's
say
now,
the
main
purpose
of
having
this
dashboard
is
to
to
conduct
the
the
phrase
quantifications
and
me
as
an
administrator.
I
I
that
that
is
that
that's
the
reason
why
I'm
here
that
I
would
like
to
to
perform
a
quantification
for
a
price
period
that
is
has
just
been
concluded.
A
So
let's
say
we
are
in
the
end
of
january,
so
I
choose
here
a
quantification
periods
and
you
can
see
that
there
we
have
two
prior
periods
so
for
the
first
week
of
january
and
the
second
week
of
january,
and
but
now
I
need
to
to
create
this-
this
new
period.
A
We
have
chosen
not
to
allow
the
system
to
create
periods
automatically,
because
we
believe
that
there
will
be
situations
where
you
would
like
to
set
a
specific
end
date
for
for
a
period
because
of
holidays
because
of
a
airdrop
or
because
of
a
token
launch
whatever.
So
we
think
it's
it's
easy
enough
to
just
create
them
when
you
need
them
and
we
plan
to
create
them
bi-weekly.
A
So
let's
call
this
last
weeks
of
january
and
set
the
end
date
to
january
31st.
A
So
there
we
have
a
new
phrase
period
and
clicking
on
that.
We
get
an
overview
of
a
summary
of
that
period
and
we
can
see
there
is
a
quite
a
lot
of
pace
that
has
been
coming
in
connected
to
this
period.
A
And
the
next
step-
and
of
course
all
of
these
praise
have
a
prey
scores
of
0
because
we
haven't
started
the
quantification.
Yet
so
the
next
step
for
me
as
an
admin
would
be
to
to
assign
quantifiers
to
this
to
this
period,
and
I
do
that
for
from
the
same
same
screen,
and
this
is
the
screen
that
the
sort
of
the
regular
users
don't
have
access
to.
A
So
I
choose
assign
quantifiers,
and
it
tells
me
that
the
quantifier
pool
has
seven
members
and
using
our
algorithm
and
the
settings
we
choose,
for
instance,
how
many
each
praise
needs
to
be
quantified
by
x,
amount
of
x,
of
quantifiers
and
and
all
quantifiers
should
not
have
to
quantify
more
than
x
amount
of
trace.
Those
are
the
two
parameters
deciding
how
the
the
pool
requirements
so
in
this.
B
Case
sorry,
to
cut
you
off
christopher
and
then
what
about
the
overlap
so
that,
like
quantifiers,
are
overlapping
on
the
praise
that
they
they
quantify.
Was
that
a
parameter.
B
A
B
A
A
Just
for
myself,
like
I
do
not
come
from
my
like
imagine
like
okay,
I
press
septimus
for
recording
whatever
I
put
one
million
points
or
whatever
right
then
I
think
that's
wrong,
but.
A
The
rules
we
have
is,
of
course
one
quantifier
should
only
be
able
to
quantify
one
praise
one
time
and
a
quantifier
should
not
be
able
to
quantify
at
their
own
praise
those.
Those
are
the
two
guiding
principles
in
addition
to
the
parameters
I
mentioned.
So
let's
see
how,
if
the
algorithm
does
a
good
job
of
assigning
quantifiers
here,
press
assign
and
in
a
second
here
now
we
have
six
quantifiers
assigned,
and
I
told
you
the
the
the
cutoff.
A
We
said
that
it
was
the
algorithm
tries
to
assign
circa
50
praise
per
per
quantifier,
but
of
course
it
also
depends
on
the
the
number
of
it.
It's
it
impossible
to
divide.
It
is
completely
equally
because
one
of
the
rules
are
also
that
one
quantifier
always
quantifies
all
praise
for
one
praise:
receiver
for
one
period.
A
So-
and
let's
see
I
in
in
this
case,
I
happen
to
be
sydney17.
All
these
are
randomly
generated,
usernames,
hi
nebs,
I
I
I
start.
I
put
the
demo
at
first
on
the
agenda,
so
I
didn't
wait
for
you.
It's
okay.
A
A
Of
course,
I
yeah,
so
the
the
system
doesn't
really
update
super
smoothly
yet
so
that
is
one
thing
to
fix.
Now
on
the
start
screen,
it
tells
me
that
I,
that
we
have
an
we
have
an
open
period.
You
see
here
on
the
period
page
that
the
last
weeks
of
january,
we
started
now
it's
in
the
quantify
mode,
because
we
assign
quantifiers
that
it
means
it
moves
from
being
an
open
period
into
being
a
period
that
is
under
quantification
and
I,
as
a
quantifier,
have
been
assigned
the
praise.
A
A
So
if
I
want
to
just
make
it
really
quick
I'll
give
lorna
some
some
scores
here
and
that's
it
for
for
one
person.
A
And
this
doesn't
update
as
well,
unless
I
heard
refresh
and
maybe
even
yeah
lorna
there,
you
see
five
out
of
five
items
have
been
completed
and
this,
and
we
also
have
the
option
in
this
interface
to
mark
praise
as
duplicates,
and
in
that
case
I
choose
one
place
here
and
I
would
like
to
mark
this
as
a
duplicate,
so
we
have
the
best
option.
I've
come
up
with
so
far
is
having
similar
to
github
is
having
some
some
id
id
strings.
These
are
ideal.
A
These
would
be
just
plain
numbers,
but
now
we
use
the
system
id
that
we
already
have,
so
they
become
a
little
bit
more
difficult
to
read,
but
still
I
think
it's
let's
see
if
if
this
is
easy
enough,
so
in
this
case
let's
say
I
I'm,
I
say
that
this
phrase
is
a
duplicate
of
this
phrase.
A
Then
I
would
click
the
duplicate
here
and
I
would
write
something
three-fourths,
that's
the
one.
Oh
and
nothing
happens,
because
that
is
not
implemented
yet,
but
what
is
implemented
is
I
also
realized
that
this
space
is
just
someone
saying
hello
to
someone
it's
irrelevant.
It's
not
not
not
really.
A
phrase
I
will
mark
this
as
I
dismiss
this
and
I
will
do
a
hard
reload
and
hopefully
it
will
be
marked
as
dismissed
so
that
works.
A
So
we
can
put
that
setting
to
zero
if
we
don't
want
to
the
duplicates
to
be
worth
anything
at
all
or
we
could
mark
them,
as
you
know,
ten
percent,
or
or
whatever.
If
we
see
that,
there's
still
some
value
of,
we
want
to
to
give
something
to
the
duplicates
as
well.
D
First
of
all,
this
is
amazing,
it's
so
great
to
see,
and
if,
if
you
mark
one
as
duplicate,
is
that
just
for
the
batch
that
you're
quantifying
or
for
all
quantifiers.
A
No,
it's
only
for
for
the
the
batch
I'm
quantifying
and
in
the
in
the
current
calculation,
a
duplicate
is
just
counted
as
a
zero
and
and
and
the
average
score
for
for
one
place
is
what
goes
into
the
the
final
summary.
So
so,
if,
if
three
quantifiers
give,
if
three
quantifiers
quantify
one
appraise
and.
A
The
first
quantifier
gives
the
that
that
pays
a
score
of
10.
The
second
one
give
that
score
plays
a
score
10
and
the
third
one
marks
it
as
a
duplicate
or
dismisses
it.
Then
the
average
score
for
that
price
would
be
10
templates,
10,
plus
0,
divided
by
three
simple,
as
that
for
now.
D
Okay
thanks,
I
wonder
if
for
an
analysis
having
a
metric
that
could
analyze
all
duplicates
and
then
display
that
in
the
end,
like
oh
this
period,
there
was
x
duplicate
phrases
so
that
if
we
had
that
that
wouldn't
influence
the
different
quantifiers
that
are
analyzing
the
same
set,
would
it
sorry
I
don't
know
if
it
made
sense.
D
D
A
It
it
will
show
all
the
raw
data
goes
to
the
are
included
in
in
the
export
okay.
So
so
so
each
quantification,
no
matter
if
it's
a
a
duplicate,
if
it's
a
a
score
or
that
there
are
those
three
the
score,
a
score:
a
duplicate
or
dismissed,
everything
is
included
and-
and
this
is
and
how
it
affects
other
quantifiers.
That
is
also
a
question,
and
the
general
rule
here
is
that
quantifiers
will
not
be
able
to
view
the
quantifications
of
other
quantifiers
before
a
period
has
been
closed.
A
A
So,
going
back
to
the
last
weeks
of
january,
we
see
now
sydney
that
is
me.
I
have
finished
3
out
of
my
60
items
and,
let's
see
lorna
got
some
score
here
and
now
we
move
into
this
page
is
the
receiver
summary
for
a
whole
period.
So
this
is
a
a
page
that
will
be
publicly
publicly
accessible
for
anyone
that
is
have
received,
pace
or
given
pace
that
you
can
go
into
and
see.
A
What
praise
did
I
receive
for
a
certain
period
and
see
a
summary
of
your
score
and
also
after
the
period
has
been
closed,
everything
is
disclosed.
You
can
see
how
much
what
did
the
different
quantifiers
give
me?
How
did
the
quantifiers
quantify
the
my
place
so
also
answering
again
the
time
here?
A
A
And
here
there
will
be
an
export
button
where
you
can
export
the
csv
data
file
format
and
move
move
into
the
next
step,
where
the
quantifiers
can
import
the
data
into
the
the
spreadsheets
together
doing
any
final
adjustments
and
then
move
on
to
the
rad
analysis
and
this
yeah
the
distribution
step
and,
of
course,
for,
for
instance,
that
this
this
final
step
of
of
doing
the
the
final
adjustments
as
a
group.
A
That
is
a
one
feature
that
most
likely
will
be
included
in
the
in
the
system
in
the
future
versions
and
also
the
kind
of
analysis
that
label
you.
You
talked
about
all
kinds
of
analysis.
I
think
that
in
in
addition
to
the
more
in-depth
analysis
that
nagin
and
ms
and
octopus
are
doing,
we
need
like
a
base
set
of
analysis
for
for
for
pace
periods
so
including
integrated
in
this
interface.
You
can
see
some
basic
statistics
etc.
C
Yeah
I
had
a
question
about
like
the
distribution
of
place
like
this
is
just
the
current
example
like
one
1.5
got
60
and
another
one
got
27.
like
moving
forward.
Can
this
be
a
potential
issue
with,
like
larger
quantifier
pools,
all
with
a
larger,
larger
praise
items,
because,
like
the
way
you
described
it
get
distributed
like
all
the
praise
of
one
person
gets
assigned
to
one
quantifier
at
a
time
like
you,
don't
distribute
that
up?
Could
that
be
a
potential
issue.
A
C
No,
I'm
not
talking
about
it.
I'm
talking
about
how
the
praise
items
get
distributed
between
different
quantifiers.
So,
for
example,
in
this
case,
say
there's
six
people
that
got
placed
okay,
not
six.
That's
too
small
12,
12
people
that
caught
place,
and
at
least
six
of
them
have
like
200
places
or
something
and
like
the
what
what
happens
is
that
some
quantifiers
get
a
large
amount
of
price
items
and
the
rest
don't
get
any
so
can
we
split
it
up
if
it's
too
big.
A
That
is
what
we
have
tried
to
avoid
so
far,
because
we
splitting
the
praise
up
between
different
quantifiers.
That
does
then
that
doesn't
allow
you
to
mark
duplicates
in
a
fair
way.
A
So
I
think
that
the
the
issue
of
fairness
is,
and
you
can
say
what
what
happens
if,
if
the
to
duplicate
praise
land
on
on
different
sides
of
of
a
period
the
period
border
sort
of
yeah,
then
those
those
two
the
first
period
could
be
assigned
to
one
quantifier
and
the
next
period
could
be
assigned
to
another
quantifier
so
that
that
price
wouldn't
be
marked
as
a
duplicate.
A
D
A
D
You
can
think
about
the
amount
of
praise
someone
could
actually
receive.
So
if
you
think
like
we're
we're
talking
about
a
period
of
15
days,
if
a
person
is
praised
every
day,
there
would
be
15
praises
to
get
like
200
praises
in
15
days.
It's
nearly
impossible.
I
think
so.
It
feels
like
this
cap
of
50
per
person
is
a
good
number,
because
I
don't
think
I
don't
think
it
even
gets
to
that.
A
D
A
That
is
weird,
it
doesn't
yeah.
I
closed
the
period
that
was
bad
so
now
I
actually
cannot
access
the
quantification
interface
anymore,
because
I
closed
the
period.
Otherwise
I
I
would
would
have
shown
that
the
actually
me
my
my
user
sydney
here
had
had
a
bunch
of
quantifiers
assigned
to
me
and
because
you
you
see
that
these
are
the
the
number
of
praise
each
user
have
received
over
this
period.
So
so,
in
order
for
me
to
get
up
to
60,
I
would
have
need
to
be
assigned
to
at
least
five
six.
A
Seven
price
receivers.
A
A
Roughly
the
same,
you
would
see,
you
wouldn't
see
the
quantifier
pool.
This
is
so.
This
is
an
administrative
page
where
you
add
people
to
or
remove
them
from
the
quantified
pool.
A
B
A
The
page
is
visible,
but
when
you,
when
you-
because
this
is
a
transparency
thing-
that
you
should
be
able
to
see
who
were
the
the
quantifiers
who
who
received
praise,
what
place
did
they
receive
and
how
was
it
quantified,
but
so
that
the
rule
for
the
general
user
is
the
same
as
for
for
quantifiers
that
you
they
can
see
everything
in
in
in
periods
that
are
closed
and
nothing
in
periods
that
are
still
open
to
quantification
yeah.
A
B
A
Okay
cool,
so
let's
move
on
to
other
topics
and
the
the
system
being
at
least
almost
ready
means
that
we
can
plan
for
actually
doing
the
trial
quant
for
for
real.
B
A
If
we
say
if
it
says
that
the
date
will
make
sure
it
it'll
be
ready,
but
by
then
now
it's
you
know
what
what
you
saw
is
that.
B
B
I
mean
we
can
know
roughly,
but,
like
you
know,
it's
gonna
be
hard
to
communicate
something
clear
to
30
people
when
you
know
the
development
isn't
finished.
D
B
Okay,
well,
I'm
not
gonna
communic,
okay,
all
right
I'll,
think
about
it
and
then
from
there
sorry,
I'm
just
moving
right
into
the
the
topic
there
and
then
from
there.
Zep
and
ms
are
going
to
finish
the
onboarding
document.
C
B
A
A
B
Yeah
and
so
there's
27
people
signed
up
for
quantifiers,
I'm
hoping
to
get
a
nice
even
30.
So,
like
I
don't
know
I'll,
probably
just
chill
it
one
more
time
and
see
if
three
more
people
can
come
out.
So
that's
kind
of
what
I
was
shooting
for
for
the
trial
quant,
so
we're
pretty
much
there.
B
Just
something
like
what
christopher
was
mentioned
when
we're
creating
the
quant
periods,
it's
like.
We
have
to
figure
out
what
the
time
commitment
is
going
to
be
for
quantifiers.
You
know:
do
we
expect
them
to
do
two
hours
of
work,
three
hours
of
work?
How
does
that
translate
into
like
actual
numbers
of
praise
to
quantify.
D
A
A
So
maybe
if
we
are
done
with
this
the
second
week,
we
can
move
on
and
talk
to
talk
about
the,
for
instance,
the
meeting
meeting
tracker
bot,
because
that
is
not
necessarily
included
in
the
trial
quant,
but
in
in
the
trial
reward
board
exercise.
A
We
would
very
much
like,
of
course,
to
do
the
have
the
source
credit
data
as
well,
so
so
my
goal
would
be
to
to
set
up
the
source
credit
system
as
well
during
next
week,
so
that
we
have
the
no
the
month
of
november
in
in
the
system
and
and
we
can
have
that
exported
in
the
in
the
right
way
as
well.
C
Yeah,
I
think
we
can
maybe
do
that.
I
did
get
a
meeting
organized
with
it
said
and
we'll
probably
figure
out
how
to
do
things
in
source
grid
then.
But
as
far
as
the
weighted
graph
is
concerned,
like
last
time,
I
showed
it
to
everyone
it.
There
was
a
small
issue
that
it
was
weighing
based
on
how
many
people
were
in
the
meeting,
but
that's
that
that
has
been
solved
it
just
faced.
Based
on
how
many
meetings
you
attend.
A
So
sorry,
just
let
me
post
you
there.
Sorry,
if
I
I
wasn't
here,
I
I
didn't
did
not
mean
you
that
the
goal
would
have
to
be
that
you
are
finished
with
the
meeting
tracker
bot,
because
I
know
that
is
there's
still
some
work
left
to
do
on
that.
I
meant
the
source
credit
in
in
general,
with
the
the
github
tracking,
et
cetera,
all.
C
Yeah
I
would
try
to,
but
this
is.
This
is
like
a
test
distribution.
All
these
people
attended
one
meeting,
these
people
running
two
meetings
and
three
meetings.
So
it's
about
0.99
per
meeting.
We
can.
We
can
multiply
this
by
a
constant
so
that
we
have
control
over
how
what's
the
worth
of
one
meeting
but
yeah
the
this
should
work
for
now.
A
Nice
and
have
you
had
any
progress
with
the.
A
The
issue
on
how
to
integrate
with
the
the
identities
in
source,
credit.
C
Yeah
about
that,
I'm
gonna
talk
with
it
said,
but
from
what
I
see
is
that
we
might
need
to
make
our
own
identities
and
then
merge
them
separately
with
and
rather
than
using,
the
ones
from
the
discord
plugin,
because
this
is
like
an
external
plugin
and
those
objects
are
created
with
an
internal
plugin.
But
I'll
have
to
discuss
this
with
them,
and
you
know
try
to
figure
out
if
we
can
just
use
the
data
created
by
the
discord,
plugin
and.
A
C
If
possible,
if
needed,
we
can
maybe
for
the
discord,
plugin
and
edit
it
a
little
bit,
but
then
that's
another
mess
to
deal
with,
because
then
you
have
to
maintain
it.
That's
that's
still
an
option
on
the
table.
If
we're
having
complications.
A
So
so
what
would
your
your
own
estimate
be
of
when,
when
the
the
meeting
tracker,
what
could
be
done.
C
So
it's
dependent
on
information,
so
I
think
if,
if
the
sync
with
it
said
goes
great
and
you
know
I
get,
I
get
the
information
I
need
to
implement
it.
Hopefully
we
should
have
a
deployment
by
next
week,
but
if
it
doesn't,
then
you
have
to
contact
someone
else
subscribe
and
they
they
have
limited.
They
don't
have
many
time
slots
right
now
because
they
took
some
time
off
slowly,
opening
them,
but
but
I'll
try
to
get
this
done
with
in
at
least
like
two
weeks.
A
A
Yeah
and
over
next
week
also
I'll
try
to
to
schedule
a
work
session
with
the
hc
and
and
mateo
and
to
to
yeah
adjust
the
settings
for
our
current
source.
Credit
instance
so
that
it's
running
with
a
tracking
github
and
discourse
that
we
already
are
tracking.
A
A
No
there's
there's
nothing
to
report
once
we're
closer
to
the
yeah.
Once
the
back
end
is
finished.
Maybe
we
can
kind
of
review
if
the
the
file
input
format
is
still
right,
but
for
now
it's
as
it
was
yeah.
A
So
when
when
we
have
the
export
function
ready,
so
those
are
the
last
two
back-end
endpoints
that
we
are
working
on
is
the
the
importing
of
phrase
and
exporting,
because
we
also
need
to
be
able
to
import
old
praise
so
importing
and
exporting,
and
when
we
have
the
exporting
feature
done
that
we
can
make
a
test
export
of
the
the
test
phrase
data
and
just
to
see
that
the
format
works.
C
I
had
a
question
about
the
the
bot
that
will
be
used
for
inserting
data
into
phrase
is,
is
have
we
started
working
on
it
and
like
what
are
we
using?
Are
we
using
like
a
text
command
or
the
new
slash
commands.
A
Slash
command-
hopefully
I
haven't
heard
back
from
casale.
Yet
after
after
christmas
new
year,
but
just
before
christmas,
he
reported
that
he
has
had
something
up
and
running,
not
a
full,
fully
working
bot,
but
he
was
trying
out
commands
and
etc,
and,
as
I
understood
it,
he
had
some
difficulties
of
allowing
you
to
praise
more
than
one
user
in
in
a
in
an
easy
fashion.
A
A
I
haven't
seen
that
in
action
myself,
I
I
don't
know
if
that
would
be
a
a
total
deal,
breaker
for
using
slash
commands
at
all.
If
you
would
have
to
select
from
from
a
list,
I
guess
you
can
type
something
to
to
help.
You
find
the
right
user
is,
so
you
don't
need
to
scroll
through
all
the
users
on
the
server.
C
Yeah
yeah,
you
can
type
a
search
through
the
list,
but
the
issue
is
that
that
that
only
allows
you
to
select
one
user
at
a
time
and
like
the
command,
has
a
fixed
number
of
fields
that
you
can
add.
A
A
No
know
so
that
is
a
one
separate
thread
that
that
I
haven't
read
up
on
yet,
but
I
know
that
ms
have
been
looking
up
in
into
that
the
so
the
the
glitches
in
the
in
the
praising
that
the
the
people
have
not
been
receiving,
praise
or
or
praise
givers
have
not
been
able
huanka,
for
instance,
haven't
been
able
to
to
praise.
As
far
as
I
know,
the
the
what
have
it
hasn't
picked
picked
up
their
information.
A
So
I
guess,
if
we,
if
we
were
to
develop
a
bot
using
the
old
method
of
text
parsing,
we
would
run
the
risk
of
ending
up
in
the
same
situation.
A
C
D
C
A
Yeah,
the
last
thing
here
added
praise
on
behalf
praise
on
behalf
but
yeah.
I
discussed
this
with
with
grief
also
praised
by
proxy
or
praise
on
on
behalf
of
someone
who
who
added
this
to
the
agenda.
C
D
So
why
you
had
given
that
idea
of
praising
on
behalf
of
someone
else,
and
I
think
that
could
really
work
if
we
had
like
permissions
for
who
can
do
that.
If
it
wasn't
just
anyone
that
can
praise.
C
C
Or
one
thing
we
could
do
is
just
have
that
that
command
can
only
be
run
by
one
person
like
one
one
account
one
proxy
account.
We
can
call
it
tc
praises
or
something
else,
and
that
access
to
that
account
is
given
is
shared
by
whoever's
doing
the
pricing,
so
that
would
involve
trusting
one
of
the
stewards
to
share
access
with
only
people
that
are
trustable.
A
And
since
the
the
prey
spot
will
be
integrated
in
the
into
the
the
place,
the
back
end
and
the
that
authentication
system,
we
could
also
do
the
management
for
from
there.
You
saw,
I
think
you
saw
the
the
screen
where
you
could
add
quantifiers,
and
we
could
easily
manage
that
thing
there.
A
And
if,
if
we
develop
a
feature
like
this,
it
would
be
nice
if
you
could,
from
the
place
dashboard
just
mark
a
person
say
that
this
person
has
the
has
the
permissions
to
to
praise
on
behalf
of
other
users,
and
that
means
that
when
they
they
access
that
bot
command
next
time,
they
they
can
yeah.
That
page
goes
through
and
if
they
don't
have
the
permission
that
they
will
be
told
by
the
bots.
Sorry,
you
don't
have
those
permissions.
C
Yeah
yeah
that
doesn't
make
sense
and
I
think
we
might
have
to
change
the
back
end
a
little
bit
to
also
store
the
information
of
who
cross-roasted
it.
And
and
do
we
want
that
to
be
shown
to
the
qualifier.
And
I
think
we
don't.
C
A
A
So
technically
it's
a
as
a
really
small
small
addition
to
to
what
we
are
already
doing
and
and
when
it
comes
to
to
quantifying,
etc.
It
wouldn't
affect
the
system
at
all.
So
so
it's
only
when
we
when,
when
we
export
the
raw
data,
we
want
that
information
to
be
included,
and
I
also
had
a
discussion
with
this
about
this
with
griff,
and
so
I
know
I
know
it's.
We
have
placed
it
high
up
on
the
on
the
wish
list
for
future
versions.
A
And,
depending
on
how
high
it
is,
it
could
be,
it
could
be
a
feature
worth
focusing
on
before
we
release
what
we
call
the
version
version,
one,
the
the
the
stuff
that
happens
in
between
the
the
trial
quant
and
the
mvp
version,
and
the
version
one
we
haven't
planned
any
like
additional
features
during
that
period,
but
more
like
building
the
making
the
thing
into
a
an
easy
installable,
stable,
open
source
system
that
could
be
used
by
many
communities.
A
Yeah,
on
the
other
hand,
we
just
continue
doing
what
we
have
done
for
for
a
long
long
time.
It's
also
possible
that
due
to
praise
by
proxy-
but
you
it
only
skews
the
the
data
a
little
bit-
that
it
looks
as
a
mount
manu
is
a
big
appraiser,
for
instance,
so
that
of
course
works
as
well.