►
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/
C
There
won't
be
we're
going
to
be
pausing
the
rewards,
because
four
of
us
are
going
to
be
on
vacation
in
the
reward
board
for
at
least
like
two
or
three
weeks
right,
and
so
we
did
the
last
reward
distribution
that
went
out
that
included
source
cred,
and
so
we
got
that
working.
We
got
it
figured
out
and
then
we'll
just
like
pick
up
where
we
left
off.
A
C
C
Any
development
updates
the
quantifications
we
just
finished
the
last
one
on
monday
and
then
again
we'll
be
taking
a
break.
Basically
until
I
come
back
from
burning
man
and
then
just
do
like
a
big
catch-up.
C
Yeah,
it's
pretty
big,
there's
a
lot
what's
going
on
there,
but
hopefully
it
goes
well.
C
Nice
did
you
ever
talk
to
nothing
about
the
the
rad
dashboard
or
the
rad
tool.
B
B
Yes,
he
he
told
me
about
it.
I
had
a
discussion
with
him
and
I
said
I
was
gonna.
Basically
try
compare
the
distributions
between
praise
and
non-praise
so
try
and
try
and
get
an
understanding
of
what
appraises
being
good
at
as
an
is
it
capturing
other
streams
of
value
which
aren't
being
captured
by
monetary
value
already
just
gonna.
Take
a
look
at
that.
B
I
haven't
done
much
much
work
on
it.
Yet,
aside
from.
B
I've
basically
got
any.
I
I've.
I've
basically
got
a
script
to
just
download
me
the
history
of
transactions
for
for
the
working
groups.
I'm
gonna
try
and
match
up
the
the
the
different
sources.
You've
got,
so
the
the
user
to
address
table
the
some
of
the
historic
distributions
and
then
just
compare
it
to
a
x,
die
outgoings,
historic
table
just
by
by
user,
filtered
filtered
by
the
the
the
users
which
are
our
embrace
and
just
try
and
see.
B
If
there's
a
much
difference
between
the
monetary
and
and
praise
systems
or
if
there
isn't,
let's
just
see
what
I
can,
what
I
can
see
in
there
it
might,
there
might
be
something
there.
It
might
not
be,
maybe
maybe
praises
capturing
absolutely
nothing.
Maybe
the
phrase
distribution
is
completely
different.
C
Yeah
you
could
see
like
we
tried
to
do
this,
like
hey
nate,
by
the
way
how's
it
going
good.
I
don't
think
there's
a
meeting
like
a
formal
meeting
today.
I
know
that
are
on
vacation.
Oh
yes,.
D
One-On-One
or
anything
like
that,
I
was
just
trying
to
catch
up
on
everything.
So
no.
C
D
Okay,
do
you
do
you
mind
if
I
listen
in?
If
not,
I
can
I'm
not.
C
So
the
yeah
you
can
see
like
we
tried
to
capture
like
other
forms
of
contribution
through
source
cred,
but
ultimately
it
failed
because
source
cred
is
no
longer
maintained.
So
that
was
a
huge
blocker.
B
B
Nerf,
basically,
to
reduce
the
the
praise
for
people
that
are
already
getting
money.
C
A
A
B
C
A
B
A
C
So,
like
I
was
saying
to
rex
nate
we're
kind
of
going
to
be
on
hiatus
for
maybe
about
three
or
four
weeks,
because
not
again,
myself,
zepty
and
christopher
are
all
gonna
be
on
vacation.
A
D
I
I,
and
in
terms
of
things
that
I'm
kind
of
focused
on
with
the
treasury
stuff,
I
really
wanted
to
ask
you
about
runway
in
terms
of
the
reward
system.
A
D
Whether
we
should
be
incorporating
a
priority
to
fund
the
rewards
with
tec
tokens
through
that
treasury,
because.
D
Yeah
so
or
yeah
or
through
the
the
the
gains
from
our
treasury,
and
that
way
you
wouldn't
have
to
go
through
the
common
pool,
and
I
wasn't
sure
if
that
was
something
that
was
feasible
or
a
good
idea
or
not
it's
something
that
we
kind
of
commented
on
and
discussed
a
little
bit.
But
I
don't
know
treasury
so
yeah,
one
of
the
like,
as
setting
it
as
like
one
of
the
goals
for
the
treasury
would
be
to
to
to
provide
outside
of
our
you
know.
C
C
Because
that'd
be
cool
if
people,
if
we
could
get
some
conviction
yeah
while
we're
away
so
basically
yeah,
I
think
we
still
have
another
we've
20k
tac
still
in
the
reward
board.
D
D
D
Yeah
one
one
of
the
big
downsides
to
our
current,
like
the
abc
stuff,
is
that
we
only
have
a
limited
amount
of
te
tokens
minted
in
the
only
way
to
make
new
ones
is
to
actually
go
through
the
abc,
and
so
that
becomes
a
bit
problematic
in
terms
of
how
we
manage
it,
because
I
think
the
laser
tag
wallet
has
what
like
50
000
left.
C
A
D
C
We
have
plan
ahead
right,
so
if
we
know
we've
got
four
months
left
rewards
more
or
less,
then
we
should
put
up
something
now.
Yeah.
D
A
C
C
D
C
We're
getting
good
feedback
to
like
improve
the
product
in
itself.
We've
got
a
really
good
analysis
system.
D
Yeah,
I'm
just
curious
to
see
and
do
you
do
you
have
like
a
pool
that
a
list
of
the
pool
of
quantifiers
and
is
that
automated
for
each.
C
A
C
Hey
by
the
way,
is
that
something
that
either
of
you
would
be
interested
in
doing.
D
I
mean
I
wouldn't
mind
it,
but
at
the
moment
I
am
kind
of
overwhelmed
with
a
bunch
of
stuff.
So.
A
A
B
C
C
C
Thanks
we're
just
there's
no
formal
meeting
today,
so
we're
just
having
a
quick
chat
about
the
reward
system
and
answering
any
questions.
A
That's
awesome,
I'm
actually
quite
new
here
in
this.
You
know
the
tea
channel
and
I'm
I
I
want
to
sign
up
for
the
fundamentals.
The
one
that's
gonna
begin
soon,
but
I
don't
really
know
how
oh.
C
Yeah
nate's
got
it
perfect.
Yeah.
C
Cool,
do
you
guys
have
any
more
questions
about
the
reward
system
or
praise
or
anything.
D
Cool,
I
actually
have
a
question
about
the
source
grid
thing
yeah,
we're
doing
that
for
a
set
period
of
time
and
then
ending
it
is
that
correct.
C
Yeah,
basically,
we
just
have
one
bulk
amount
that
we
calculated
from
everyone's
credit
score
since
the
beginning
of
time.
So
I
think
it
was
like
march
2021,
based
on
their
their
github
and
discourse
contributions
or
their
activity
and
the
weights
that
we
chose,
and
then
we
assigned
an
amount.
I
think
it
was
like
12
000
tec
based
total
and
then
distributed
according
to
credit
scores,
and
then
we
vest
that
10
bi-weekly
right
yeah,
so
that'll
be
10
rounds
and
then
we'll
be
done.
A
D
Yeah-
and
so
are
we
completely
like?
Are
we
abandoning
that
realm
of
rewards
in
terms
of
like
tangible.
E
C
A
C
C
Cool,
I
actually,
I
have
I'll
make
a
github
issue
for
this,
but
there
is
some
consistent
feedback.
I've
had
for
the
praise
system
for
the
quantification.
A
C
When
people
are
quantifying
like
say,
there's
like
a
blanket
praise
like
we
praise
five
or
six
different
people
in
like
the
same
instance
of
praise,
people
are
saying
it's
hard
for
them
to
remember
the
scores
that
they
gave
to
somebody
else.
For
the
same
instance
of
praise.
E
E
Appraised
being
sent
to
me,
multiple
recipients
is
being
split
in
into
in
individual
praise.
So
the
only
way
to
find
out.
C
E
That
quite
inefficient,
but
yeah-
I
I
actually
I
thought
about
that
quite
a
long
time
ago,
when
I
I
did
the
quantifications
myself
that
you
know
wanting
to
give
the
same
score
to
these
multi-recipient
praise
to
the
different
people.
C
E
If
you
gave
recipient
a
a
score
of
10
and
then
you're
scoring
recipient
b,
then
we
could
say
when,
when
it's
time
to
score
that
sort
of
the
the
same
praise
we
we
could.
You
know
highlight
that
next,
to
that
phrase
saying
like,
when
you
scored
a
recipient,
a
for
the
same
praise,
you
gave
that
a
10.
E
B
So
one
thing
you
could
do
is
pre-generate
these
right,
so
you
could
create
some
sort
of
keyword,
association
and
so
basically
have
like
some
sort
of
dictionary
that
attaches
the
the
word
to
some
sort
of
in
integer.
B
And
then
you
just
like
yeah
you
full
it.
It's
going
to
be
a
big
dictionary,
but
you'd
be
able
to
just
run.
Do
free
text
search,
you
can
just
split
it
by
spaces
and
have
a
little
dictionary
and
just
try
and
create
each
of
the
each
of
the
words
and
see
the
accounts.
Do
it
that
way
and
then
try
and
find
ones
that
have
a
high
match
rate.
E
C
But
then,
when
I
do
the
flow,
if
we
look
here,
for
example,
I
don't
think
I'll
be
able
to
get
into
it,
but
each
recipient
will
have
their
own
separate
page
of
praise
that
they
received.
So
when
I'm
doing
rex's
praise-
and
maybe
I
already
scored
christopher's,
I
can't
remember
the
score
that
I
give
christopher
when
of
quantifying
rex
for
the
same
action.
C
E
E
It's
just
a
question
of
how
to
how
to
communicate
that
information
to
the
quantifier.
Let's
say
if
you
for
some
reason
are
assigned
to
quantify
the
receiver
say
you
have
three
of
the
receivers
you
have
are
supposed
to
quantify
or
get
the
same.
Praise
and.
A
C
The
feedback
was
received
from
the
the
quantifiers
and
then
phil
has
like
another
point
that
he
was
trying
to
make.
So
the
first
point
is
the
one
that
we
discovered
and
then
the
second
would
be
how
they
have
typically
scored
over
their
entire
history
of
quantification,
and
I
think
that
builds
into
the
the
categories
and
keywords
system
that
z-wave
built
into
the
rad.
E
That
yeah
yeah-
I
I
thought
of
that
that
would
be
an
easy
optimization
to
do
just
do
a
hash
of
the
phrase
reason
and
and
to
optimize
the
search
yeah.
That's
a
good
idea.
C
C
E
A
E
E
A
E
E
This
seems
to
me
like
a
difficult
one
to
to
implement
it's
a
I.
I
sometimes
see
certain
features
so
sort
of
like
describing
as
a
microsoft
features
or,
like
word
excel
features.
You
know
it's
the
the
kind
of
features
where
the
system
tries
to
automate
the
stuff
for
you
based
on
assumptions
that
are
not
right.
E
So,
for
instance,
based
on
the
assumptions
that
you
would
like
to
have
a
punctuation
every
time
you
hit
this
and
this
key
or
if
you,
when
you
write
a
certain
word,
that
it
would
be
all
to
formatted
with
a
certain
in
a
certain
way.
Like
word,
can
do
this
weird,
automations
and
and
the
initial
you
know,
the
initial
idea
is
good,
based
on
the
the
assumption
made
by
the
person
writing
the
code.
C
What
about
just
like,
instead
of
using
categorizations,
we
just
have,
we
just
have
keywords,
so
it's
like
it
could
be
just
like.
You
historically,
have
scored
praise
with
this
keyword.
This
amount.
A
E
E
And
and
a
free
text,
searches
or
hashing,
the
praise
reason
to
find
the
the
sibling
of
a
praise
is
totally
doable,
but
the
long-term
solution
is
to
allow
praise
to
have
multiple
recipients,
basically,
which
we
do.
When
sending
the
praise
we
allow
for
multiple
recipients
or
multiple
receivers,
but
in
the
internal
in
the
system
it
gets
split
up
into
separate
phrase
items,
and
that
is
a
design
choice.
So
we
did
it
to
simplify
some
stuff,
but
it's
it's
wrong.
E
It's
so
we
so
sometime
in
the
quite
near.
E
I
would
like
to
change
the
price
data
schema
to
allow
one
one
phrase
item
to
have
multiple
recipients,
and
then
we
wouldn't
have
this
problem
at
all,
because
then
you
would
you
know
you
wouldn't
need
to
find
the
little
sibling,
because
there
is
only
one
praise
with
one
praise
reason.
E
A
A
C
C
Talking
about
just
like
what
did
we
say
in
the
last
meeting,
let's
look
here:
oh,
I
didn't
even
write
it
down.
A
E
E
E
E
Data
analysis,
engine
sort
of
where
we
can
feed
multiple
data
streams
into
so
we
can
feed
this
or
an
events,
data
engine
that
we
can
feed
data.
We
can
feed,
rewards
data
and
activity
stream,
so
we
can
feed
the
price
information
into
this
engine.
We
can
feed
the
discord
like
meeting
tracker
information.
We
can
feed
this
course
activity
or
token
log
activity
or
whatever.
E
Yeah
yeah,
I'm
this
chord,
won't.
Let
me
there
and
maximize
and
minimize
again.
E
This
would
be
some
sort
of
of
our
architecture
overview
of
the
next
generation
of
rad,
where
we
have
this
events,
data
engine
in
the
center,
and
we
have
to
the
left
a
bunch
of
sources,
feeding
data
into
that
data
engine
and
the
main
purpose
of
that
data
engine
is
to
store
the
data
and
making
it
available
to
to
consumers.
That
does
things
with
the
data.
E
So
what
one
of
the
main
things
to
do
with
the
data
is
to
analyze
it
the
same
way
that
we
have
analyzed
using
rad,
and
that
is
the
thing
down
to
the
right
in
the
right
corner.
The
python
based
analysis
tool
is
what
we
used
to
call
rad,
and
then
we
can
all
do
other
stuff
as
well.
We
can
generate
token
distributions
or
we
can
export
the
data
to
ceramic,
to
create
this
independently,
verified,
verifiable
proofs
of
contributions
or
activity
and
to
use
it
as
a
source
of
reputation
and
that
kind
of
stuff.
E
E
This
is
what
I've
been
discussing
with.
Libya
also
wants
to
take
rad
into
this
direction
of
of
not
just
analyzing
rewards
but
being
able
to
analyze
any
kind
of
activity
stream
related
to
what
goes
on
in
in
a
tower
in
a
community.
So
in
this
case
I've
just
modeled
a
meeting,
tracker
discourse
and
token
log
as
three
examples
of
of
producers.
E
E
Imagine
a
having
to
run
a
server
where
you,
you
have
praise
and
you
should
make
make
sure
that
praise
can
feed
data
into
the
system,
and
you
have
discord
this
course
and
token
log
and,
and
you
need
to
somehow,
even
though
we
have
built
a
super
sleek,
this
events,
data
engine
or
a
plug-in
interface
or
whatever.
Even
we
made
a
super
nice
work.
Someone
still
needs
to
maintain
these
data
sources
and
make
sure
that
they,
you
know
that
this
course
is
accessible,
that
maybe
discord
updates
their
api.
E
Something
happens
and
then
you
need
to
you
know,
have
a
someone
needs
to
care
for
this
or
over
time,
and
and
so
whatever
the
question
I
wanted
to
throw
out
is:
is
this
even
feasible
to
think
that
a
community
could
manage
a
system
like
this?
Even
you
know,
given
that
the
sort
of
the
the
tech
stack
in
the
center
is
that
is
easy,
easily
manageable.
This
thing
it
just
runs
you
you
never
have
to
deal
with
that.
But
sorry
this
is
a.
E
This
is
a
vague
question
but
and
any
any
any
thoughts.
I.
C
Think
it's
feasible.
I
mean
if
we're
looking
at
open
source
and
it's
the
same
way
as
like
when
a
browser
updates
itself,
and
then
you
have
to
update
the
extensions
that
you
use
like
it's
not
up
to
us
to
constantly
be
keeping
up
on
the
things.
It's
it's
the
people
who
built
the
plug-ins
right.
So
you
build
this
plug-in
that
feeds
into
this
rad
tool,
and
then
there
there's
the
person
who
built
it
and
the.
E
Maintainer
yeah,
so
in
in
theory
in
your
web
browser
you,
you
have
it
on
your
computer,
you
just
it's
just
a
one
button
click
in
this
setup.
It
still
would
be
this
analysis.
Server
would
be
you
know
it's
a
physical
server
running
somewhere.
You
need
to
log
in
you
need
to
edit
a
config
file.
Perhaps
we
can
make
a
some
some
some
kind
of
dashboard,
but
still
you
know
it
needs
a
system
administrator
to
to
care
for
this
and
sort
of
based
on
some
things.
I've
noticed
when
working
with
the
tec.
E
You
know
the
kind
of
heada
amount
of
headache
we
have
had
with
the
with
source
cred-
and
just
I
remember
just
for
weeks
and
weeks,
trying
to
discuss
with
mateo
and
and
getting
you
know,
updating
the
source,
cred
config,
so
that
it
tracks
all
the
github
repositories
we
want,
and
then
we
add
new
repositories
so
that
then,
maybe
not
all
were
tracked
in
the
end,
I
think
there
were,
but
but
yeah
you
see
what
I'm
getting
at.
So
a
lot
of
takes
a
lot
of
work
to
maintain
a
system
with
many
components.
B
E
Yeah
yeah,
so
those
are
the
two
options
then
so
there
are.
There
are
three
options
to
not
push
forward
with
this
idea
at
all
the
most
boring
option,
and
the
second
option
is
to
instead
plan
for
a
software
as
a
service
thing.
Where
we
we
say
you
don't
have
to
host
your
own
server,
you
don't
have
to
install
your
plugins,
etc.
E
You,
you
pay
us
a
monthly
fee
who,
whoever
else
is,
if
it's,
the
the
dao
analysis,
dao
or
whatever,
who
offers
this
service
to
the
world
or
or
the
third
option
would
be
like
a
service
dao.
E
B
So
by
software,
so
what
the
service
that
was
to
suffer
as
a
service,
I'm
not
understanding
that
the
difference
you
you
mentioned
but
having,
even
if
we
like
make
the
installation
as
simple
as
possible,
have
a
bunch
of
docker
containers
which
are
already
kind
of
interconnected,
and
then
the
config
files
are
fairly
simple.
It's
still
going
to
be
a
pain
in
the
neck.
To
set
this
up.
E
E
We
have
a
a
docker-based
installation
scripts,
so
you
don't
have
to
you
know
the
only
dependency
you
have
to
have
on
the
server
is
docker,
and
then
you
can
run
the
docker-based
setup
and
still
there
is
a
fair
amount
of
head
scratching
when
setting
it
up,
and
this
would
be
vastly
more
complex
than
than
just
setting
up
the
phrase
system,
because
for
all
these
source
source
plugins,
you
would
of
course
need
to
define
some
some
parameters
like
it's
for
the
meeting
tracker.
What
will
in
what?
E
E
Now,
what
I
meant
with
the
service
service
style
would
be
there.
We
of
course,
could
be
a
general
service
down
that
that
serves
a
dao
with
any
like
dev
op
needs
it.
It
doesn't
need
to
be
only
serving
without
supporting
this
system.
It
could
be
now
we
help
you
set
up
your
mail
server
and
your
and
make
sure
your
web
server
doesn't
crash,
etc.
E
E
Yeah
yeah,
and
that
is
also
an
interesting
idea
to
like
a
red
dow
and
the
purpose
of
that
tao,
is
to
sort
of
install
and
maintain
these
rad
instances
in
in
other
dows
and
all
all
those
wanting
to
take
to
enjoy
this
service.
Of
course,
we
need
to
have
to
support
the
rad
dao
to
do
the
work
it
needs
to
do
somehow,
because
there
one
problem
with
the
hosting
it
as
a
as
a
monolith.
E
Software
as
a
service
thing
is
that
you
sort
of
embark
on
a
more
startup-like
journey,
yeah,
which
is
fun
in
a
way
because
then
you
could
offer
you
would
be
tempted
to
offer
this
service
for
free
to
any
dow,
and
you
would
soon
get
you
know,
hundreds
of
users
or
thousands
of
users,
because
you
would
want
people,
it
won't
want
it
to
be
free
to
sign
up,
and
then
somehow
you
need
to
try
to
monetize
your
biggest
users,
either
by
a
monthly
fee,
or
you
know
something
something
else.
E
E
E
Anyway,
so
this
is
just
something
I'm
thinking
about
and
about
the
for
the
future
of
rad
and
we'll
be
discussing
more
with
torif,
who
is
involved
in
giveth
on
friday
to
discuss
the
technicalities
of
the
setup
we
have
been
discussing
using
apache
kafka
as
the
the
events
data
engine,
which
is
a
events.
E
So
to
be
continued,
but
if,
if
anyone
erects
or
anyone
else,
if
you
feel
if
this
feels
like
an
interesting
topic
to
continue
discussing
and
somehow
be
involved
in
because
we
will
try
to
what
we
need
to
try
to
do
is
to
formulate
what
the
next
generation
of
rad
could
be
should
be,
how
it
should
look
and
feel-
and
we
want
to
describe
that
in
like
a
product
brief.
E
And
then
libya
has
talked
to
the
to
the
people
behind
the
the
proposal
inverter,
and
they
are
say
that
they
would
be
happy
to
host
the
next
generation
rad
as
one
of
their
first
projects
that
we
could
attempt
to
finance
through
the
proposal
inverter.
So
then
the
challenge
would
be.
You
know,
describe
the
pro
describe
the
project
of
the
product,
the
project
and
then
try
to
hook
up
a
number
of
of
dows.
That
would
be
willing
to
co-finance
this
using
the
proposal
inverter
and
then
recruit
and
get
going.
E
Yeah
now
it's
it's
perfectly
suited
to
do
this
thing
where
you
have
many
many
sources
of
data
should
many
sources
of
data
and
many
producers
and
many
consumers,
and
they
should
be
loosely
coupled,
and
so
it's
when
you
want
to
build
a
system
that
contains
consists
of
parts
that
communicate
asynchronously.
E
No,
it's
a
so
so
kafka
is
sort
of
a
message
broker
in
in
the
center
and
and
it's
using
so
it's
a
message
broker
and
it
feeds
all
the
data
into
logs.
It's
so
every
producer
generates
data
in
what
what
is
called
a
topic.
E
So
so
there
will
be,
it
would
be
a
praise
topic
and
it
basically
is
a
log
of
of
json
objects
and
static,
or
you
cannot
modify
it
afterwards.
So
you,
you
keep
an
event
log,
so
it's
perfectly
suited
also
to
bridge
this
and
and
store
copies
of
it
on
some
kind
of
decentralized
storage
system
like
ceramic
or
something
this
event,
log
and
basically.
A
E
Should
be
able
to
to
read
if
you
read
the
event
log
from
from
start
to
from
beginning
to
current
time,
you
should
be
able
to
recreate
the
the
states,
the
state
of
the
system
based
on
that
information.
So
you
you,
you
track
all
all
events
generated
by
the
system
if
you
build
a
fully
events
based
system.
Of
course,
you
can
choose
just
to
track
some
information,
but
if
you
choose
that
as
your
main
component
in
the
center,
instead
of
maybe
using
a
relational
database,
then
that
would
be
the
the
goal.
E
And
it
has
the
capacity
to
handle
like
millions
and
millions
of
of
topics
and
millions
and
millions
of
messages
per
second
and
it's
yeah.
So
it's
a
bit
of
a
corporate
thing.
It's
being
kafka
is
being
used
by
you
know:
linkedin
and
the
biggest
players
in
the
industry
to
handle
events
and
data
streams.
B
A
B
C
Oh
cool
well,
I
think
I
want
to
just
figure
out
before
this
meeting
ends.
When
are
we
doing
the
next
meeting.
E
C
A
C
E
Yeah,
I
I
was
thinking
about
stepping
out
for
stepping
away
from
holding
these
after
you
get
back
and,
like
I
said
after
maybe
we
do
this
race
year
in
review.
This
deeper
analysis.
First.
E
Yep
and
then
let's
aim
for
that,
it's
a
it's
a
good
good
place
to
to
make
a
pause
as
well,
because
now,
as
the
the
first
source
credit
rewards
payout
is
out
and
we
don't,
we
don't
really
have
any
any
things
on
the
agenda
other
than
daily
business
like
quantifications
and
new
payouts,
etc.
So
it's
no
no.
A
E
I
think
that
don't
have
to
wait
until
you
get
back.
A
A
C
So
do
we
sorry
everyone
if
this
is
boring,
you're
free
to
leave,
but
the
so
then,
when
is
the
next
scheduled
call,
assuming
that
myself
and
zepty
won't
be
available.
E
I
think
doing
doing
the
rewards
payouts
and
having
the
discussion
about
the
things
that
come
up
through
the
quantifications
would
be
the
main
thing
going
forward
and
since
we're
not
doing
those,
we
don't
have
much
to
discuss
before
we
we
get
started
with
the
quantifications
again,
let's
say
once
we
get
started
with
the
quantifications.
We
start
these
meetings
again.
C
C
So,
do
you
guys
want
to
have
a
check
in
that
first
week
of
september,
then.
A
A
C
Okay,
cool!
Well,
I
think
that's
it
we're
four
minutes
over
great.