►
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
Basically
when
we
add
work,
work,
I'm,
advertising
again
we're
providing
too
many
nodes,
so
this
was
cropped
up
is
likely.
If
you
try
to
do
an
IP
FSI
on
NPM
it
just
my
understandings.
It
just
takes
forever
to
complete
if
never
completes,
and
that's
because
it's
having
to
do
pitch
of
advertising
for
all
of
the
individual
individual
blocks,
and
so
it
ends
up
happening.
Is
that
we
turn
off
content
routing
to
do
that
ad,
and
so
our
goal
is
to
allow
you
to
do
250
times
not.
B
A
Our
advertised
notes
what
that
looks
like
the
shape
of
it,
how
to
we
have
to
figure
out
how
to
encode
info,
for
which
notes
to
provide,
so
that,
if
I,
if
we
have
a
strategy
for
deciding
which
notes
to
provide
when
you
fetch
those
notes,
you
you're
using
the
same
strategy
to
provide
this
name.
This
thing
knows
and
then
is
a
deterministic
strategy,
or
is
it
kind
of.
C
C
C
Like,
like
Michael,
said
currently
we're,
basically,
he
like
providing
for
every
block,
and
that's
just
like
at
some
point
before
we
even
done
doing
that
we
have
to
like
to
start
reading
what
we're
currently
doing
and
then
we're
just
like
infinite,
like
not
ever
getting
like
getting
the
first
iteration
done.
So
what
we
are
like
doing
instead,
would
we
like,
like
ideas,
thing
but
like
that's
like
really
not
feasible,
to
see
like
have
a
lot
of
provider
records
store
it
at
the
do
only
for
the
room?
No,
but
like
with
a
lot
of
information
side.
C
So
like
another
thing
we
considered
is
like
only
like
only
make
these
work
over
the
entire
subtree,
but
only
to
the
entire
subtree.
Until
you
hit
the
next
anchor
know
like
the
next
node.
That's
that's
going
to
be
provided,
which
has
like
similar
problems,
but
like
that's
bad,
because
it's
like
you
can,
for
example,
provides
the
the
index
of
like,
for
example,
the
FBM
registry,
which
is
like.
Maybe
it's
like
a
couple
megabytes,
maybe
a
couple
tens
or
hundreds
of
megabytes.
C
But
it's
look
like
terrorize
the
data,
so
you
can,
for
example,
provide
for
the
index,
provide
the
index
of
NPM
or
or
which
media
and
without
providing
without
storing
all
the
data,
which
is
the
index
and
providing
the
index
so
I,
especially
for
like
the
the
subtree
case
it's
like
for
for
the
for
the
case,
where
you
only
provide
the
subtree
up
to
the
next
anchor
nodes.
You
can
say:
okay,
even
if
I
just
install
one
package,
I
have
to
you
download
the
entire
index.
C
You
download
like
every
time
you
done
with
the
subtrees
of
everything
and
then
announce
these.
But
then
you
first,
you
download
a
lot
more
data
than
you
initially
requested
and
you
seek
more
data
than
you
initially
request
it
and
you
don't
actually
know
what
the
data
is.
So
that's
also
like
not
like.
Maybe
it's
like
not
what
you
really
want
so,
but
at
the
end
of
the
day,
what
we?
C
What
do
we
really
like
to
see
is
that,
even
if
you
just
request
a
little
more
turn
off
the
data,
you
still
see
that
data
and
not
like
teaching
a
patron
comes.
So
like
another
strategy.
We
were
discussing
what
we
like
really
at
the
end
of
the
discussion,
is
that
you,
like
in
the
provider
record
like
clearly
say
which
parts
of
this
subtree
you
can
seed
and
kind
of
like
offer
for
download
and
yeah.
C
That's
like
a
lot
of
different
options
like
first,
we
were
talking
a
bit
fields
at
like
bloom
filters,
and
it's
it's
like
still
up
to
discussion
and
we're
you
about
it.
But
it's
like
like
one.
One
main
criticism
is
like
encoding
too
much
information
in
the
provider
record
makes
them
too
large,
and
also
if
everyone
agrees
on
the
same
provider,
we're
gonna
have
a
lot
of
these.
So
too
much.
D
A
B
A
B
Guess
I,
don't
think
we
can
all
agree
on.
Is
that,
like
a
lot
of
these
dependent
only
use
case
by
use
case
and
requires
a
lot
of
experimentation
rather
and
so
like
developing
a
bunch
of
bench
warrants?
A
bunch
of
the
tests
like
set
up
different
network
topologies
and
different
use
cases
will
then
get
us
to
have
better
informed
decisions.