►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-12-02
Description
Learn more about the work of the IPFS Docs & Developer UX Working Group and how to join our weekly syncs: https://github.com/ipfs/docs
Notes: https://docs.google.com/document/d/1EOD-pJi4GvRmGi9HHocgVV8uVHMFIZlyVgJDkvC3DQ4/edit#heading=h.dgr8wcldbq68
A
All
right,
good
morning
afternoon
and
or
evening
everybody
and
welcome
to
the
ipfs
documentation
and
developer
UX
working
a
group
weekly
sync.
Thank
you
for
joining
us.
If
you
would
like
more
information
or
if
you'd
like
to
follow
along
in
the
notes,
everything
you
need
to
get
started
is
at
the
is
at
the
readme
model
on
our
github
repo
at
github,
comm,
slash,
ipfs,
slash
docs.
A
We
use
this
meet
a
meeting
as
a
way
to
check
in
with
our
ok
ours,
and
so
as
such,
we
will
actually
be
going
through
those
in
the
document
that
I'm
sharing
on
my
screen,
one
by
one
johnny.
I
am
going
to
wait
for
you
at
the
end,
since
you
are
still
typing,
but
basically
we
are
starting
in
our
priority.
For
the
rest
of
the
quarter
is
the
beta
launch
of
the
new
documentation
site.
It
is
being
tracked
in
the
milestone
that
you
see
alert
on
the
first
bullet
point
of
the
notes
document.
A
A
Let's
see
so
I
call
out
links
between
the
legacy
and
the
beta
pages.
Just
the
item
I've
got
highlighted
at
the
moment.
There
are
a
lot
of
items
that
you're
gonna
see
here
that
are
labeled
as
nearly
done,
but
a
little
bit
derailed
due
to
illness
on
christenings
part.
You
know
this
does
sort
of
highlight
an
issue
that
we've
got
in
that
in
terms
of
development.
A
He
is
nearly
done
with
implementing
those
call-out
links
between
the
legacy
and
the
beta
pages.
I
took
her
the
links
on
the
legacy
site
last
week,
so
those
are
ready
to
go.
All
we
need
to
do
is
merge.
The
PR,
the
beauty
agents,
were
a
little
bit
more
complex,
so
he
is
rolling
that
into
a
PR.
That
includes
a
couple
of
the
items
below
dinner
with
the
content
sub
pages
for
content
that
does
not
exist
yet
act
you
want
to
talk
about.
It
sounds
like
you,
YouTube
were
the
last
sub
conversation.
C
B
It's
because
it
was
related
to
the
changes
that
we've
made
a
related
to
the
testing
and
so
I
just
put
it
down
there
with
testing,
but
I
can't
Coco.
You
know,
Occam's
razor
is
really
the
rule
of
thumb
here.
The
simplest
approach,
I
think,
is
going
to
be
the
the
best,
especially
when
we're
talking
about
a
page
that
is
at
its
core,
a
frustration
page.
B
A
Also
have
a
link
for
each
of
the
I
believe
it's
eight
pages
that
are
gonna.
Have
this
content
sub
temporarily
until
we
finish
the
content
on
them,
we
do
have
a
spreadsheet
here
with
the
related
links
all
ready
to
go.
So
it's
just
a
matter
of
Chris
sticking
them
in
there
or
once
he's
got
the
template.
I
can
toss
those
in
there
pretty
easily.
So
that's
awesome.
That
is
nearly
done.
Seo
meta
tags.
A
This
issue
involves
us
getting
into
place
of
very,
very
basic
SEO
meta
content
and,
ideally
a
social
media
link
card
in
each
of
the
content
pages
in
the
docs
Vita
I
did
some
investigation
last
week
into
exactly
how
this
works
was
repressed
about
matter.
It's
fairly
straightforward,
Araki
were
gonna,
make
a
social
card
and
I
was
just
gonna,
get
that
SEO
meta
data
suck
in
there
this
week,
bare-bones
CSS
edits
are.
B
Just
defining
the
bare
minimum,
as
the
word
implies
there,
that
we
can
apply
toward
the
like
out-of-the-box
view.
Press
seem
to
just
to
make
the
design
as
user-friendly
as
possible.
You
know
we
have
a
lot
of
content
on
the
left
side,
for
example,
and
we
want
to
make
sure
that
visually
it's
it's
scannable
that
you
can
that
you
can
quickly
find
what
you're
looking
for-
and
you
know
from
a
accessibility
standpoint
that
the
colors
are
of
sufficient
contrast.
You
know,
we've
got
some
pretty
light
greens
in
there
right
now,
for
example,
that
don't
quite
meet.
B
You
know
trimming
away
from
that,
although
that
that
isn't
super
super
visual
and
super
crazy
anyway,
but
with
an
eye
to
getting
you
know
not
letting
the
better
be
the
enemy
of
the
good,
getting
something
out
there
as
quickly
as
possible,
and
then
I
may
try
and
actually
dive
in
and
do
some
of
those
edits
myself
in
order
to
lift
the
load.
Chris
cool.
A
A
I
know
how
much
you
love
CSS
cool
cool,
I.
The
communications
plan
I
actually
addressed
all
of
the
content
here
before
the
holiday
rest
after
the
content
comments
on
that
content
totally
welcome,
since
those
are
written
and
probably
reflect
my
own
voice
to
certain
extent,
but
we
have
an
entire
communications
plan
laid
out
here.
A
There
are
some
highlights
for
some
things
that
are
not
yet
ready,
mm-hmm,
but
are
or
just
URLs.
Obviously,
things
won't
happen
until
we
start
posting.
You
know
I
can't
link
to
read
it
until
we
actually
post
about
it.
We
have
all
of
that
queued
up
and
ready
to
go,
including
the
timeline
and
the
core
messaging
in
the
calls
to
action,
so
that
is
good
I'm,
also
hoping
that
we
can
use
that
as
sort
of
a
working
template
for
a
variety
of
other
communications
efforts
going
forward,
I'm
just
good.
A
A
If
we
at
lunch
on
time,
our
next
stage
of
implementation
would
be
the
9th
of
December
when
I
start
putting
together,
like
I'll,
throw
the
blog
post
in
the
blog
repo
for
circulation
and
approval
that
sort
of
thing
let's
hold
off
on
talking
about
the
ipfs
hosting
stuff,
because
that's
probably
going
to
turn
into
some
conversation
and
I
want
to
make
sure
that
we
address
everything
else.
Johnny.
You
want
to
talk
about
your
age
to
work,
yeah.
D
Just
pretty
quickly,
so
we
updated
a
bunch
of
the
headers
just
so
that
the
the
basic
search
function
that
we
have
just
works
a
bit
better.
So
with
the
P,
the
things
that
people
are
actually
searching
for
are
so
much
of
what
the
headers
that
we
have.
So
this
involve
like
adding
removing
and
updating
some
of
them,
and
so
me
and
Jessica
take
another
look
at
them
and
it
seems
to
work
from
our
end.
The
next
thing
we
need
to
do
is
just
kind
of
reach
out
to
some
extent
on
people.
A
You
have
time
this
week
to
try
to
do
like
a
20-minute
zoom
call
with
the
two
folks
from
two
three
folks
from
our
internal
testing,
who
really
struggled
with
that
the
most
I
think
Lydell
was
one
of
them.
Does
anybody
else
remember
and
should
Eric
I'm
sure
they're
in
Eric's
notes,
but
I
would
I
would
try
to
grab
20
minutes
with
Lydell
Eric?
Can
you
think
of
anybody
else
who
was
struggling
with
the
search
you
Johnny
want
to
talk
to.
D
A
A
About
Johnny's
work
with
the
h2s,
he
went
just
to
make
sure
that
they
render
better
in
the
search,
keyword,
wise
I,
think
in
this
situation,
we're
probably
okay
at
this
stage
with
internal
testing,
particularly
since
after
lunch
we're
thinking
about
you
know,
we
do
intend
to
investigate
deeper
full-text
search
without
goal.
Yeah
do
you
are
completely
yeah.
B
A
B
A
C
A
That
we
can
close
out
the
issue
yeah,
okay,
continuing
on
the
legacy
Docs
deprecation
plan.
I
know
we've
all
sort
of
had
off-the-cuff
discussions
on
this
and
we've
accumulated
some
notes.
I'm
gonna
start
assembling
those
collected
notes
this
week
after
I
get
the
SEO
meta
tag
stuff
done
Johnny.
You
said
you
would
offer
to
review
this
since
you've
deprecated
the
site
in
the
past.
Anybody
else
wanna
play
along
I,
know
close.
A
Know
Chris
had
some
thoughts
as
well,
so
I
think
if
Johnny
and
I
can
put
together
a
list
for
Chris's
review.
Really.
This
is
just
about
getting
our
heads
in
the
right
place
with
an
initial
plan
that
will
then
presumably
enact
in
key
one.
So
not
that
big
of
a
deal
I
just
want
to
make
sure
it
gets
done
in
time.
Awesome,
metrics
definitions,
laughter,
you
wanna,
wanna
chat
about
that
time.
D
Yes,
so
we
just
kind
of
list
it
out
on
the
github
issue
that
length
just
a
sense
of
those.
These
two
sections
of
metrics
that
we're
gonna
copy,
so
there's
need
a
nice,
so
there's
need
so
we
definitely
need
so
cool
you're
open
to
an
officer.
I
remember
what
they
are
here.
We
go
yeah
so
like
location
native
language
of
the
user.
This
would
be
super
useful
in
our
localization
plan
of
our
office,
trying
to
figure
out
what's
going
on
there,
how
they
got
there.
D
D
That
is
pretty
much
the
need,
then
there's
nice
to
have
things
or
like
how
long
sorry,
the
low
time
they
were
on
each
page,
so
how
long
it
took
to
mode
so
that
would
be
really
useful
in
terms
of
like
is
ipfs
doing
what
we
needed
to
do
in
like
a
fast
enough
time,
then
there's
like
those
four
other
things
are
like
free
to
visit
stuff
like
that.
I
want
to
sync
up
with
Chris
just
to
make
sure
that
the
the
top
five
things
that
we
have
in
need
are
in
fact
doable.
A
And
he
did
wake
up,
the
the
present
at
least
launched
will
be
using
GA
and
he
did
set
up
a
GA
profile
specifically
for
this
site
on
Thursday
Friday,
so
so
I
know
this
is
in
progress,
which
is
awesome.
Gourgeist
was
sick
as
a
dog.
I
did
also
add
this.
Other
question
about
I
know
that
we've
got
specific
metrics
sitting
on
the
helpful
and
not
helpful
buttons
and
the
legacy
site
that
I
to
my
recollection,
those
are
the
only
that's
the
only
sort
of
specific
analytics
trail
that
we've
got
sitting
on
the
site
right
now.
A
D
A
And
it's
also
been,
it's
also
been
explicitly
helpful
over
the
last
two
months
to
identify
on
yeah
we
had
some
allies
were
just
clicking,
not
helpful
and
I'm
surfacing
any
other
info,
and
that
did
gave
us
some
pointers
for
things
to
look
at
so
possible,
awesome,
awesome
and
then
the
underneath
that
the
beta
site
is
this
helpful
feedback
mechanism
that
is
getting
implemented
by
Chris
right
now,
last
I
heard
on
Friday.
He
said
he
was
nearly
done,
but
was
not
quite
there
yet.
A
B
July
I,
yes,
a
usability
testing
and
we're
able
to
get
in
on
site
internal
on
site
face
to
face
just
a
brilliant
group
of
brilliant
people
who
are
super
engaged
in
this
content
and
we're
very
excited
to
dive
in,
and
you
know
the
number
one
feedback
point
that
we
had
from
everyone
is:
oh,
my
god.
This
is
amazing.
A
B
To
and
yeah
and
I
tried
to
the
other
day,
I
distill
from
all
of
the
many
gems
distill
some
of
the
actions
that
we
might
want
to
that
we
might
want
to
take
you
know
things
like
you
know,
borrowing
from
how
cool
pro
school
is
how
they
have
a
little
sandbox
where
you
can
try
out
code,
and
maybe
you
know,
maybe
even
having
like
a
spun
up
instance
of
ipfs.
There
I
mean
it's
it's
you
know,
certainly,
if
you're
doing
ipfs
you
need
to
you
need
to
have
something
running
on.
B
B
You
know
that
kind
of
thing
really
that
kind
of
feedback
is
it's
kind
of
less
about
usability
and
more
about
just
a
really
neat
feature
idea
from
that
can
only
come
from
someone
who
really
understands
the
space,
and
so
it
was
really
great
to
get
that
kind
of
feedback.
But
we
had
a
really
wide
range
of
folks,
including
people
who
have
never
not
used
my
kfs.
B
A
Yes,
yeah
Molly
have
a
good
point.
Yes,
I
guess
I
didn't
resonate.
You
can
get
yeah
like
like
90%
of
the
way
there,
so
we
were
actually
actually
been
talking
to
Alex
about
sort
of
a
good
mix
of
actually
using
in-browser
ipfs
and
then
also
for
some
of
the
more
complex
things
cheating
it
a
little
bit
with
the
straight-up
emulator.
That
was
just
pretending
to
be
ipfs
in
the
terminal
that
was
at
least
respond
with
the
right
error
codes
that
turns
into
a
bigger
you
know
that
turns
into
sort
of
a
bigger
test.
A
It's
a
really
interesting
one.
I
think
that
we
all
sort
of
like
when
that
was
brought
up
is
like.
Oh,
that's,
a
really
interesting
look
around
and
we
all
kind
of
lit
up
on
that.
So
watch
that
space
actually
Eric
I'll
go
through
I'll,
go
through
your
test
plan
summary
and
add
a
couple
of
issues
based
on
stuff
like
that
that
we
can
at
least
get
in
the
ice
box.
So
we
don't
forget
about
them.
A
Sweet,
sweet,
okay
realize
we're
starting
to
run
out
of
time
content
improvement.
To
be
completely
honest,
we
are
pausing
on
content
improvement.
That's
been
hanging
out
in
our
Rico
until
after
the
beta
launch,
unless
something
really
dire
comes
up
or
unless
something
from
a
contributor
comes
up,
particularly
because
I
know
we
closed
more
than
20
issues
in
the
quarter
to
date,
which
is
pretty
great.
We
don't
want
to
rest
on
our
laurels.
What
we
do
have
a
lot
of
other
stuff
to
do
right
now,
I
picked
three
C
content
close
reading
this
one's
yours,
Johnny.
D
Yeah
pretty
much
what
it
says,
finished
close
reading,
so
those
always
understand
even
what's
going
on
at
the
docks
now
Rover
pull,
which
is
on
the
github
issue
and
then
raised
a
bunch
of
issues
based
off
that
report.
So,
like
things,
we
need
to
update
stuff
that
needs
to
go,
though
I
linked
in
the
work.
Oh,
it
did.
D
Yeah
here
is
the
super:
exciting
long
report
go
through
it.
If
you
want,
don't
go
through
it,
if
you
don't
so.
D
E
E
A
A
You
will
notice
that
there
is
a
lot
of
dependency
on
Chris
as
our
sole
full
stack
developer
on
the
team,
and
they
saw
the
fact
that
we,
many
of
us
were
travelling
to
meet
up
in
person.
We
had
many
of
us
on
holidays
and
then,
oddly
enough,
as
a
result
of
the
in-person
meeting,
like
a
disproportionate
number
of
us,
got
extremely
sick,
including
unfortunately
Chris.
You
know
this
sort
of
leaves
us
we
are.
We
are
definitely
in
a
time
crunch.
A
We
have
been
hitting
and
also-
and
also
frankly,
due
to
the
fact
that
this
is
a
pretty
intensive
task
for
Chris.
He
will
benefit
from
having
the
time
and
space
to
devote
to
that
without
a
whole
lot
of
internal
interruptions.
So
at
the
moment
to
be
completely
honest,
we
are
hitting
these
other
options
first.
A
That
does
mean
that
we
would.
We
would
almost
certainly,
unless
any
more
of
us
get
sick.
He
left
in
the
position
where,
on
the
17th,
we
have
all
of
these
but
hosting
beta
on
ipfs
done.
So
that
leaves
us
with
two
possible
options.
One
is
we
hold
off
until
we
get
that
taken
care
of
the
other
is
that
we
expose
the
links
to
the
site,
as
is
temporarily,
and
this
is
this-
is
a
call
that
I
think
really
backs
above
all
of
our
levels
of
authority
within
the
working
group.
So
that's
a
decision.
A
That's
going
to
have
to
be
made
by
others.
We
have,
as
a
working
group
given
thought
to
the
idea
of
allowing
people
to
use
the
site
so
that
we
can
gather
metrics
so
that
we
can
continue
to
do
our
work
so
that
we
can
give
Chris
and
any
external,
internal
and
external
fix
that
he
needs
time
to
do
this
correctly.
A
We
did
have
some
uncommon
that
a
lot
of
really
interesting
and
useful
stuff
came
out,
particularly
the
idea,
like
a
very
bare-bones
implementation,
for
a
simple
site
hosting
mechanism
that
would
actually
be
a
built
directly
into
ipfs
desktop,
and
the
response
to
that
was
like
amazing,
like
ridiculously
amazingly
positive
among
all
of
the
folks
in
our
intern,
in
person
meeting,
which
suggested
that
you
know
this
is
a.
This
is
a
large
issue.
You
know
we're
all
aware
that
this
is.
This
is
a
pretty
substantial
issue.
A
Yeah
we
dog
food
whenever
we
possibly
can,
but
if
the
dog
food
is
not
very
good
and
we
need
to
make
the
dog
food
better
to
make
things
better
for
everybody,
so
you
know
this
is
a
decision
that
is
gonna
have
to
be
made
by
others.
I
do
propose
if
we
do
decide
to
temporarily
just
find
us
if
we
temporarily
launch
using
our
existing
mechanism
that
we've
been
developing
on,
you
know
we
had
to
have
built
into
the
communications
plan.
Some
pretty
straightforward
means
for
addressing
this.
This
is
exactly
it.
You
know.
A
If
we
want
to
build
the
dock
site,
we
wanted
to
see
in
the
world
we
needed
to
solve
some
hitches
in
deploying
the
site
using
NTFS
and
that
those
issues
have
been
pain.
Points
to
a
lot
of
other
developers
in
common
tool
sets
to
build
web
apps,
and
we
are
working
on
the
best
means
of
addressing
this.
But
we
don't
want
to
make
books
wait
for
improved
documentation
in
the
meantime,
and
we
also
want
to
give
folks
as
much
time
as
possible
to
give
feedback
on
the
new
site.
A
C
Is
there
a
plan
written
down
somewhere
of
the
approach
we're
taking
for
getting
this
moved
over
ty
DFS
I
saw
the
issue
the
tracking
issue,
but
it
doesn't
have
kind
of
stages
or
steps.
There's
a
lot
of
different
potential
pathways
to
do
this,
some
that
are
real
hard
and
some
that
are
exactly
what
we've
done
for
Hugo
and
other
sites
like
where
we
write
the
plug-in
needed
to
make
it
work,
which
is
also
super
useful
for
everyone
else.
Who's
using
yeah,
yeah,
yeah.
A
And
the
short
answer
to
that
is
no.
It
is
not
in
the
issue
because
it
was
stuff
that
Chris
was
working
on,
like
literally
as
he
was
getting
on
the
plane
to
come,
hang
out
with
us,
but
we
have
had
a
discussion
about
that.
The
most
straightforward
solution
is
probably
going
to
be
the
one
that
we
take,
because
that
would
that
would
increase
the
time
that
we've
got
available
to
do
something
really
cool
like
build
some
basic
functionality
inside
EFS
desktop
so
yeah.
It's
it's
it's
a
reasonably
quick
solution.
A
However,
he
was
very,
he
thrust,
a
good
deal
of
uncertainty
and
the
timeframe
needed
to
test
it,
and
so
therefore
didn't
want
to
make
like
a
super
firm
commitment.
It
was
like
yeah
we've
done
similar
for
Hugo
and
the
like,
but
this
there
there
are
some
areas
of
this
where
it's
a
little
bit
of
uncharted
territory.
I
wish
I
could
be
more
specific
about
that.
To
be
honest,
I,
don't
remember
exactly
what
those
were.
A
A
Think
the
rest
of
the
team
and
I
had
a
pretty
pretty
lengthy
discussion
on
this
I
believe
I'm
speaking
on
behalf
of
the
rest
of
team,
everybody
else
feels
her
to
smack
me
on
the
head,
metaphorically
and
zoom,
whatever
that
takes
where
we,
where
we
were,
we
were
prepared
to
launch
with
what
we've
got
right
now,
for
the
sake
of
being
able
to
get
a
couple
of
weeks
of
user
feedback
of
user
testing
in
there.
It's
also
really
a
commitment
to
transparency.
A
C
Just
realize
I'm
late
to
my
other
meetings,
actually
I
did
jump
up
real
fast,
but
I.
We
have
very
strong
feedback
on
this
all
the
way
from
on
clear
on
exactly
what
we
need
in
order
to
communicate
this
out
more
more
publicly,
and
so
a
question
on
my
mind
is
cool.
There's
all
these
other
things
that
are
also
planning
pick
up
Chris's
time.
Are
there
other
folks
who
can
jump
in
and
help
out
with
some
of
those
tasks,
that'll
allow
Chris
to
focus.
C
A
A
And
it
may
be
to
be
completely
honest,
a
lot
of
that
stuff-
that's
like
so
far
in
stream
that
it's
basically
crisp
wrapping
up
work
on
a
couple
of
things,
so
it
may
not
like,
like
handing
that
work
over
to
somebody
else
at
this
point,
may
not
be
the
most
productivity
of
his
time.
I
will
ask
him
again
about
that,
obviously,
and
but
really
suppose
at
this
point,
the
the
biggest
thing
you
know,
obviously
we're
all
gonna
combine
on
anything.
We
can
do
to
take
Chris's
workload
off
those
items.
A
He's
got
open,
but
I
think
my
biggest
question
for
you
and
Molly
is
policeman
over.
You
know
what
this
means
visiting
our
deadline,
whether
we're
willing
to
sort
of
have
this
two-month
interim
period
as
an
example
of
you
know
really
just
very
straightforward
transparency,
while
also
still
giving
us
the
opportunities
or
test.
If
that's
not
the
case,
then
then
will
delay
launch
until
we
get
this
done.
A
You
know
that
does
give
us
the
opportunity
to
tweak
a
few
more
things,
but
it
does
mean
that
we're
lacking
some
user
testing
the
communications
plan
we're
ready
to
pull
the
trigger
on
the
weeks
notice
on
the
comms
plan.
Whenever
you
know,
whenever
that
weeks
notice
exists,
you
know
obviously
we're
all
very
keen
on
meeting
our
deadlines.
This
is
our
way
of
meeting
our
self-imposed
deadline.
If
that's
not
a
possibility,
that's
not
a
possibility.
So
I
will
leave
that
in
your
head
to
spin
around
you
and
or
anybody
else,
making
a
decision
on
that.
A
C
Good
yeah,
I
think
I'm
top
level
is
like
I've
got
an
extremely
clear
feedback
on
this,
which
is,
we
cannot
do
a
public
launch
of
a
dock
site.
That's
replacing
our
existing
dock
site,
which
is
on
my
PFS.
That's
something!
That's
not
my
PFS,
so
I
I
have
really
clear,
like
black
and
white
and
guidance
on
this
and
want
to
make
sure
that's
clear
to
everyone
else
here.
So
we
don't
spend
a
lot
of
time
pushing
for
it
on
something,
that's
long
option.
We
can
of
course,
keep
pushing.
A
We
will
we
will
launch
on
ipfs
it's
just
a
matter
of
whether
we
wanted
a
several
week
stopgap
in
order
to
give
folks
a
chance
to
actually
play
with
the
thing
I
mean
it's,
it's
extremely
beta,
and
so
that
was
sort
of
that.
That
was
what
we
were.
We
were
sort
of
leaning
on
is
like
all
right.
This
is
this
is
in
parallel
with
the
existing
site.
It's
definitely
in
development.
A
You
know
it.
So
it's
it's
a
little
bit
different
than
a
straightforward
public
launch,
but
yeah
I
guess
our
request
to
you
would
be
to
you
know,
having
a
just.
Have
one
more
thing
see
if
there's
any
point
having
a
parent
lunch,
if
there's
not,
let's,
let's
get
that
on
on
paper,
preferably
in
the
in
the
issue
itself,
if
you
don't
mind
which
espera.
C
A
Requirement
sure
sure
and
I
think
you
know
to
answer
your
question
about
a
timeline
yeah
we're
still
there's
still
a
fair
amount
of
uncertainty
and
that,
with
the
test
phase,
the
actual
building
of
it
is
a
little
bit
more
certain,
but
testing
still
pretty
much
up
in
the
air,
so
say,
yeah,
I'm
sure
Chris
has
seen
your
comment.
I
will
check
in
with
him
as
well,
but
I
think
you
know
this
doesn't
keep
us
from
the
pace
at
which
we're
plugging
away.
We
just
might
be
a
little
bit
delight
awesome.