►
Description
Timecodes:
00:00 - Agenda
01:41 - Roadmap to First Quant
05:23 - Rules of Praise and Quantification
24;24 - Technical platform
26:09 - Sourcecred
38:44 - Wareframes
🙏 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
If
we
need
to
take
a
short
discussion,
we
can
do
that
on
each
each
stream,
but
it
would
be
good
to
reserve
like
20
minutes
at
the
end
or
something
to
have
space
for
talking
about
what
comes
next.
A
B
A
Good
in
that
case,
my
the
first
one
out
is
mitch,
but
he's
not
here,
so
I
guess
I
can
describe
it
talk
a
little
bit
about
what
he's
been
up
to.
Maybe
I
should
try
to
find
the
that
document.
A
Yeah,
so
mitch
has
been
doing
a
really
solid
work
of
of
putting
words
to
describe
the
the
process
from
here
to
the
the
first
quant
and
then
that
so
that
aligns
with
the
our
mvp
development
of
the
first,
the
first
version
of
the
new
phrase
backend,
and
he
has
described
that
process
from
from
here
to
then,
because
there
are
some
steps
that
needs
to
be
taken
along
the
road
like
getting
community
approval
for
our
proposed
parameters
and
and
which
will
be
in
the
rewards
committee
and
sort
of
getting
getting
feedback
of
the
on
the
overall
process
as
well.
A
But
he
has
been
working
really
great
with
with
this.
So
it's
not
completely
finished
yet,
but
but
it's
almost
there
I
would
say
we
have
been
bouncing
a
lot
of
ideas
in
the
comments
and
if
you
have
time,
please
join
join
that
discussion
before
it
turns
into
a
proposal
and
then
feel
free
to
add
more
comments
to
it.
A
I
don't
know
if
there's
anything
more
to
say
about
that.
Yeah.
A
But
what
we
also
did
is
I
I
did
some
sort
of
infographic
that
is
in
line
with
his
descriptions,
so
that
is
on
on
the
mirror
board.
So
we
will
attach
that
to
any
any
proposal
we
make
or
any
document
or
yeah
welcome
mitch.
A
And
I
I
just
described
what
you
have
been
doing
and
that
we
have
had
a
good
discussion
in
the
comments
etc
and
that
I've
made
an
info
infographic,
also
trying
to
sync
with
your
your
document.
So
what
are
the
next
steps
for
that?
When,
when
will
we?
E
So
I'd
like
to,
if
you
have
any
feedback
before
that,
please
do
it
like
now,
basically-
and
I'm
gonna
put
together
something
formal
and
the
only
reason
that
I
want
it
done
so
quickly
is
to
meet
our
deadline,
which
is
to
have
it
done
in
what
six
seven
weeks
christopher
yeah
yeah.
So
I
mean,
I
feel,
like
we've,
had
a
pretty
good
idea,
but
of
course,
more
input.
A
A
So,
let's
move
on
to
next
next
dream,
which
is
the
rules
of
praise
and
quantification
leave
it.
You
have
something.
C
Yeah,
so
for
the
rules
of
quantification,
we
had
a
call
this
week
mitch
and
I
and
we
were
brainstorming
a
little
bit
and
I
think
we
got
to
an
interesting
place.
That
is,
I
posted
in
the
the
reward
process
description,
but
that
the
appraised
data
would
be
clustered
by
contributors
and
anonymized
for
quantification.
C
So
that
would
fix
a
few
problems.
One
we
were
thinking.
It
would
be
great
if
the
people,
if
in
the
time
of
the
quantification
we
didn't,
have
names,
so
the
value
could
be
attached
to
the
action
and
not
to
the
person.
C
But
then
we
thought,
oh
sometimes
it
is
relevant
to
know
that
is
the
person,
because
you
get
so
much
more
information
from
there.
But
since
we
are
trying
to
bring
more
new
people
to
the
quantification
and
in
an
effort
of
being
more
transparent
and
fair,
if
we
have
more
descriptive
praise,
then
it
would
be
easier
for
quantifiers.
C
But
then
I
was
thinking
what,
if
what?
If
there's
a
lot
of
double
praise
like
that
happened,
a
lot
with
zaptimus,
for
example,
that
he
would
he
was
praised
multiple
times
by
recording
the
calls
and
then
from
there.
We
have
multiple
signals
like
one
should
like
he
was
praised
so
many
times
that
he
should
be
that
there
is
a
huge
signal
of
how
valuable
it
is,
what
he's
doing
so.
Maybe
he
should
receive
like
something
for
all
of
those
phrases
or
was
his
pray.
C
Was
he
praised
by
accident
multiple
times,
because
someone
didn't
see
that
he
was
praised
before
or
how
like?
We
could
solve
that.
So
we
thought
that
clustering
all
of
one
person's
contribution
like
one
next
to
the
other,
then
we
would
have
an
understanding
of
how
much
they
are
receiving
for
an
action
in
specific
and
how
important
is
that
action,
considering
the
signal
of
how
many
people
praised
so
yeah?
That
is
the
direction
we
thought
for
quantification.
D
Really,
I
feel
like
one
of
the
really
important
things
about
praise.
Is
this
like
ability
to
have
decentralized,
updates
and
like
if
you
come
in
and
quantify
and
you
get
to
learn
who
is
doing
what
you
know
like?
Oh
this
person
is
doing
all
this
work.
Okay,
I
know
I
can
go
to
them
now.
You
know
and
like
there's
like
this
decentralized
update
approach
that
are
factored
like.
I
feel,
like
praise,
has
two
unique
things
that
other
reward
systems
don't
have.
D
That
is
decentralized
updates
from,
like
you
know,
from
the
edges
and
then
real-time
acknowledgement.
So
I
feel
like
removing
the
names
in
many
ways,
gets
rid
of
the
value
of
the
of
updating
people.
C
B
We
still
keep
the
names,
but
it's
just
for
the
quantifiers,
like
everyone
is
seeing
all
the
names
and
all
the
action
happening,
but
it's
just
five
or
fifteen.
I
don't
know
how
many
quantifiers
we
will
end
up
having
and
it's
just
these
people,
the
ones
who
are
not
going
to
see
the
names,
but
the
rest
of
the
community
is
going
to
see
everything.
D
C
A
This
is
a
super
important
discussion.
Could
we
pause
that
for
for
now
and
then
continue
it
asynchronously
and
then
make
a
decision
together?
On
that
I
I've
noted.
I
noted
the
comment,
but
what
I'm
also
looking
for
in
in
the
in
the
the
rules,
the
guidelines
is,
you
know,
instructions
to
the
the
quantifiers.
How
should
you
these
are
the
guidelines
for
quantifying?
A
Is
it
is
the
quantifying
only
like
choosing
one
number,
even
if
it's
a
free
free
form
number
or
we
choose
a
have
this
fibonacci
sequence
scale
or
how
we
do
it.
Is
that
the
only
thing
you
choose
for
for
each
place
or
is
there
something
else?
Is
there
you
choose?
Also
a
category:
is
there
you
you,
you
do
something
we
have
the
the
the
possibility
of
do
doing
something
more
to
better
categorize
or
give
the
appraiser
a
real,
a
good
value.
C
H
I
wanted
to
offer
something
if
there's
space
for
it,
I
didn't
want
to
cut
you
off,
though
no
go
ahead,
the
there's
something
about
source
crud,
where
we're
using
it.
Where
there's
like
potential,
I
believe
to
capture
more
data.
H
If
you
actually
have
a
quantifier
or
like
a
metric
for
like
the
things
you
want
to
capture
or
like
make
a
certain
value
like
maybe
a
handshake
emoji
is
when
people
collaborate
together,
or
you
know,
just
using
the
emojis
different
and
having
somebody
who
is
quantifying
having
like
a
legend
even
perhaps,
and
then
maybe
maybe,
then
it
would
be
possible
to
see
like
the
graph
project
out
the
data
separated.
Somehow
in
those
categories,
that's
something
I've
been
itching
forever.
I
don't
know
if
it's
a
possibility.
A
I
think
we
all
already.
We
have
noted
that
for
like
a
future
thing
to
just
to
explore,
how
could
we
use
reactions
within
praise?
I
think
it's
definitely
out
of
scope
for
the
first
version,
because
we
need
to
get
something
ready
that
is
fairly
similar
to
the
thing
we
we
have
but
yeah.
Definitely
I.
E
Just
had
a
maybe
a
quick
thought
about
that.
That's
actually
a
really
interesting
idea,
because
how
the
praise
bot
already
puts
a
check
on
to
receive
praise
and
it
could
actually
maybe
add,
like
two
or
three
other
emojis,
and
then
the
user
could
provide
more
data
if
they
wanted
to,
which
would
be
just
like.
You
were
saying,
like
a
handshake
or
something
like
that
which
would
auto
categorize
it
within
the
system.
B
I
just
want
to
say
mitch:
I
like
that
from
a
technical
standpoint,
because
we
kind
of
have
that
infrastructure
already
from
the
work
that
muhammad
did
on
the
praised
data
set
with
the
clustering.
So
it's
like
an
automatic
classification,
so
that'd
be
pretty
cool
if
it
just
populated
emojis,
right
away.
C
C
Yeah
yeah,
I
agree
hello.
E
A
I
C
A
C
A
C
C
I
I
could
look
into
it
more,
but
those
were
some
of
the
things
that
were
coming
up
as
things
that
should
continue
to
be
praised
that
we're
praising
someone
for
volunteering
for
taking
initiative
for
unsingling
things
for
preparing
something
for
asking
relevant
questions,
giving
direction
listening,
giving
hard
work,
commitment,
providing
information
and
insights
leadership
being
supportive,
holding
space
being
proactive,
sharing
responsibilities,
inviting
someone
to
join
being
welcoming
giving
valuable
high
vibes
being
amazing,
like
things
like
this
are
the
bulk
of
phrase
and
that
I
feel
like
it's
really
hard
to
capture
in
other
systems
and
then
some
of
the
things
that
can
be
automated-
that
we're
also
being
praised,
is
like
producing
graphics.
C
How,
if
this
was
an
issue,
this
could
be
captured
by
by
a
source
cred.
So
it's
not
like
the
act
of
producing
a
graphic
that
would
be
praised,
but
maybe
the
quality
in
which
they
put
to
produce
these
graphics
and
then
tweeting
and
engaging
in
the
forum,
and
things
like
that
can
be
automated.
C
C
So
I
think
we've
been
avoiding
these
things,
and
this
might
be
for
a
lack
of
information
that
we
have
like.
Maybe
I
don't
know
what
juan
did
for
the
training,
but
I
just
see
that
he's
there
involved
with
it.
So
I'll
praise
him
for
the
training.
But
how
could
I
get
to
know
more?
How
could
I
be
more
descriptive
of
the
praise?
I'm
dishing-
and
maybe
this
will
like
long-term
incentivize
more
of
this
communication
or
people
that
have
like
more
insights
about
something
to
to
bring
it
up.
C
So
I
was
thinking
like
this
could
be
the.
I
don't
think.
I
think
it's
good
that
we
don't
have
so
many
rules
and
then
for
the
quantification
that
I
really
like
what
you
suggested
christopher
of
the
fibonacci
sequence.
So
it
wouldn't
categorize
things,
but
we
would
just
have
like
same
numbers
that
people
are
operating
from
and
there
is
a
scale
of
like
less
relevant,
more
relevant,
less
impactful,
more
impactful,
but
to
the
subjectivity
of
the
quantifier.
F
You
know
they
feel
is
appropriate
inside
each
of
those.
It
doesn't
have
to
be
that
prescriptive,
but
it
might
be
relevant
data
that
already
exists,
so
you
could
sort
of
have
a
breakdown
in
a
way
that
people
can
quantifiably
understand
it,
because
those
are
the
the
qualitative
points
like
the
it
are
more
go
to
them
like
the
motivation.
But
it's
like
thinking
about
how
much
praise
is
being
driven
in.
You
know
this
working
group
versus
that
working
group,
maybe
just
a
just
a
thought.
A
Yeah,
it
is
really
tempting
to
say
to
to
wanting
to
add
more.
I
I
I'm
tempted
by
that.
Definitely
because
I
see
before
every
extra
data
point
we
we
added
the
the
our
ability
to
do
really
cool
analysis
gets
gets
better
and
better,
but
at
the
same
time,
when
moving
from
one
data
point,
which
is
the
price
weight
or
price
score
to
two
data
points,
that
is
the
double
amount
of
work
for
for
those
quantifying.
So
I
think
it's
a
really
fine
balance.
F
I
was
thinking
about
the
emojis
like
it
could
be
linked
to
the
emoji
like
each
working
group
would
have
an
emoji.
So
if
you're
going
the
emoji,
I
mean
you
have
to
think
about
what
the
emoji
means.
Like
a
definition,
maybe
I
mean
if
you
want
to
have
it
any
time
so
that
you
could
run
like
you
could
get
some
analysis.
That
could
be
one
way
to
integrate,
that
without
adding
bureaucracy
to
it,.
D
Well,
I
I
think
the
easiest
way
is
just
tracking
what
channel
it's
dished
in
and
not
having
one
phrase
channel.
That
being
said,
I
definitely
like
the
idea
of
keeping
the
mvp
scope,
narrow
and
keeping
things
clean,
but
yeah,
but
I'd
put
it
on
the
praiser
and
make
them
just
start
playing.
H
I
think
discord
developers
could
probably
find
a
way
to
read
the
reactions
and,
if
you
had
everybody
who's
a
contributor
on
like
some
sort
of
spreadsheet,
that
was
broken
out
by
the
work
groups.
They
could
probably
feed
the
data
to
it
and
it
would
show
you
who's
liking.
What
and
where
it's
going
to
like
that
way.
E
E
But
I
think
for
the
first
quant
and
just
for
like
the
that
initial
phase
of
like
getting
people
to
quantify
less,
might
be
more
useful
to
us
right
now.
G
I
had
a
few
thoughts
about
this
since,
since
they're
talking
about
trees,
couldn't
we
just
maybe
add
a
scope
to
the
phrase
trace
command
where
you
couldn't
specify
which,
what's
the
context
behind
it,
we
need
we,
I
think,
like.
G
Instead
of
using
our
old,
like
text
based
workflow,
we
could
use
the
new
slash,
commands
ui
from
discord,
so
it
kind
of
shows
you
what
things
you
can
put
in
and
we
could
have
like
an
optional
parameter
for
what's
the
context
here,
I
would
like
that
could
have
options
like
which
working
group
you're
related
to
or
something
like
that,
would
that
be
feasible.
A
Definitely
look
let's
look
into
that
and
and
see
if
it
fits
within
the
scope
of
the
first
version
and
or
or
not,
but
but
that
is
super
interesting.
Of
course
you
have
putting
the
the
weight
is
some
more
weight
on
the
people
actually
doing
the
praising,
because
they
are
more
than
putting
the
more
more
load
on
the
quantifiers.
A
A
A
So
then
I'll
I'll
cover
for
him
and
we
we
have
had
a
the
discussion
about
going
back
and
forth
about
the
technical
platform
for
for
the
back
end,
but
we
have
decided
to
to
go
with
the
java
as
a
back
end,
because
our
core
developer
or
our
lead,
develop
back-end
developer.
Rudolph
is
really
proficient
with
that
platform.
A
It's
a
stable
platform
that
has
been
used
for
many
years.
It's
not
the
the
coolest
newest
technology,
but
someone
would
say
that
that
is
a
good
thing
as
well
and
and
me,
and
the
noggin
also
have
some
some
job
experience
and
then
for
this
mvp.
It
feels
like
the
right
decision
it.
A
It
allows
us
to
move
forward
really
quickly
and
then,
at
a
later
later
stage
we
will
probably
be
wanting
to
look
at
moving
towards
a
web
3
back
end,
somehow
together
with
someone,
but
but
that
is
out
of
scope
for
for
this
first
version
for
the
mvp
I'd
say.
A
So
I
I
don't
have
that
much
more
to
say
about
that,
and
moving
on
to
the
front-end
architecture
will
be
there.
There
haven't
been
so
much
discussion
about
that.
I
think
everyone
is
happy
with
doing
a
react
front
end
similar
to
for
for
the
instance
that
e-commerce
website
or
params
et
cetera,
so
that
nothing
strange
there.
A
Source
cred,
mateo
or
viv.
Maybe
you
could
say
something
about
the
the
twitter
and
meeting
attendance
bots.
G
So
I
haven't
started
working
on
the
twitter
part,
but
I
did
for
the
meeting,
but
I
don't
remember
the
name
that
we
talked
about
yesterday.
I
formed
that
one
and
it's
working,
I
think
maybe
you
can
deploy
it
with
a
little
bit
more
changes,
so
maybe
like
a
day
or
two,
we
could
like
smooth
out
the
details
and
have
something
that's
easy
to
use
and
does
the
things
we
need
and
like
which
channel
do
we
need
this
to
be
posted
in?
G
Is
there
like
a
new
channel
we'd
make
for
source
grid
messages
or
something
like
that
where
people
can
react,
and
you
know
the
reactions
count
as
whoever's
being
mentioned
in
that
message,
or
something
like
that?
The
way
like
the
props
channels
work
in
one
hive
and
other
terms.
A
G
No,
so
discord
throws
off
an
event
whenever,
like
someone
joins
a
first
call,
but
yeah
we'd
have
to
there's
like
two
ways
to
go
with
it.
We
call
a
meeting
whenever
the
first
person
joins
a
call,
and
we
say
it's
a
meeting
until
a
person
leaves
the
call
or
in
other
ways
that
we
make
a
manual
command
for
this.
A
But
it
would
place
the
the
burden
on
the
the
the
meeting
host
to
to
enter
a
command
saying,
like
start
tracking,
this
meeting.
G
And
one
thing
one
thing
we
could
do
is
that,
since
I
think
we
already
have
a
schedule
whenever
we
have
our
main
calls
etc.
So
for
most
of
the
calls
we
could
just
automatically
have
like
a
cron
job
telling
the
board
when
to
count
things
as
a
meeting
or
something
like
that.
A
It
doesn't
sound
like
a
bulletproof
setup,
but
maybe
it's
difficult
to
know
what
what
is
a
meeting
if
it's
in
the
tc
calendar,
then
it's
meeting
if
yeah
yeah.
G
So
since
we
already
have
like
a
reminder,
application,
one
thing
we
could
do
is
like
make
a
like
a
copy
of
our
main
calendar
and
then
have
that
calendar
act
as
the
source
guide
for
our
bot
for
reminders,
as
well
as
tracking
meetings
so
like
whenever
it
like
checks,
the
calendar
every
x
minutes
or
something
like
that,
and
whenever
a
call
starts,
it
takes
notes
down
time
and
it
pretty
much
tracks
whoever's
entering
a
voice
channel
all
the
time
we
just
lock
the
data
whenever
we
know
that
a
coil
is
going
on
right
now,.
A
Yeah
cool
so
there
to
some
sum:
it
up
there's
a
loads
of
possibilities
of
tracking
meeting
attendance.
We
will
that
work
is
not
concluded,
but
we'll
we'll
continue
with
that
and
when
it
comes
to
the
twitter
bot
that
that
is
a
separate
thing
that
is
not
yet
developed.
So
that
is
something
we
have
to
look
it
deeper
into
how?
How
can
we
track
twitter
data?
What
kind
of
twitter
data
would
we
like
to
track
and
and
yeah.
G
Yeah,
so
we
could
have
an
application
that
like
tracks,
hashtags
and
mentions,
or
interactions
with
our
with
our
twitter
account,
but,
like
from
what
I
have
noticed,
we
could
use
a
two
lake
orbit
to
keep
track
of
that.
G
I
don't
know
if
we'd
be
open
to
like
using
an
external
tool,
but
it's
somewhat
like
source
grid,
but
for
social
platforms,
and
we
could
just
use
it
for
twitter,
and
you
know,
I
think
it
gives
you
like
an
interaction
score
between
the
people,
interacting
on
your
twitter,
etc,
and
that
we
could
use
that
or
we
could
set
up
our
own
books
like
I'm,
not
sure
how
much,
how?
What
are
the
exact
parameters
we're
looking
for?
Do
we
look
for
like
how
many
likes
someone's
retweet
off
our
tweet
gets,
or
what?
G
A
A
Yeah,
I
forgot
to
mention
that
we
source
credit
was
it's
its
own
heading
and
if
I
haven't
said
that
we
we
we
have,
I
think
we
did
that
before
this
week,
but
it
it
has
become
clear
that
we
need
to
separate
the
the
streams
of
of
the
phrase
streams
and
the
source
credit
streams.
So
we
sort
of
we
treat
them
as
as
two
two
separate
projects
within
the
tec
reward
system,
so
for
everything
that
can
be
automatically
quantified,
we
go
with
source
grid
and
and
everything
that
cannot
be
automatically
quantified.
A
A
And
then
we
make
needs
to
need
to
make
sure
that
everything
that
we
want
to
cover
is
covered
by
source
code,
so
that
we
include
all
the
github
repositories
and
that
it
doesn't
miss
anything
so
that
that
is
a
part
of
the
work
that
needs
to
be
done
during
this.
This
period
until
the
first
quant
when
when
it
comes
to
source
cred
but
mateo.
Sorry.
A
Yeah
he
has
a
good
good
idea
about
configuring.
The
params
and
and
also
source
code
has
offered
to
assist
us
a
bit
with
setting
params
as
well.
E
Yeah
speaking
to
that,
there's
that
the
appendix
I
made
in
the
process
description
and
I'm
not
sure
if
it's
exhaustive,
because
some
of
these
source
credit
instances
I'm
not
sure
how
they
work
like
as
they
relate
to
twitter
and
the
data
that
we'll
be
getting
from
alexandra
for
meeting
attendance.
E
So
I
don't
know
if
that's
everything,
and
maybe
somebody
who's
more
familiar
with
source
cred,
could
just
fill
that
out
or
validate
it.
A
C
G
G
Question
related
to
that,
would
we
be
using
alexander,
or
do
we
want
to
make
our
own
pawn.
A
C
A
F
A
So
then
I'd
say
we
have
the
option
of
using
alexandre
as
a
bot
to
feed
data
into
source
grid,
also
with
some
some
some
tweaks,
but
this
other
other.
What
we
we
found.
It
was
specifically
tailored
for
doing
that,
but
we
can
look
at
them
both.
B
E
G
They're,
like
tracking
meetings
and
we
can
pre-specify
meetings
like
the
other
bot.
We
were
working
on,
we
hoped-
and
we
might
be
using
that
one
is
that
we'll
have
like
a
specific
time
period
for
which
it
locks
things
so
that
I
think
that
can
address
our
concerns
with
respect
to
that
and
another
thing
we
could
maybe
do,
I'm
not
sure
we
should
do
it
is
like
have
a
bot
in
the
channel
that
listens
to
audio
and
see
who's
speaking
or
not,
but
I
don't
know,
I
think,
that's
slightly
invasive.
F
I
just
want
to
throw
out
the
question
why?
Because
I'm
working
on
something
similar
where
I'm
working
but
like
the?
Why
do
you
want
to
incentivize
meetings
because,
actually,
in
the
one
I
was
working
on,
we
actually
wanted
to
say
meetings,
don't
count
as
a
criteria,
because
we
wanted
to
disincentivize
meetings
and
only
give
praise
for
like
the
the
actual
the
value.
So
I'm
throwing
that
out.
There.
D
I
I
would
say
that
it's
all
coordination
and
it
always
has
been-
and
unfortunately
in
our
in
our
meeting
culture
like
in
our
remote
culture,
the
only
way
to
really
effectively
I
mean,
there's
lots
of
ways
to
coordinate
via
chat,
but
there
is
a
lot
of
value
in
like
meeting
face
to
face
on
video
and
there's
office.
You
know
I
went
personally
on
on
this
stuff
I
wouldn't
try
to
over
prescribe
like
I
would
try
to
find
a
way
to
monitor
outside
of
the
tracking
so
like.
D
If
someone
is
abusing
the
system
finding
a
way
to
flag
them
in
discord
and
say
this
person's
gaming,
the
system
and
just
like,
then
just
remove
them.
You
know
or
or
give
them
graduated
sanctions
through
a
different
means,
but
let
the
bot
manage
the
bot
like
we
have
four
hour
hack
sessions.
I
would
love
to
see
off,
like
octopus
is
doing
office
hours
right
and
if
no
one
shows
up
for
those
office
hours,
you
should
still
get
the
you
should
still
get
the
the
praise
for
doing
it.
You
know.
E
A
A
So
I
have
started
doing
simple
wireframes,
I'm
not
a
graphic
designer,
but
I
I
I'm
happy
to
work
with
the
the
flow
in
the
application.
So
for
this
this
thing,
for
instance,
is
the
user
activation
flow?
When
you
have
been
dished
praise
and
then
you
need
to
activate
your
account.
A
The
current
suggestion
proposal
is
that
we,
instead
of
activating
on
on
discord,
we
we
we
provide
a
link
in
the
activation
in
the
message.
This
is
saying
that
you
have
been
dish,
praised
and
take
the
user
to
the
to
the
web
interface
instead,
where
they
log
in
with
them
their
metamask
voltage,
wallet
and
sign
a
message
and
then
they're
they
are,
the
account
is
activated,
so
that
is
one
of
one
of
the
two
main
flows
actually,
because
this
is
a
really
simple,
simple
app.
A
So
so
praising
and
activating
your
account
is
like
one
big
thing
and
then
the
other
big
thing
is
quantifying
and
then
there's,
of
course,
administrative
small
tasks
around
that.
But
what
we'll
try
to
keep?
It
really
is
simple
in
this
first
iteration,
so
the
the
the
second
flow
would
be
yeah
you
as
a
quantifier
you
log
in
to
the
the
web
page.
A
You
see
a
list
with
all
the
praise
and
from
there
you
can
move
on
to
doing
the
the
quantification.
I
I
didn't
finish
that
one
before
the
meeting
something
along
those
lines,
perhaps
we
should
connect
and
add
a
graphic
wizard
to
the
team.
Maybe
that
would
be
good,
even
if
we
try
to
keep
it
really
simple.
A
Yeah,
because
we
I'm
thinking
it
will,
this
whole
thing
will
be
more
of
a
snapshot
looking
thing
so
a
quite
wide,
simple
tool,
rather
than
something
that
is
super
tec
branded,
because
we
want
to
be
able
to
use
it
easy
with
also
with
other
communities
as
well.
D
So,
are
you
looking
for
ux
graphics
or
are
you
looking
for,
like
ui
design,.
A
I'm
more
more
ui
designers
giving
us
a
choosing
a
font
setting
a
color
scale,
saying
yeah.
You
should
have
rounded
buttons
or
square
buttons
or
you
know,
having
a
so,
we
can
have
a
something
to
lean
against.
D
That
might
be
more
rodri
than
acid
laser.
I
don't
know,
ask
them
both
and
see,
but
I
know
rodri
does
more
ui.
When
I
chewie.
Do
you
know
acid
laser?
Does
he
do
a
lot
of
ui
design
or
is
it
mostly
just
graphics.
I
Oh,
it's
mostly
graphics.
He
doesn't
have
experience
in
in
ui,
but
I
know
that
he's
been
doing
some
reads
the
past
week
because
it's
he's
interested
in
in
the
field,
but
I
don't
know
if
it's
gonna
be
like
enough
for
this
stage,
but
I
can.
I
can
ask
him
and
if
he
feels
competent
enough,
I
can
put
him
in
touch.
B
A
Cool
thanks,
and
also
on
the
topic
of
front-end
and
wireframes
and
front-end
development.
I
I'd
like
to
introduce
striker,
as
I
joined,
joined
us
to
to
help
out
with
the
the
front-end
development
strike.
Would
you
like
to
say
just
introduce
yourself.
J
Yeah,
hey
guys,
yeah
I've
been
talking
with
christopher
today
as
well
as
this
week.
About
I
mean
this
is
really
the
very
beginnings
very
beginnings
of
of
what
it,
what
the
front
is
going
to
look
like.
J
I
guess,
but
we
moved
the
the
repo
today,
so
I
just
get
cloned
it
just
now
and
did
a
yarn
install
and
give
me
a
little
rough
outline
of
a
login
page
and
what
what
the
page
wants
to
look
like
once
you
log
in
so
yeah,
it's
like
a
nice
big
ball
of
of
clay
and
you're
gonna
start
shaping
it
with
something
so
yeah
I've
got
it
all
sitting
here,
ready
and
just
want.
J
You
know
some
colors,
some
palettes
and
yeah
pretty
much
just
like
colors
and
stuff.
This
is
just
kind
of
the
interest
that
I
have
but
other
than
that
yeah.
No,
I'm
glad
to
be
here
and
yeah,
and
I
think
I
gave
a
chat
to
negan
earlier
about
this
whole
front.
End
project.
So
thanks
to
him
for
bringing
you
here
and
yeah
cool
hi.
E
We
have
a
question
about
your:
are
we
going
to
have
any
sort
of
ui
for
the
rewards
dao
committee
to
analyze
the
information.
A
Yes,
and
maybe
when,
when
I
drew
the
process
earlier
today,
I
I
did
it
like
this,
so
so
I
in
the
left-hand
stream,
it's
it
is
praised
with
the
the
rope
raised
data,
the
manual
quantification
and
and
then
we
we
calculate
the
the
the
rewards.
But
I
I
added
this
step
outside
of
praise
for
now.
I
don't
know
if
we
will
have
time
to
do
an
ui
for
the
for
the
manual,
the
validation
step
as
well.
A
A
E
E
Maybe
we
still
need
to
figure
out
like
what
the
power
is
given
to
this
sub-dial,
but
it
they
need
a
way
to
be
able
to
interface
with
the
data
that
we're
collecting,
even
as
simply
as
viewing
it
and,
secondly,
to
that
point,
how
will
we
be
able
to
actually
do
the
the
blockchain
part
like
the
interfacing
so
collecting
the
data
and
then
distributing
tokens.
B
A
Now
my
my
proposal
just
now
is,
is
to
to
have
a
cautious
approach
to
this
and
to
be
sure
that
we
we
are
finished
on
time
and
and
let
both
praise
and
source
cred
export
their
data
back
actually
into
a
google
spreadsheet
again,
and
in
that
spreadsheet
you
you
do
the
the
validation
and
you
also
do
the
the
calculate
the
token
allocations
and
then
from
there.
You
need
to
be
able
to
export
that
into
a
in
a
data
format
that
dao
can
accept
and
and
then
distribute,
distribute.
B
E
C
D
A
And
the
the
way
I've
illustrated
it
here
is
that
the
the
the
reward
systems
committee
or
how
I
interpreted
your
your
doc
as
well,
is
that
they
have
only
like
really
a
few
responsibilities:
the
the
reward
system
committee.
They
they
set
the
the
parameters
for
for
praise
and
and
source
cred,
and
also
collect
feedback
from
the
community
and,
if
needed,
there
is
a
vote
to
change
the
parameter
assembly.
A
But
they
are
responsible
for
for
managing
the
instances
and
setting
the
the
params
and
then
the
quantifiers
do
most
of
the
work
and
or
source
cred,
which
is
automatic.
And
then,
at
the
end,
that
committee
they
do
request
the
funds
from
tec,
the
the
funds
that
will
be
distributed
and
they
approve
the
distribution
and
basically
that's
it.
For
the
rewards
committee.
C
E
So
this
is
what
we
were
talking
about
the
other
day
in
the
phone
call
it's
like
do
we
want
to
reward
praise
in
die
or
tec
and
we
kind
of
favored
tec,
but
then
how
do
we
get
it?
You
know,
so
we
would
actually
have
to
take
the
die.
That's
been
allocated
and
use
that
to
buy
from
our
bonding
curve
tec
yeah
at
the
price
at
the
marketplace.
D
Yeah
I
mean,
hopefully
the
reward
system
will
get
the
initial
buy
right
and
get
a
nice
fat
stack
and
then
the
tec
price
will
mathematically
go
up
because
all
the
tokens
are
locked
after
that
which
is
kind
of
cool.
Most
projects
can't
say
that,
but
all
the
tokens
we
met
will
actually
be
locked,
so
the
price
can
only
stay
the
same
or
go
up
even
if
no
one
buys
because
no
one
can
sell.
D
So
we
should
end
up
with
a
good
deal
on
tc
tokens
to
start
and
then,
after
that,
when
we
do
re-ups,
it's
really
nice.
For
the
I
mean
the
original
design
of
this
system
was
that
every
time
the
conviction
voting
pays
out,
it
sends
it
to
the
bonding
curve,
buys
tokens,
and
then
you
get
the
tokens
out
and
that's
a
that's
a
module.
D
I
want
to
build
for
sure
post
launch
so
that
that's
so
easy,
but
I
think
it's
easy
enough
to
just
have
the
money
go
to
a
trusted
actor
who
then
just
goes
and
buys
into
the
bonding
curve
and
then
sends
it
to
the
reward?
D
E
C
That
mm-hmm
sorry
I'll
go
quick
and
I'll
pass
you
to
it.
If
that
is
in
the
works,
then
maybe
we
don't
even
need
to
think
about
that
proposal,
but
focus
on
the
reward
system
be
making
the
initial
buy
out
and
then,
when
those
funds
run
out,
then
we
make
another
proposal
for
how
that
will
happen,
but
maybe
by
then
we'll
have
this
module
installed
already.
I
Time,
leaving
for
what
you're
saying
just
a
a
suggestion,
if
it,
if
there's
gonna,
be
an
initial,
if
there's
gonna
be
an
initial
buy,
that
is
gonna,
be
funding
the
reward
system,
just
as
a
like
a
like
a
gaming
prevention
measure,
I
feel
that
yes,
this
could
be
done
in
tec
tokens,
but
if
it's
pegged
to
the
wrapped
exit
price
it
could
prevent.
I
Just
like
you
know
people
I
mean
if,
if
there's
like
a
price
right
now,
and
then
it
does
like
3x
for
the
next
distribution,
I
don't
think
that
people
should
get
the
same
amount
of
tec.
So,
if
there's
any
way
in
which,
while
we
figured
this
part
out,
that
could
be
pegged,
I
I
feel
that
it
could
prevent
some.
I
E
A
I
just
wanted
to
show
you
quickly.
The
last
thing
I've
been
doing
in
preparation
for
this
call
is
to
try
to
do
a
sort
of
a
story
story
map
of
all
the
different,
some
of
some
of
the
different
features
that
we
think
that
this
system
will
have
and
for
for
the
developers
and
everyone
on
the
on
the
team
going
forward
with
this
we
need
to.
A
Basically,
we
need
to
schedule
a
sprint
plan
planning
meeting
and
we
need
to
pick
stuff
from
this
this
board
and
and
choose
what
we
will
focus
on
in
the
coming
coming
two
weeks.
So
so,
let's
schedule
that
I
will
ping
you
all
and
find
the
time
early
next
week.
A
But
before
that,
please
have
a
look
at
the
board
and
see
if
I
have
missed
something
obvious
and
or
add
stuff,
it's
a
it's
a
sort
of
compartmentalized
in
three
different.
Sorry
like
overall,
like
really
overall
functionality,
it
becomes
more
and
more
granular
granular,
the
the
yellow
ones
are
the
big
chunks
and,
and
the
green
ones
are
a
little
bit
more
detailed
and
then
the
blue
bluish
ones
are
the
most
detailed.
H
I
ask
a
super
fast,
fine
question:
this
is
back
just
a
touch
further.
Where
does
the?
How
do
you
quantify?
H
How
do
you
guys
quantify
the
big
medium
posts
like
when
people
write
medium
posts,
and
things
like
that
where
you,
because
I
saw
twitter
was
on
there,
and
I
wonder
if,
like
that's
another
thing
that
is
tracked
that
way
or
if
I
don't
know.
A
And
the
short
answer
is
that
that
is
up
to
the
quantifiers.
We
we
give
them
now.
We,
it
seems
like
we're
not
going
to
give
them
strict
rules,
but
more
object
guidelines
that
this
is.
These
are
the
kind
of
things
we
usually
praise,
and
it
would
be
up
to
to
us
all
to
find
out
how.
How
much
does
the
the
community
value
medium
posts?
I
guess
so
the
whole.
The
whole
price
system
is
sort
of
like
an
emerging,
emergent
property.
F
Sorry,
I
just
just
remind
myself
again
how
the
what
is
like
the
like
the
electoral
process
or
the
the
the
appointment
of
the
quantifiers,
because
they
sort
of
have
the
delegate
they're
like
being
the
delegated
authority.
I.
E
So
basically,
it's
going
to
be
an
an
opt-in
pool.
So
basically,
in
my
head
I
was
thinking
exactly
how
celeste
chooses
keepers.
So
it's
an
opt-in
system.
You
get
added
to
like
a
big
list
and
then
automatically
you
pull
randomly
from
a
pool.
E
E
Random
yeah,
just
like
like
drafting
a
jury,
basically.
A
Oh,
thank
you
all
for
for
coming
today
and
I'm
really
looking
forward
to
you
to
going
yes
starting
some,
some
real
real
development
to
to
sum
things
up.
We
have
yeah,
we
we
have
the
basic
facts.
We
that
we
need
to
to
be
able
to
move
on
with
the
development
the
reward
system.
The
process
is
not
100
finished,
but
will
be
later
today.
The
guidelines
will
be
coming
on
under
during
next
week
and
will
yeah
we'll
continue,
develop.