►
From YouTube: Fleek & Space - 2021 Roadmap
Description
Harrison Hines joined us to give both a recap on the very cool things the Fleek, and later Space, teams were able to accomplish in 2021, as well as a peek at what’s next.
Learn more about Fleek at https://fleek.co/
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
A
How
can
we
just
make
really
good
user
experiences
and
products
that
make
that
really
easy
to
do,
and
so
that
was
one
good
example
of
what
we're
trying
to
double
down
on
is
just.
How
can
we
make
really
good
user
experiences
to
like
to
develop
products
that
get
these
technologies
into
users,
hands
super
seamlessly
and
almost
in
a
abstracted
way,
and
so
we
did
the
fleeq
launch
in
in
march.
A
We
really
did
focus
on
the
user
experience
and
making
sure
that
it
felt
like
a
web
2
app
and
experience,
but
even
better.
So
we
feel
pretty
proud
about
what
we've
accomplished
and
the
tech
stack
we've
built
it
on
top
of
especially
textile
and
the
ipfs
work.
So
it
was
great
to
understand
the
new
things
in
ipfs
and
that
roadmap,
because
where
we
are
going
is
essentially
next
year,
is
really
focused
on
two
things.
One
is
like
the
space
daemon.
We
have
a
space
sdk,
we're
about
to
drop
in
two
weeks.
A
That's
essentially
like
an
upgraded
version
of
the
space
stamen.
Everything
is
broken
out
into
different
modules.
So
it's
not
all
packaged
into
one
thing.
It's
much
much
easier
to
work
with,
but
you
know
we
compare
ourselves
a
lot
on
the
fleek
side
to
like
netlify
and
they
pioneered
the
jam
stack
and
basically
like
with
space.
A
We
view
it
as
kind
of
an
extension
of
the
jam
stack,
so
we're
obviously
have
to
call
it
space
jam,
but
essentially
it's
a
way
to
add
web3
functionality
to
jam
stack,
apps
and
so
with
space,
sdk
space,
daemon,
space.js
they're.
Just
these
libraries
that
enable
people
to
easily
package
or
add
functionality
like
you
know,
peer-to-peer
or
you
know
ethereum.
A
While
it's
for
authentication
or
all
the
cool
things
you
could
do
with
textile
into
these,
like
libraries
that
you
could
add
to
a
gatsby
site
or
different
site,
but
part
of
where
we're
going
and
where
space
and
fleek
cross
is
the
main
big
thing
we're
working
on
for
next
year
is
with
fleek
v1.
The
main,
I
would
say
like
thing-
that's
not
great
about
it-
is
it's
still
centralized
to
us
and
our
ipfs
infrastructure.
A
So,
with
space
we
have
a
browser
and
a
desktop
app.
The
desktop
app
has
an
ipfs
node
that
lives
on
the
user's
machine,
and
so
where
we're
really
trying
to
move
with
all
this
space
sdk
these
these
libraries
that
make
it
easy
to
integrate
these
these
functionalities
and
now,
with
ipfs,
becoming
more
natively
integrated
in
browsers
and
things
like
that.
The
idea
is
to
start
with
the
desktop
app
as
a
way
to
for
the
redundancy
layer
of
with
fleek
hosting.
A
We
use
a
cdn
to
make
it
performant
and
then
our
own
ipfs
nodes
under
the
hood
so
now
with
space.
What
we're
essentially
going
to
enable
is
that
an
app
that's
hosted
through
fleek
will
be
able
to
like
have
the
option
to
do
a
community
hosted
version
where
the
sites,
especially
if
they
use
ens,
but
even
if
they
don't
users,
could,
through
the
space,
desktop
app
search
for
dapps
that
they
might
want
to
help
power
or
host,
and
we
would
essentially
handle
the
automatic
updating
of
the
pins.
A
Where
not
only
are
you
taking
advantage
of
edge
infrastructure,
that's
either
run
by
a
company
like
cloudflare
or
netlify,
or
a
network
like
filecoin,
or
you
know
the
retrieval
miner
layer
on
top,
but
also
including
users
in
that
sort
of
redundancy
and
hosting
layer,
but
also
eventually
in
the
future,
in
the
delivery
layer.
And
so
that's
why
yeah
like
I
was
saying
these
updates
to
ipfs
making
them.
You
know
work
more
natively
in
browsers
having
the
way
to
automate
the
pinning
to
like
other
data,
redundancy
layers
from
the
browser.
A
That's
all
super
cool
to
start.
It
would
just
be
with
users
in
the
desktop
app
with
those
local
ipfs
nodes,
adding
to
the
redundancy
and
over
time,
as
we
figure
out
how
to
handle
them
doing
the
delivery
and
stuff
like
that,
which
you
know
we're
we're
kind
of
in
the
same
boat
as
the
community,
with
just
seeing
how
that
develops
what's
possible
and
where
it
makes
sense
over
time.
A
That's
the
idea
is
we'll
be
able
to
effectively
not
only
include
users
in
the
redundancy
aspect
of
hosting
a
site
and
helping
power
adapt
to
really
make
like
decentralized,
hosting
and
community-powered
hosting,
but
then,
eventually
you
know
working
towards
how
do
we
also
enable
more
and
more
of
this
to
be
delivered
by
these
users
and
not
so
much
going
through,
like
http
and
through
the
cdn,
so
that's
kind
of
what's
on
our
roadmap
for
2021.,
we
did
hire
a
full-time
marketer
who's.
Recently,
you
can
see
we've
been
making
some
more
noise
sharing.