►
From YouTube: Fil+ dashboard
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
Yeah,
I
want
to
talk
a
little
bit
more
about
the
general
like
dashboards
and
tracking
and
stuff,
so
laura
first
up
like
thank
you
so
much
for
sharing
you're
like
more
on
on
fieldbus
at
info,
like
it's
been
a
tremendously
useful
tool
for
me
already,
and
I
think,
having
many
tools
like
that
is
very
useful
for
the
system
as
well
like
it
leads
to
better
accountability,
better
transparency
and
also
data
integrity,
and
so
there's
like
a
couple
of
dashboards
that
are
being
worked
on.
This
is
the
other
one
that
I
briefly
mentioned.
A
A
The
intent
is
to
have
multiple
independent
sources,
data
that
provide
their
perspective
and
view
so
that
together
we
can
work
to
build
agreement
on
the
state
of
the
ecosystem
and
make
sure
that
we're
all
sort
of
like
on
the
same
page,
about
progress,
that's
being
made
and
tracking
like
the
right
set
of
metrics,
and
so
the
a
couple
of
things
I
want
to
highlight
on
this
particular
dashboard
are
the
the
following.
So
the
first
is
as
a
community.
A
One
of
the
metrics
that
we've
been
anchoring
on
recently
is
this
concept
of
like
time
to
data
cap
time
to
data
cap
is
the
idea
that,
like
it
takes
some
amount
of
like
time
from
as
a
client
entering
the
ecosystem
to
actually
receiving
data
capture
address
that
you
can
then
use
to
go,
make
deals.
It's
like
the
latency
that
you
would
incur
if
you're
someone,
that's
actually
like
interested
in
leveraging
this
particular
ecosystem,
but
need
to
go
through
the
flow
right
like
you
need
to
go
understand,
what's
actually
happening.
A
A
So
there's
a
couple
of
like
there's
a
couple
of
ways
in
which
this
happens
like,
as
I
mentioned
previously
in
my
talk,
you
can
get
data
cap
automatically,
so
that
means
like
going
to
like
a
site
like
this,
where
you
like
log
in
via
your
github
account,
and
you
get
32
gigabytes
of
data
cap
almost
instantly
right,
like
the
delta
here
is
like
30
seconds,
and
if
you
look
at
this
particular
notary,
the
the
automated
notary
here,
the
the
amount
of
people
that
have
gone
through
this
flow
is
like
pretty
substantive
so
like
this
is
the
notary
that
owns
verified.left.io
of
like
the
330ish
clients
that
have
come
to
this.
A
200
of
them
have
come
to
this
flow,
so
for
these
particular
clients,
their
time
to
data
cap
was
like
30
seconds,
which
is
not
a
lot
at
all,
and
so
the
I
may
actually
make
this
full
screen
as
well.
So
I
can
share
some
other
parts
of
it,
but
yeah
so
30
seconds
brings
the
time
down
substantially,
but
for
the
remaining
like
data
cap,
applications
that
are
coming
through
those
are
all
manual
they're,
all
coming
through
github.
A
They
require
like
interaction
between
a
notary
and
a
client,
to
actually
discuss
like
aspects
of
an
application.
So
I
think
the
one
that
I
was
like
jumping
into
before
was
this.
This
application
right.
So
this
again
not
to
pick
on
anybody
specifically.
I
just
randomly
picked
this
one
because
it
has
numbers
but
like
you
can
see
that
there's
this
github
application.
That
came
in
like
similar
to
what
you
just
saw
on
fieldbus.info.
A
There's
like
this
interaction
between
a
client
and
notary,
and
this
takes
time,
and
so
what
we
want
to
do
as
a
community
is
like
track
this
and
ensure
that
over
time
we
can
reduce
how
long
this
takes,
because,
ultimately,
if
we're
measuring
ourselves
on
making
file,
client,
more
productive
and
making
the
ecosystem
more
useful,
then
bringing
this
number
down
means
that,
like
clients
themselves,
are
able
to
be
unblocked
as
fast
as
possible
and
have
the
minimal
like
perceived
friction
from
the
actual
ecosystem,
to
bring
their
stuff
onto
the
network.
A
And
so
this
is
something
that,
like
I've,
been
paying
a
lot
of
attention
to
in
our
like
bi-weekly
calls
and
we've
also
got
other
data
sources
that
have
popped
up.
I
know
andrew
hill,
for
example,
has
started
tracking
some
of
this
stuff
as
well
through
a
github
file
that
can
be
downloaded
and
used
by
any
other
dashboard,
that's
being
built.
So
what
I'd
like
to
call
out
is,
like
specifically,
you
know
if
you're
interested
in
getting
into
this
ecosystem,
helping
build
transparency
is
absolutely
one
really
really
useful
way
to
do
it.
A
The
foundation
will
be
talking
about
grants
that
are
available
for
you.
If
that's
the
path
you
want
to
take
that
pursue
or
if
you're,
just
already
part
of
falcon
in
some
way,
such
as
the
case
was
with
the
file
drive
project,
you
know
you're,
probably
already
intimately
familiar
with
how
some
of
these
things
work.
You
should
feel
free
to
get
started.
A
The
other
thing
that
I'd
shown
earlier
in
the
talk
earlier
in
this
conference
that
I'll
just
briefly
highlight
again
for
those
of
you
that
have
just
joined,
is
part
of
this
flow
like
similar
to
what
you
saw
in
football.info,
where,
like
once
you
click
into
like
an
actual
like
client.
A
You
can
see
the
amount
of
deals
that
they've
made,
which
is
with
the
data
cap
that
they've
used
so
far,
how
they've
made
their
deals
and
where
those
videos
are
actually
going,
and
this
is
interesting
because
as
part
of
the
client
due
diligence
process,
oftentimes
like
clients
are
also
sharing
information
on
their
data
cap
usage
plan
and
their
like
storage,
onboarding
and
allocation
plan
on
the
network
and
so
building
transparency
and
auditing.