►
From YouTube: IPFS in the Second Half of 2020 - Dietrich Ayala
Description
What’s next for IPFS in 2020? Ecosystem lead Dietrich Ayala shares the next half of the IPFS roadmap during the August meetup.
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
Hello,
everybody
welcome
to
the
ipves
virtual
community
meetup.
My
name
is
dietrich
ayala.
I'm
the
ecosystem
lead
protocol
labs
for
ipfess,
and
today
we're
going
to
talk
about
a
few
things
thanks
for
joining.
First,
please
share
your
information
in
the
chat,
see
a
whole
bunch
of
folks
in
there
share
with
group
where
you
are
coming
from
how
you're
involved
in
ipfs
or
what
you
want
to
learn
and
if
you're
currently
using
ipfs.
Let
us
know
let
everybody
else
know
what
your!
A
A
We
have
standards
for
behavior
and
in
this
community
we
want
people
to
feel
welcome
everybody
to
be
able
to
participate
in
a
way
that
feels
okay
with
them
and
we'll
out
of
our
way
to
be
able
to
help
you.
If
you
have
any
issues
in
this
community,
so
there's
contact
information
there.
Please
do
reach
out
and
let
us
know
if
you
need
any
help
at
all
today.
We're
gonna
have
a
couple
of
different
talks.
I'm
gonna
give
a
really
quick
update
now
on
our
plans
for
the
second
half
of
this
year.
A
It
will
be
an
action-packed
hour,
you're,
probably
familiar
with
ipfs,
but
if
you're
not
familiar
with
ipfs.
A
really
quick
refresher
ipfess
is
a
decentralized
file
sharing
system
internet
scale
like
the
internet
they
use
today,
except
instead
of
referencing
things
by
their
location.
We
ask
for
them
by
the
unique
identity
of
their
contents,
as
you
can
see
in
this
slide,
how
we
ask
for
things
is
a
little
bit
different
and
it's
called
a
content
address.
Some
of
the
problems
that
ipfs
seems
to
address
are
some
of
the
shortcomings
of
the
web
that
we
know
today.
A
A
Thank
you
for
your
contributions.
It's
amazing.
The
ipf's
ecosystem
is
comprised
of
hundreds
and
hundreds
of
apps
many
different
services.
Some
people
are
using
it
for
content,
some
people
for
infrastructure,
some
people
for
ops
and
some
people
for
personal
data
sharing
and
keeping
data
alive
at
storing
data
as
well.
A
Many
of
the
projects
that
you
see
here.
Some
of
these
folks
are
in
the
chat.
So
if
you
have
questions
about
your
given
use
case
or
something
that
you
want
to
do
with,
ipfess
feel
free
to
ask
in
that
before
we
get
into
the
second
half
of
the
year.
Let's
talk
a
little
bit
about
the
first
half
of
the
year.
A
The
first
half
of
the
year
had
a
really
it
was,
was
momentous
in
a
few
different
ways,
but
one
of
the
biggest
was
that
we
launched
ipve
0.5,
which
was
the
largest
upgrade
of
performance
in
ipfs.
That
just
happened
to
date.
It
was
a
major
change
to
the
protocol
and
it
was
a
major
change
to
how
ipvest
was
able
to
respond
to
the
needs.
A
The
growing
needs
of
the
people
using
it
as
network
traffic
grows
and
use
of
ipfs
grows
as
it
be
just
grows
into
different
areas,
segments
and
different
applications
and
adds
to
browsers
it
needs
to
be
able
to
perform
in
a
way
that
meets
people's
expectations
and
that
can
provide
them.
The
network
performance
that
that
we
need
so
there's
a
massive
improvement
here,
and
there
are
more
yet
to
come.
A
The
way
that
these
improvements
were
implemented
means
that
the
we
will
be
able
to
take
more
and
more
advantage
of
them
as
as
time
goes
on.
We
also
saw
a
lot
of
integrations
and
people
building
on
top
of
of
ipfs
ipfess,
launched
in
browsers
like
opera
for
android,
the
wolfram
language
and
wolfram
engine
added
ipfs
support
new
services
such
as
ens,
unstoppable
domains,
we'll
hear
about
from
later
today
and
fleek
started.
A
We
launched
a
grants
program
in
in
the
first
half
of
the
year,
major
changes
to
how
ipf's
core
protocol
parts
work
and
then,
from
a
contributing
experience
standpoint,
we
made
a
number
of
changes
to
how
we
actually
build
ipfs
and
how
we
make
it
easier
for
you
to
be
able
to
respond
and
tell
us
how
it's
working
for
you
we
give
it
give
the
world
is
shut
down
in
a
lot
of
ways.
We
still
took
part
in
a
number
of
different
events
that
hosted
different
events
in
the
first
half
of
the
year.
A
Some
of
that
which
we'll
hear
both
spoke
at
I
participated
in
joined
and
we're
going
to
keep
doing
more
of
them
like
this
and
some
other
things
that
we
we
changed
as
well
in
the
first
half
of
the
year,
where
how
well
and
how
we
listen
to
you,
how
we
listen
to
what
the
needs
of
developers
are,
how
we
listen
and
identify
who's
building
on
ipfess.
We
have
tools
now
that
scour
things
like
docker
compose
files
and
github
repos
and
github
issues
be
able
to
figure
out
who's
using
ip
fest.
A
A
We
spent
the
first
half
of
the
year
making
sure
that
the
foundations
are
strong,
that
the
ipfs
core
protocol
is
able
set
up
in
a
way
to
scale
into
this
growth
that
we're
experiencing,
and
now
we
want
to
make
sure
that
we're
able
to
sustain
that
and
to
be
able
to
build,
on
top
of
it
internal
focus
on
those
core
bits
of
the
protocol
into
understanding
what
the
needs
of
the
people
building
on
ipfs
are
how
we
can
beat
them
best.
We're
going
to
do
this.
A
A
few
different
ways
talk
about
continuous
visibility,
understanding
who
you
are,
how
you're
using
ipfs
how
the
protocols
is
holding
up
how
our
implementations
of
it
are
doing,
maintaining
support.
So
it's
paying
attention
to
stack
overflow
to
the
forums
to
github
issues
and
the
places
where
you're,
either
making
feature
requests
or
reporting
issues
and
using
that
to
accelerate
adoption.
A
So
looking
for
places
where
we
get
ipfs,
make
it
easier
to
access
by
people
who
are
not
technical,
make
it
easier
to
use
for
people
to
both
publish
data
and
to
be
able
to
consume
it.
The
priorities
are
community
maintenance
and
maintainership,
making
sure
that
we're
shipping
their
software
on
a
regular
basis,
we're
reducing
the
time
that
it
takes
us
to
be
able
to
ship
new
updates
to
the
protocol
into
the
libraries
and
implementations.
A
If
there's
anything
that
we
can
do
to
close
those
gaps
to
be
able
to
provide
tools
to
make
it
easier
to
understand
when
when,
when
you
experience
challenges,
the
the
the
nature
of
developing
for
our
p2p
network
is
radically
different
than
developing
for
centralized
systems
and
developing
with
http.
So
we
need
to
be
able
to
understand
the
challenges
that
people
have
when
they're
making
that
transition
and
be
able
to
develop
tools
that
that
help
them
get
all
the
way
to
shipping
their
applications.
A
A
The
bifrost
team
is
focused
on
infrastructure
for
the
most
part,
making
sure
that
security
infrastructure
is
up.
That
ipfs
is
serving
the
file
coin,
hosting
needs
that
we
have
and
that
our
gateways
are
staying
up
and
that
we
have
metrics
around
that
gui
web
browser's
team
is
going
to
be
adding
a
new
feature
that
you'll
hear
about.
A
Hopefully,
in
the
lightning
talk
section
a
little
later
called
pinning
services,
one
of
the
things
that
you
know,
if
you
add
something
to
ipfs
on
your
laptop
and
then
you
shut
your
laptop,
it's
no
longer
necessarily
available
on
the
network.
So
we
want
to
be
able
to
have
a
way
for
people
who
want
to
be
able
to
host
their
data
and
make
sure
that
it's
there
all
the
time
can
easily
do
that
from
within
the
the
products
that
we
ship.
A
The
ecosystem
group
is
really
focused
on
systemic
views
of
the
project,
so
looking
at
overall
community
needs
making
sure
that
we're
meeting
our
community
needs
from
our
communication
standpoint
that
we
have
automation
to
be
able
to
make
sure
that
our
small
team
can
actually
sustain
and
survive
the
incoming
amount
of
questions
from
all
from
places
like
forums,
rc,
matrix
and
stack
overflow.
We
want
to
be
able
to
understand
for
dot
developers
specifically
how
well
ipves
is
working
for
them.
A
We
want
to
know
what
tools
they're
using
what
tools
they
need,
whether
our
documentation
is
meeting
their
needs.
We
also
want
to
be
able
to
develop
systems
of
understanding
overall
project
status,
both
for
ipvs
and
the
other
projects
like
protocol
labs.
We
are
using
a
system
of
dashboards
right
now
kind
of
what
I
mentioned
earlier
about
github
repo
tracking
and
crawling
to
be
able
to
understand
where
things
are
growing
or
shrinking
or
changing
or
how
ipfs
has
been
used,
and
we
wanted
more
tools
like
that.
A
So
we
can
leverage
that
and
make
this
better
decisions
about
what
we
do
with
the
core
protocol
and
when
and
then
finally
identifying
and
integrating
a
set
of
well
understood
metrics
into
the
projects.
We
understand
whether
what
we
do,
what
we're
doing
is
actually
working
or
not.
The
core
implementations
for
go.
Have
the
supporting,
depending
ecosystem
again
is
building
services
ecosystem.
A
It
gives
a
really
high
priority
and
then
a
number
of
things,
including
a
specification
for
the
dht,
so
that
dhc
implementations
can
be
implemented
in
multiple
languages
instead
of
just
go
in
javascript,
there's
a
whole
bunch
of
performance
improvements
that
are
coming
as
well
as
a
few
different
things
like
integrations
with
react,
native
and
typescript.
We
want
to
be
able
to
provide
libraries
that
work,
how
javascript
developers
are
working
today
and
make
sure
that
ipfs
is
a
choice
that
they
can
have
when
they're
building
their
applications.
A
There's
a
number
of
different
success,
metrics
that
we're
looking
at
these
are
some
of
the
ones
that
we
look
at
today
across
a
couple
of
different
areas,
but
we
don't
have
visibility
into
some
of
these
areas.
So,
there's
still
some
work
to
do
for
us
in
both
meeting
these
metrics,
but
also
getting
better
insight
and
understanding
and
how
they're
working
for
us
and
whether
or
not
these
are
the
right
metrics.
A
A
There's
more
microsoft
ion
is
a
decentralized
digital
identity
system,
that'll
be
launching
later
this
year
that
uses
ipfs
for
storage
ucam,
which
maybe
will
hopefully
get
to
a
future.
One
of
these
to
be
able
to
talk
is
a
privacy-oriented
home
security,
camera
that
uses
ipfs,
and
I
have
one
of
these
right
now
and
I
have
it
sitting
in
my
backyard
looking
for
mooses,
so
not
a
typical
use
case,
but
hopefully
it
will
put
the
product
to
the
test.
A
More
of
these
coming
soon
and
like
I
said
before
the
painting
services
api,
this
is
currently
a
specification
that
is
progress.
Feedback
is
really
wanted
if
you're
interested
in
either
both
consuming
or
hosting
pinning
service
definitely
share
your
thoughts
with
us,
so
we
can
make
sure
that
it
meets
your
needs.
Brave,
ipfs,
native
integration
and
brave
is
coming
soon.
A
The
grants
program
still
has
a
number
of
grants
that
are
in
progress
and
a
few
new
ones:
you're
gonna
see
maps,
integration,
more
and
deeper
chromium
integrations
and
more
work
with
wikipedia
and
also
nixos
coming
soon.
And
finally,
there
are
a
number
of
events
that
are
happening
right
now
in
order
to
prepare
for
the
filecoin
mainnet
launch.
A
lot
of
these
developers
are
using
ipfs
heavily
and
the
hackfest
month-long
hackathon
is
is
ending
this
week,
I
believe,
and
the
feedback
we've
gotten
from
developers.