►
From YouTube: IPFS All Hands 🙌🏽 📞 Feb 19, 2018
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
C
C
C
D
This
will
be
decision.
Airily
done.
We
are
finalizing
some
permission-based
user
interface
and
we
will
probably
have
a
better
ID
with
all
all
security
related
fixes
to
that
version.
That
is
in
the
master
branch
is
functional,
but
it
does
not
solve
all
security
issues,
so
you
can
experiment
with
that,
but
it's
not
safe
to
use.
Yet
that's,
but
that's
all
from
my
end.
There
are
no
questions.
D
No,
we
like
the
window
EFS
is
something
that
will
all
be
present
on
every
webpage
after
you
install
our
browser
extension
browser
extension
is
called
a
TFS
companion.
So
what
we
decided
is
that
if
you
have
ipfs
companion
installed,
you
will
have
this
object
on
every
webpage.
It's
like
extension
of
your
browser
engine.
F
All
right
with
your
other
questions,
Johnny
yeah,
so
just
the
security
concerns,
so
this
is
actresses
of
using
a
proxy
to
your
running,
go
ipfs
or
JIS
ipfs
instances.
So
it's
not
its
own
instance
of
an
IP
FS.
So
the
key
management
is
stored
in
either
chrome,
sandbox
and
so
exec
being
encrypted
and
for
runtime
and
like
a
secure,
vault.
Well,.
D
Like
right
now,
it's
like
you
have
this
browser
an
extension
and
this
browser
extension
will
be
able
to
ship
its
own
JSI
PFS
note,
or
you
can
set
up
here
this
browser
extension
to
connect
to
external
node
and
right
now
we
assume
the
access
to
the.
There
is
no
access
control
when
it
comes
when
between
browser
extension
and
your
note,
if
you
like,
set
up
some
kind
of
basic
alpha
or
stuff
like
that,
maybe
that
will
work.
But
right
now
we
don't
have
any
key
key
based
access
control
for
node.
C
G
I,
like
a
simple
explanation,
would
be
how
the
geolocation
permissions
in
the
browser
work
trail
or
the
microphone
where
you
navigate
to
a
page,
and
they
try
to
use
like
the
effort
from
the
browser
extension
and
you
never
used
it
before.
There
will
be
a
little
pop-up
request,
your
permission
to
use
files,
add
or
whatever
so
nothing
is
handled
by.
The
actual
extension
is
just
a
proxy
with
like
a
tiny,
ACL
layer
tied
to
the
origin
of
the
website.
D
D
Right
now,
if
there
is
an
X
okay,
so
when
it
comes
to
window
ipfs,
it's
just
there.
So
if
you
have
a
extend
other
browser
extension
that
can
inject
content
scripts
into
web
pages,
it
will
just
have
access
to
window
ipfs
and
it
will
be
able
to
execute
JavaScript
against
that.
That's
one
of
the
reasons
why
we
have
access
control
to
that.
This
is
purely
based
on
the
content
scripts.
D
C
D
F
Just
can
you
run
multiple
proxies,
one
for
let's
say
public,
IP,
FS
and
then
one
for
a
private
one.
At
the
same
time,.
C
B
A
kind
reminder
this
Wednesday:
we
will
test
the
webinar
picture
of
zoom
and
it's
the
feature
that
will
enable
us
to
livestream
to
YouTube
and
get
the
recording
there
automatically
without
having
to
do
this.
All
of
these
extracts
in
the
beginning
of
the
call
right
now
we
have
four
people
that
volunteered
to
test
it
with
me.
B
C
H
Yeah
I
just
threw
that
in
there
really
quickly,
because
if
I
remember
correctly,
the
part
of
the
purpose
of
the
conference
test
and
the
streaming
to
YouTube
was
more
inclusiveness
in
this
call
and
I
was
kind
of
tasked
with
creating
possible
action
items
were
evolving.
This
call
to
be
more
inclusive,
which
I
think
might
be
across
purposes
with
the
Sprint
meetings,
so
I'm,
essentially
proposing
creating
a
new
call
for
new
comers
new
ideas,
just
something
more
comfortable
for
new
people
to
throw
in
rather
than
going
all
through.
These
existing
sprint
bullet
points.
C
H
C
Alright,
would
you
be
able
to
I'm
trying
to
I'm
so
I'm,
trying
to
listen
to
you
and
read
your
proposal
at
the
same
time?
Is
there,
are
you
so
are
you
proposing
to
have
a
discussion
about
how
it
should
be
structured?
Are
you
are
you
proposing
that
we
have
some
sort
of
discussion
on
github
about
a
completely
different
structure,
for
these
calls
yeah.
H
H
F
Johnny,
how
it
just
takes
some
of
the
items
on
discourse
and
actually
just
have
a
webinar
to
actually
to
walk
through
them,
and
so
that
it's
not
burning
the
All
Hands
call,
but
actually
like
it's
meaningful
dialogue
about
the
top
issues
that
are
coming
up
on
discourse,
whether
it
be
introduction
to
ipfs
what
is
a
dag
and
just
to
roll
through
and
actually
have
video
documentation
of
of
those
items.
In
this
course.
F
I
find
discourse
like
just
it's
just
a
whole
bunch
of
stuff
that
and
I
not
very
useful,
but
I
think
I'm
very
much.
A
visual
learner
and
I
like
to
see
examples
and
I
think
it.
It
allows
to
kill
two
birds
with
one
stone
which
is
actually
have
a
generalized
discussion.
I'm
a
high
PFS,
not
burning
the
all-hands
contributors,
but
actually
it
has
bringing
in
a
community
with
watching
videos
and
the
yet
at
the
same
time,
tackling
those
those
items
on
discourse.
C
You
know
I,
like
that
proposal.
I'm
also
wondering
so
it's
like
there's
that
and
open
discussion
and
then
there's
time
for
demos
and
then
there's
time
for
the
teams
to
coordinate
and
I
agree
that
breaking
it
out
might
make
sense
and
so
that
each
of
them
it
doesn't
really
influence
the
time
commitment
of
the
others.
C
C
If
anyone
else
has
ideas
right
now
that
you
want
to
kick
out
that
the
jury
could
add
to
that
issue
or
sort
of
folding
as
comments
go
ahead
and
speak
up,
okay,
great!
Well,
then
I,
look
forward
to
seeing
that
that
that
item
evolving
cuz
you're,
definitely
right
that
it's
a
little
bit
murky
of
like
what
is
this
specific
call
for
and
if
we
shorten
it
to
30
minutes
what
is
getting
cut
out
and
what
is
being
included.
C
B
This
quick
announcement
there
will
be
yes,
I,
think
that's
wheelies
coming
up.
Hopefully
this
week
you
can
see
the
link
to
the
issue.
Yeah,
there's
a
really
a
lot
of
stuff,
like
that.
The
last
view
is
was
in
January
16,
so
one
month,
and
there
was
new
things
added
to
repute
appear,
which
is
a
relative
Josiah
things
added
to
IPL,
be
that
house
are
available
to
Jessica
first,
and
also
a
lot
of
things
that
you
just
said.
You
can
sort
of
bug
fixes
a
lot
of
dogs.
B
What's
off,
improve
with
examples,
as
usual,
I
will
create
that
iolite
section.
It
just
takes
some
time
to
write
and
so
right
now
you
have
the
issue
and
you
like
the
release
checklist.
Doing
it's
like
you'll,
see
the
authorites
and
yeah
if
you
are
using
just
activist
and
if
you
have
a
batch
of
tests
that
we
can
easily
try
them
like
just
keep
calm
the
repo
and
p.m.
B
link
the
way
this
just
a
profess
and
run
a
test
and
see
if
something
breaks,
let
me
know,
because
I
would
love
to
test
your
app
and
help
you
migrate
to
the
new
ipfs
or
even
understanding
if
we
broke
something
that
we
didn't
intend
to.
There
were
some
minor
changes
and
nothing
on
the
main
epi,
mostly
on
the
lip,
up1
and
yeah.
That's
it.
I
J
I
So
I
just
wanted
to
ask
not
not
necessarily
a
proposal,
but
has
anybody
here
tried
before
since
I
haven't
been
around
that
long
having
some
sort
of
regular
like
few
hour,
two
or
three
lon
like
office
hours
sort
of
time?
This
is
very
like
beginner-friendly
like
sign
on
and
ask
questions
and
we'll
have
one
or
two
like
people
who
go
I'd.
I
This
is
all
about
making
it
work
as
opposed
to
like
getting
to
use
it
so
like
and
I
do
this
like
have
a
different
call
as
this
sort
of
sense
of
like
what's
the
more
beginner
new
people
to
the
community,
welcome
open
space
and
I
think
a
lot
of
that
revolves
around
not
being
so
in
it
in
all
the
minutiae
about
what
happens
here,
but
like
big
picture
like
been
uncomfortable
in
the
community
and
then
maybe
showing
up
to
office
hours
like
help,
explain
to
other
people
or
whatever.
So
just
a
thought.
B
Well,
from
the
beginning
of
the
project,
we
definitely
tried
multiple
versions
of
office
hours
in
the
beginning.
It
was
all
IRC
we
didn't
even
have
calls
and
like
we
were
available
from
a
period
of
time.
Every
day,
that's
like
we
were
like
just
thing:
lots
of
attention
to
IRC
and
people
would
come
and
ask
questions.
Well,
there
see
channel
now.
I
was
like
more
than
thousand
people
and
make
it
really
hard
to
have
discussions
there.
B
And
so
then
we
jump
into
calls
and
we
have
calls
per
project
and
they
were
brought
like
PM
calls
but
and
answered
questions
calls,
and
then
it
evolved
to
this
type
of
call
that
we
have
right
now
we
try
to
have
office
hours
again
and
and
I
think.
The
reason
why
we
stopped
was
not
because
they
were
not
useful.
B
B
It
is
just
like
hard
to
keep
everyone
in
check,
making
sure
that
office
hours
happen
and
that
they
are
productive
and
that
they
are
well
communicated
and
that
there
is
notes
with,
like
those
ask
questions,
etc,
etc,
etc,
and
so
if
people
want
to
like
try
it
again,
I'll
definitely
be
really
help
to
try
it
again.
Probably
this
time
with
a
little
bit
more
explicit
department
than
the
previous
ones.
B
C
K
Like
looking
added,
also
one
on
a
one-on-one
time
with
developers
and
so
on,
is
very,
very
useful,
but
I
think
there
should
be
added
benefit
to
rest
of
the
community,
because
this
hour
to
that
developer,
spends
literally
like
creating
ad
hoc
documentation,
for
someone
could
be
spent
at
the
same
time
creating
this
documentation
for
everyone.
So
some
approach,
like
like
quick
like
at
the
same
time,
creating
the
documentation
that
is
being
transferred
by
call
and
creating
an
F
form
that
allows
others
to
also
use.
It
would
be
also
quick.
C
Yeah
I
guess
that
was
that
would
come
back
to
the
proposal
of
the
Johnnies
proposal
of
basically
picking
plucking
things
from
discourse
and
telling
people
in
advance
we're
going
to
talk
about
this
topic
this
week
and
answer.
Then
people
who
are
interested
in
that
topic
know
that
it's
going
to
be
discussed.
They
join
in.
We
know
that,
like
there's
a
framing
around
that
recording
of
it's
a
discussion
of
that
topic,
you
can
add
a
link
to
it
from
that
discourse
issue
so
that,
rather
than
it
being
entirely
unstructured
of
just
show
up
at
this
time.
C
If
you
have
questions,
but
then
that
takes
then
there's
a
curatorial
overhead
of
choosing
what's
a
feature
and
scheduling
it
and
telling
everyone
that
is
scheduled
and
all
of
that,
so
we
would
have
to
make
sure
to
make
provisions
for
doing
all
right.
We
did.
Could
we
defer
that
discussion
to
the
github
issue?
Yes,.
C
C
Okay,
so
last
week,
I
showed
everyone
how
we're
doing
these
scores
that
well,
let's
look
at
the
core
working
groups
sheet.
C
First,
so
core
working
group
set
a
bunch
of
a
bunch
of
objectives
and
a
bunch
of
key
results
that
measure
whether
they're
making
progress
for
those
towards
those
objectives,
and
then
we
rank
them
by
priority
p0
being
the
highest
priority
before
bidding
the
lowest
every
K
R
has
an
owner,
and
then
what
we
did
this
last
week
is
that
we
set
so
for
mine
for
this
first,
one
I
think
I've
done
about
a
third
of
the
work
towards
actually
hitting
this
key
result
and
I
think
that
I'm
projecting,
even
though
we're
halfway
through
the
full
court
I'm
projecting
that
by
the
end
of
the
quarter,
I'll
have
this
done
so
I'm
projecting
a
one
out
on
it.
C
Even
though
I've
only
done
a
third
of
the
work
right
now.
So
that's
what
everyone
has
done
with
all
of
their
K
ours,
they've,
put
in
how
much
work
have
I
done
up
to
now
and
how
much
do
I
think
will
be
done
at
the
end
of
the
quarter
on
this
particular
key
result,
and
so
we
have
lots
and
lots
of
working
groups
and
lots
and
lots
of
chaos.
One
of
the
things
that
we're
learning
is.
C
Ideally,
you
should
only
have
like
three
objectives
for
each
of
these
sheets.
For
each
of
these
working
groups
and
within
each
of
those
objectives,
there
should
only
be
like
a
maximum
of
four
K
hours.
It
should
be
like
three
or
four
K.
Ours
maybe
finds
weird.
If
you
can
look
through
these
sheets,
some
of
the
K
ours,
as
some
of
the
groups
have
like
lots
and
lots
of
chaos
under
an
individual
objective,
and
we
just
sort
of
let
that
happen.
We
said
you
know
we're
learning
something
new.
This
is
it's
a
new
skill.
C
It's
a
new
thing,
we're
trying
it
out.
So
we've
left
left
room
for
how
people
that
have
a
lot
of
noise
and
use
sheets
but,
as
a
result,
makes
a
little
bit
hard
to
read
unless
you're
really
involved
in
the
work
of
that
that
particular
group.
So
we
have
this
one
sheet
that
gives
you
sort
of
bubbled
up
version.
Just
shows
you
the
objectives
for
each
of
the
working
groups
and
I've
extended
that
to
show
you
what
their
scores
are.
So
I
can
report
back
from
the
core
working
group.
C
This
is
basically
the
tech
leads,
plus
one
plus
me
I,
and
it's
more
figuring
out
the
overall
structure-
and
you
could
say
the
essential
thing
we're
focusing
on
is-
is
giving
clarity
to
what
is
this
structure
for
working
groups?
How
do
working
groups
form?
How
do
they
dissolve?
How
do
they,
what
are
their
responsibilities
and
I've
been
working
on
an
art
of
c2?
For
that
proposes
that,
and
actually,
if
you
go
to
ipfs
/r
se,
that
in
that
github
repo,
you
can
see
that
stuff
evolving.
C
C
B
I'll
do
just
any
fess
is
a
little
bit
like
Charlotte
cross,
also
just
sweep
it
appear
and
just
like
you'll
be
the
the
objectives.
The
primary
objectives
for
Jessica
Frances
quarter
were
really
growing
the
team
and
if
people
dedicated
to
the
most
pressing
issues
like
things
like
HP,
more
people
on
relay
and
so
on
and
Matt,
if
you
don't
mind
like
just
switching
the
tabs
or.
B
Energy
is
progressing
quite
nicely
like
this
row
has
been
doing
a
great
job,
just
like
owning
that
circuit
really
Dimitri
has
been
exposing
last-mile
issues.
Lots
of
bug,
fixes
everywhere
and
yeah
I've
been
also
working
on
refactoring
would
appear.
There
is
an
issue
on
just
a
few
degree
call
with
review
next
that
lists
all
the
issues
that
are
happening
there
for
the
IPL
be
part.
B
L
B
And
two
new
formats
were
added
to
just
a
plv
length,
Bitcoin
empty
cash.
So
right
now,
I
believe
we
have
full
feature
authority.
We
IPL
the
ingo
with
I,
guess
the
difference
being
that
we
have
the
back
API
available
for
people
straight
up
and
so
yeah.
What
there
will
be
an
example
that
Volker
is
working
on
or
and
I
played
an
example,
so
that
people
can
like
check
this
out
themselves
and
I.
B
Think
this.
Is
it
there's
a
lot
of
work,
also
in
dynamic
data
and
Peter
isn't
around
but
Pedro,
like
so
dynamic
data
things
like
CR
DPS
there.
There
is
a
repo
for
this
working
group
that
has
a
lot
of
issues
with
current
research
problems
on
TR
d,
landscape,
things
like
garbage
collection,
snapshotting,
fast
sinks
and
so
on.
C
M
M
M
C
J
K
C
C
J
J
We
mostly
group
under
this
objective,
just
fixing
issues
doing
the
small
features,
stability,
improvements
and
another
of
testing.
The
testing
side
is
not
getting
dumb
too
much
so
far,
but
we
have
to
see
right.
It
depends
how
how
we
have.
We
do
the
large
files
thing
and
if
we
have
some
time
at
the
end
of
the
quarter,
we
probably
make
some
more
progress
there
and
then
I'm
done
below.
We
have
advanced
fault
tolerance.
J
J
J
J
The
cluster
team
will
be
growing
next
month
and
we
can
talk
about
that
next
month,
probably
and
welcome
adriaen
and
we're
still
looking
to
grown
the
governor.
This
idea,
first
side
of
things,
which
is
a
completely
separate
project,
but
the
main
a
stakeholder
there
right
now,
it's
cluster,
because
we
have
a
lot
of
cluster
tests
for
kubernetes
ipfs
and
the
last
objective
was
some
Simeone
collaboration
with
partners.
We
wanted
to
to
start
having
closer
collaborations
with
some
people
that
may
deploy
and
make
use
of
ipfs
cluster.
D
Yeah
yeah
so
like
for
the
first
part
of
this
quarter
in
browser
in
web
browsers
working
group
mostly
focused
on
the
first
one
and
I'd
say
third,
one
on
the
having
shared
understanding
of
how
IP
fest
should
work
in
web
browsers.
It
was
a
lot
of
prototyping
and
designing
design
related
work
done
by
Agatha,
and
at
this
stage
we
have
like
more
most
free
for
our
around
70%
ID,
say
of
the
design.
D
Work
is
done
by
Agatha
and
the
team
started
to
extracting
some
design
language
into
reusable
components
and
libraries
we
already
are
using
it
in
the
parts
of
companion.
Ipfs
desktop
is
totally
being
redesigned
using
this
common
visual
language.
So
that's
an
ongoing
work
will
continue
and
on
the
moving
towards
ipfs
working
seamlessly
in
web
browsers.
We
have
those
two
key
features
that
will
be
released
this
quarter
when
we
finish
solving
all
the
user
experience
issues.
D
Those
are
features
we
are
focusing
on
some
smaller
things
are
solved.
Some
new
things
have
priority,
so
we
may
be
able
to
close
some
stuff,
but
we
may
need
to
prepare
prioritize.
For
example,
mozilla
change,
the
way
they
publish
by
the
developer
channel,
which
to
be
exact,
they
are
shutting
it
down
and
we
have
to
figure
out
a
different
way
of
publishing
Bettis.
C
All
right
thanks
and
then
we
have
anyone
who
can
give
an
update
on
the
docs
and
education.
Oh
well,
okay,
there's
Lars
is
not
here
and
then
rob
has
been
doing
a
lot
of
work
on.
He
was
preparing
for
an
overhaul
in
from
of
the
information
architecture
of
our
documentation.
Those
are
the
main
updates
on
the
dachshund
education.
G
G
That's
as
much
as
I
know
about
the
infrastructure
stuff,
but
with
the
dev
team
enablement,
which
is
the
working
group
that
I'm
100%
on
the
plan
is
to
move
on
the
CIA
stuff
to
Jenkins.
So
we
can
run
a
chapter
and
we
can
build.
However,
we
want
with
with
whatever
we
want,
basically
more
flexibility.
It's
moving
forward.
We
almost
caught
it
fully
working
in
J's
ipfs
go
ipfs
is
missing
the
shortcuts
right
now
and
some
parsing
of
the
test
input
other
than
that.
We
have
bunch
of
projects
that
were
using
Jenkins
already.
G
So
it's
getting
are
then,
regarding
the
integration
testing,
Dimitri
has
been
doing
some
progress
on
the
Interop
repository,
so
we're
moving
forward
without
us
for
trying
to
make
it
a
bit
easier
to
write
the
test
and
to
maintain
the
past
as
well
with
the
developer
productivity,
which
is
the
board
ergative.
We
have.
We
me
I
haven't
done
too
much
on
it.
The
plan
was
to
have
more
time
to
focus
on
a
chair
and
to
make
sure
we
have
a
maintainer
there.
I
had
not
had
too
much
time
so
far,
but
I'm
getting
there.
G
The
most
work
have
been
on
setting
up
a
process
for
people
to
report
time
things
that
I
hope
will
be
ready
soon.
Then,
regarding
the
fifth
one,
the
plan
is
to
have
a
bit
better
maintenance
and
standard
from
module
creation.
Hath
not
came
very
further
either
and
might
not
have
much
time
left
to
work
on
this.
G
This
quarter,
but
they're
6:1
I'm
doing
some
good
progress
on
trying
to
refactor
at
the
touch
may
need
to
isolate
them,
so
we
could
run
them
in
parallel
and
that
we
don't
have
false
positive,
false
I
guess
for
the
tests,
which
happens
frequently
when
we
run
tests
and
they
forgot
to
clean
something
up
so
making
good
progress
there.
That's
one!
That's
the
the
quick
overview
of
things.
C
C
N
N
Yeah,
it's
to
be
really
quick.
I'll
do
this
lightning
fast,
but
forest
introduced
some
requests
tracing
stuff
into
Lib
pap
a
little
while
ago,
and
we
are,
and
we've
been
working
on
our
distributed.
Algorithms
are
awful,
I
mean
Eid
to
improve
them,
and
to
do
that,
we
sort
of
need
to
learn
a
few
things
about
writing
a
good
distributed
algorithm,
and
so
I
just
want
to
make
everybody
aware
of
this
quick
repo
that
we've
built
to
sort
of
help,
because
we
think
it'll
help.
N
Other
people
understand
peer-to-peer
are
things
a
little
better
through
visualizing
through
request
trees,
so
really
quickly.
I
will
share
my
screen
and
hopefully
walk
through
some
of
this.
So
for
those
of
you
yeah,
this
is
the
repo
itself.
It's
really
really
small,
but
it
basically
does
one
thing
you
can
run
peer-to-peer
test
but
and
it'll
spit
up
a
simulated
Network
with
in
this
case,
20
nodes
in
it,
and
then
it
will
do
a
couple
peer-to-peer
things
it'll
record
those
traces
and
make
that
available
at
this
URL,
which
I
can
show
you
here
yeah.
N
So
if
we
go
to
this
hit
this,
this
is
actually
a
recording
of
traces
of
a
couple
of
distributed
algorithms
in
execution,
so
we
can
actually
see
the
like
set
up
and
if
I
I
find
this
person
I
find
this
tracing
sort
of
information
really
nice.
This
spans
sort
of
says
this
is
how
long
it
took
to
set
things
up.
This
is
the
creation
of
the
actual
network,
and
then
we
can
drill
into
the
actual
pure
connection
work,
and
so
this
is
every
peer
dialing
to
every
other
peer
and
our
little
simulated
network.
N
N
I
have
a
better
demonstration
here
which,
and
so
this
actually
shows
the
execution
of
each
peer
running
the
snapshot
in
parallel
and
so
I
don't
want
to
take
up
too
much
time,
because
I
know
everybody
has
to
leave
for
one
o'clock,
but
I
just
want
to
make
everybody
aware
of
this.
We're
gonna
be
sort
of
actively
trying
to
develop
good
examples
of
peer-to-peer
algorithms
in
this
repo
and
testing
them
out
here.
N
It's
recording
of
each
peers,
local
state
and
a
given
point,
and
so
you
can
actually
see
what
each
peer
recorded,
which
makes
for
I
think
it
makes
a
little
easier
to
sort
of
tell
the
story
of
a
distributed
algorithm
in
action
and
yeah.
It's
been.
It's
already
been
massively
helpful
for
us
in
terms
of
debugging
and
under
saying,
as
you
can
see,
we
have
some
sort
of
bug
where
this
snapshot
is
finalizing
too
early
but
yeah.
So
the
peer,
the
repos
here,
would
be
more
than
welcome
to
welcome
any
for
requests
on
it
and
well.
N
I
think
will
be
the
most
exciting
is
when
the
new
logging
package
for
inside
of
ipfs
itself.
This
can
you
can
actually
leverage
events
in
go
log
and
those
will
show
up
in
traces
as
events
as
well.
So
you
actually
will
get
introspection
into
the
whole
lid
p2p
stack
as
it's
executing,
which
would
be
I,
think
really
exciting
yeah.
So
that's
about
it.
N
N
C
Great
thank
you
and
thank
you
for
finishing
one
minute
before
yeah.
So
thanks
everyone
that
was
sort
of
a
reversion
back
to
our
hour-long
format
and
that's
actually
some
good
thing
to
flag
for
redesigning
things.
When
we
have
these
periodic
updates,
we
will
have
to
have
longer
calls
but
better
to
have
it
scheduled.
So
everyone
knows
all
right.
So
thank
you.
Everyone
and
we'll
see
you
online
this
week
and
we'll
have
a
bunch
of
updates
for
next
week,
including
a
fixed
helper
bot,
giving
people
assigning
people
to
the
moderator
in
note-taking
next
week.