►
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
So
this
was
a:
we
had
a
content,
routing
track
about
privacy,
so
this
is
where
we
explored
the
medium
to
long-term
goal,
set
around
building
properly
private
networks,
and
here
we
were
focusing
on
the
content
routing
part,
so
not
just
the
not
the
whole
content,
not
the
privacy
model
of
a
consumer
trying
to
download
data,
but
just
specifically
how
consumers
find
providers
of
data.
A
The
big
reason
is
that
we
think
if
we
don't
do
this
well,
bad
things
will
happen.
So
we
want
to
avert
some
like
really
bad
things
from
happening.
We
had
a
ton
of
really
useful
talks
from
a
number
of
folks,
including
so
we
had
talks
around
high
level,
definitions
of
the
problem,
space
and
introductions
to
private
content
routing
and
why
it
matters.
We
had
very
concrete
projects
like
private
set
intersection
for
bitswap
and
something
that
we
can
build
now
and
deploy
it.
A
We
had
the
announcement
of
a
new
fund
to
fund
private
retrieval
and
so
there's
a
whole
blue
fund
blue
network
fund
to
drive
r
d
for
research
in
in
in
prior
retrieval.
This
includes
yeah.
This
includes
everything
in
the
r
d
pipeline.
So,
from
early
research
all
the
way
through
building
libraries
and
shipping
things,
we
had
discussions
around
mixnets
and
content,
routing
and
also
kind
of
making
oblivious
routing
systems.
A
We
talked
about
double
hashing
and
dhts,
and
and
so
improvement
proposals
for
dhts
to
become
more
private.
We
had
discussions
around
use
cases
for
privacy
across
the
stack.
We
had
an
awesome
survey
of
different
approaches
from
a
crypto
primitives
lens
around
private
information,
retrieval
and
content
writing.
So
thinking
of
specifically
of
the
content
writing
problem,
how
can
we
use
all
of
the
existing
techniques
out
there,
and
then
we
had
a
number
of
discussions
around
hey
what
are
open
problems?
What
are
projects
that
we
want
to
want
to
work
on
and
so
on.
A
So
there's
a
bunch
of
really
important
things
that
came
out
of
out
of
this
track
and
is
yeah
really
promising.
So
there's
we
have
a
ton
of
learnings,
primarily
that
we
first
it's
extremely
critical
to
do
this,
but
it's
very
hard
and
we
need
to
scale
the
community
of
practice
working
on
this.
So
this
includes
yeah
everything
from
academic
research,
to
building
things,
to
deploying
things
to
forming
larger
collaborations
and
so
on.
So
there's
a
lot
of
effort,
that's
going
to
go
into
just
booting
that
academic
field.
A
It
also
was
brought
out
that
in
a
few
discussions
that,
having
that
the
liberty,
p
being
different
from
the
http
stack,
prevents
us
from
using
a
lot
of
the
improvements
that
are
happening
in
the
hp
world.
So
it's
another
point,
data
point
that
shows
us
that
we
should
absorb
http
into
the
fps
stack
and
be
able
to
like
layer
a
lot
of
ipf's
implementations
just
on
top
of
on
http,
so
things
like
online
routing
with
http
and
so
on.
A
A
Then
there's
like
the
whole
booting
of
the
academic
field,
which
will
take
longer
and
have
more
effort,
require
more
effort,
but
we
think
this
is
going
to
be
really
valuable
long
term
and
then
we
need
to
publicize
the
the
private
retrieval
fund
and
that
might
be
websites,
docs
and
so
on.
So
here
are
some
milestones
in
in
this
next
quarter.
We
think
we
need
to
do
that
publicizing
of
the
fund
we
and
we
should
be
able
to
have
candidate
roadmaps
for
psi,
bitswap
and
dhdht.
A
A
The
we
then
want
to
kind
of
like
form
private
retrieval
as
a
project
with
communications
and
discussion
places.
So
we
need
to
do
some
project
tooling
around
that
we
need
to
then
start
defining
open
problems
and
posting
rfps
and
so
on,
and
then
maybe
do
some
some
publishing
of
blog
posts
and
potential
papers
and
so
on,
and
then
we
hope
that
in
a
year
from
now
we
we
have
something
to
show
for
it.
A
Not
just
in
terms
of
projects
started,
but
an
academic
community
grown,
but
in
in
terms
of
actual
improvements
delivered
to
running
ipfs
systems,
so
we
think
that
ipfs
privacy
should
be
able
to
improve
significantly
by
you
know
a
year
from
now,
so
that
means
potentially
might
mean
shipping
psi,
bitswap
or
dhcft
or
other
things
like
that
great
that's.
It.