►
From YouTube: hyper63-tsc-2-2-2021
Description
hyper63 Technical Steering Commitee Meeting, Feb 2, 2021
C
B
C
C
C
He
did
a
lot
of
refinement
and
a
lot
of
word.
Smithing
on
there-
and
I
think
it
looks
really
great
so
thank
you
all
and
thank
every
everyone
else.
If
I
forgot
you
I'll
remember
next
time,
so
that's
kind
of
welcome
and
you
know
kind
of
the
shout
outs
and
then
the
next
section
I
got
is
updates.
So
on
the
documentation
site,
I've
been
tracking
a
change
log.
C
C
The
main
reason
for
the
changelog
is
just
to
give
everyone
kind
of
a
quick
communication
of
what's
happening,
so
you
can
feel
up
to
date
and
you
know
feel
like
you're
informed
with
where
the
project's
going
and
kind
of
what
the
status
of
it
is
so
so
check
it
out.
I'm
not
going
to
go
through
all
of
them.
I'm
just
going
to
go
through
a
couple
of
highlights
the
last
two
weeks.
I
think
it
was
the
last
two
weeks
we
launched
documentation
site.
C
C
Let
me
try
this
archbie
thing.
It
looks
nice
and
pulled
it
up
and
I
was
able
to
start
getting
stuff
done.
So
I
don't
know
if
this
is
the
end,
all
be
all
of
our
documentation
site,
but
I
was
able
to
put
together
a
lot
in
a
very
short
amount
of
time
and
get
a
lot
of
eyeballs
on
it
and
plus
it
all
kind
of
exports
down
to
markdown,
which
is
nice.
So
if
we
do,
you
know,
I
would
prefer
it
to
be
close
to
the
code.
C
I
would
prefer
it
to
be
auto-generated,
but
also,
I
know
when
people
are
starting
to
look
from
the
outside
of
the
project
being
able
to
see
some
some
documentation
is,
is
good,
and
so
anyway,
any
anyone.
Anyone
have
any
thoughts
about
the
the
documentation.
Is
it
a
good
start?
Is
it
you
know
a
bad
start?
D
I
mean,
I
think
it
looks
good
I
haven't
used
archery
before,
but
if,
if
brian's
backing
it,
I
tend
to
trust
brian
on
sort
of
product
recommendations.
He
has
a
pretty
good
eye
for
this
sort
of
stuff.
So
I
I
think
it
looks,
I
think
it
looks
good
and,
like
you
said
at
the
end
of
the
day,
it
makes
you
more
productive
than
and
getting
something
out
before
then
great.
B
Robert
yeah,
a
lot
of
the
stuff
we
talked
about
like
two
weeks
ago,
was
like
ideal
world.
You
know
big,
you
know
hand
wavy
stuff,
but
I
mean
in
two
weeks
look
where
we
are
now
look
where
you
are
now
and
and
what's
what's
great?
Is
that,
like
you
know,
if
you
can
get
at
if
you
can
export
all
this,
like
you
said,
do
markdown.
B
A
C
So
that's
good,
but-
and
you
know
it
one
of
the
things
that
that
you
know
I
thought
about
going
back
and
forth
with
you
know,
using
like
a
medium
or
dev2
or
or
something
else
was
that
I
just
keep
going
about
owning
your
own
content
and
the
need
to
own
your
own
content
and
and
those
wild
gardens
are
great
for
reach,
but
then
they're
not
so
great
either
because
they
become
that
content.
So
I
took
the
ghost
route
set.
C
B
D
That
they
mean
nothing
besides,
what
robert
was
just
saying
and
like
all
the
all
the
blog
posts
that
you've
posted
they
sound,
really
nice.
I
know
you
you
had
concerns
about
it
sounding
too,
like
salesy,
but
it
just
sounds
like
the
content
just
seems
more
just
informative
and
educational
and
kind
of
just
preaching
kind
of
what
you're
saying
just
keeping
your
business
logic
all
in
one
place
and
not
spreading
it
out
throughout
your
app
and
a
certain
frameworks
or
tools.
Sort
of
advocate
you
doing
that.
D
B
You
know
because,
like
I
feel,
like
developers,
see
so
much
like
salesy
stuff,
that,
like
we
have
such
a
good
nose
for
it
and
we
just
kind
of
glaze
over
and
forget
it,
but
if
we
can
give
value
out
of
you
know
what
you're
teaching
or
preaching
then
later
you
know.
If
not
now,
then
later
you
know
we'll
come
back.
B
C
True
right
when
people
think
of
hyper,
they
should
be
thinking
well,
you
know
they're,
focusing
on
trying
to
improve
the
developer
experience
and
there's
a
product
that
helps,
but
at
the
end
of
the
day,
it's
about
you
know,
and
I
don't
think
the
41
tech
debt
got
a
lot
of
hits,
but
at
the
same
time
to
me
I
don't
think
a
lot
of
people
realize
how
much
it
cost
just
to
do.
You
know
kind
of
keeping
the
lights
on,
especially
once
a
project
gets
about
three
years.
C
C
C
And
then
you
know
we'll
use
this
time
in
the
future
to
talk
through
these
features
as
a
technical
steering
committee
right.
So
the
technical
steering
committee
will
really
focus
on
trying
to
determine
what
what
should
go
from
under
review
to
plan
and
then
from
plan
would
be.
You
know
it's
it's
kind
of
approved
and
then
someone
just
needs
to
own
it,
and
that
would
shift
it
to
in
progress
and
then
we'd
have
a
column
for
a
particular
version
for
shipping.
Does
that
sound
good
to
you
guys?
A
Or
recommendations,
I
definitely
think
something
is
needed.
So
after
the
last
meeting
I
tried
to
look
somewhere
to
sort
of
get
a
foothold
in,
but
I
wasn't
really
sure
where
to
go,
because
I
know
there
there's
some
like
descriptions
and
you
know
look
at
some
code
and
all
that's
great,
but
I
just
you
know.
I
didn't
really
know
what
I
could
do
as
far
as
like
where
to
go
where
to
start.
So
I
think
that
will
be
very
helpful
for
them.
C
C
C
C
D
That
not
much
thought
to
that,
but
just
a
question
on
something
you
said
just
now
with
the
dual
node
and
dino.
Capable
is
the
idea
there
to
have
like
the
the
files
that
are
esm
and
then
use
something
I
don't
know
like
rola
or
babel,
whatever
to
produce
the
seat
like
the
common
js
and
like
transpile
it,
and
then
that
way
you
use
the
source
with
dino.
Or
are
you
talking
about
like
another
another
strategy
to
support
both.
C
Yeah
a
couple
of
things:
one
is
kind
of
the
native
esm,
end
node
and
then
having
that
depth
file
the
the
depth
file
kind
of
switch
based
on
what
you're
building
right.
So
so
everything
would
import
like
in
dino
through
depths
js
and
you
just
use
a
node
depths
or
adino.
Depths
is
one
way,
but
I'm
kind
of
waiting
a
little
bit,
because
I
have
a
feeling-
and
I
haven't
read
a
lot
more
about
it.
But
but
I
have
a
feeling
that
snowpack
is
kind
of
moving
to
this.
C
Moving
to
the
streamable
package
management
system
and
if,
if
it
works
the
way
that
I
understand
it,
then
basically,
if
snowpack
will
become
kind
of
this
streaming,
npm
install
right.
You
just
do
import
whatever
from
jspm
or
import
from
skypack
and
boom
it'll
pull
it
down
and
it'll
manage
the
cash
for
you.
So
so
I
think
in
another
another
six
to
eight
weeks
that
that
might
be
a
potential
alternative.
C
So
so,
basically,
you
know
what
what
dino
does
is
when
you
run
it,
it
just
does
a
dino
install
and
pulls
all
the
your
files
down
and
puts
it
in
a
dino
modules,
folder
right,
so
so
what
snowpack,
with
their
streaming
updates
would
do
the
same
thing
so
that
you
would
never
have
to
use
npm,
install
or
yarn
install
again.
It
would
just
it
would
just
take
your
you
know:
imports
and
exports
and
build
the
manifest
dynamically
and
build
the
log
files
and
and
pull
those
down
from
a
registry.
B
C
E
C
C
We
have
a
node.js
client,
but
this
client
is
very
opinionated
basically,
and
I
need
to
do
some
documentation
on
that.
But
basically
it
sets
up.
You
give
it
a
a
name,
an
app
name
like
foo,
and
then
it
just
gives
you
all
the
commands
as
if
that's
one
kind
of
entity,
so
you
don't
have
to
specify
the
data
store,
name
or
the
cache
name
or
the
search
name
or
the
storage
bucket
name.
C
It
just
takes
your
app
and
names
it
that
so
then
you
can
just
start
writing
docs
or
search
indexes
or
whatever
right
into
right
into
the
api.
So
we
may
need
another
kind
of
general
node.js
client,
one
of
the
things
that
I
was
planning
on.
Adding
to
this
one
was
some
flags
like
auto
caching,
where
you
could
give
it
a
document
type
and
just
say
cash,
true
or
something
like
that,
and
then
what
the
client
would
do
is
every
time
you
added
a
doc.
C
It
would
add
the
doc
to
the
data
store
and
that's
successful.
Add
it
to
the
cache
and
then
every
time
you
updated
the
doc.
It
would
invalidate
the
cache
and
update
with
the
new
one
and
then,
lastly,
if
you
did
a
query,
it
would
query
the
cache
first
for
all
the
documents
and
then
query
the
database.
C
So
it
would
just
basically
add
this
pattern
of
putting
caching
and
cache
and
validation
around
these
type
types
of
documents
like
widgets
or
movies,
or
something
and
then
another
flag
is
like
searchable
right,
which
would
do
the
same
thing
so
you
could
get.
Let's
say
you
had
a
type
of
document
like
a
movie
with
the
client.
You
could
flag
that
document
type
as
searchable
and
then
basically
every
time
you
add
a
document,
it
would
automatically
index
that
document
into
the
search.
C
D
D
I
think
you've
done
a
some
really
great
work
and
sort
of
making
it
really
easy
to
build
an
adapter
with
like
the
the
ports
and
using
zod
for
the
validation
that
just
sort
of
wraps
the
whole
thing
that
serves
as
your
test
as
well.
It's
really
cool.
So
I
might
just
reach
out
to
you
just
to
make
sure
I'm
on
the
same
page
and
hopefully
life
permitting.
It
doesn't
like
jump
out
at
me
and
I
can
actually
work
on
this
yeah.
No.
C
Yeah,
I
think
I've
got
the
the
documents
to
where
basically,
I've
got
this
mini
search,
adapter,
which
is
like
a
little
node
module.
But
when
setting
up
a
search,
you
have
to
pass
it
a
mapping
object
and
that
mapping
object
basically
has
a
fields
object
which
takes
an
array
of
all
the
fields
that
you
want
to,
search
for
and
then
a
store
fields,
object
which
takes
an
array
of
all
the
fields
that
you
want
to
store
in
the
document
and
that
maps
over
nicely
there's
a
little
work
with
elasticsearch.
C
So
you
can
say
you
know
here's
my
query
string
like
what
was
the
best
movie
of
1984
right
and
then
you
could
also
include
a
filter
and
that
filter
is
an
object
that
has
a
key
and
a
value.
So,
in
this
case,
your
filter
would
be
the
key
year
with
the
value
1984,
because
you
you
don't
want
to
search
for
a
movie
that
wasn't
published
in
1984
right
and
then
there's
a.
C
I
can't
remember
the
name
of
the
property,
but
it's
like
terms.
So
basically,
if
you
give
the
search
index
fields
that
you
want
to
search
on
or
like
title
and
content
and
year,
then
you
can,
in
your
query,
specify
that
you
know
for
this
query.
I
only
want
to
look
at
the
title
field
for
the
search
index
or
I
want
to
look
at
the
title
and
the
year
for
my
search
index,
but
not
the
content,
so
you
can
kind
of
specify
what
index
you
want,
but
by
default
it
would
use
all.
C
A
C
We
got
a
killer
new
website
right
now.
We've
got
a
function
that
we're
kind
of
calling,
middleware
and
and
basically
how
that
works
is
so
there's
a
app
interface
and
then
there's
these
adapters
and
then
there's
a
core
module.
The
the
app
interface
now
is
kind
of
specified
and
it
could
be
anything,
but
it's
specified
off
of
express
and
we've
got
two
kind
of
app
implementations.
We
have
a
rest
one
and
a
graphql
one,
but
they
both
kind
of
run
off
of
express.
C
So
this
middleware
allows
you
in
your
config.
If
you
put,
you
know
like
a
security
module
or
whatever,
and
you
basically
can
just
create
a
script
and
it's
a
function
that
gets
past
the
app
and
then
you
can
do
whatever
you
would
do
in
express
with
the
app
and
then
you
return
it
so
that
it
can
chain
through
an
array
of
middleware.
E
C
So
so
here
I
I
created
this
play
site
and
it's
using
jwt
for
security,
but
but
also
in
order
to
save
time.
I
actually
created
the
static
kind
of
web
page
for
it,
so
it
actually
uses
express
static
and
runs
public
there
and
and
then
I
also
created
the
ability
to
send
a
token
to
whoever
enters
the
token
as
middleware,
and
then
I
just
kind
of
configured
all
of
that
up
in
a
hyperconfig
file
where
I
just
added
this
middleware.
C
I
don't
know
where
I
sent
it,
but
but
that's
sort
of
how
we're
handling
security
is
we're
just
basically
saying
there's
so
many
opinions
about
security,
so
we're
just
going
to
give
you
a
hook
to
add
it
in
via
middleware,
and
then
you
can
add
your
own
security
based
off
of
that
middleware.
Does
that
make
sense.
A
A
C
Yeah
so
I
kind
of
just
like
the
pl
approach
of
modularity
and
and
then
that
way,
because,
like
security
for
a
multi-tenant
kind
of
sas
portal
will
be
different
than
security.
For
you
know
a
hobby
project
right
and
I
think
you
kind
of
you
know
you
kind
of
kind
of
have
to
get
opinionated
about
it,
but
if
you
can
think
of
a
way
to
not
be
opinionated
and
that's
better
than
than
this
approach,
I'm
all
ears.
B
You
have
a
question
yep
so
trying
to
think
of
like
the
user
flow.
For
you
know,
they're
like
okay,
we
want
to
have
our
custom
off
or
their
own
off
stuff
and
using
hyper
63.
So
I'm
thinking
of
like
all
right,
we've
got
this
agency
that
makes
apps
for
whatever
for
car
companies
or
startups
or
whatever
so
they've
got
like,
say:
they've
got
like
10
different
clients,
but
they
want
to
use
hyper
63
for
each
one
of
the
clients,
they're
still
going
to
have
like
their
core
app
right
where
they
are
like.
B
This
is
they've
got
their
core
app
with
their
business
logic,
but
then
they
use
that
server-side
app
to
call
out
to
hyper-63.
So
I'm
assuming,
if
they're
on
the
web,
they're
going
to
be
using
their
own,
like
they're,
already
going
to
have
their
own
kind
of
auth
set
up
and
then
they're,
just
like
hey
hyper
63,
I'm
this
company
calling
in
for
this
client
you
know
like
you,
can
use
my
off
stuff
to
access
my
shared
space.
C
C
So
again,
most
if
you're,
if
you're,
building
your
api,
you're
you're,
going
to
manage
your
user
base
authorization
through
that
api
and
that's
super
important
if
you're,
building
a
server-side,
app
and
let's
say
you're,
connecting
to
something
like
mysql
or
postgres,
normally
the
server
side,
app
kind
of
manages
a
couple
of
roles
to
that
database.
Like
report
user
or
read
only
user
right
or
admin,
I
can
do
everything
user.
C
So
I
kind
of
envision
hyper,
63
kind
of
you
know,
that's
what
you
would
be
setting
up
is
kind
of
these
kind
of
more
roles
and
responsibility,
users
and
and
then
in
this
middleware
you
know
you
can,
and
I
think
scopes
is
a
great
way
to
do
that
right.
You
can
do
scopes
and
then
use
the
jwt
audience
attribute
to
represent
a
tenant
and
I'm
actually
working
on
a
blog
post
to
talk
about
this
stuff.
But
but
basically
you
know
it.
C
Ideally,
if
you
are,
you
know
running
hyper
inside
your
cloud.
You
know
you
have
certain
security
requirements
there.
If
you're
running
it
over
the
wire,
you
know
using
public
and
private
keys
electrical
curve,
encryption
and-
and
just
you
know,
having
your
server
application
either
call
a
service
that
generates
those
tokens
or
generate
the
tokens
and
send
them.
The
hyper
63
is
is
the
best
that
I've
come
up
with
and
again
open
to
that.
But
but
you
can,
with
this
middleware
you
can
go
and
I
think
it's
pretty
cool.
C
Maybe
this
jwt
can
give
you
an
example,
but
you
can
go
over
each
endpoint
and
and
basically
map
scopes
and
create
rejections
based
on
those
scopes
before
it
even
gets
to
hyper
63..
So
you
could
say
you
know
app
use
and
my
scope
is
slash.
Data
or
my
endpoint
is
slash
data,
so
all
slash
data
endpoints.
C
If
this
user
is
a
read
only
user,
then
they
can't
call
post,
they
can't
call
put.
They
can't
call
delete
right
so
with
the
middleware,
you
can
basically
layer
that
and-
and
my
thought
is
to
maybe
have
some
example-
implementations
of
that
for
people
that
they
can
kind
of
fork
and
make
it
their
own.
So
here's
an
example
of
something
heavily
scoped
based
on
some
common.
C
C
So
that's
one
is
this:
the
playground
we
talked
about
last
two
weeks:
I've
got
that
set
up,
I'm
just
working
out
the
documentation,
but
it's
out
there
and
you
can
go
to
the
site.
Put
your
email
address
and
get
yourself
a
jwt
token
amy
yeah,
so
you'll
you'll
get
yourself
a
jwt
token
emailed
to
you
and
you'll
have
access
to
play.hyper63.
C
F
C
C
One
hour
live
streams
where
I'm
like
actually
working
on
hyper
for
an
hour
and
let
people
join
and
record
that
push
that
up
on
youtube
and
then
hopefully
that
can
can
serve
as
a
interim
and
I'm
able
to
get
some
stuff
off
the
list.
So
it
makes
me
accountable,
but
you
guys
can
kind
of
tune
in
and
get
familiar.
Does
that
sound
like
a
good.
A
C
D
B
C
Cool
all
right,
we've
got
a
couple
of
minutes
left
any
any
other
closing
thoughts
or
comments,
things
that
I
I
missed
I'm.
I
definitely
am
working
on
a
post
about
just
api
security
in
general
and
and
kind
of
a
tutorial
on
how
you
might
go
set
up
api
security,
that's
kind
of
tool,
agnostic,
right,
it's
just
kind
of
and
then
then
suggesting
like
you-
could
use
all
zero
or
cognito
or
firebase
auth
or
whatever,
or
this
go
true,
is
another
example
to
to
implement
off
and
see
how
that
goes.
A
C
C
C
Cool
well,
thank
you
all
for
your
time.
It's
very
much
appreciated
and
if
you
have
any
questions
you
know
feel
free.
There
are
several
places
now.
There's
discussions,
github
discussions-
I
don't
know
if
you
guys
have
seen
these,
but
I
kind
of
set
these
up.
So
if
anyone
wants
to
post
anything
on
hyper
63
github
discussions
is
a
great
place,
whether
it's
an
idea
or
q,
a
show
and
tell
questions
about
contributing,
that's
a
great
place
to
do
it.
C
Then
we
have
the
discord
channel
and
don't
know
what
to
do
about
that.
Yet
I
try
to
post
things
in
there
every
once
in
a
while,
and
then
we
have
our
slack
channel
and-
and
I
think
that'll
probably
be
a
topic
for
the
next
meeting
is.
Is
you
know
I
I'm
so
comfortable
with
slack?
It's
super
easy,
but
at
the
same
time
it's
kind
of
a
walled
garden.
So
so
anything
you
put
in
there
is
not
super
transparent.
C
C
C
C
B
E
C
Yeah
and
that
that's
another
thing
I'm
going
to
work
on
in
the
next
two
weeks
without
reading
me
is
get
all
the
contributors
on
the
readme
and
let
you
guys
put
your
bios
there
and
try
to
make
that
a
little
bit
more
formal,
because
I
definitely
appreciate
and
get
everybody
a
hat.
So
I
got
to
get
ben
and
everybody
else
that
contributes
a
hyper
63
hat.