►
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).
B
A
C
A
C
A
B
D
B
D
E
A
D
D
D
D
D
B
C
B
D
B
B
A
B
B
D
D
B
D
B
B
B
D
B
D
A
D
D
D
C
B
C
D
B
B
D
B
Early
days,
oh
the
baby's
fine,
nothing
wrong
with
me.
Oh
look!
Look!
He
is
my
JavaScript
that
changes
they
help
the
iframe.
Where
is
it
in
home,
j/s
I
didn't
see
a
home
touch
a
house.
What
other
is
it
probably
gets
compiled
down
into
site
that
day
as
an
embedded
at
the
top
of
the
page
on
the
bottom
of
the
page?
No.
B
D
B
B
D
B
B
B
D
B
B
D
B
D
A
D
D
D
D
B
D
What
happened
there?
I,
don't
know
it's
exec.
E
B
B
D
The
cookie
so
here's
the
thing
I'm,
seeing
though
yeah
there's
two
issues
here.
There's
the
code,
the
JavaScript
never
came
down
like
this.
This
new
cookie
compliance
right
right,
it
doesn't
even
like
get
bundled
up,
so
you
can
blame
him
all
you
want.
Maybe
how
did
the
build
not
bring
it
in?
Where
is
it
so
back
up
for
a
bit
home?
Jay
s
is
part
of
what
I
assume
it's
inside
of
a.
B
Place
behind
a
yes
and
you'll
see
that
it's
referenced
in
like
the
gulp
file
and
all
that
type
of
stuff.
Obviously,
because
that's
where
it
is,
and
then
it's
a
script
reference
for
it
and
it
only
renders
if
modeled
up
next
show
scheduled
is
true.
Ooh.
Okay,
hang
on,
he
may
have
put
that
code
in
there.
E
A
D
B
D
B
So
when
we
came
through
and
did
the
sweeping
changes
for
the
cookie
compliance
stuff,
like
obviously
some
of
those
stuff
wasn't
obvious,
and
so
you
can
get
into
these
weird
states,
as
we
just
found
that
if
you
don't
schedule
the
next
show
I
don't
render
the
home
screen
JavaScript,
because
you
don't
need
the
countdown.
So
why
would
you
accept
that
we're
now
relying
that
for
the
live
show
which
we
didn't
before
the
live
show
just
used
to
be
embedded
directly?
There
was
no
JavaScript
interaction
at
all,
so
yay
for
debugging
live.
We
have
three
people.
B
C
D
B
D
B
It
takes
that
into
consideration.
So,
if
you're
on
end,
which
means
you
either
have
live,
show
you
embed
all
live,
show
HTML
you're,
currently
watching
a
show,
then
it
turns
out.
You're
gonna
need
the
script.
Now
that
is
scandalous.
It's
what
happens
when
you're
over
optimized
at
home,
I
appreciate
I,
appreciate
that.
A
E
D
A
B
A
A
E
F
A
A
He
so
chained
calls
out
configuration
builders
explains
that
talks
about
how
he
set
things
up
with
docker
all
this
stuff,
so
very,
very
nice,
thorough
walkthrough,
so
good
job
gem
with
two
on
Jason
localization
configurations
up
making
a
request
culture
provider
in
this
one.
So
basically
you
know
pulling
in
a
localization
culture
from
Jason
files
explaining
how
he
did
that
and
then
he
continues
in
into
that
in
more
detail
with
localization
resources
pulled
from
Jason
as
well.
No
really
interest
yeah,
so
very
cool
yeah.
B
A
Interesting,
very
cool
yep,
so
neat
I'm
speaking
of
localization
I,
hope.
Someone
appreciates
the
smooth
flow
that
I've
built
here.
Damian
Bowden,
talking
about
identity
server
for
localization,
with
oh
I,
DC
implicit
flow,
so
he's
talking
about
in
angular,
so
he's
updated
his
his
sample
here
and
he's
showing
how
to
localize
that
so
cool
there's
a
ton
of
code
here.
This
is
this:
a
very
in-depth
one:
okay,
so
master
Christensen
announced
mini
blog
core.
So
this
is
a
new
blog
engine.
A
It's
one
of
the
specific
focuses
he
really
looked
into
here
was
highly
like
optimized
for
web
technology.
So
he
explains
in
here
or
some
of
the
things
he
did
web
fonts
image,
optimization
with
his
a
sure
image,
optimizer,
etc.
So
this
is
good
both
for
if
you're
looking
for
a
blog
and
then
also
just
looking
at
what
he's
done
as
far
as
satisfying
the
requirements
here,
he
calls
out
his
web
developer
checklist.
So
just
talking
about
you
know
how
to
make
sure
that
this
is
taking
advantage
of
all
the
latest
browser
technologies,
cool,
Steve
Sanderson.
A
He
just
blogged
about
updating
blazer.
So
a
blazer
is
the
web
assembly.
A
thing
for
running
dotnet
in
the
bra
in
the
browser-
and
so
here
he
talked
about
how
it's
been
moved
over
from
dotnet
anywhere
to
run
with
mono
in
the
browser
I
had
to
play
with
this.
The
other
day
it
it
was
some
of
the
earlier
builds
were
a
little
bit
tougher
to
get
running.
For
me,
this
was
just
boom
boom
boom.
It
worked
right
out
of
the
out
of
the
gate
and
it
was
really
so.
This
is
interesting
where
he
explains
it.
A
Some
of
the
limitations
that
were
hit
with
dotnet
anywhere,
including
being
kind
of
old
and
not
maintained,
so
not
up-to-date
with
the
latest
dotnet,
you
know,
features,
but
also
some
of
the
missing
features
that
were
required
from
the
hackathon.
He
does
call
out
that
it
is
bigger,
so,
whereas
old
one
was
300
some
kilobytes,
this
is
now
four
megabytes,
but
this
is
before
optimization.
So
anyhow,
he
links
in
there
to
the
repo
very
quick
to
get
started
with
that
mohamed
rohan
Sahid
he's
talking
about
asp
net
core
cashing
in
practice.
A
So
this
is
cool
talking
about
some
of
those
headers
that
people
don't
dig
into
very
often
so
things
like
cache
control
header.
He
talks
about
you
tag
and
how
to
set
etags
kashkin
more
stuff
with
cache
control.
So
this
is.
This
is
a
very
good
kind
of
in
in
down
honest
good
yeah
this
these
headers,
if
you've
it's
possible.
If
you
set
one,
it's
not
taken,
it's
not
honored.
Unless
you
set
another
that
kind
of
thing
it's
it's
kind
of
difficult
to
get
these
right.
A
So
it's
nice
to
have
this
kind
of
written
out
in
detail
with
some
code
there
and
my
last
one.
This
is
from
Matthew
and
he
talked
about
something
that
they've
been
using
on
Winton
technology
at
their
company.
This
is
an
SEO
NuGet
package,
so
the
idea
is
in
order
to
SEO
optimized
a
site.
You
need
to
have
sitemap
robots.txt
you.
A
You
need
to
kind
of
have
the
proper
files
in
order
to
make
sure
that
your
site
is
being
indexed
the
way
you
want
it
to
so
he
has
kind
of
they've
set
up
a
solution,
they've
been
using
it
internally
for
awhile
and
so
now
they're.
Releasing
it
as
a
as
a
new
get
package,
so
this
is
pretty
cool.
This
is
going
through
and
and
it's
using
ASP
net
core
internals
to
do
things
like
just
get
rid
of
pages
and
that
kind
of
stuff.
A
A
A
D
D
D
All
of
this
stuff
that
says,
Nutella
gence
dot
is
14.
15
year
old
code
running
under
don''t
standard
Wow,
then
das,
blog
dot,
web
dot,
UI
and
core
are
the
new
things
that
sit
on
top
of
the
existing
das
blog
runtime
and
he's
swapped
out
the
templating
and
replaced
it
with
razor
but
85
90
percent
of
the
stuff
just
works
that
cool.
That's.
D
A
D
D
We've
been
working
on
this
for
a
while,
like
Josh
blog,
is
still
being
actively
worked
on
he's
added
reCAPTCHA
and
he's
added
SEO
and
all
kinds
of
cool
stuff,
but
I
would
like
to
be
able
to
get
das
blog
working
on
dotnet,
core
and
I.
Don't
want
to
rewrite
the
thing
from
scratch,
so
tech
take
a
look.
It's
at
github.com,
slash
pop,
a
string,
very
cool
cool,
yeah,
definite
and
there's
no
joke
like
that
I
trying
to
come
up
with
examples
of
how
cool
it
is
and
converting
17
year
old
code.
D
D
C
B
B
A
B
B
We've
I've
been
struggling
to
put
together
the
roadmap,
because
we've
kept
we've
been
churning
on
a
bunch
of
decisions
and
changes
about
when
and
how
we're
going
to
do
some
certain
things.
We
got
some
clarity
over
on
that
in
the
last
week,
so
my
hope
is,
and
then
vias
code
put
out
their
roadmap
and
completely
shamed
everyone
on
the
planet,
because
their
roadmap
is
amazing
and
it
doesn't
talk
about
dates.
B
It
just
says
like
for
2018:
these
are
the
things
we
care
about,
and
so
I
was
inspired,
so
I'm
gonna
try
and
get
something
together
at
least
phrase
minute
core.
We
do
have
some
dates
floating
around
now
for
our
plans
to
the
next
release
and
we'll
chat
to
our
boss
soon
to
figure
out
how
he
wants
us
to
go
about
sharing
those.
But
at
least
now
we
seem
to
have
some
some
momentum
behind
what
shape
the
next
release
will
have.
Pat
chin
was
asking
a
question
about
patching.
B
Patching
is
coming
so
like
there'll,
be
a
patch
release
shortly.
I,
don't
know
the
exact
date,
but
within
the
next
month,
or
so
then
there's
a
few
fixes
in
that
patch
and
will
continue
to
do
patch
releases
even
after
we've
released
two
one
as
part
of
the
whole
LTS
long
term
support
versus
current
stuff,
which
again
we're
still
we're,
still
reviewing
that
policy
for
how
it
applies
to
2x,
but
that's
all
sort
of
in
flux
right
now,
we're
still
we're
still
doing
that
stuff.
B
Some
of
the
the
I
want
to
go
through
priorities
and
stuff.
At
some
point,
we
don't
have
time
now
about
the
things
into
one
that
we
have
some
very,
very
large
items
that
we're
working
on
that
we
that
are
deemed
the
most
important
one
of
them
is
what
we
call
inner
loop
performance.
You
can
simplify
that
down
to
there's
a
build
perf.
We
know
that
the
dotnet
core
developer
experience
right
now
isn't
great
as
soon
as
you
start,
adding
more
projects
or
your
app
gets
any
anything
beyond.
B
You
know
very,
very
simple,
and
even
when
it
is
simple,
it's
still
not
fast
enough,
and
so
we're
doing.
There's
a
massive
multi
team
effort
underway
to
to
look
at
that
and
to
get
improvements.
There's
already
been
in
previous
made,
their
improvements
made
in
the
202
SDK.
There
are
improvements
in
the
upcoming
SDK
releases.
B
Some
of
the
bigger
efforts
we
talked
about
like
more
integration
of
the
open,
API
spec
and
having
that
via
default
experience
in
our
Web
API
stack,
including
generation
of
proxies
and
those
type
of
things,
we're
not
quite
sure
whether
it's
going
to
land,
yet
whether
we
get
that
into
one
arm
or
whether
we
have
to
rethink
some
things
because
of
fact
we
have
other
stuff.
We
have
to
do
first,
but
I
want
to
talk
through
all
these.
B
These
things
a
little
more
depth
next
time,
hopefully,
and
a
lot
of
these
things
will
be
in
the
roadmap,
but
so
yeah
I
just
wanted
to
like.
Let
people
know
that
we're
working
on
some
big
things
and
they're
gonna
take
a
bit
of
time
for
us
to
get
right
before
we
can.
You
know
start
promising
when
we're
going
to
get
a
release
out.
D
D
B
Obviously
for
us
to
be
able
to
say
to
an
enterprise
yeah.
We
support
everything
in
the
platform,
even
though
we
don't
own,
like
20%
of
it.
That
becomes
very
difficult
because
of
the
way
dotnet
works.
It's
not
like
jQuery.
When
we
started
this
in
the
late
2000s
we
can
like
worst
case.
You
can
just
patch
jQuery,
just
source
files.
B
We
can
just
like
update
the
template
and
just
ignore
the
the
root
project
in
the
worst
case
scenario,
if
we
have
to,
we
can't
do
that
with
dotnet
because
of
type
safety
and
identity
and
NuGet
package
IDs
and
those
type
of
things.
So
we
have
to
think
about
a
little
bit
differently.
So
yeah
we
got
some
some
stuff.
We
have
to
work
through
and
we'll
start
sharing
some
of
the
thoughts
and
decisions
on
that
shortly,
but
in
the
meantime,
developers
are
still
doing
work.
B
So
if
you're
watching
the
github
repos
you'll
see
work
happening,
you'll
see
fixes
going
in,
there's
been
some
good
fixes
made
based
on
feedback
to
200
that
have
already
gone
into
the
active
dead
branches,
and
we
look
forward
to
getting
those
improvements
out
to
customers
as
soon
as
we
possibly
can.
So
all
right.
That's.
B
A
C
B
B
D
B
B
B
Cool
things
as
well
and
frankly,
and
some
of
the
some
of
this,
but
we've
only
very
we've,
only
really
just
started.
So
we
only
have
some
simple
scenarios.
We
expect
that,
once
we
add
more
complicated
solutions,
the
difference
has
to
become
a
lot
more
stock.
But
as
they
say
here,
we
like
to
embrace
the
red,
which
means
that
you
need
to
visualize
your
problems
and
make
sure
that
you
understand
them
and
like
communicate
them
up
the
chain
so
that
you
can
do
something
about
them.
So
that's.