►
From YouTube: IPFS Web and GUI Biweekly 2020-07-28
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1169
About IPFS GUI and Browsers Biweekly:
https://github.com/ipfs/team-mgmt/issues/790
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
And
we
are
live,
welcome
to
really
no.
B
B
C
D
No,
if
you're
typing,
as
security
starts,
sometimes
it
takes
the
key
and
then
goes
to.
A
All
right,
let's
see,
if
I'm
able
to
do
some
advanced
stuff
like
sharing
my
screen
and
telling
people
about
cleaning
services.
Why
not
all
right?
This
is
like
a
quick
update.
We
got
a
bit
refreshed
and
updated
api
spec
it's
in
the
face
where
people
are
some
pinning
services
are
actively
start
like
actively
started
implementing
this
api,
so
the
spec
is
at
the
link.
A
I've
posted
in
the
notes
there's
like
a
little
bit
more
context
on
the
pin
life
cycle
and
overall,
the
way
we
present
api,
it's
probably
much
better
than
it
was
before
you're
now
able
to
through
your
traverse
data
structures,
for
example
like
here.
If
you
query
for
multiple
results,
you
can
see
that
there's
like
array
of
results
and
each
object
is
pin
status
object,
and
then
you
got
a
pin
object
here
with
the
pcid,
that's
actually
pinned.
A
So
it
should
be
easier
to
learn
by
exploration.
Using
this
and
just
to
quickly
note.
We
started
gathering
some
feedback
from
pinning
services
which
will
be
implementing
this,
and
there
are
two
open
pull
requests
to
make
changes
to
the
api.
A
The
pin
request
enters
the
pinning
service
and
that's
important
for
multiple
reasons,
one
it
make
it
easier
for
users
to
find
pins
which
are
recent
and,
more
importantly,
it
makes
pagination
more
deterministic.
Now,
when
results
are
sorted
by
the
creation
date,
it's
more
it's
easier
to
traverse
a
huge
pin
sets
with
thousands
of
pins
without
skipping
anything.
A
Also,
we
remove
the
manual
offset
parameter,
which
was
in
the
place
of
time-based
parameters.
So
if
anyone
is
interested
on
this
change,
please
provide
feedback
on
the
pr.
We
probably
will
merge
it
around
wednesday
unless
there
are
like
some
concerns
which
needs
to
be
addressed,
and
the
second
open
issue
is
simplifying
access,
token
spec.
So
so
far
we
supported
both
http
header
and
query
parameter,
and
this
pull
request
simplifies
the
that
and
we
will
only
have
http
header.
So
those
are
two
pending
changes.
A
They
don't
really
change
much
how
the
api
works,
but
are
directly
addressing
feedback.
We've
got
so
far
from
implementers
yeah.
So
that's
on
the
on
the
api
spec
site
work
on
the
go
ipfs
site
to
implement
client
for
this
started.
We
are
in
the
planning
phase.
Probably
we'll
have
some
updates
next
time.
A
I
don't
think
so
all
right,
I
kept
my
screen
sharing
because
there's
a
bounty
which
is
pretty
pretty
cool.
I
wanted
to
mention
that
those
improvements
are
coming,
so
we
got
a
contribution
with
directory
page
the
directory
listing
page
improvements
and
long
story
short.
The
improvements
are.
A
Yeah
yep,
so
the
breadcrumbs
are
now
clickable.
You
can
jump
to
the
arbitrary
level
of
the
path
and
there's
a
column
with
c
ids.
Here
I
believe,
that's
it.
I
wanted
to.
C
A
So
and
a
lot
of
improvements
happen
behind
the
scenes,
just
jessica
made
it
much
less
painful
to
maintain
this
module,
which
is
responsible
for
rendering
directory
listing.
I
I
looked
at
it
and
we
may
be
able
to
improve
it
even
further,
but
I
did
not
want
to
like
totally
entire
like
block
that
the
bounty
yeah,
probably
after
that
bounty
is
merged.
A
We
may
move
away
from
the
git
sub
module,
which
is
like
right
now.
That's
just
like
sub
module
in
go
ipfs
repo,
which
it's
no
longer
necessary.
It
was
like
necessary
due
to
like
legacy
reasons,
but
now
we
could
make
it
just
a
regular
go
module
which
should
make
things
easier
for
everyone
yeah.
So
that's
coming
to
probably
I
want
to
squeeze
that
into
go
ipfs
0.7,
hopefully
in
both
guys,
you
first
and
iphone's
desktop
at
some
point.
E
That
also
includes
like
the
favicon
and
stuff,
which
did
not
make
it
into
go
ipfs,
so
you're
actually
getting
the
previous
generation
of
changes.
If
we
can
get
that
in
as
well,
yeah
yeah.
A
Yeah,
the
problem
is:
that's
the
problem
with
sub
module.
It's
unless
someone
is
bumping,
the
sub
module
and
committing
that
and
after
the
committing
that
regenerates,
like
the
binary
data
for
directory
listing,
the
change
will
not
be
populated.
So
that's
super
painful
and
easy
to
yeah.
E
A
Yeah
cool
fun
times
will
land
at
some
point.
Hopefully
yeah
directly.
Do
you
want
to
talk
about
ipf's.
D
D
Yeah
so
alex
landed
a
patch
to
fix
a
buffering
problem
that
was
happening
in
the
js
ipfs.
D
So
now
that
is
there,
you
can
update
stuff
on
the
web
ui
to
take
advantage
of
it,
but
it
ended
up
being
a
cascade
of
things
that
need
to
happen
so
right
now
I
have
a
pull
request
to
rip
out
the
redux
bundle.
Ips
redux
bundle
that
comes
with
its
own
ipvs,
which
is
also
old
and
honestly,
doesn't
really
do
does
much.
D
Instead,
however,
I'm
having
some
problems
with
testing
and
I'm
not
exactly
sure,
what's
going
on
there
yet
I'll,
once
I'll
figure
out,
hopefully
we
can
land
this
once
this
is
in
then
I'll
actually
upgrade
ipfs
to
the
new
one,
but
there's
a
little
bit
of
work
to
be
done
in
terms
of,
I
think
it's
on
an
older
version
with
a
different
ipfs
api,
so
every
place
we
use
ips
needs
to
update
it,
be
updated
to
use
a
new
api
once
that's
done
as
well.
D
Then
I
can
update
the
pull
request
that
I
wrote
originally
to
do
the
web
ui
patch
to
do
the
uploading,
because
there's
also
buffering
happening
in
the
web
ui,
so
we'll
have
to
remove
that
too,
and
now
we'll
go
to
new
ipfs
once
that
is
done,
I'll
write
a
patch
for
the
http
client,
because
right
now
it
uses
a
fetch
api
that
doesn't
provide
any
progress.
D
Upgrades
updates
at
all
so
I'll
be
switching
that
to
xml
http
requests,
which
does
have
a
progress
events,
and
so
once
that
is
done,
then
we
can
update
web
ui
to
integrate
source
events.
So
we
can
render
the
progress
bar
on
file
uploads
the
reason
those
are
separate
tasks,
so
we
can
like
parallelize.
Hopefully
some
of
it.
A
A
D
I
was
trying
to
avoid
updating
ipfs
without
changing
the
api.
Maybe
I
can
combine
those
two
patches
into
one.
D
D
Well,
maybe
then
one
of
you
can
review
the
pull
request
that
is
linked
in
the
notes
and
if
you
can
land
it
without
that,
I
I
can
also,
I
guess,
do
another
patch
on
top
of
it
that
will
upgrade
ipfs,
so
hopefully
at
least
that
way
we
can
test
it.
D
D
I
noticed
that
my
pull
request
didn't
run
anything
so
maybe
we
should
enable
it
somewhere.
Okay,.
G
A
That's
all
on
my
own
yeah,
this
endeavor
to
upgrade
to
the
latest
js
api
like
programmatic
js
api,
which
which
you
will
be
doing
in
web
ui.
Actually,
I've
hit
a
similar
problem
with
companion,
which
is
using
the
old
one
and
there's
another
issue
on
the
agenda,
which
is
sekaio
deprecation.
I
believe
like
in
go
ipfs
0.7.
A
It
will
be
either
like
removed
or
disabled
by
default,
and
the
problem
is
we
use
and
like
in
brave,
you
can
opt
in
to
embed
js
ipfs
and
that
js
ipfs
has
access
to
tcp
sockets
and
due
to
that
fact,
it
actually
can
connect
to
appears
which
announced
themselves
on
the
dht.
So
we
enable
delegated
peer
and
content
routing
modules
from
the
p2p,
okay
and
long
story
short.
A
No,
no,
it's
like
the
brave
it's
using
yeah,
a
brave
is
using
our
public
delegated
notes,
which
are
also
preload
nodes
for
like
delegated
dht
effectively.
A
Okay
and
the
problem
is
that
relies
on
a
browser,
node
being
connected
to
delegate
node
the
moment
it
executes
that
call
and
right
now
those
connections
are
handled
over
secaio.
I
believe,
okay,
so
that
may
be
a
problem
when
and
and
also
when
it
tries
to
connect
to
remote
peer.
That
appear
is
probably
go
ipfs.
A
So
when
go
ipfs
0.7
ships,
that
means
js
ipfs
nodes,
which
are
older,
like
the
one
in
brave,
won't
be
able
to
connect
to
go
ipfs.
So
that's
just
I
mentioned
it
because
the
plan
is
to
ship
go
ipfs
0.7
like
around
the
end
of
august
and
wish
we.
We
should
like
finish
this
migration
before
that
happens.
To
avoid
that
sorry
I
mean
so
which
migration
just
general
migration
of
embedded.
E
A
In
brave
it's
a
part
of
companion,
there's
like
open
pr,
I
only
mention
it
in
case
someone
is
running
like
go
ipfs
from
master
or
using
the
release
candidate,
and
they
experience
problems
with
that
work
with
connecting
to
that,
that's
why
it's
because
sakaio
is
no
longer
a
thing:
js
ip,
like
entire
jsr
system,
jsl
p2p,
is
switching
to
noise.
A
I
believe,
and
and
there's
a
discussion
about
like
enabling
nose
noise
in
older
versions,
but
the
threshold
of
up
to
which
all
the
version
is
possible
is
the
moment
we
switch
to
this
new
api.
So
you
need
to
use
this
new
api
where
there
are
like
asking
iterators
and
stuff
to
leverage
noise
that
so
far,
there
are
no
plans
to
backboard
it
to
the
older
versions.
A
A
I
believe
yeah,
I
believe
it's
only
related
to
companion
and
specifically
to
companion
in
brave.
I
looked
all
over
like
all
the
other
places
in
our
gui
applications
and
and
stuck,
and
we
don't
like
it,
we
are
not
impacted.
That's
the
only
like
overlap
with
this
problem.
Got
it.
Okay,.
A
E
Don't
I
don't
have
it
on
my
local,
you
want
to
give
me
a
minute
I'll
bring
it
watch
it,
but
I
don't
have
it
running
right
now.
I
can
walk
you
through
the
screenshots
on
the
ps4.
C
E
Okay
cool,
so
basically,
what
this
is
doing
is
this
started
out
is
needing
to
give
us
somewhere
to
launch
the
welcome
screen
from
and
then
after
conversations,
I
believe,
with
raphael.
A
little
while
ago
we
talked
about
the
expand
collapse,
functionality
and
the
nav
are
just
like
really
being
kind
of
pointless.
E
So
what
this
pr
does
is
really
streamlines
the
nav
bar
at
both
widths
and
also
gives
us
an
affordance
something
that
we
can
click
on
to
launch
the
welcome
screen
content
that
we
want
to
handle
in
1463,
which
will
be
instrumental
to
onboarding
new
users.
So
this
is
what
it
looks
like
at
desktop
with.
E
Basically,
it
brings
the
text
underneath
gives
adds
a
little
bit
of
vertical
space,
but
not
a
whole
whole
lot
just
tightens
up
the
whole
thing.
Overall,
this
cube
is
no
longer
clickable
to
expand
collapse,
the
that
nav
bar,
but
it
does
take
you
to
the
welcome
screen
which,
right
now,
you
never
ever
see,
except
on
first
launch.
E
This
is
how
it
looks
on
mobile.
The
nice
thing
about
mobile
is
this
actually
gives
us
less
side-by-side,
scroll
and
narrow
widths
in
that
menu
raphael.
I
think
you're,
okay
with
it
lyle,
I
think
you've
had
a
quick
look,
but
I
would
appreciate
a
final
review
for
you
before
I
make
it
real.
A
I
tested
it
on
my
setup,
which
is
useful
because
I
have
a
non-standard
phone
setup,
so
yeah,
okay
and
it
looks
fine.
So
that's.
A
The
only
the
nuance
is
that
I'm
not
sure
if
I
commented
it
or
was
about
to
comment
in
a
review,
but
the
welcome
screen
you
mentioned
yes,
I
realized
you
can
get.
I
think
you
can
get
to
that
screen
by
clicking
the
top
right
corner.
There's
this
like
connection.
A
But
I
think
it's
fine,
it's
even
like
better,
because
intuitively
when
you
click
on
the
the
cube
you
want
to
sort
of,
like
maybe
switch
to
different
cube
items.
E
It's
also
consistent
with
what
we're
doing
in
companion
I
just
want
to.
I
want
to
get
started
on
that
welcome
screen,
because
I'm
not
entirely
sure
what
needs
to
go
in
there
at
this
point
and
then
also
we'll
want
to
make
changes.
Some
of
that
content
appears
in
other
locations
like
if
you
have
on
the
files
page
when
you
don't
have
any
files,
so
that's
that's
probably
going
to
take
a
little
bit
longer
than
I
would
think
so.
A
Yeah,
the
sort
of
like
the
the
main
use
so
far
like
the
the
origin
of
that
screen
was
what
happens
when
you
are,
if
a
offline
state
or
when
your
node
suddenly
goes
offline.
That
screen
that
welcome
page.
E
E
Yeah
and
it's
and
it's
sort
of
strange
because
you
end
up
in
that
situation,
where
it's
like
you
know,
do
you
of
course,
requests
enabled
and
then
over
on
the
right-hand
side,
it's
like
what
is
ipfs
and
so
that's
kind
of
some
mixed
messaging.
So
I
want
to
pull
apart.
Where
are
all
of
those,
and
I
believe,
there's
those
are
sort
of
componentized
to
agree
a
degree,
and
I
want
to
see
where
all
of
those
bits
appear
elsewhere
in
the
app
and
when.
A
Yeah,
oh
speaking,
about
components,
just
piggybacking
back
to
what
directly
mentioned
that
parts
of
web
ui
needs
to
be
refactored
to
the
new
api.
Ipv
ipld
explorer
is
a
separate
component,
it's
a
separate
npm
dependency
and
I
believe
it's
using
the
old
api,
I'm
not
sure
if
yeah,
if
the
dog
api
actually
changed.
So
that's
yeah
like
yet
another
layer
of
work,
but
we
can
discuss
that
separately.
I
guess.
B
A
No
like
we
recently
were
successful
with
releasing
new
ipld
explorer,
so
I
I'm
able
to
like
help
yeah.
Is
there
a
reason.
D
E
E
A
E
A
D
I
think
that's
what
creates
a
coordination
issue,
because
first,
this
needs
to
go
in
before
you
can
pull
it
in
here
and
then,
like
you,
end
up
stacking
things
up,
but
if
it's
in
one
place,
then
you
can
send
them,
even
if
they
are
released.
There's
separate
packages.
A
Yeah
it
honestly,
it
makes
sense
to
think
about
this,
maybe
like
mid-term
long
term,
because
we
have.
E
A
Is
one
thing
we
also
got
this
cid
that
ipfs
io
website,
which
is
separate?
We
got
like
a
dag
or
files,
one
which
is
not
advertised
much,
but
those
things
could
be
part
of
web
ui
like
one
big
repo.
They
could
be
also
separate
websites,
but
having
something
like
like
js
ipfs
would
be
much
easier
like
much
better
experience
than
right
now
and
there's
this
problem.
A
We
have
right
now,
especially
with
those
things
which
require
like
which
operate
on
lower
level,
primitives
like
cids
or
multihashes
or
multicodex,
when
we
add
something
new
the
time
it
takes
to
bubble
up
to
that
end,
product
that
website
or
that
component
is
payfully
long
and
you
need
to
make
sure
it's
bubbled
up
to
all
of
them.
So
if
we
had
like
one
central
place,
it
would
remove
the
friction.
A
A
And
it
was
extremely
problematic
in
case
of
ipld
explorer
because
you
could
have
on
the
website
it's
pounding
its
own
embedded.js
ipfs,
and
that
could
be
a
different
version
of
api
than
the
one
in
web
ui,
where
you
have
http
client
yeah.
A
Cool
so
we'll
review
the
navbar
promise.
D
E
Yeah,
it's
a
left
right
scroll,
there's,
not
a
more
elegant
way
of
doing
that
without
ripping
it
out
entirely,
which
is
on
my
longer
term
agenda.
But
but
at
least
there's
far
less
side-by-side
scroll
than
there
was.
D
Another
question
is:
how
do
you
actually
use
webbian
mobile
is
that's.
E
C
D
A
Don't
know
well
if
you
load
it
from
that
remote
origin,
that
origin
is
oh.
D
D
A
But
honestly
there
there
are
for
android,
there
are
distributions
of
ipfs.
I
think
it
one
is
called
suite
ipfs
another
one
is
like
ipfs
droid
and
you
are
effectively
running,
go
ipfs
on
your
phone
and
then
you
are
on
the
local
host.
So
you
just
open
that
local
host
page,
that's
what
I
was
using
for.
I
was
using
that
local
node,
with
firefox
for
android,
which
was
running
regular
extension
and
companion,
was
connecting
to
to
the
note
on
my
phone
and
that
worked.
E
And
just
raphael,
yeah
good
point
about
hamburger
menu
or
some
similar
thing.
This
is
sort
of
like
trend,
this
fine
line
because
we've
got.
We
have
a
bunch
of
concept
sketches
for
desktop
and
web
ui
in
general.
E
That,
at
this
point,
are
about
a
year
old
that
came
from
eric
ronnie,
which
need
to
be
like
a
lot
of
stuff
has
changed
since
then,
and
our
understanding
of
we're
trying
to
solve
for
has
changed
since
then
there's
a
lot
of
really
good
kernels
of
truth
in
there,
and
that
is
on
at
least
my
longer
term
agenda
to
try
to
unify
some
of
that
into
a
more
complete
design.
E
G
C
Yeah,
so
I've
merged
everything
to
epic,
slash,
pinning
integration,
and
we
already
have
all
the
models
for
adding
new
integrations
and
custom
integrations
and
showing
the
integrations.
What
we
need
to
do
now
is
the
screen
for
editing
that
integration
and
also
the
pop-up
for
deleting
the
integration,
I'm
not
entirely
sure.
If
we
have
the
edit
integration
screen,
do
we
jessica?
C
G
E
C
A
C
A
Here's
the
thing:
what
the
current
security
model
when
it
comes
to
secrets
in
go
ipfs,
config
and
accessing
that
over
http
api
is
that
you
can
send
you
can
like
set
value.
You
can
overwrite
existing
value,
but
once
you
set
it
it's
impossible
to
read
it
back
over
http
api.
A
So
that
means
you
can
like
display
those
like
asterisks
and
if
you
submit
a
change
with
just
like
name
or
endpoint,
that
will
not
change
the
api
key.
But
the
moment
you
change
api
key
that
will
override
it.
User
won't
see
the
the
api
key
anyway
because
it
would
should
be
like.
C
C
E
I
mean
that's,
that's
the
same.
That's
the
same
mental
pattern
that
we
experience
every
single
time.
We
go
to
a
config
page
for
service,
for
which
we
don't
actually
remember
our
passwords,
for
so
we
don't
even
run
our
mouse
over
the
password
box
with
its
little
dots
in
it.
So
I
mean,
I
think,
that's
would
be
completely
acceptable.
G
A
Yeah
yeah,
so
that's
like
a
low
level
concern.
I
still
we
still
don't
have
a
good
picture
of
how
exact
mappings
will
look
like
but
yeah.
So
hopefully,
next
time
we
will
see
something.
C
A
Hopefully,
we'll
get
some
eta
like
this
week
or
next
week,
where
we,
when
we
will
have
the
actual
api
and
we'll
make
a
decision,
is
it
worth
like
creating
a
mock-up
service
or
before
that
lands,
because
we
don't
want
to
be
blocked
by
that
fact
and
we'll
need
something
to
interact
with
and
test
in,
go
ipfs
and
jsfpfs
as
well.
D
I
had
a
question
that
I
forgot
to
ask:
how
well
is
web
ui
tested?
Should
I
be
worried
in
terms
of
when
I
updated
new
ipfs
api?
Should
I
like
go
and
try
to
break
it
or
is
test
supposedly
gonna
catch
that
I'm.
A
Pretty
sure
the
tests
are,
we
got
like
a
canary
test
for
each
screen,
so
on
for
the
status
screen,
we
expect
the
peer
id
to
be
there.
That
means
you
are
able
to
fetch
the
id
information
over
api
same
for
files.
We
try
to
add
a
file
and
then
confirm
it's
added
to
the
listing,
similarly
to
the
peer
screen
and
to
settings
so
there's
a
canary
test
for
each
screen
and
that
test
runs
in
actual
browser.
We
use
puppeteering
and
chromium.
A
So
as
long
as
like
end-to-end
tests
pass,
I
would
not
worry
if
some
tests
fail.
It
may
be
because
like
structures
changed
and
the
test
expects
something
else,
but
if
they
pass
it
should
be
fine
yeah
and
if
you
have
any
problems
with
end-to-end
ping
me
because
I
recently
fixed
them.
So
I
have
a
fresh.
D
A
Oh
yeah
yeah,
it's
possible,
it's
possible
that
we
use
http
client
internally
for
orchestrating
notes
as
well.
There's
this
tool
called
ipfsd
control,
which
was
created
by
hugo
and
older
versions,
who
it's
possible
that
all
the
versions
depend
on
http
client
which
used
ky.
So
that's
why
you
see
that?
A
D
A
D
D
A
Yeah,
I
think
I
could
definitely
can
take
a
look
it's
on
the
is
the
pr
with
removing
redux
bundle
right.
A
Cool
always
yeah
highlights,
I
think
we
are
at
the
end
of
the
agenda.
So
we
are
super
efficient.
This
week
highlights
are
ipfs,
companion,
battleships
and
I
will
screen
my
screen
share.
My
screen
now.
A
This
long
version
number
means
a
new
beta
release
and
this
new,
better
release
improves
error
page
for
protocol
handling
in
firefox,
and
it
also
is
the
first
version
which
opens
release
notes
on
the
update.
So
now
users
will
see
what's
changed,
thanks
jessica,
for
improving
those
protocol
handler
screens.
A
So
now
a
user
gets
this
human
readable
error
page
which
lets
them
convert
cid
using
cid
inspector
or
command
line
and
fix
it.
And
now,
when
we
upgrade
to
a
new
version,
release
notes
are
displayed
to
tell
user.
What's
up,
what's
new,
that's
it
on
ipv's
companion,
oh
no.
We
got
rejected
from
chrome
web
store.
I
I
forgot
about
that.
E
A
Oh
yeah
totally,
I
think
I
got
this
here
yep,
so
it's
here
you
got
this
toggle
show
release
notes
on
update.
If
you
don't
want
them,
just
disable
them,
that's
it.
That
being
said,
you
can
make
a
release,
but
if
google
does
not
accept
it,
no
one
will
see
that
release.
So,
like
a
week
ago,
we
got
rejected
with
vague,
automated
response.
A
I
suspected
it
was
before
because
of
this
white
space.
But
honestly
we
never
changed
it
and
we
had
multiple
releases
with
it.
With
this
so
turns
out.
It
was
like
internal
mistake
on
the
google
part,
which
is
a
bit
concerning,
because
we've
got
a
browser
extension
and
for
some
reason
it's
suddenly
taken
down.
The
good
thing
is
that
we
got
a
better
channel
which
is
a
separate
extension.
It's
a
separate
destination
id.
So
what
I
do
I
make
a
better
release.
A
A
A
C
A
Background
here
is
that
we
have
like
multiple
places
where
we
would
like
to
have
a
some
sort
of
like
a
progress
indicator.
Personally,
I
I
found
a
way
for,
like
companion
to
this
temporally
display
a
page
sort
of
like
a
splash
screen
when
people
try
to
load
the
content
which
not,
which
is
not
on
their
local
note
and
needs
to
be
like
looked
up
over
dht,
which
may
take
a
few
seconds
or
sometimes
a
few
minutes,
so
we
could
introduce
sort
of
like
a
loading
page.
A
So
this
animation
is
pretty
useful
for
something
like
that.
Yeah.
C
E
C
D
E
C
A
All
right,
folks,
I
think
it's
we
are
at
the
end
of
highlights
and
I
don't
see
any
additional
agenda
items,
so
I
will
stop
the
recording
now.
Thank
you
for
watching
this.
If
you
are
watching
this
or
listening
to
this
and
see
you
hear
you
in
two
weeks,
alright,
bye.