►
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
A
So
hopefully,
next
week
we
are
grael
has
been
working
on
the
server,
but
he
has
not
been
available
for
the
last
few
days.
So
we
have
that
progress
has
sort
of
halted,
but
we
will
get
that
online
soon,
because
I
think
what
is
we
need
to
to
scale
set
a
date
for
the
first
real
quant.
Basically,
the
system
is
ready.
A
Of
course
it
would
be
nice
to
have
the
latest
version
running
on
on
the
correct
domain,
but
but
if,
if
we
don't
get
up
and
running
because
it's
a
a
bunch
of
additional
issues
of
getting
the
production
server
up
and
running
like
the
ssl
certificates
and
the
domains
and
backups
and
a
lot
of
stuff
making,
it
come
real
production
worthy.
But
the
test
server
also
works
fine
and
we
have
hourly
backups.
So
not
much
much
can
happen.
A
Yeah
yeah
we
have
some.
We
have
some
actual
work
to
do,
but
let's
begin
with
the
when
it
comes
to
first
quant
preparations.
Let's
begin
with
the
the
the
update,
so
praise
praise
front,
end
and
nebs.
If
you
would
like
to
just
share
what
you've
been
up
to
and
what
you're.
B
Last
week
I
did
set
up
identification
on
database
in
the
docker
and
I
was
working
on
a
settings
page
that
was
also
work
on
backend
and
frontend,
but
I
need
to
finish
that
and
I
just
pushed-
and
I
think
finished
changes
that
we
did
for
api
inputs.
So
we
are
validating
and
sanitizing
inputs
that
we
are
getting
from
from
the
user,
so
application
is
more
secure.
That
way.
A
C
Sure
yeah,
I
christopher,
gave
me
a
few
tickets
last
week
and
I
started
working
on
them,
but
I
kept
running
into
blocking
issues.
So
one
was
like
dependencies
weren't.
It
wasn't
finding
dependencies
that
were
in
another
workspace,
so
I
just
dove
into
that
and
upgraded
to
yarn
too,
which
has
a
much
better
way
to
handle
like
multi-work
space
dependencies.
It
looks
like
so.
Hopefully
nobody
has
issues
with
that
and
then
I
believe
I
did
one
more
pr
for.
C
Some
little
minor
issue
and
then
I
think
yeah
I'll
take
on
I
can
take
on
one
of
those
back
end
tickets
for
speeding
up
the
quantification
process
this
week.
If
that's
still
the
priority.
A
Yeah
I'd
say:
that's
definitely
a
priority.
It's
one
of
the
greatest
flaws
with
the
system.
Right
now
is
that
assigning
quantifiers
to
a
quantification
period.
That
has
a
lot
of
praise
takes
a
lot
of
time.
It
takes
like
15
20
seconds.
If
you
have
two
three
thousand
praise-
and
that
is
it's
a
one
time
thing,
but
I
still
think
it's
it's
not
unworthy
and
not
acceptable.
C
A
Also,
when,
when
loading
praise
periods,
that
has
a
lot
of
praise
receivers,
calculating
the
scores
for
all
these,
those
praise
takes
a
long
time
and
what
what
it
up
is
the
the
duplicate
praise,
because
the
duplicate
praise.
If
you
mark
a
praise
as
a
duplicate,
you
need
to
fetch
that
duplicate
praise
and
get
the
score
from
that
praise
in
order
to
calculate
the
because
we
want
to
give
the
original
phrase
a
we
want
to
give
the
the
duplicate
phrase.
A
percentage
of
the
original
one.
A
C
D
A
A
Yeah-
and
I
also
like,
if
you
would
like
to
or
or
if
we
can
just
talk
a
minute
about
yarn
two
yeah
about
the
should,
what
should
we
check
in?
Should
we
check
in
though
the
whole
yarn.yarn
folder
and
also
the
cache
folder?
And
then,
although
we
are
not
using
the
the
the
plug-and-play
features
of
yarn
too,
are
we.
C
Right
right,
yeah
we're
not
using
the
plug
and
play
we're
just
using
the
it's
called
like
no
install
or
something,
and
basically
it
just.
It
actually
includes
like
the
dependencies
themselves
in
the
it
has
you
check
them
into
the
repo
which
is
kind
of
like
not
what
we're
used
to,
but
I
was
reading
through
the
rationale
I'm
new
to
yarn
too
as
well.
C
So
I
was
reading
the
rationale
and
they
basically
said
like
it
just
makes
it
like
you,
don't
have
to
run
yarn
install
every
time
you
like
switch
a
branch,
so
that
kind
of
makes
sense,
but
it'll
make
the
repo
quite
a
bit
bigger
and
then
the
one
other
concern
is
that
you
need
to
make
sure
that
nobody,
like
maliciously
checks
in
a
dependency.
That's,
like
you,
know,
a
fake
dependency.
C
So
I
would
just
make
make
sure
on
any
pr's
that
if
there's
any
dependencies
checked
in
that
you're
very
sure
of
them,
the
other
option
is.
We
could
just
change
the
settings
to
not
include
all
the
dependencies
that
works.
Fine
too,
with
yarn
two.
You
just
change
a
config
and
then
and
then
you
just
have
to
run
yarn
install
like
we're
used
to.
A
A
Yeah-
and
I
also
remember
that
the
thing
that
I
wasn't
wasn't
I
wasn't
able
to
get
up
and
running,
was
the
plug
and
play
thing
and
that's
why
I
reverted
back
to
yarn
one
when
I
tried
to
get
it
up
before.
C
A
Yeah,
no,
no!
It's
so
now
that
it
was
a
great
deep
dive
and
I'm
happy
happy
you
did
it
so
praise
front
and
back
and
do
I
have
to
say
something
more
about
stuff
that
I've
been
doing
yeah
I've
sort
of
concluded
that
this
big,
this
big
refactor,
that
I've
been
doing
for
a
little
above
two
two
weeks
and
yeah.
Now
it's
done
and
I
hope
that
the
performance
issues
would
be
be
resolved
by
moving
a
lot
of
the
computational
logic
from
the
front
end.
A
It
was
in
used
to
be
in
recoil
in
the
front
end
and
moved
that
to
the
back
end,
but
it's
still
a
slow
performance
yeah,
but
at
least
the
the
the
refactor
is
mostly
concluded,
and
the
code
base
is
in
much
better
shape
than
a
few
weeks
ago.
A
So,
let's
move
on
to
next
issue
and
the
next
topic.
First,
quant
preparations
and
execution
and
mitch
and
levy
are
not
here.
Let's
see
if
I
can.
B
A
A
septimus
arranger
for
a
review,
so
we
have
a
document
with
a
fair
bunch
of
comments,
so
it
was
really
a
good
helpful
conversation
and
I
think
also
I've
been
asking.
You
know
we
have
an
open
quantification
now,
which
was
which
is
the
third
the
test
quantification
and
I
have
asked
those
who
have
not
finished
their
quantifications
to
do
that,
so
that
we
can
end
up
with
a
finished.
B
A
That's
great
and
I
I
have
a
sense
that
we
will
be
one
person
short
of
having
a
complete
data
set
because
I'm
not
getting
getting
any
response
from
one
person,
but
but
maybe
that
is
okay,
it's
still
everything,
except
for
for
one
one
person:
okay,
cool
thanks.
A
Yeah
we
need
to
set
a
date
for
for
first
quant
and
but
if
mitch
and
liv
is,
are
not
here,
I'm
sort
of
a
bit
reluctant
to
go
and
propose
something,
because
mitchell
is
the
one
who
does
the
heavy
lifting
when
it
comes
to
cat
hurting
all
the
quantifiers
to
actually
appear
on
the
first
quantification
date.
But
my
hope
hopes
are
that
that
we
can
do
the
first
quantification,
not
the
coming
monday,
but
the
monday
after
that.
A
So
in
a
little
about
one
and
a
half
weeks,
something
because
I
think
it's
time
and
for
every
week
that
passes
the
the
the
work
of
the
backlog
becomes
longer
and
longer
bigger.
A
But
we
have.
We
have
work
to
do
before
that
and
it's
not
glamorous
work,
but
it
needs
to
be
done,
and
that
is
we
need
to
identify
some
missing
discord,
ids
and-
and
I
would
like
to
tap
into
the
collective
intelligence
here
possibly
and
get
help
with
that-
and
I
made
a
a
spreadsheet.
A
So
this
is,
these:
are
the
the
a
bunch
of
ids
that
appeared
when
grail
made
a
script
that
converts
the
the
data
we
have
in
the
google
spreadsheet
into
c
into
json
format,
and
then
I
made
an
import
script
that
that
is
supposedly
is
going
to
import
the
data
into
the
database
and
that
script
identifies
empty.
Empty
accounts,
empty
account,
ids
empty
discord,
ids,
and
this
is
the
list
of
empty
accounts
with
no
discord
ids
for
the
whole
period
that
we
are
going
to
work
our
way
through
and
the
first.
A
The
the
oldest
phrase
that
we
will
quantify
is
the
12th
of
july
last
year,
so
the
data
set
I
have
exported
is
to
begin
with
from
july
12th
to
december
31st,
and,
and
luckily
there
aren't
that
many
there
are
153
accounts
that
the
script
could
not
find
the
the
discord
id
for
and
and
the
reason
for
that
is
because
the
the
the
user
has
a
changed
username
since
july
12th
and
in
the
old
praised
discord
in
the
the
praise
spreadsheet,
we
only
store
usernames.
A
B
A
Great,
do
we
have
some
some
other
volunteers,
it's
a
basically
it's
a
it's
an
this
spreadsheet
and
and
the
the
way
to
do
it.
Is
you
just
right
click
when
you
locate
the
person
on
the
discord
you
you
right,
click
on
the
person
and
copy
their
id
and
input
it
into
the
this,
the
sec,
the
third
column
and
next
to
the
username
you
can,
if
you
will
also
find
the
avatar
id
that
that
takes
a
little
bit
more
work,
but
that
that
is
not
necessary.
A
A
C
A
Yeah
I'll
make
the
the
document
open
to
everyone
and
I'll
post
the
the
the
link
and
it's
first
come
first
served.
A
A
A
D
Wow
great
news,
yeah,
that's
cool,
I
think
also
so
on
the
3rd
of
march.
We'll
have
an
event
from
the
reward
system.
Research
we'll
have
a
presentation
to
the
tc
and
I
think
a
lot
of
the
people.
There
could
be
interested
to
participate
in
the
work
we're
doing
and
like
since
that
is
ending
they
will.
They
will
have
some
hours
that
they
could
probably
help
us
with.
D
A
Yes,
that
would
be
next
thursday,
and
my
plan
was
to
get
this
started
the
the
monday
after
that's
a
monday,
the
7th.
D
A
A
A
Yeah,
maybe
let's
bring
up
that
when
it
comes
to
edu.
He
also.
A
If
we
are
finished
with
the
that
planning,
we
can
move
on
to
something
he
brought
up.
We
had
a
one-on-one
they're
talking
about
the
communities
and
and
the
need
for
praise
education.
A
I
hope
that
he
was
going
to
be
here
to
talk
about
it
himself,
but
so,
basically,
I
don't
have
much
to
to
say
other
than
that
he
highlighted
so
sort
of
brought
to
my
attention
that
there
most
likely
is
a
need
to
do
not
quantification
education,
but
education
about
praise
in
general.
What's
the
purpose,
how
do
you
do
a
good
praise,
bad
praise,
blah
blah
blah?
A
So,
let's
leave
do
you
have
any
any
ideas
how
to
move
that
forward?
How
where
that
should
happen?
If
that
should
happen
within
this
working
group
or
within
communities,.
D
I
think
within
communities.
I
can
I'll
message
him
now
and
I
can
coordinate
one
of
us
or
as
many
of
us
as
we
want.
We
can
jump
in
there
and
talk
about
the
system
that
we
have.
A
Yeah,
that
would
be
good.
Is
there
like
a
periodic
call
for
for
new
new
members,
or
is
it
a
recording
only.
D
A
A
Yeah,
and
if
we
move
on
to
my
last
topic
for
today
is
about
source
cred
and
both
about
I've
sort
of
grouped
them
together
a
bit
more
now,
so
both
the
the
bot
and
the
params
we
need
to
talk
about
when
it
comes
to
the
bot,
the
params.
I
think
we
need
just
to
schedule
a
new
session
to
finish
the
work
we
started
by
with
setting
the
params.
D
No,
I
was
just
gonna
say
that
ask
if
we
had
someone
from
source
correct
that
could
join
us
in
that
call,
because
I
think
that
was
our
main
blocker
last
time
to
like
not
understand
some
parameters
and
then,
if
we
could
lock
that
time
with
someone
and
have
them
walk
us
through
everything,
and
I
think
that
would
be
valuable
for
us
to
document
also
because
we
might
use
the
reward
system
for
other
communities
as
well.
E
A
B
B
I
guess
I
guess
I'd
say
that
my
my
experience
with
source
credit
is
more
on
on
on
how
it
affects
the
community
instead
of
the
technical
side
but
yeah.
Maybe
I
can
try
to
chat
with
someone
that
subscribe
as
well
and
see
if
they
can
pop
in.
A
Yeah,
that's,
I
think
that
sounds
great,
and
ideally
you
you
and
matia
would
sync
up
a
little
bit.
You
you
two
about
about
time
and
and
potential
people
from
source
code
that
could
join
and.
A
A
E
E
But
since
that
moment
I
think
I
I
don't
know
anymore.
So
it
would
have
been
amazing
that
he
was
here
to
to
answer,
but
I
think
that
we
can
talk
to
him
later,
but
yeah
we
were
in
the
process
of
testing,
but
in
a
moment
there
it
was
hard
to
actually
test
because
the
the
the
instance
wasn't
actually
getting
in
sync.
A
Yeah,
I'm
finding
it
a
little
bit
difficult
to
see
what
I
can
do
to
to
to
to
push
this
forward,
except
for
for
getting
into
all
the
the
gritty
details
myself,
and
I
would
like
not
to
to
have
to
do
that
because
I
be
sure
short
on
time.
So
would
you
would
you
mind
reaching
out
to
us
again
and
try
to
to
put
that
ball
in
in
motion
again
and
and
if
you
need
help
from
from
viv
to
to
just
get
that
help
and.
A
Okay,
nice,
do
we
have
any
other
topics
we
need
to
discuss
or
should
discuss.
We
have
30
minutes
left,
so
we
could
do
a
whole
param
session.
If
we
like
or
finish
early.
B
Which
is
about
the
documentation,
I've
I've
been
looking
at
the
handbook
and
I
don't
think
there's
like
it's
clear
enough
or
there's
like
enough
information,
for
you
know
for
people
to
just
look
and
read
and
know
how,
like
what's
phrase,
how
to
praise.
How
does
phrase
gets
quantified,
others,
quantifying
means,
etc,
etc.
I'm
actually
having
a
hard
time
figuring
out
those
things
myself.
A
B
D
E
D
B
D
Yeah,
so
the
praise
process
collects
subjective
data,
so
everything
we
praise
each
other
for
it's,
not
something
that
a
bot
can
just
come
in
and
transform
that
into
a
value.
So
that's
the
quantification
process
is
many
of
us
in
the
community,
looking
at
each
one
of
those
phrases
and
then
giving
a
value
for
it
that
will
turn
into
tc
tokens
in
the
distribution
and
then
now
before
we
we
were
using
just
the
appraised
process
and
now
we
are
combining
it
with
source
crowd,
because
there
is
a
lot
of
things
that
were
being
praised.
D
That
could
be
automated,
for
example,
attending
meetings
or
your
engagement
on
twitter
engagement
on
the
forum.
Things
like
that,
so
we
are
taking
all
of
these
things
out
of
the
scope
of
the
quantification,
because
a
bot
can
do
that
based
on
the
parameters
that
will
decide
for
source
grant.
So
what
is
each
thing
valued?
How
it
should
be
set
and-
and
then
in
the
end,
there
is
a
combination
of
both
those
values
from
praise
and,
first
from
source
grant
that
are
distributed
to
people.
A
But
when
it
comes
to
documentation,
I
think
nate
has
offered
to
lend
a
hand
to
writing
the
document
like
general
documentation.
So
I
think
I
already
thought
we
will
accept,
accept
that
hand
and-
and
happily
let
him
write
about
praise
and
we
have.
We
have
the
forum
posts
and
that's
that
we
have
some
some
material
to
get
him
started.