►
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
So
welcome
everyone
to
the
this
rewards
work
group
meeting
and
it's
february
the
second
today
I
guess
we
have
a
few
status
updates.
I
don't
have
like
the
like
one
singular
big
topic
to
discuss
today.
So
today
will
be
more
like
a
standard
status,
update,
meeting
and
we'll
see
what
what
comes
up.
A
I
think
we
have
definitely
things
to
to
talk
about
and
plan,
and
my
hopes
were
that
maybe
viva
v
could
tell
us
a
little
bit
something
about
what
the
latest
update
on
the
prey
spot,
but
he
has
not
yet
arrived.
A
B
Yeah
yeah
so
last
few
days
on
the
back
end,
we
are
doing
refactoring
as
we
reached
mvp.
So
right
now
we
are
doing
some
changes
in
the
code
and
I
think
today
we
are
at
the
same
place
where
we've
been,
but
it's
much
nicer
code
and
more
robust.
I
would
say
so
from
this
point
forward.
We
can
develop
new
features.
B
A
So
we
are
sort
of
back
at
the
same
place
where
we
was
one
week
ago.
So
we
have
we've
been
on
a
detour
of
refactoring
and
now
we're
back
again,
and
I
agree
it
was
needed
and,
like
you
said,
it
would
allow
us
to
have
a
more
stable
foundation
to
build
on
and
so
that
that
is
a
part
of
the
process
of
moving
towards
the
the
production
environment.
A
So
what
what
is
happening,
except
apart
from
from
us
doing
the
refactoring
is
that
we
are
going
to
package
the
front
end
and
the
back
end
into
one
like
mono
repository
package,
because
that
will
make
it
easier
for
us
to
deploy
this
system
for
other
communities
later
on.
When
we
have
a
mostly
one
repository
to
work
work
in,
and
we
are
also
setting
up
the
production
server
as
of
now
so
that
the
the
current
server
we're
using
we'll
we
will
be
using
as
a
as
a
test.
A
The
database
has
been
accessible
from
the
outside
world,
even
though
we
have
had
a
firewall
set
up
so
somehow
the
if
the
firewall
is
here,
everything
that
is
has
been
running
in
the
the
docker
containers
have
been
sort
of
running
outside
of
the
firewall
still
and,
and
that
has
made
the
the
database
an
easy
target
for
various
troll
killer,
bots
running
on
the
internet,
looking
for
open
ports
etc.
So
that
that
is
our
current
guess
that
that
that
is
what
has
caused
the
data
database
crashes
and
hopefully
so
now
the
ser.
A
The
database
is
running
on
the
right
side
of
the
firewall
and
we
will
also
add
extra
layers
of
security,
and
hopefully
this
will
not
appear
occur
again.
A
And
if
we
yeah
mitch
just
appeared
so
mitch,
we
were
just
concluding
the
status
update
for
praise,
frontend
and
backhand,
and
maybe
we
could
talk
a
little
bit
about.
C
Well,
I
mean
it
was.
It
was
a
bit
difficult,
the
second
one
that
we
did
because
it
seemed
like
there
was
a
lot
of
issues
like
the
the
the
information
kept
on
being
lost
and
people
were
not
having
the
the
quantify
panel
show
up
for
them,
but
I
feel,
like
that's
user
testing
stuff
more
than
like
quantification
practice,
but
I
think
those
are
still
big
issues
that
we
need
to
figure
out
before
we
can
move
on
from
doing
test
coins.
A
Yeah
those
those
issues
were
an
effect
of
the
database
not
being
there
so
so.
Actually
it
was
no.
The
does
the
system
behave
as
expected,
so
when
a
new
user
logs
in
a
a
user
account
is
a
user
account
is
created.
So
what
what
happened
and
what?
What
caused
the
people
not
seeing
the
quantification
dashboard
was
that
they
had
accidentally
received
two
user
accounts
because
they
they
logged
in
when
the
database
was
empty,
creating
a
new
account
and
then
I
restored
the
backup
creating
recreating
their
old
accounts.
A
C
A
Then
I
think
we
should
plan
to
to
do
a
slightly
smaller
test
quant.
This
would
mean
I
guess
I
don't
know
how
everyone
would
feel
about
that
if
we
were
to
sort
of
delete
the
quantifications
that
have
been
done
now
or
do
you
think
we
should
continue
on
on
the
current
quantification,
because.
A
A
100
praise
per
person,
because
the
the
ideal
solution
is
a
situation
would
be
if
we,
if
we
could
finish
that
quant
mostly
because
then
we
could
export
a
quite
complete
data
set.
You
know
with
with
all
the
numbers
in
all
the
columns,
and
that
would
be
a
good
for
the
taking
it
into
the
next
step.
If
we
were
to
export
the
current
price
period,
that
would
it
would
consist
mostly
of
holes
and
zeros.
So
so
the
whole
analysis
step
would
be
weird.
A
Because
then,
the
next
steps
would
be
sort
of
to
to
to
conclude
that
that
quantification,
export
the
data
move
into
the
analysis
step
and
run
through
that,
and
I
don't
know
if
we
should
try
to
do
a
dry
run.
Also
of
the
it's
difficult
to
do
a
dry
run
of
the
actual
distribution.
I
guess
because
we
don't
have
a
a
test:
net
dial
setup
or
anything.
A
D
C
A
Yeah
and-
and
the
thing
that
we
would
like
to
test
is
perhaps
the
the
the
thing
that
sam
has
mentioned,
that
they
are
working
on
this
evm
crispr
way
of
paying
everything
in
one
batch
automatically
when
the
vote
is
approved,
because
I
guess
that
is
not
a
tried
and
tested
solution
using
the
dispersed
app,
I
guess,
would
would
not
need
to
be
tested,
because
that
is
a
it's
a
thing
out
there.
It
has
been
used
for
a
while.
So
if
we
can
produce
a
csv
file.
C
It's
easy
enough.
I
I
know
how
to
use
evm
crispr.
So
in
terms
of
making
this
script,
I
could
probably
figure
it
out.
A
A
A
Cool
so
then
we'll
try
to
set
up
some.
Some
new
data
in
the
system
set
up
a
new
praise
period,
a
short
one,
and
but
I
don't
think
we
can
just
assign
everyone
that
is
in
the
quantified
pool,
because
I,
my
guess
would
be
that
not
all
of
them
are
set
to
do
another
round
of
test
quantification.
So
I
think,
before
we
assign
quantifiers,
we
would
need
to
sort
of
gauge
who
who
who
is
interested
to
do
it
once
once
more.
A
Which
is
praise
revision
and
neither
ms
or
noggin
is
here,
but
I
can
just
recap
what
we
have
been
talking
about
unless
we
covered
this
in
last
week's
meeting.
I
don't
think
so.
Did
we
do
that?
We
are.
A
We
need
to
do
a
clean
up
of
the
praised
data,
the
old
phrase
data
because
there's
some
there
has
been
some
some
issues
with
the
with
some
phrase
not
being
registered
for
for
some
users
at
occasions,
and
there
are
also
some
some
other
issues
with
the
data
stored
in
the
google
spreadsheet
containing
all
the
place
history.
A
So
it's
sometimes
the
praise
are
bunched
together.
It's
it's
a
it's
on
the
margin.
I'd
say
it's,
my
guess
would
be
it's
less
than
one
percent
of
the
total
praise
amount
affected
by
some
some
kind
of
thing,
but
there's
there's
some
some
noise
in
in
the
old
place
data
and
and
ms
and
then
nagan
will
try
to
identify
the
different
classes
of
noise
and
find
ways
to
remove
it
from
from
the
from
the
phrase
the
old
place
database
and
and
for
for
transparency.
A
We
will
store
that
in
in
a
separate
repository
before
importing
everything
into
the
new
prey
system.
So
we
will
have
the
the
original
the
original
price
data.
We
would
have
the
the
proposed
changes
by
msn
and
nagan,
and
then
we
will
have
a
filtered
the
data
set
with
the
changes
applied
and
then
we'll
have
that
data
set
converted
into
a
json
importable
file
and
all
those
files
will
be
in
in
that
repository.
A
So
anyone
can
see
follow
the
process
from
being
beginning
to
end
and
we'll
do
do
that
before
before
importing
the
final
data
into
the
production
price
server.
A
A
And
the
source
cred
now,
let's
see
and
mateo,
is
not
here
or
has
either
so
I
can
report
a
report
for
them
as
well.
We
had
a
meeting
earlier
today
talking
about
the
the
pollenbot
and
the
short
story
is
that
the
the
pollenbot
is
up
and
running
and
we
are
testing
it
now.
So
it's
running
on
a
a
hidden
channel
on
the
tc
server
and
I
just
tried
it
myself
and
it
seems
to
be
it'd,
be
running
fine
and
the
problem.
A
The
purpose
of
the
pollen
body
is
for
for
us
to
be
able
to
self-administer
our
user
profiles
in
the
source
code
system,
so
for
us
to
be
be
able
to
receive
tokens
based
on
the
the
data
in
the
source
grid.
We
need
to
connect
our
source
credit
identities
with
the
our
github
profiles
and
our
disk
course
profiles
and
also
verify
for
our
discord
accounts.
So
so
we
need
we.
We
interact
with
this
the
problem
bot
to
to
verify
our
profiles.
A
And
let's
go
back
to
the
praise
bot
bye-bye
v
he's
not
here,
so
I
can
report
for
him
as
well
a
lot
of
me
talking
today
but
yeah.
So
what
has
happened
with
the
prey
spot
by
the
way
he's
he
has
been
refactoring
there,
a
little
bit
as
well.
The
prey
spot
is,
is
active
in
it
and
it's
working.
We
are
modifying
the
the
way
that
messages
get
posted
back
to
the
to
the
channel.
A
The
bot
uses
a
little
bit
more
compact
so
that
it
doesn't
take
up
so
much
space
in
the
in
the
chat
channels,
but
other
than
that,
it's
the
the
the
actual
praise
bot
the
new
place
body
is
nearing
near
incompletion.
A
So
soon
we
will
be
able
to
remove
that
item
from
this
agenda
completely.
I
think.
A
D
Just
quick
that
I
had
a
feedback
from
the
quant
that
it
would
be
helpful
to
have
some
type
of
guidelines
of
like
base
measures
of
certain
things,
and
I
think
especially
for
this
quant,
that
we're
doing
that
is
things
that
we
won't
quantify
in
the
future
like
meetings
and
twitter
and
forums
and
stuff.
Maybe
for
these
things
we
could
set
a
base
value
just
to
accelerate
the
process.
Now
of
the
old
quant,
like
the
same
value
that
we
will
set
up
on
source
credit.
C
Yeah,
let's,
let's
define
that,
I
guess
a
little
bit
more
but
like
what
exactly
do
we
give
base
values
for.
D
Yeah
twitter
forum,
like
forum
activity,
twitter
activity,
presents
and
calls.
A
D
A
D
C
That's
cool.
We
have
35
minutes,
I
don't
know
I'd
I'd
love
to
just
like
set
up
the
test,
quant
now
and
then
get
it
rolling
before
the
weekend
comes
in.
D
C
A
I
am
not
certain
that
I
can
run
the
script
that
grahal
made
myself
so
so
that
I
can
import
the
december
data
because
that
is,
I
haven't
looked
into
the
he
has.
He
has
it's
in
a
repository
that
I
have
access
to,
but
I
haven't
tried
running
it
so
so
I
I
cannot
promise
that
I
can
do
it
myself
and
in
in
that
case
I
need
to
wait
until
tomorrow
when
grail,
you
know
it's
night
time
in
the
philippines.
A
Now
so,
okay,
but
I
I'll
I
can
give
it
give
it
a
try.
Definitely
it's
a
ruby
script.
It
shouldn't
be
that.
A
D
A
E
A
A
Well,
I
I'll
give
it
give
it
a
try
and
let's
hope
that
it
runs.
E
Hey
everyone-
I
I
am
you
know
being
part
of
the
dow
research
group
and
then
focusing
on
tc
praise.
I've
been
meaning
to
jump
in
this
call
for
a
while.
So
it's
just
really
cool
you
guys
are
all
doing.
I
was
just
a
few
questions.
I
was
thinking
because
I've
been
mulling
this
over,
as
I
was
doing,
a
bit
of
a
deep
dive
in
source
cred
for
the
research
side
was
on
the
policies,
that's
being
envisioned,
because
you
have
this
one.
E
Where
you
can
you
know
your
reputation,
sort
of
continues
with
you
or
that
it's
it's
sort
of
you're,
only
looking
at
each
interval
period
and
then
it's
sort
of
reset
across
the
board.
So
I
was
just
curious
like
what
what
the
sentiment
is
on
that
and
then
on
these
instances
and
weights
that
we're
going
to
be
that
ultimately
get
configured.
E
A
To
answer
you,
the
your
second
question
that
there
will
be
no
configuration
of
weights
and-
and
there
will
be
the
discussion
about
you-
should
be
like
standardized
like
we
mentioned
this
standardized
values
for
these
most
simple
types
of
praise.
But
then
it's
a
it's
an
exercise
in
collective
intelligence.
So
so
we
will
not
provide
clear
guidelines.
You
should
place
this
this
kind
of
contribution
with
this
score,
so
it
it
would
be.
A
It
would
be
an
emergent
property
that
grows
out
of
the
the
group
of
quantifiers.
Over
time
there
there
will
emerge
practices,
common
practices
and
and
sort
of
maybe
a
common
understanding
on
how
to
value
things,
but
we
will
try
not
to
steer
that
process
from
the
beginning,
because
that
would
be
mean
that
we
take
a
top-down
approach
and
we
really
don't
want
to
do
that.
E
This
this
first
one
was
on
source
cred,
so
not
on
praise
but
like
on
the
source.
Cred
policy
configuration
where
you
have
two
options
where
your
cred
score
basically
lives
with
you
throughout
time.
So
you're
constantly
sort
of
increasing
your
reputation
or
it's
sort
of
it's.
It's
reset
across
the
board
in
each
interval.
A
That
would
be
a
topic
of
discussion
for
tomorrow's
parameters
called
yeah.
E
A
Yeah,
the
the
reward
board
will
be
will
have
the
responsibility
to
manage
to
manage
those
parameters
initially
and
and
people
in
the
reward
board
can
be
replaced.
I
don't
know
how
we
defined
that
how
that
process
looks
in
detail,
but
generally
the
the
reward
board
has
the
responsibility
to
to
check
with
the
community
and
in
in,
if
needed,
do
advice,
process
or
even
voting.
A
If
that
that
it
becomes
apparent
that
there's
a
there's
like
a
split
in
the
community
on
how
how
the
community
views,
how
much
to
value
different
things
and
if
the
the
community
don't
think
the
reward
board
does
a
good
job.
I
I
there
has
to
be
a
way
for
the
community
also
to
replace
the
reward
board,
but
but
but
the
general
idea
is
that
the
the
reward
for
each
praise
period
will
evaluate
the
current
parameters
and
we'll
be
able
to
tweak
them
if
they
see
that
the
results
are
skewed
in
in
some
some
way.
A
That's
cool
and
that's
what
that's!
What
one
of
the
really
cool
things
of
of
starting
this
bi-weekly
process
of
every
two
weeks:
sort
of
re-evaluating
the
parameters
and
re-evaluating
analyzing
the
results
and
making
maybe
small
adjustments.
If
we
see
that
something
seems
off
and
see
how
that
develops
over
time,
and
our
hopes
are
that
it
will
lead
to
too
vastly
better
results
than
before.
E
Yeah,
I
I
can
see
a
benefit,
and
I
was
even
thinking
around
this
in
the
research
was
like
not
totally
having
a
chaos.
Theory
approach,
but
like
so
that
people
don't
at
the
onset,
because
otherwise
you're
setting
the
rules
and
people
know
that
what's
rewarded.
So
that's
clear
if
it's!
If
the
community
has
a
clear
thing,
they
want
to
incentivize
they'll
get
more
of
it,
but
if
it's
not,
it
can
be
more
authentic
because
no
one's
clear
what
gets
rewarded
anyway.
Sorry,
I'm
just
going.
I
just
wanted
to
throw
that
that
out
there
thanks.
A
Unless
we
have
any
anything
else,
that's
we
need
to
bring
up.
I
I
suggest
we
we
we
close
it
here
and
then
try
to
set
up
this
new,
this
new
quant
and
I'm
going
to
jump
in
to
dive
into
the
ruby
script
and.