►
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
Does
anyone
have
any
thing
that
they
I
don't
know
I've
been
like?
I
I
something
I
noticed.
That's
that
actually
reba
said
on
the
thing
which
is
like
there's
this
trade-off
of
like
trust
and
verifiability,
and
I
he
was
like
just
throw
out
incremental
verifiability.
If
you
have
any
trust-
and
I
was
like,
I
think
we
mean
the
same
thing
like
when
I
say
incremental
verifiability,
which
I
don't
think
anyone
else
here
is
like,
I
think
balance.
B
A
And
verifiability,
not
every
block
must
be
verified
before
you
take
another
one.
C
Yeah-
and
that
was
also
part
of
my
my
talk
yesterday,
I
was
like
you
can
as
long
as
as
long
as
there
is
a
mechanism
for
the
client
to
get
some
minimal
amount,
like
some
amount
of
like
strict
verifiability,
you
can
allow
them
to
expand
that
for
their
own
performance,
as
opposed
to
like
a
yes,
no
lever.
That
seems
pretty
useful
if.
D
A
A
E
A
E
B
A
C
A
C
Bit
just
like
a
little
bit
it
you
can
build
so
so
one
of
the
things
that's
the
pc,
which
is
which
is
not,
which
is
not
like
the
cool
protocol
stuff
that
we
like
learning
about,
but
like
it's
like.
How
do
I
look
convenient,
gives
me
these,
like
handy
functions
where
I
can
like
do
to
identify
and
figure
out
what
do
you
support
and
then
like
switch
things
up,
and
so
that's
cool,
but
then
there's
like
how
do
I
glue
them
together?
C
Right
if
I
support
multiple
of
them,
and
that
piece
is
like
super
sorely
innocent
and
as
sort
of
my
my
like
example
of
this
is
you
can
run
with
sloth
against
a
car
car
b2
is
having
a
season
front.
You
could
replace
half
one
pass
with
a
look
up
in
the
index
which
right
and
that
will
work
and
then
replace
walk,
lock.
C
And
you
can
run
this
in
parallel
with
this
slot,
because
it's
basically
the
same
problem
right,
but
there's
no
tool,
and
so
I
feel
like
this
in
order
to
make
this
work.
B
Place
of
these
are
the
use
cases
we
want
to
support.
Yes,
bitswap
is
fully
general
and
does
everything,
but
it
has
these
other
trade
odds
when
we
switch
to
another
thing
and
what
are
the
parts
in
that
stack
that
we
can
just
copy
just
directly
and
include
it
the
same
way
like?
Should
we
just
standardize
the
car
files
or
whatever
the
thing
is
and
then
now
at
some
layer
we
can
reuse
what
you're
doing
and
then
say?
Well,
I'm
going
to
put
over
the
wire
like
this
and.
B
And
then
on
the
other
right
and
that
all
of
this
thing,
all
these
things
are
a
question
of
what
are
the.
Where
should.
B
Go
to
prioritize,
it
has
to
start
from
these
cases
right,
like
dude.
Do
we
care,
let's
put
in
my
clients,
do
you
hear
about
supporting
browsers
right
like
all
of
these
questions,
and
so
I
think
it's
really
easy
for
us
to
go
from
a
purely
technical
point
of
view
and
say,
like
it
wouldn't
be
great
if
you
do
x
or
y
or
like
this
seems
to
be
powerful,
but
I
almost
want
to
flip
it
around
to
like
a
certain
chronicles.
A
I
just
it's
an
interesting
conversation,
because
we
should
we
may
have
different
product
requirements
too,
like
like,
like
I
mean
you
know,
I
I
make
shady
shady
remarks
about
http,
but
I
mean
that
comes
from
like
that.
Is
the
file
coin
product
requirement
just
move
the
data
fast.
We
don't
care
how
screw
the
whole
design
you
know
of.
D
Issues
and
having
to
sort
of
like
figure
out,
okay
and
how
to
just
get
a
b
and
that's
part
of
what
I
think
did
was
playing
active.
It's
like
we've
gone
looking
at
number
zero
for
the
literature
data
transfer
and
it
is
like
not
as
thorough
as
we
would
hope
and
like
this
feels,
like
their
drive,
is
underexplored
to
try
and
build
a
reliable
multi-party
fancy
protocol
that
is
competitive
with
hcp,
which
the
record
has
a
lot
of
time
and
energy
behind
it.
D
And
so
this
is
a
really
high
hill
and
I
just
understand
how
most
of
the
strategies
that
you've
seen
for
application
developers
can
be
to
just
move
to
trusts
and
setups
right
and
just
get
like
the
sacramental
verification
question.
It's
not
that
it's
controversial,
but
is
it
practical
to
deal
with
that
when
practicalities
when
practicing
is
during
the
day
and
we're
we're
moving
on
so
like
it's
just
fine?
D
A
It's
interesting
because
in
some
ways
pl
has
become
more
of
an
application
developer,
because
our
application
is
filecoin,
yeah
right
and
we're
almost
like
it's
funny,
because
we're
almost
like
new
newbies
to
this
and
we're
going
like
the
other
direction.
Real,
quick
there's
I
mean,
I
think,
an
interesting
way
to
phrase
it
by
the
way.
There
is
someone
on
the
slack
who
disagrees,
who
thinks
it's
just
not
important
if
you
rebus-
and
I
are.
A
One,
I
think,
one
way
to
phrase
the
problem
is
like
what
is
worse:
downloading
200
gigs
of
of
data
that
turns
out
to
be
wrong
or
not
getting
your
data
at
all
or
getting
it
so
slowly
that
it's
unpractical
right,
like
maybe
that's
a
way,
that's
a
good
way
to
measure
the
trade-off,
because
there
is
a
real
problem
in
the
other
end
too,.
D
Yeah,
I
would
argue,
there's
a
reporter
in
he's
like
like
you
need
to
get
bytes
first
independently,
if
I
can't
verify
them,
because
I
can't
ever
verify
anything
that
I'm
going
to
get
so
it's
not
coming
to
me.
I
don't
care
about
anything
other
else
than
like.
I
need
to
move
to
me
and
then
I
can
start
worrying.
It's
like
a
food
water.
C
E
C
C
I
don't
want
to
like
any
of
this
I
wanted
to
like
I
just
I
found
a
link
somewhere
online
like
play
it
for
me.
I
guess
I'll
trust
wherever
it
is.
I
come
with
me
and
like
for
some
areas
where,
if
this
makes
sense
and
there's
somewhere
like,
I
feel
like
you've-
maybe
missed
the
point
of
a
lot
of
what
we're
building
but
okay,
I
guess
it
works
for
you
right
and
like
those
areas,
I
think.
C
D
A
A
Yeah,
or
at
least
the
ipfs
one,
can
I
just
throw
one
more
thing,
and
I
will
go
right
to
you
another
thing
that
reba
said
on
the
slack,
which
I
think
is
really
another
angle
to
add
on
to
this
question
of
tradeoffs
is
like
he's.
He
said
we
should
avoid
hard
things,
which
is
an
interesting
question,
because
my
whenever
we
have
one
of
these
trade-offs,
my
instinct
is
well.
If
I
just
build
like
an
algorithm
that
balances
trust
and
builds
it.
A
You
know
like
in
real
time
and
makes
you
know
bigger
requests
and,
like
you
know,
but
still
doesn't
verifiable
viable,
like
my
instinct,
is
to
like
get
real
technical
and
like
try
to
think
that
I
can
solve
it
with
the
right
algorithm
so
that
I
don't
have
to
make
the
trade
off,
or
at
least
like
there's
a
penalty
in
going
too
deep
into
like.
A
How
can
we
solve
it
because
you
come
up
with
solutions
like
I
mean
it's
not
easy
to
write
like
if
you
write
an
algorithm
like
that
is
gonna
like
let's
say
we
wrote
the
like.
The
incrementally
verified
manifest
right
and
it
like
was
real
smart
about
like
how
far
it
looked
ahead
before
it.
You
know
in
terms
of
how
much
it
requested
and
it
requested
more
over
time.
A
That
starts
to
get
more
complicated
in
code,
and
maybe
that's
a
bummer
too
so
anyway,
I
mean
most
people
are
attracted
to
this
sort
of
space
because
they
like
that,
but
also.
B
A
Have
to
factor
that
in
yeah,
maybe.
E
This
is
more
a
comment
about
the
evolution
of
these
transport
protocols
from
the
original
ipfs
and
I
feel,
like
the
there's,
been
a
specialization
towards
just
getting
the
data
here
and
the
model
of
and
to
me,
it
indicates
a
change
in
the
model
of
data
distribution
on
the
network
versus
what
it's
intended
for
envisioned
in
how
it's
like
like
to
me,
the
shallow
wide
bra
right
here.
It's
like
it's
coming
from
those
appears,
and
I
can
just
spread
it
out.
Shotgun
requests
and
I
can
get
all
the
bits.
I
want
multiple.
E
But
if
you're
parallelizing,
that
that
that
request
flow
to
multiple
ones
that
actually
have
the
information,
it
makes
sense.
But
then
we
specialize
to
like
well,
you
know.
B
E
Realistically,
only
one
other
person
in
the
world
has
my
file
right
now
and
how
I
had
to
get
it
from
them
as
fast
as
possible.
So
I
think
there's
a
framing
of
that.
E
Just
it's
never
going
to
work
for
us,
but
so
I
feel
like
there's
an
aspect
of
like
maybe
methods
of
pre-emptive,
pushing
and
all
of
this
need
to
come
into
how
we
actually
think
about
data
distribution
in
the
network
to
actually
assist
in
all
this,
because
I
feel
like
just
relying
on
data
transfer
is
never
gonna
like
it's
always
gonna,
be
just
as
good
as.
A
A
Like
solved
the
case
of
how
do
we
make
that
a
lot,
somebody's
laptop
actually
useful
in
most
cases
you
know
like
and
but
we're
starting
to
encounter
that,
because
there
are
people
building,
retrieval
networks
with
browser
nodes
and
they're
like
well,
they
have
a
terrible
upload
speed.
So
if
we
don't
bit
swap
it,
then
it's
gonna
be
useless.
You
know,
what's
up
cool,
all
right.