►
From YouTube: Quilkin Monthly Project Update - June 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Wonderful,
I
dumped
a
bunch
of
stuff
on
here.
I
figured
we
could
also
talk
about
some
of
this
one
of
the
the
stuff
that
I'm
working
on
and
some
of.
B
A
A
hugely
honorous
task
cool
that
was
easy
decision
made
done
awesome.
Do
you
want
to
start
with
like
an
update
on
where
things
are
at
with
xts.
D
Oh
yeah:
well,
I
think
we
we
did
a
review.
D
That
we
covered
the
review
of
the
current
pr
there's
not
been
too
much
change
since
then.
The
thing
they
are
mainly
doing
now
is
just
polish
work.
To
figure
out,
there
have
just
been
some
slight
bugs
in
production
like
oh,
I
needed
to
call.
I
wasn't
calling
the
watcher
in
like
one
of
the
invariants
where
it
modifies,
and
I
just
need
to
update
that
and
stuff
like
that.
D
It's
very
small
changes
so
like
I
would
also
like,
I
would
say,
I'm
going
to
after
this
meeting,
I'm
going
to
push
that
pr
as
a
clean
pr
that
can
then
be
merged,
because
I
think,
even
if
there
are
any
bugs
or
improvements
left
to
your
mind,
they're
like
a
couple
of
lines
compared
to
the
rest
of
the
code,
they're
not
going
to
change
a
lot.
A
Absolutely
and
so
I'll
I'll
go
through
it
and
I'll
just
see.
If
there's
anything,
that's
like,
oh
god.
What
is
that?
But
I
I
very
much.
D
D
D
My
mic,
just
I
don't
know
the
hardware
mic
on
the
hardware,
mute
somehow,
but
it
will
sorry
monster.
D
You
can
have
management
level
filters
where
essentially
like
you
can
think
about
how
we
have
it
right
now,
where
you
have
to
set
up
the
entire
logic
yourself,
whereas,
like
you
could
think
about,
if
you're,
an
organization
like
google
or
like
embark,
studios
and
stuff
like
that,
you
might
want
to
have
some
general
network
filters
and
stuff
like
that,
that
you
could
apply
anyone,
and
rather
than
having
to
have
all
your
developers,
add
in
and
maintain
that,
like
branch
of
logic
themselves,
you
could
have
stuff
like
oh
every
load.
D
A
D
Yeah,
I
think
you
can
also
yeah,
I
would
say,
feel
free
to
merge
that
I
need
an
approval.
Oh
yeah,
yeah
I'll
I'll
I'll
hit
the
approval
button
after
this
meeting.
If
there
is
anything.
E
A
A
Better,
I
agree
with
that.
The
only
other
thing
is
okay.
Let
me
know
I've
still
got
it
in
the
make
file
that
it's
defaulted.
So
let
me
move
that.
A
B
B
C
A
All
right,
cool
cool,
cool,
cool,
all
right,
sweet
that
makes
life
very
easy.
We
were
having
some
interesting
discussions
about
like
a
valid
validation
packet,
filler
validation.
I
was
at.
A
Yeah
we
were
going
back
and
forth
and
I
was
like
about
whether
or
not
that
should
be.
You
know
I'll
share
this.
D
A
So
I
was
like
okay
say:
I
want
to
check
that
like
the.
Where
am
I
thinking
where
was
I
yeah?
I
want
to
check
that
the
packet's
between
five
and
ten
ten
ten
ten
bytes
long
right,
that's.
D
Well,
you
could
definitely
well
right
now
you
have
the
prefix
and
suffix,
and
you
could
you
could
set
those
and
say
hey
at
least
this
length.
You
can't.
D
Length
like.
D
Regex
can
definitely
do
it
where
you
can
say,
and
that's
also
that's
kind
of
where
why
I
kind
of
think
they're
a
lot
similar
because,
like
if
you
think
about
regex
like
right,
jaxy,
is
a
language
to
validate,
and
then
they
also
have
like
a
sub
language
inside
that
for
capturing
like
pieces
of
what
you
validate.
You
know.
A
So
like
say
we
have
like
say
we
had
to
validate
the
capture
for
argument's
sake,
so
I
think
I
think,
that's
quite
easy
to
read
and
comprehend
because
you
can
be
like
validate.
Does
it
match
this
rejection
between
five
and
ten
and
if
it
does
right,
then
you
can
match
on
it
and
say
like
okay,
if
it's
valid
then
like
it's
true
otherwise
drop
right.
D
Now
is
there,
I
guess
to
sort
of
talk
about
it
and,
like
I
think
to
my
results,
like
my
main
concern
is
more
about
the
reduction
like.
I
don't
think
I
would
have
a
problem
with
like
having
essentially
capture
that's.
D
B
A
Because
then,
yes,
I
was
like
if
we
move
it
to
that's
an
interesting
point
of
view,
could
do
it
that
way
the
other
option
was
like
okay.
So
if
we
say
we
say
it's
pause
or
something
yeah
yeah,
and
so
in
that
case
it's
like
so
the
scenario
here
we're
starting
was
between
five
and
ten,
but
I
want
to
grab
the
the
scientific.
E
A
B
D
Well,
yeah,
I
guess
just
just
even
in
terminology
like
again
we're
talking
about
what
we
expected
like
with
capture.
I
can
always
expect
it
to
capture
both
paris
like
I
would
almost
expect
like
drop
true
to
be
implicit
right
like
I
would
expect.
In
fact,
the
opposite,
like
the
you
would
set,
drop,
false
and
drop.
True
would
be
the
default
because,
like
parising,
is
usually
validate
capturing
and
then
dropping
if
it's
not
valid
and
stuff
like
that,.
B
D
Having
I
think,
yeah
the
thing
I
care
about
most
like
yeah,
we
should
have
shared
capture
functionality
for
this
with
the
capture
struct,
but
then
we
can
definitely
do
like.
Okay
yeah
have
a
different
filter
with
a
completely
different
configuration
as
long
as
it
uses
that
same
internals,
I
think
that's
totally
fine,
okay,
yeah.
D
E
Yeah
cool
cool:
let
me
capture
those
notes
chatting
in
you
have
a
separate.
C
C
E
A
D
D
After
that,
to
get
that
stuff
out
there
and
then
if
anyone
comes
back
with
major
errors
and
stuff,
we
can
see
so
yeah.
I
think.
D
In
there
it
should
be,
I
should
have
documented
it
like.
I
think
the
guide
probably
needs
to
be
updated.
I
think
that's
the
one
thing
I
have
yeah
I
can.
I
might
I'm
gonna
try
to
do
that
tomorrow,
because
I
also
actually
some
of
it
as
it's
just
a
separate
pr.
Oh
actually,
I
think
maybe
we
actually
did
do
some
of
it
as
a
stuff.
E
D
A
E
D
There's
a
I'll
send
you
a
link
to
this
crate.
Actually,
they
were
sharing
at
work.
It
was
it's
called
cargo
public
api.
It
does
what
kind
of
sounds
like
word:
it's
like
a
release
tool
where
it'll
download
one
version
of
your
release
and
download
the
other
version
of
your
release
for
like
a
library,
and
I
actually
try
to
compare
the
public
api
and
be
like.
Oh,
there
are
these
new
methods.
This
method
has
now
changed
its
return,
type
and
stuff
like
that
automatically.
A
A
C
A
The
other
thing
that
hasn't
had
some
discussion
in
a
while
was
rules
and
actions.
We
went
back
and
forth
anyways
still
here.
D
A
Yeah,
I
keep
coming
back
to
conversations
that
I
have
I'm
having
sort
of
with
some
people
internally
and
some
some
about
customers
and
stuff,
and
I'm
like
it's
sort
of
like
okay.
How
do
we?
How
do
we
react
or
how
do
we
have
a
system
that
reacts
accordingly
when
something
happens,
like
rate
limiting,
is
the
massive
thing
right
or
you
want?
You
want
to
use
quillkin
to
be
the
source
of
intelligence,
to
go.
Tell
another
system
to
do
something
right
like
this.
A
That
kind
of
stuff
so
having
having
something
that's
like,
oh,
I
can
send
an
event
or.
B
A
Action
or
what
do
we
want
to
call
it?
I
don't
really
out
to
something
else
and
like
how
does
that
work,
and
some
of
those
each
filter
probably
has
its
own
set
of
rules
about
how
to
do
that,
but
we
probably
need
to
have
some
common.
A
A
Oh
you've
over
like
this
person's
gone
too
far
right,
like
they've,
sent
two
impacts
which
may
be
different
than
say,
say,
pars,
or
something
like
how
many,
how
many
times
does
a
single
person
have
to
like
mock
up
before
we
send
an
event?
D
The
thing
that
just
came
to
me
there,
where
you're
talking
about
rules
like
yeah,
why
couldn't
this
just
be,
for
example,
an
error
case
in
the
filters,
so
that,
like
you
right
now,
we
have
option,
read
response,
you
can't
perception,
you
get
a
read
response
or
you
don't,
but
we
could
have
a
result,
read
response
and
then
an
error
type,
that's
like
either
drop
or
event.
D
I
guess
to
be
clear:
you
probably
could
also,
probably
you
probably
would
not
do
it
that
way,
because
you
probably
want
to
have
it
wrapped
in
both
cases,
because
you
might
want
to
have
events
in
both
cases.
But
I
think
if
something
like
that
or
just
having,
I
think
what
we
have.
I
feel
the
term.
D
Like
maybe
event
dispatcher
would
probably
be
the
term
to
like
something
you
pass
in
the
context
that
essentially
just
a
reference
to
a
component
that
you
can
then
call
to
trigger
an
event,
and
then
we
just
have
a
separate
component.
That's
from
managing
all
those
events.
A
Yeah,
no,
I
I
they're
we
absolutely
yes.
Yes,
however,
however,
we
do
it
internally,
like.
A
Like
how
do
we,
how
do
we
configure
that?
I
guess
we.
D
D
On
the
filter
right,
some
of
them,
probably
only
gonna,
have
it
in
code
like
some
of
them
are
going
to
trigger
events
in
code
like
yes,
absolutely
versus
some
are
going
to
want
to
have
configurable
things.
So
I
guess,
like
that's.
Probably
it's
like
a
rate
limit.
Probably
always
has
a
code
path
to
trigger
a
rate
limit
right,
yeah,
it's
just
that,
there's
an
option
that
says:
when
is
that
rate
limit
too
much
and
that
maybe
by
default
it's
like
fairly
high,
so
that
you
don't
accidentally
trigger
it
or
something.
C
D
Right,
I
think
I
think
I
would
say
it's
like
that's
for
the
comp,
the
event
dispatcher
component,
I
would
say
it's
like
yeah
in
terms
of
the
bank
concern
it's
like
what
like
a
successful
api
would
just
be
that
the
quilting
filter
sends
an
event,
and
it
doesn't
worry
about
it
after
that.
Yes,
I
agree.
I
agree
the
event.
B
D
Accepts
like
events
essentially
unlimited
or
like
in
a
queue
in
in
the
threa
in
the
process,
and
then
it's
responsible
for
like
either
immediately
streaming,
those
out
or
logging
them
out
to
some
place
or
something
so.
A
What
I'm,
what
I'm
hearing-
and
I
think
I
think,
makes
a
lot
of
sense-
is
we
have
per
filter?
I
think
purely
configuration?
Oh,
my
god,
my
dog
is
like.
Why
haven't
you
taken
me
for
a
while
again
per
filter
configuration
on
we'll
call
it
rules
and
actions,
but
like
rules
and
actually
rules.
A
On
on
when
to
fire
an
event
there,
we
go.
That's
a
like
that
and
then
at
the
main,
like
the
proxy
config.
D
I
guess
the
thing
I
maybe
say
is
like
in
terms
of
what
we
want
to
do
is
we
just
want
to
allow
filters
to
fire
an
event
somehow
like
through
the
context
or
or
either
like?
I
think
the
two
options
are
that
either
it
passes
something
into
the
context
that
fires
independently
or
that
we
terminate
the
results
and
that
the
results
also
come
with
events.
B
D
A
D
Yeah,
like
I
think
we
want
to
leave
it
to
the
filter,
to
decide
yeah
like
is
an
event
good
or
bad,
so
I
think
yeah.
Definitely
we
want
to
having
having
something
in
the
context
that
fires
independently,
I
think,
makes
more
sense
because
then
we
don't
have
to
worry
about,
like
accidentally,
not
propagating
those
events.
If
we
have
like
an
early
return
or
something.
D
So
yeah,
then
each
filter
gets
this
event,
dispatcher,
which
is
similar
to
what
we
were
doing
with
the
xcsf,
where
it's
like
an
arc
and
it's
like
some
component
or
something,
and
then
you
fire
that
and
then
some
atomic
way
it.
I
probably
would
probably
be
a
queue
more
than
that,
because
we
probably
want
to
have
back
off
and
stuff
for
events.
D
Related
to
this,
like
I've,
been
thinking
about
that
there's.
Another
issue
where
we're
talking
about
like
oh
is
like
is
ip
routing
the
same
as
content,
writing
and
stuff.
Like
that,
I
don't
think
it
is.
I
think
that
is
like
an
interesting
session
like
there
are
some
things
where
it's
like.
You
might
know
it
at
like
a
better
level
at
the
quilting
level
than
like
at
the.
C
D
Level
and
stuff
like
that,
where,
like
feel
like
quilting
like,
for
example,
like
some
of
the
rate
limiting
stuff,
might
be
better
as
like
not
as
a
filter
but
as
in
the
proxy
itself,
because
you
could
look
at
stuff
like
is
the
current?
Is
there
a
current
session?
How
much
has
this
current
session,
like
how
many
sessions
overall
and
stuff
like
that,
yeah.
C
D
D
A
D
I
think
that's
also,
maybe
something
just
like,
because
we
have
had
that
problem
before
where
we're
talking
about
like
we
do
have
some
stuff
like
that,
where
we
have
the
ttl
map
like,
I
think
I
think
that
is
like
a
good
decision
for
like
we
should
have
some
sort
of
like
session,
based
like
storage,
for,
like
a
filter
to
get
like
hey
like
what
a
like.
D
Is
there
some
information
in
this
session
that
I
can
get
like,
for
example,
if
you
have
a
rate
limit
filter
to
be
able
to
see
oh
this
session,
how
many
requests
has
a
session?
How
much
data
has
this
session
sent?
I
think
that
is
something
that
you're
writing.
If
you
want
to
have
that
logic
in
the
filter,
I
think
that's
something
the
filter
does
need
to
know.
D
A
A
Kind
of
cool
yeah,
so
maybe
I'll
talk
about
that
line.
A
D
D
A
A
Around
session
management
and
having
a
filter
that
could
kind
of,
if
you
had
what
was
it,
no
I'm
trying
to
remember
what
it
was.
It
was
either
something
like
if
you
it
was
like
like
I
was
like
if
you
wanted
to
like
kind
of
dmoc
sessions,
if
you
were
like
or
or
filters
could
have
control
over,
if
you
had,
if
you
had
a
filter
level
at
the
filter
at
like
the
session
level,
and
it
had
control
over
how
sessions
got
created
and
deleted,
you.
D
D
D
Oh,
like
doing
like,
like
like
time
to
live,
heartbeat
requests
and
stuff,
so
yeah.
D
Keeping
a
connection
alive,
even
though
the
other
connection.
A
Yeah,
no,
no,
it's
totally
gone.
It'll
come
back
to
me
at
some
other
point
in
time.
I'm
sure
it
was
something
about
like
like
legacy
servers
that
were
not
built
for
like.
D
Event,
dispatcher
and
and
we'll
probably
need
to,
I
would
say,
probably
yeah
good
to
start
with,
like
a
filter
and
like
what
events
you
want
the
filter
to
have
and
then
yeah
there
built
the
event
dispatcher.
With
those
events
in
mind.
E
A
Probably
regulator
is
the
is
the
easy
one.
D
A
D
A
And
I'm
assuming
it
would
be
like
where
to
send
the
events
like
it's
just
something.
D
I
guess
well
at
least
apparently.
D
Right
now,
I've
been
thinking
about
it
just
in
an
event,
agnostic
way,
yeah
but
yeah.
I
think,
and
then
yeah
we
could
just
have
like
if
the
event
source,
like
yeah
a
web
hook
like
in
my
mind,
yeah,
you
would
have
the
event
dispatcher
and
then
like
similar
type
tracing,
does
it
where
you
have
a
event
subscriber
yeah
like
we
would
just
have
an
event
subscriber
and
one
for
like
a
web
hook
or
whatever
so
yeah.
D
E
C
A
Yeah
no
yeah,
I
will.
I
will
start
at
the
configuration
level
like
I.
D
C
A
It
looks
like
and
stuff
and
then
and
then
we'll
dig
into.
D
Yeah,
that's
I've
done
that
quite
a
few
times
forever.
Like
like
the
cluster
stuff,
I
spend
much
time
where,
whereas
I
wrote
it
with
localities
as
keys
because
it
made
it
way
easier
in
the
code
and
then
I
tried
to
write
it
in
the
configuration
I
was
like.
Oh
no.
This
does
not
work
at
all
completely.
A
C
D
What
videos
no
plan?
What's
the.
D
D
B
C
D
A
D
It's
very
childlike,
but
I'd
say
it's
like,
like
an
adult
swim
cartoon,
almost
where
it's
like
adult
themed,
where,
like
it's
all
these
fun
farmers
and
stuff,
but
you're,
helping
like
a
farmer
with
like
his
marital
problems
with
his
wife,
the
archaeologists
and
stuff
like
that.
You.
A
B
And
all
right,
it's
actually
it's
on
it's
on.
Oh
that
looks
like
fun.
B
Oh,
that's
something
completely
different,
I'm
literally
pulling
up
steam,
so
I
can
edit
my
wishlist.
So
I
don't
forget.
A
D
With
like
it's
like
very
pokemon,
pokemon
snapdesk,
like
it's
very
like
everybody,.
A
D
D
D
Did
you
see,
I'm
gearbox
is
publishing
a
new
game.
Actually
I
don't
know
if
you
haven't
paid
attention
to
like
the
gaming
press
or
whatever,
but
there's
a
nintendo
showcase
like
yesterday
or
whatever
blnc,
where
it's
like
this
nameless
story
where
it's
like
these
two
foxes.
It
looks
really
cool
and
they're.
The
people.
D
You
can
see
it's
like
it's
black
and
white
like
it
looks
like
it's
drawn,
but
it's
also
really
animated
and
stuff.
It's
very
nice.
D
A
C
A
E
D
Not
this
month,
but
next
month,
I'll
definitely
chat
to
you
once
I
get
back
and
you
know
catch
up
and
like
try
to
see
everything.
That's
been
done.
Awesome
well,
yeah.