►
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
Hi
everybody
I
know
it's
late
in
the
day.
I,
hopefully
go
quick
with
this,
so
my
name
is
Brennan.
We
work
at
query.
We
do
distributed
data
set
version
control
I'm
that
popular
thank
you
yeah.
So
we
worked
on
this
thing.
We've
been
using
this
inside
of
query
for
a
long
time.
Do
you
think,
is
basically
just
our
sink
for
DAGs
and
for
us
this
was
something
we
had
to
build
just
to
sort
of
like
solve
a
very
specific
problem.
A
Inside
of
our
stack
and
today
what
I
want
to
present
to
you
is
an
effort
to
sort
of
take
some
of
what
we
learned
and
ideally
share
it
back
with
the
community.
So
this
is
our
problem.
Just
I
have
stuff
in
my
IPF's
Reid,
fest,
ipfs,
repo
and
I
know
where
I
need
it
to
go.
Just
put
this
over
there
I,
don't
care
how
you
do
it
I,
don't
want
to
ask
you
how
it
happens.
A
It's
just
pure
a
pure
B
go
over
there,
I,
don't
I'm,
mostly
there
like
things
inside
of
the
D
web,
that
are
less
desirable
when
we're
building
products.
We
have
this
like
content
resolution
times.
Brother
truckin
nat
traversal
issues
like
just
like
stuff
that
gets
in
the
way
of
being
able
to
just
say:
I
have
a
thing:
I
want
to
go
over
there,
I
want
to
go
as
fast
as
humanly
possible,
and
so
for
us.
The
thing
that
we're
trying
to
look
for
is
just
this
point
to
point.
A
So
we've
got
a
couple
of
differences
that
we
have
from
like
traditional
amazing
that
I'm
saying
traditional
in
ipfs
like
bits.
A
lot
base
like
content
resolution,
I,
like
speaking
to
this
crowd,
I
was
like
yeah,
that's
the
new
norm,
and
so
we're
talking
about
just
point-to-point,
setups
and
so
we're
gonna
leverage.
The
fact
that
we
know
we
have
a
very
different
problem
set
from
bit,
swap
where
we
now
just
we
can
sort
of
take
advantage
of
a
different
set
of
constraints
and
solve
for
some
different
solutions.
A
So
things
we
do
in
desync
that
are
different
from
your
traditional
bit.
Swap
movement.
Is
we
set
up
the
conversation
beforehand?
This
is
very
similar
to
our
sync.
We
leverage
blocks
for
sync,
because
if
you
look
at
the
arsenic
algorithm,
we
have
there's
actually
a
rolling
checksum
calculation.
Instead
of
arcing,
so
you're
doing
on-the-fly
content
addressing
to
do
our
sync
properly,
but
we
already
we're
talking
about
sinking
a
miracle
DAGs,
so
we
don't
have
that
problem
at
all.
We
can
just
start
start
with
the
blocks
themselves.
We
don't
want
to
send
stuff,
we
already
have.
A
Early
cool
I
got
to
move
quicker,
so
we
did
this
as
an
IP
FS
plugin,
which
I
think
is
just
to
like
sort
of.
We
wanted
with
this
in
the
loop
you
to
be
because
it's
that's
where
it
belongs.
We
have
this
like.
This
is
generally
the
sort
of
form
factor
which
is
just
decent
push
this
to
that
put
this
the
ID
over
there.
Hopefully
this
works
I
recorded
a
demo
of
it.
So
on
the
Left
we
have
one
person
using
oh
yeah.
A
Well,
I'll
just
talk
to
this
as
we
go
so
I'm
I'm
Alice
on
the
Left
Bob
and
Alice
as
usual,
so
I'm,
gonna,
pin
I
have
nothing
pinned
on
this
side
and
then
on
the
right
side.
I'm
Bob,
with
that
Kerr,
ID
and
I
have
something
pinned:
okay,
cool
and
I
want
to
push
something
from
Bob
to
Alice,
so
I'm
gonna
run
IGFs
daemon,
oh
I'm
gonna,
get
it
wrong
and
then
I'm
gonna
type,
my
PFS
daemon
and
then
you're
gonna
see
something
fun
in
new
there's.
A
This
D
sync
plug-in
started
because
this
new
plug-in
API
is
really
cool.
You
should
totally
check
it
out
if
it
exists,
and
then
we
have
a
really
simple
command-line
wrapper,
which
is
just
like
desync
and
then
do
you
think.
Allow
so
I
have
to
bring
some
trust
to
this,
so
I'm
gonna,
say
I
want
to
allow
Bob
to
send
me
stuff.
A
That's
an
important
caveat,
so
Bob's
now
on
the
allowed
list
of
Alice,
and
so
I'm
just
gonna
say
push
this
to
that
and
we're
done,
and
so
that
figured
it
all
out
and
moved
it
across
that
was
over
lip
p2p.
It
was
also
on
my
local
machine,
so
like
latency
simulated
in
your
brain
but
yeah,
that's
how
distinct
works
we
so
there's.
Oh
yeah
I
have
to
click
this,
but
there
are
some
like
issues
here.
This
is
where
the
code
is
living,
so
you
can
check
it
out,
but
this
is
mainly
approval.
A
Concepts
I
had
to
fork
a
PFS
to
add
something
to
core
API
that
is,
should
be
discussed.
Basically,
we
needed
access
to
Lib
p2p
inside
of
the
plug-in
we
got
to
get
to
the
host,
which
is
a
bit
of
a
question
mark
whether
that
should
even
be
okay.
So
for
me
this
like
thank
you,
but
also
this
invites
a
really
interesting
conversation
about
what
plugins
should
do
and
I'm
really
excited
to
have
that.