►
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
Let's
get
started,
shall
we
hi
again
everyone
welcome
to
the
rewards
working
group
meeting.
It
is
march
16th
and
as
always,
we
have
a
quite
stacked
agenda.
A
Let's
begin
with
the
regular
status
updates
from
the
phrase:
development
source
credits,
the
red
dashboard
and
the
current
ongoing
rewards
round
too,
and
then
we
have
some
discussion
topics
we
need
to
mention
briefly
the
plan
or
the
talk
about
the
plan
for
what
rewards
around
three:
let's
talk
about
bright
id
integration
and
continue
the
discussion
about
when
when
and
how
to
launch
the
the
new
praise,
bot
and
also
talk
a
bit
about
phrase
automation.
A
B
Yeah
hi
everybody,
so
I
did
a
bunch
of
little
tickets
this
week.
But
the
one
to
note
is
that.
B
I
refactor
the
authentication
system
to
use
refresh
tokens,
so
the
only
important
thing
is,
if
you're
doing
development
just
make
sure
you
add
these
new,
these
two
new
environmental
variables
to
the
api.
A
Yeah
at
the
environment
of
variables,
and
then
I
was
weirdly
logged
out
of
the
system.
I
thought
it
was
a
bug.
Yeah
I'd
say
that
that
is
not
as
a
small
ticket.
That
was
quite
a
major
thing
that
has
been
on
on
our
board
for
quite
some
time:
the
ability
to
refreshed
tokens
without
being
logged
out
et
cetera,
it's
a
important
for
the
user
experience.
B
I've
just
been
pulling
from
the
top
of
the
sprint
backlog
board
and
just
whenever
I
take
something
I'll,
just
assign
it
to
myself
so
yeah
as
long
as
nobody
else
is
working
on
stuff
that
they
haven't
assigned
to
themselves.
I'll.
Just
keep
keep
doing
that
pulling
from
the
top.
A
Yeah,
I
might
add,
in
in
general,
we
try
to
that's
that's
what
you
also
pushed
us
to
do,
mata,
to
to
focus
on
focus
on
the
issues
that
are
focused
on
the
right
issues,
the
coming
week
and
weeks,
the
issues
that
mostly
have
affect
the
ongoing
quantifications,
etc.
So
we
will
also
be
focusing
on
new
new
features,
but
if
you
quantifiers
come
up
with
like
bugs
appear
when
doing
quantification
etc,
those
are
the
the
issues
we
should
take
on.
First.
C
Yeah
right
now,
I'm
working
on
file
upload
for
settings
and
I
also
had
the
same
issue
as
you
added
forgot
about
new
variables,
because
I
just
I
worked
on
my
branch
for
a
long
time
and
today
I
merged
there
and
all
the
changes.
So
I
had
much
conflicts.
I
think
I
fixed
those
and
yeah.
I
was
logged
out
every
time
I
make
requests
and
didn't
know
why,
but
yeah
and
also
in
the
branch
I
fixed
one.
Other
issue
is
settings
so
so
this
that
should
be
okay.
After
I
push
my
changes.
A
Yeah,
but
what
I
wanted
to
say
is
that
I
I
think
that
we
should
prioritize
these
these
issues
at
the
top,
the
ones
that
I
have
marked
the
red
and
high
priority
before
doing
anything
else.
Basically
so,
and
the
number
settings
are
fixed,
this
error
when
marking
duplicate
price-
that
is
a
real
blocker
for
the
quantifiers.
A
Correctly
mitch
that
it's
difficult
to
work
around
and
yeah,
the
refresh
token
is
fixed.
It
wouldn't
didn't
need
fixing.
A
Remove
message:
there
is
no
active
quantification,
yeah,
a
small
one,
remove
no
no
active
quantification
yeah,
that's
the
one.
A
Yeah,
so
basically
that
the
the
only
it
would
be
nice
here,
nebs
if
you
can
take
on
the
yeah,
I
can
do
that.
The
error
I'm
trying
to
market
duplicate
phrase
cool
and
what
will
I
do?
What
have
I
been
doing?
A
So
in
the
coming
days
I
will
set
up
the
the
production
server,
a
new
production
server
so
that
we
can
move
from
having
this
ip
address,
that
we
redirect
the
quantifiers
to
to
actually
use
the
real
address
that
which
will
be
praise,
dot,
t
commons.org,
so
I
will
say,
set
up
a
new
new
production
server.
A
A
A
So
we
can
merge
the
source,
credit
data
with
the
price
data
and
when
it
comes
to
the
rad
dashboard
nagin
has
been
not
well
the
last
week,
so
he
is
unable
to
demo
the
red
dashboard,
but
he
says
that
he
will
do
it
next
week,
which
is
good,
and
let
me
just
show
you
quickly
what
I'm
I've
been
planning
for
the
for
the
structure
of
that.
So
this
is
the
general
idea.
I've
set
up
a
repository
for
quantification
or
or
rewards
rounds
data.
A
So
in
this
this
repository
we
will
create
a
folder
per
rewards
round
and
there
we
will
store
all
the
the
source
data,
like
the
the
the
page
exports,
the
the
list
of
the
members
of
the
reward
board,
the
source,
cred
grain
data,
and
then
we
also
will
have
the
the
right
dashboard
running
there.
It
doesn't
run
on
github
because
it's
too
large
yeah
it
did
run.
Actually
that
would
be
really
cool
if
we
could
run
the
analysis
dashboard
just
by
clicking
on
on
the
file
in
github.
A
A
Python
notebooks
con,
including
lots
of
graphs,
etc,
are
not
meant
to
be
run
directly
on
github.
Here's
the
the
this
should
be
a
graph,
for
instance,
but
the
the
general
setup
is
that
so
one
one
folder
per
reward
round
and
if
we
produce
a
pdf
for
a
scoreboard
or
whatever
in
in
in
the
in
the
analysis
afterwards,
we
will
just
place
it
there.
So
we
have
a
nice
structure
to
get
good
transparency,
etc.
D
Yeah
lots
of
cat
hurting
there's
like
maybe
what
half
a
dozen
people
that
haven't
finished
yet
and
we're
already
hitting
into
our
first
corner
issue
there
where
people
aren't
responding
and
they're,
they
aren't
doing
the
quants
so
kind
of
expected
to
happen
honestly,
but
we
need
to
figure
out
a
way
as
an
administrator
to
like,
remove
them
or
replace
them
or
like
just
do
the
quant
so
that
the
the
entire
process
doesn't
come
to
a
screeching
halt.
D
A
D
A
Yeah
and
the
question
there
is:
what
is
the
solution
is
a
phrase
being
quantified
by
two
quantifiers
instead
of
three
is,
is
not
in
itself
a
problem.
Of
course.
It's
the
the
final
score
is
a
little
bit
less
relevant
if
it's
quantified
by
just
one
quantifier
instead
of
three,
I
would
say
it's
definitely
a
problem.
A
A
D
Yeah,
like
being
able
to
replace
somebody,
would
be
especially
useful,
because
I
know
that
there's
people
who
would
quantify
this
stuff
right
away,
you
know,
and
so
when,
as
as
an
admin
and
like
you
can
have
a
change
log
and
everything
there
like,
I
can
remove
an
active,
quantifier
and
put
one
in
in
their
place.
So
they
get
the
same
set
of
praise.
B
E
The
finger
you
are
going
to
quantify,
it
goes
kinda
against
our
process,
so
maybe
like
we
could
say
you
could
even
feed
people
under
the
world
or
with
people
who
is
not
in
the
world
but
also
wants
to
keep
quantifying
when
the
price
is
needed
and
then
have
like
a
second
pool.
I
don't
know
if
that's
complicated
many
things,
but
I
feel
like
that
would
be
more
fair
than
saying.
Hey
yourself,
don't
quantify
this.
D
A
A
So
sorry,
if
if
the
quantification
is
already
ongoing,
so
let's
say
a
person
quantifies
a
quantifies,
a
third
of
their
assigned
quant
praise
and
then.
B
B
D
Assigning,
I
I
think,
it'll
be
easier
to
to
pick
somebody
like.
We
still
have
the
randomness
of
the
initial
draft
and
then
like
an
admin
can
manually
put
somebody
in
you
know:
there's
there's
a
change
log,
there's
a
certain
level
of
accountability
to
it,
so
that,
like
it's,
it's
transparent
still,
but
it's
like
there
has
to
be
some
way
where,
like
an
administrator,
can
take
direct
action,
so
the
system
can
can
keep
moving
and
playing.
This
like
randomness
game
like
doesn't
help
us
when
we
need
to
take
like
immediate
action.
A
A
Like
the
administrator,
you
know,
booting
someone
and
picking
someone
you
know
more
favorable
to
whatever,
but
I
think
the
the
the
the
change
log
a
visible
changelog
would
ameliorate
most
of
that,
because
it's
a
small
community,
everyone
knows
everyone
more
or
less
and
as
long
as
your
actions
are
highly
visible,
the
social
pressure
of
doing
the
right
thing
is
enough.
With
my
hunch
at
least.
A
Yes,
we
can,
we
can
hack
a
reassignment
script
fairly,
easy,
I
think,
if
we
want
to
get
it
done
like
really
soon
soon,.
A
Yeah
that
should
work
shouldn't
it,
because
it's
the
the
same
that
the
quantifier
quantification
objects
in,
in
the
phrase
those
those
can
stay
and
we
just
replace
the
the
user,
the
user
ids
in
the
quantification
objects
and
reset
to
zero.
B
A
Okay,
then,
then
make
sure
your
wish
can
come
true,
send
send
us
the
the
list
of
who
who
gets
booted
and
who,
who
takes
their
place
and
will
fix
it.
D
Cool
and
maybe
for
carrying
this
discussion
forward,
should
we
pack
this
all
into
a
github
issue
or
what's
the
best
way
to
go
about
github
issue.
Okay,.
B
Yeah,
I
think,
that's
good.
I
would
like
to
think
about
a
little
more.
Like
I
don't
know,
I
would
like
to
keep
as
much
of
the
credible
neutrality
as
possible
with
like
reassignment.
C
F
I
was
just
thinking
in
advance
that,
like
the
signal
would
be
done
once
and
would
be
there
in
advance.
Well,
there
is
not
like
so
much
of
a
hand
picking
like.
Maybe
it
could
be
a
random
of
those
that
are
assigned,
because
there
is
a
difference
of
participating
in
a
full
period
and
being
called
the
last
minute
to
do
everything
in
a
day
it's
different
types
of
availability.
I
think.
D
Okay,
yeah:
let's,
let's
get
this
stuff
written
down
I'll,
make
an
issue
right
now.
A
And
I
also
I
I've
thought
about
that:
the
the
the
drawbacks
of
doing
the
the
random
assignment
if
we
have
a
large
quantifier
pool.
That
means
that
you
know
maybe
you're
not
assigned
the
this
period
and
nothing
appeared
after
that,
and
you
know
it
takes
the
two
months
pass
and
you're
not
assigned
as
a
quantifier
and
then
all
of
a
sudden
you
are
assigned
and
then
then
you
might
not
be
available
anymore.
B
B
A
And
that
that's
the
cool
thing
with
working
with
this
discord
bot
and
we
have
started
talking
about
sending
messages
from
from
admins
to
quantifiers,
etc,
to
initiate
a
message
from
from
the
from
the
dashboard
or
from
from
a
bot
command
initiating
that
message
and
and
when
you,
as
a
quantifier
user,
gets
the
message
from
the
discord
bot.
You
can
react
to
that
message
directly
and
just
with
a
an
emoji
or
a,
I
think
you
can
add.
A
I
don't
know
if
you
can
add
buttons
or
if
that
is
only
in
in
telegram
stuff
like
that,
so
that
would
be
cool
to
explore
how
we
can
make
those
kinds
of
interactions
really
smooth.
A
Perhaps
we
should
move
on
if
mitch,
if
you're
done,
raising
that
down,
we
could
move
on
to
talk
about
rewards
around
the
three
and
we
have.
I
think
we
have
like
eight
eight
rounds
to
do
before.
A
We
are
back
to
present
time,
but
then,
of
course,
time
passes
while
we
were
doing
the
so,
I
think
it
would
be
like
ten
ten
runs
or
something
before
we
are
back
to
present
time,
unless
we
we
add
another
month
to
the
next
period
and
do
two
months
at
a
time
now
to
me
it
felt
like
doing
I
I
was
assigned
180
praise
that
went
really
quickly
to
do
and
like
50
percent
of
those
praise
is
the
praise
of
the
kind
pay
someone
for
attending
a
meeting.
So
it's
just
like
click.
Click.
D
A
Or
maybe
maybe
it's
not,
maybe
it's
a
wise
not
not
to
push
it.
If
we
have
a
pace,
we
know
that
this
amount
around
200
praise
per
per
quantifier
in
a
week
that
that
that
is,
okay.
That
has
worked
for
those
that
do
their
quants.
D
A
Yep
but
rewards
round
the
three
starts
on
monday
and
it's
for
the
full
month
of
september
then
or.
D
Yeah
september
and
then
we'll
schedule,
another
call
I'm
curious
to
see
how
the
call
is
going
to
go
today
like
the
the
tweak
session.
D
Maybe
that's
another
point
but
yeah
so
I'll
close
the
round
on
friday,
assuming
that
we
figure
out
these
delinquents
and
then
we'll
set
it
up
and
open
up
round
three
for
monday
and
we'll
we'll
do
another
lettuce
meet
and
we'll
organize
the
tweak
session
and
all
that
jazz.
A
D
So
I
I
think,
maybe
we'll
have
to
do
the
tweak
session
on
like
the
friday
or
like
the
monday
after,
when,
like
the
next
round,
is
already
open,
because
I
think
five
day
at
three
days
isn't
enough
for
people
to
get
around
to
it.
F
A
D
It'd
be
cool
like
just
to
have
the
whole
thing
done
like
within
a
week
right,
but
it
would
still
work
like
you
open
up
the
round.
It
still
would
be
done
on
the
same
day,
so
it
would
be
theoretically
done
on
the
wednesday.
D
You
could
have
the
the
sync
session
at
the
end
of
the
week
and
then
you
could
have
the
distro
go
out
the
friday,
the
same
time
when
the
next
round
opens-
and
this
is
only
exceptional,
because
I
think
once
we
are
all
caught
up-
we're
going
to
be
doing
this
bi-weekly
so
we'll
have
quite
a
bit
more
breathing
room
after
we
caught
up.
F
B
I
think
I'm
thinking
about
the
confirmation,
as
during
the
quantification
period,
just
basically
automating
reassigning
any
quantifiers
who
aren't
going
to
be
able
to
commit.
I
don't
think
it
necessarily
changes.
The
schedule.
F
B
Yeah
yeah:
that's
one
option:
it
could
also
be
it
could
it
could?
I
think
it
would
be
functionally
the
same
either
way
whether
it
had
the
difference
is
my.
My
version
could
be
like
asynchronous
like
it
could
replace
a
single
like
they
could
start
the
quantification.
A
bunch
of
people
could
start
working
and
then
it
could
swap
out
people
that
couldn't
commit.
F
That
could
still
happen,
but
I
think
it
would
be
good
to
have
like
I
mean
if
people
commit
and
they
don't
show
up,
then
maybe
what
you're
saying
could
come
in
place,
but
it
might
be
good
to
have
that
one
day
of
awareness
without
like
mitch
having
to
hurt
every
single
person.
You
know
to
have
that
process.
Automated.
A
Okay,
let
I
want
to
throw
in
another
option
a
quantifier
that
doesn't
deliver
so
you,
you
press
you
as
an
administrator
press,
a
button
in
the
the
praise
dashboard
to
to
reassign
that
phrase
and
all
available
the
quantifiers
get
notified
and
the
one
who
jumps
on
it.
First
gets
assigned.
A
The
future
yeah,
no,
I
I
really
believe
we
we
could
build
really
cool
and
good
user
experiences
using
sort
of
a
mesh
between.
D
A
A
So
we
have
25
minutes
and
we
have
three
topics
to
to
cover
the
bright
idea
and
integration,
the
phrase
bot
launch
and
praise
automation.
So
let's
go
right
ahead
with
the
bright
id
integration
leave.
What
would
you
say?
What
is
the
current
is
that
I
was
hoping
that
perhaps
that
adam
was
going
to
be
here
but
he's
not.
F
Yeah,
I
think
he
gave
a
good
suggestion
that
we
could
do
something
like
this
page
for
the
tc.
When
we
put
the
link
on
the
chat.
A
F
So
you
would
have
this
process
of
like
getting
verified
and
then
providing
your
address
and
linking
the
address
to
bright
id
yeah,
and
from
here
we
could
do
yeah.
We
could
like
match
with
our
database.
The
only
challenge
here
would
be
that
we
have
two
different
databases
from
source
grad
and
from
praise.
A
F
A
We
need
to
to
to
keep
the
use
cases
separate.
What
what
do
we
want
to
achieve?
I'd
say
the
the
the
one
thing
is
that
we
want
to
mint
this
reputation
token,
and
we
want
to
be
sure
that
we
we
pay
out,
rewards
only
to
to
bright
id
verified
users
for
that
we
don't
need
any
integration
with
the
place
or
source
cred.
We
just
need
this.
A
That's
on
the
screen
now,
because
we
will
have
a
list
of
ethereum
addresses
when
the
distribution
is
calculated
and
done,
and
if
we
can
filter
that
list
to
from
any
addresses
that
are
not
quite
id
verified,
then
we
have
all
we
need
to
to
mint
the
reputation
token
and
ensure
that
we
do
payouts
only
to
to
verified
users.
So
that
is
one.
A
F
No,
I
don't
think
that's
even
in
discussion.
I
think
everyone
should
be
able
to
praise
and
that
we
should
have
access
to
this
data
from
all
the
community
and
have
the
analysis
with
that
and
all
just
not
distribute
the
rewards
and
then
having
something
to
people
that
weren't
verified
and
maybe
they
get
verified
in
the
future
and
they
could
still
access
their
score.
A
Yeah
yeah
and
that
will
be
a
headache
with
or
without
bright
id
verification,
because
that
is.
E
A
That
that
is
the
last
remaining
and
the
not
the
last,
but
a
big
remaining
question
mark.
How
do
we
keep
track
of
if
we
have
10
praise,
rewards
periods
and
we
have
different
ethereum
addresses
in
each
period
and
how
do
we
keep
track?
Who
gets
paid
for
what?
And
if,
if
I,
as
a
user
connect,
my
ethereum
addresses
when
poor
appraised
periods
have
passed?
How
do
we
make
sure
that
how
do
I
make
sure
that
I
get
paid
for
the
those
periods
that
I
have
missed?
A
D
A
This
solution
is
not
integrated
with
praise
at
all.
It's
a
this
is
a
standalone
web
page
that
you
allow
it
just
links
your
ethereum
address
to
bright
id
and
then,
as
the
last
step
in
in
our
our
process.
We
can
query
that
information,
but
you
know
that
that
is
after
the
the
rad
dashboard
has
been
run
through
so
so
that
is
I
I
don't
know
how
we
do
that.
In
fact,
if
we
build
a
script
to
to
run
this
or
if
we
do
it
just
manually
or
I'm
so
that
is
still
to
be
discovered,.
F
I
guess
the
two
solutions
that
adam
suggested
was
just
that
we
could
use
the
the
bright
id
discord,
bot
that,
from
my
understanding,
it's
pretty
much
ready.
We
could
just
like
plug
and
play,
and
then
we
would
just
need
to
have
a
map
of
addresses
with
discord
handles,
or
we
could
build
this
web
page
that
I'm
showing
that
it
would
be
like
the
solution
would
be
ready.
We
wouldn't
need
this
map
of
discord
and
addresses,
because
we
would
have
that
already
and
and
that
both
and
that
building
this
is
fairly
simple.
F
How
do
we
incentivize
people
to
sign
up
for
bright
id?
From
my?
What
I
understood
from
five
iv
was
that
we
could
put
in
the
onboarding
of
the
tc
in
general
and
as
soon
as
people
join,
they
are
already
like
directed
to
bright
id,
or
we
could
put
that
in
the
box
that
people
register
to
source
credit
in
praise.
A
Yeah
and
that's
that
that's
much
more
complicated
because
then
we
like,
I
wrote
in
the
thread
we
then
we
need
to
add
a
bunch
of
code
to
already
existing
bots
etc,
and
I
think
that
this
solution
is
really
simple
and
beautiful.
We
just
put
up
this
web
page
and
I
think
the
incentives
are
are
super
clear.
You
register
with
bright
id
to
be
able
to
receive,
rewards
and
register
with
bright
id
to
receive
reputation
token
that
will
allow
you
to
to
vote
in
the
conviction
or
in
the
quadratic
voting.
A
Those
are
strong
incentives
and
it
will
be
a
nice
looking
landing
page
where
we
also
can
you
know,
squeeze
in
other
messages
about
tc,
so
it's
become
sort
of
a
also
a
branding
for
it
for
the
tc
and
but
we
still
can
integrate
it
with
the
onboarding
bot.
So
the
survivor
reintegrates
that,
with
the
when
you
become
a
member
of
the
discord
or
whether
of
the
tc,
we
will
link
you
to
this
page.
F
That
sounds
nice
and
then
just
of
course
the
only
problem
would
be
if
people
register
right
id
with
one
address
and
reward
systems
with
another
address
that
maybe
would
have
to
be
like
a
cultural
awareness
thing.
F
Yeah,
okay,
cool
and
then
the
last
last
part
is
just
this
minting
reward
to
wrap
tokens
that
we
would
need
some
would
we
need
someone
from
the
board
committed
to
that
every
period
or
it's
something
we
can
program
kind
of
automate.
A
My
guess
is
that
the
the
process
that
would
need
to
look
basically
exactly
the
same
as
as
not
exactly
the
same
as
paying
out
the
tc
tokens,
because
we
have
them
in
a
wallet
very
similar
that
we
we
need
to
meet
new
tokens
each
time,
and
that
is
that
is
always
a
fairly
manual
process.
Unless
we
build
some
some
sort
of
server
that
has
the
private
keys
so
that
it
can
mint.
F
A
A
Mitch,
you
know
the
the
the
argon
agent
et
cetera.
Would
it
be
possible
to
have
like
feed
one
list
of
addresses
and
amounts
into
the
dao,
an
arrogant
agent,
and
that
agent
or
transfer
tec
tokens
and
mints
reputation,
tokens.
D
A
A
A
D
Well,
I
think,
I
think
minting
it
is
easy
enough.
You're
just
gonna
have
to
get
somebody
smarter
than
me
to
figure
out
what
what
the
actual
script
would
look
like,
but
I
think
it's,
I
think
it's
possible.
A
Yep,
I
think
sam
offered
to
give
us
assistance
on
on
avm
crispr.
A
Cool,
it
seems
like
we
have
a
rough
plan.
We
will
need
to
hash
out
the
details.
A
Let's
move
on
to
the
new
praise,
bot,
launch
and
and
the
the
question
the
the
number
one
question
is:
did:
are
we
ready
to
to
launch
the
bot
on
the
community
call
next
week?
Why
you,
you
told
me
you
you
could
do
a
short
demo.
C
A
C
I
think
once
we
move
to
the
new
command
structure,
there
shouldn't
be
any
issues
with
that.
We
should
probably
have
a
smooth
transition
unless
there's
any
breaking
changes
that
pop
up
during
the
next
week.
A
And
other
than
that,
are
there
any
launch
there
isn't
much
of
a
launch,
but
but
is
it
somewhat
someone
opposing
that
we
should
should
demo
it
and
retire
the
old
pre-spot
next
next
week.
A
If
something
doesn't
work,
we
could
always
re
in
state
the
the
old
bot
yeah.
C
The
thing
that
we
might
want
to
look
into
is
like
ensuring
that
this
is
the
command
structure
that
we're
willing
to
stick
with
just
because
like
if
we
introduce
one
type
of
command
to
the
community,
and
then
we
certainly
change
it.
People
keep
using
the
old
command
and
then
forget
about
it.
Yes,
yeah.
A
Now,
that's
why
I
wanted
to
lock
the
the
new
structure
down.
C
Something
that
isn't
exactly
critical,
but
I
think
it
would
probably
be
need
to
handle.
It
would
be
like
rendering
the
the
ids
inside
the
message
content
for
the
roles
in
the
channels,
mostly
because
it's
like
harder
to
quantify,
then
it's
just
a
number,
but
I
don't
know
we
can
probably
make
a
for,
like
temporarily.
We
can
make
like
a
reference
document
where
they
can
look
up
all
the
ids
slightly
more
work.
C
But
if
we're
not
like
still
decided
on
what
kind
of
path
we
want
to
take
with
structuring
this,
we
could
probably
just
stick
with
like
a
temporary
solution
for
now.
A
Yeah
and
for
those
of
you
who
don't
understand
what
this
is
about
is
when,
when
we
receive
when
the
prey
system
receives
a
raw
praise
from
from
discord-
and
someone
has
mentioned
someone
else
or
mention
the
channel
or
mention
that
we
get
a
a
tag
and
a
a
an
id
number,
that
is
what
you're,
seeing
when
quantifying
these
these
tags,
that
don't
say
say
much
and
the
question
is:
do
we
we
would
like
to,
of
course,
transform
them
back
into
something
readable.
A
And
if
you
have
a
long
list
of
praise,
should
we
try
to
fetch
from
the
from
the
discord
api
for
each
each
of
those
numbers.
That
might
not
be
a
good
idea,
so
we
need
to
figure
out
some
some
smart,
possibly
some
smart
caching
solution
or
filter
those
and
transform
those
tags
into
readable
information.
A
C
One
thing
we
could
maybe
look
into
is
like
caching,
all
of
the
discord
id
objects
beforehand
like
that.
That
would
involve
just
going
through
the
whole
server,
and
you
know
just
looking
at
all
the
channels
we
can
just
make
like
a
simple
map
of
the
channel
ids
and
to
the
whatever
the
channel
name.
The
the
discord
channel
object,
some
of
the
properties
we
can
probably
store,
and
also
with
the
maybe
the
roles
and
then
the.
C
It's
it's
like,
instead
of
being
something
that
it
has
to
fetch
over
from
the
discord
app,
it's
just
something
that
gets
processed
beforehand,
yeah,
so
that
we
don't
have
to
call
make
too
many
api
calls
yeah.
A
Yeah,
let's,
let's
discuss
that
further,
but
a
possible
discord,
id
cache
solution,
sort
of
would
be
one
option.
C
A
C
Does
create
a
cache
right
now
it
uses
the
default
one
that
the
library
implemented,
but
if
we
need
it,
it
has
like
the
ability
to
use
like
a
custom
custom
cache.
So
if
we
look
into
like
some
caching
solution
like
redis,
we
can
maybe
in
use
it
for
both
the
bot
and
the
back
end.
If
we're
interested
in
doing
that,
because
that
cache
automatically
gets
created
for
the
part
whenever
we
run
run
the
bot.
A
Yeah
as
long
as
we
keep
the
footprint
of
the
of
the
installation,
small
and
because
I
would
like
the
whole
thing
to
be,
but
we
you
should
be
able
to
run
the
whole
thing
on
the
like
the
smallest
or
the
maybe
the
second
smallest
digital
ocean,
droplet,
ideally
so
add
adding
redis
to
the
mix.
I
guess
it's
a
also
add
as
to
the
system
requirements,
but
let's
look
into
that
further
and
and
make
a
decision
quite
quickly.
A
A
E
Hello,
yes,
I'm
here,
hi,
hello,
so
yeah
praise
automation.
I
didn't
know
a
lot
of
the
things
that
were
happening
around
and
this
meeting
has
been
very
helpful
to
understand
all
of
the
efforts
that
are
being
done
around
around
praise
and
and
source
credit
and
automation,
but
yeah
being
involved
in
the
last
quantification
process.
I
I
just
thought
about
a
couple
of
ideas
of
making
the
process
easier.
You
know,
I
understand
that
that
the
quantification
I
was
involved
in
was
very
large.
E
There
were
a
lot
of
a
lot
of
data
that
I
needed
to
be
quantified
for,
but
I
was
just
thinking
that
some
of
the
phrase
records
like
they
were
like
like
meeting
attendances
or
you
know,
like
the
most
simple
examples
that
we
already
all
know
that
they
have
like
less
value
than
participating
in
something
larger
or
more
involved
in
the
community,
and
I
was
just
thinking
that
maybe
we
could
develop
or
I
could
develop
a
system
that
that
could
identify
those
differences
and
assign
a
value
to
them
in
a
more
automated
way-
probably
maybe
not
at
first
but
through
development,
have
it
integrated
as
a
quantification,
bot
or
just
wholly
eliminating
the
human
part
and
moving
the
human
part
more
into
a
validation
phase
of
that
quantification
like
identifying
records
that
are
not
easy
to
to
to
quantify
or
or
just
identify
inconsistencies
or
I
was
mentioning
on
the
forum
that
maybe
it
could
be
used
to
identify
when,
when,
when
users
try
to
gain
the
system,
I
don't
know
what
I
know
it's
a
it's
a
it's.
E
It's
not
a
project
that
can
be
done
like
in
a
day,
but
maybe
I
I
could
start
like
experimenting,
maybe
like
doing
something
very
simple
at
first,
like
maybe
classifying
the
the
the
praise
being
given
and
then
maybe
in
the
end,
when
the
system
is
more
advanced
or
more
developed
instead
of
having
like
five
people
quantifying,
maybe
have
four
and
the
bot
and
just
use
it
as
a
comparison
way
just
to
see
if
the
bodies
is
is,
is
learning
correctly
or
is
quantifying
correctly
and
just
get
get
that
new
software
and
your
script
into
the
process
involved,
see
where
that
gets
us.
E
You
know
so
I
just
wanted
to
discuss.
I
know
there
are
like
a
couple
of
of
things
that
are
people
are
worried
about
in
terms
of
like
gaming,
the
system
and
gaming,
the
script
or
or
or
there
were
other
elements
that
were
being
mentioned
on
the
forum
by
maddie,
yeah
and
and
and
yeah.
I
I
just
wanted
to
say
that
I'm
open
to
discussing
and
if
this
is
something
that
is
already
being
done
or
is
something
that
that
you
guys
think
that
is
is
of
no
value.
E
A
We
have
the
ambition
of
phrase
quantification
being
a
a
manual
like
at
least
a
semi-manual
process
that
that
has
a
value
in
itself
to
so
involving
people
as
quantifiers
also
make
them
involved
in
the
community,
because
they
have
to
learn
what
others
are
doing,
etc.
So
it
has
other
values,
and
these
really
simple
phrase
praising
of
simple
contributions.
A
But
I
I
still
see
that
that
there
could
be
a
need
for
something
like
this,
absolutely
not
at
least
to
something
to
verify
against
and
to
identify
patterns,
and
there
will
definitely
be
room
for
doing
like
automated
analysis
of
of
praise
and
quantifications
to
make
that
an
integrated
part
of
the
process.
E
E
A
Super
happy
to
see
already
day
one
the
benefit
of
uploading,
the
csv
files
to
to
github
yeah
yeah.
E
A
A
Okay,
to
be
continued,
thank
you
everyone
for
for
coming.
It
was
a
pleasure
as
always
and
see
you
soon.