►
From YouTube: Building Decentralized Apps using Fleek’s Space Daemon
Description
Space is a new file storage, sharing, and collaboration platform with a focus on privacy. Take control of your privacy while still enjoying all of your favorite features & tools. In this tech-focused talk, we will dive into the technology behind Space, use-cases, and getting started with the Space Daemon.
Join us for Filecoin Liftoff Week, an action-packed series of talks, workshops, and panels curated by the web3 community to celebrate the Filecoin mainnet launch and chart the network’s future. https://liftoff.filecoin.io/
Events take place all week, October 19-23, 2020. #FilecoinLiftoff
For more information on Filecoin
- visit the project website: https://filecoin.io/
- or follow Filecoin on Twitter: https://twitter.com/Filecoin
Get Filecoin community news and announcements in your inbox, monthly: http://eepurl.com/gbfn1n
Chapters
00:00 Fleek Overview
14:00 Workshop building with Fleek’s Space Daemon
A
Our
main
focus
is
building
tools
and
products
that
help
leverage
web3
technologies
and
make
them
accessible
and
easy
to
like
extract
the
value
and
like
the
unique
like
aspects
of
these
new
technologies
and
protocols,
and
so
to
start
where
the
protocols
were
focused
on
like
entirely
our
ipfs
and
textile
and
now
filecoin
is
being
added
to
that
mix
as
well
and
so
on.
The
fleek
side.
A
A
It
makes
the
process
super
seamless.
We
handle
all
the
behind
the
scenes,
things
like
auto,
updating,
ipfs
hashes
when
you
do
a
new
deployment
making
it
like
a
seamless
process.
One
click
link
your
github
and
the
rest
is
automated.
It
also
comes
with
ens
support,
so
if
you
are
using
an
ethereum
name
for
your
dap
or
or
your
site,
we
make
that
process.
Super
seamless,
where
we
auto
update
your
ens
name
with
the
new
hash.
A
If
not
better-
and
you
know,
there's
there's
there's
no
downsides,
and
that
was
one
of
the
goals
we
wanted
to
achieve
is
how
do
we
make
you
know
using
ipfs
for
different
use
cases
just
as
good?
As
you
know,
the
web
2
experiences
currently,
and
so
then
we
also
added
a
storage
product
and
a
pinning
product.
A
So
essentially,
instead
of
just
adding
these
benefits
to
front
ends,
you
know
any
files
or
that
you're
using
ipfs
for
whether
it's
images
for
nfts
or
audio
files,
you
can
get
those
same
benefits
that
we
provide
to
like
our
hosting
and
for
front
ends,
which
is
essentially
like
built
in
cdn
compression,
auto
pinning.
You
know
trying
to
take
away
all
those
headaches
and
make
it
super
easy
to
just
upload
files
to
ipfs,
pin
them
retrieve
them
and
make
it
super
performant.
A
So
we
built
those
two
products
and
then
really
from
building
the
storage
product
as
a
developer
tool.
We,
we
sort
of
felt
that
you
know,
given
the
main
benefits
of
the
technology
that
we
wanted
to
go
after,
were
the
privacy,
encryption
and
p2p
benefits
of
the
technologies,
especially
with
ipfs
and
textile.
A
You
know
we
felt
that
we're
building
a
lot
of
these
cool
tools,
but
maybe
it
would
be
great
if
we
could
showcase
some
of
the
things
that
could
be
built
with
these
new
tools
and
with
these
new
technologies.
And
so
that's
where
we
decided
to
build
the
space
daemon
and
the
space
app.
So
the
space
app
was
an
idea
we
had
to.
Essentially
you
know
the
technology
and
where
it
is
today
and
the
low-hanging
fruit
use
cases
where
we
thought
we
could
extract.
A
A
But
when
we
wanted
to
build
space,
what
we
realized
was
there
was
a
lot
of
like
ground
work.
We
needed
to
lay
in
order
to
just
be
able
to.
You
know
do
simple
things
like
upload
files
share
files
and
a
lot
of
the
work
that
textile's
been
doing
to
really
like
make
it
a
seamless,
developer,
experience
and
package.
It
all
nicely
to
make
the
app
building
experience
super
easy,
and
so
the
space
statement
was
essentially
the
the
kind
of
back
end
framework.
A
We
we
use
to
build
our
own
space
app,
but
we
open
sourced
it
because
we
realize
that
it
could
be
useful
to
anyone
trying
to
create
these
p2p
encrypted
dweb
apps.
On
top
of
these,
you
know
protocols
like
text
style
and
ipfs
and
and
follow
coin,
and
so
that's
where
the
space
stamen
kind
of
came
into
existence.
Two
months
ago
we
have
20
plus
projects
that
are
building
apps
on
top
of
the
space
stamen
already
for
tons
of
different
use
cases,
and
so
it's
super
cool
to
see
that
it
is
open
source.
A
So
you
know,
new
modules
are
being
built
by
us
by
other
people
now
contributing
to
it.
So
we
highly
encourage
that
and
recommend
people
to
you
know,
share
ideas
or
feedback,
and
you
know
let
us
know
if
there's
anything
cool,
you
think
we
should
add
or
that
you're
interested
in
adding
you
know
anyone's
welcome
to
submit
pull
requests,
but
that's
sort
of
what
fleek
is
so
our
main
three
products
are
like,
or
are
the
fleeq
platform
for
the
developer
tools,
such
as
hosting
and
storage,
and
we
plan
to
add
other.
A
You
know
products
to
that
suite
as
well
for
just
things
you
might
want
to
do
or
or
how
you
might
use
ipfs
and
textile
databases
serverless
functions,
authentication.
These
are
the
types
of
things
we're
thinking
with,
so
we
have
like
a
full
dweb
app
and
all
the
services
you
might
need
to
build
those
in
in
a
platform,
and
then
the
space
statement
is
a
separate,
open
source
project.
A
It's
it's
there's
a
github
for
it.
That's
the
best
place
to
find
out
information
about
that,
and
then
we
have
space
which
is
like
a
you
know,
a
private
encrypted
p2p
version
of
dropbox
or
google
drive
we're
launching
the
v1,
which
is
like
the
google
drive
equivalent
in
about
a
week
or
two
it'll,
go
out
to
the
first
beta
signups
and
then
we'll
be
building
apps
like
a
space
docs
like
a
word,
editor
real
time.
A
These
will
all
be
available
to
other
people.
Building
on
the
space
statement-
and
you
know
surface
so,
it'll
just
get
easier
and
cooler
to
use
it
to
build
apps
in
different
ways
in
the
future,
and
so
the
space
product
will
be
open
source
as
well.
The
the
sort
of
you
know
the
the
clouds,
the
storage
and
and
collaboration
platform,
and
so
the
idea
is
well.
You
know
we
might
build
the
first
few
apps
like
the
google,
docs
and
and
and
google
sheets
equivalents.
A
The
idea
is,
since
it's
open
source,
other
people
could
potentially
build
these
apps
and
it'd
be
an
open,
app
ecosystem
and
they
could
be
surfaced
and
kind
of
all
follow
this.
This
common,
you
know
framework
for
these
d
web
apps,
where
it's
you
know,
user
owned
accounts
encrypted
all
built
on
textile
threads
and
buckets
data's
on
ipfs
and
one
of
the
cool
parts
about
it.
A
With
this
you
could,
you
know,
offload
a
ton
of
it
where
you
know
sure,
there's
backup
requests
being
served,
that
you're
paying
for
when
users
are
offline
or
it's
a
new
content
that
needs
to
get
seated.
But
then
you
could
have
users
start
to
see
the
rest
of
it,
and
it
just
seems
like
a
very
natural
evolution
of
the
cloud
where
you
know
now.
The
edge
is
the
big
thing
where
you
know
cdns.
A
The
end
goal
in
our
opinion
would
be
that
you
can't
get
any
closer
to
the
user
than
the
user's
own
machine,
and
we
feel
that
if
you
can
put
an
ipfs
node
on
user's
machine,
whether
it's
in
a
desktop
app
like
it
is
with
the
space
stamen,
where
it's
part
of
the
app
when
they
download
it
or
it's
natively
in
a
browser
like
brave
or
opera
or
maybe
other
main
browsers
in
the
future.
These
things
will
just
get
easier
and
easier.
A
And
so
that's
another
part
of
the
the
cool
thing
about
the
daemon.
Is
you
know
right
now?
It's
it's
mainly
it's
it's
ideal
for
a
desktop,
app
experience
and
the
reason
for
that
is
because
we
could
actually
put
an
ipfs
node
and
a
textile
node
and
the
things
we
need
in
the
user's
machine
itself.
So
they
can.
A
All
these
things
would
become
easier
and
that's
where
we
really
see
things
going
and
that's
kind
of
what
we're
building
towards
so
that's
kind
of
an
overview.
If
you
have
more
questions,
you're
more
than
welcome
to
ask
here-
or
you
know,
find
us
on
slack
and
we'd-
be
happy
to
help
we're
very
like
in
contact
with
all
the
projects
building
on
the
space
station
or
using
fleek
in
general,
and
we
love
working
with
all
the
projects
in
the
ecosystem
and
yeah.
So
that's
a
that's
a
basic
overview.
B
So
now
that
harrison
has
us
fired
up
to
make
apps
on
the
space
daemon.
I'm
gonna
show
you
how
to
get
started
with
that.
So
my
name
is
samuel.
I'm
a
front-end
developer
at
fleek
and
since
I
am
a
front-end
developer,
I
do
a
lot
of
space
demand
integration
in
my
day-to-day
job.
So
in
the
next
like
30
minutes,
I'm
going
to
show
you
pretty
much
like
how
to
do
my
job.
B
B
B
B
I'm
going
to
show
you
give
you
a
tour
of
our
github
repos
because,
like
the
first
thing
that
we
need
to
do
to
make
an
app
on
top
of
the
space
demand
is
to
download
it
and
have
it
running
on
our
machine
because,
in
effect,
the
space
demand
to
use
it.
It's
it's
run
as
a
background
process
like
with
our
space
app.
B
So
here
we
are
at
github.com
hq,
that's
where
we
have
all
our
repos
for
everything
that
is
completely
related,
let's
zoom
a
little
bit,
and
there
are
three
reports
that
I
want
you
to
pay
attention
for
this
evening.
The
first
one
is
space
demon.
So
text
is
where
we
actually
are
gonna
download
the
daemon
now
to
get
the
demon.
There
are
two
ways
to
to
have
it.
The
first
one
is
to
run
it
from
source
if
you
want
to
run
it
from
source.
It's
very
simple:
you
go
here,
clone
the
github
repo.
B
B
B
B
B
We
do
it,
we
do
them
live,
so
it's
demand
ready.
So
now
the
demand
has
started.
So
everything
is
awesome.
Now
that
the
demand
is
charted,
we
can
start
interacting
with
it,
but
that's
the
first
way
to
start
the
event,
also,
a
second
method,
which
is
the
one
I
recommend
a
little
bit
more.
I'm
gonna
move
my
terminal.
B
It's
running
from
an
executable
so
pretty
much
instead
of
downloading
the
source
code
and
generating
the
executable
and
starting
it,
you
can
just
download
the
executable
and
start
it
directly,
which
is
easier
because
the
you,
if
you
do
that
you
don't
you,
do
not
have
to
provide
the
environmental
variable,
which
means
that
it's
a
bit
easier
for
you
to
get
started.
So
it's
the
recommended
manner
to
do
it
so
to
download
the
executable
as
an
alternative
to
running
it
from
source
we're
going
to
be
from
the
space
daemon.
Repo
click
on
releases.
B
B
B
So
if
you
are,
you
are
windows,
you
can
either
give
it
to
the
bits
or
64
bits
on
the
next
same
thing,
to
both
52
bits
or
64
bits,
and
if
you're
on
mac,
you
take
space
darwin,
it's
the
ones
that
correspond
to
mac,
and
then
you
just
execute
it.
It's
very,
very
easy
and,
and
then
on
the
terminal,
once
you
execute
it,
you're
going
to
see
the
same
thing
that
I'm
seeing
right
now,
the
logs.
So
it's
the
exact
same.
B
But
now
that
we
have
the
demon
like
how
do
we
actually
talk
to
the
demon
like
we
want
to
say,
tell
the
demon
like
upload
this
file
list
all
the
files
that
I
have
and
stuff
like
that
to
do
that
we
have
a
space
client.
That's
because
the
space
demand
we
talk
to
it
through
grpc
and
we
have
our
space
client
that
allows
you
to
do.
Your
space
demon
integrations
using
javascript,
so
you
can
use
it
for
your
web
apps
or
for
like
our
space
app.
We
we
do
it
with
electron.
B
You
can
also
do
that
so
to
download
the
space
client
it.
It's
very
easy.
You
go
to
the
the
flick,
hq
git
app
on
space
client,
and
then
you
can
do
a
run.
Yarn
add
flick,
hq
slash
space
client.
We
have
a
npm
repository
for
that
like
this
here
and
then
you,
you
are
then
ready
to
interact
with
the
space
client.
I'm
going
to
show
you
the
example
in
our
in
a
space
workshop
that
we
have
it's
our
church
report
that
I
want
to
show
you.
B
So
if
I
go
back
a
little
bit
test
this,
we
put
a
space
client
workshop.
This
is
just
a
a
workshop
that
we
we
made
so
that
that
we
use
like
to
show
people
how
the
demon
works
and
it's
something
that
we
use
during
our
our
live
sessions,
our
demos-
and
in
this
case
I'm
gonna,
run
you
through
our
workshop,
which
is
going
to
show
you
like
how
to
generate
a
key,
create
buckets
upload
files,
open
the
files
and
and
share
the
files.
B
B
B
Now,
while
it
is
starting
up
what
I
want
to
show,
you
is
where
we
are
where
we
are
initially
initializing
our
client.
So
here
this
piece
of
code
here,
you
might
have
seen
it
in
the
documentation.
I
showed
you
like
five
minute
earlier:
that's
how
you
initialize
the
client,
so
you
import
the
package
just
paste
client
package,
you
you
tell
you
as
an
option.
You
pass
the
port
that
the
space
demon
is
running
on
in
this
case
is
nine,
nine,
nine,
eight
and
then
from
from
then
his
client.
B
I'm
going
to
open
now
this
now
it's
done
starting.
That
is
our
workshop.
There's
steps!
It
goes
from
zero
to
seven.
That
shows
some
basic
function
of
the
the
workshop
of
the
daemon.
I'm
gonna
do
f12
just
show
you
the
console,
because
the
this
workshop
inputs
information
on
the
console-
and
I
want
to
show
it
to
you
so
at
the
first
step,
we're
going
to
do
a
generic
key
pair.
The
reason
for
that
is,
as
as
harrison
explained
earlier,
the
space
project
is
all
about
privacy,
so
like
with
the
space
app.
B
How
it
works
is
that
you
will.
The
user
is
going
to
upload
files
that
are
encrypted
to
a
pfs,
and
this
encryption
is
going
to
be
done
by
a
cryptographic
key
pair,
so
the
user
is
it's
a
bit
like
like
bitcoin,
ethereum
or
anything
or
anything
else
like
that.
The
user
is
going
to
be
identified
with
a
public
key
and
it's
going
to
have
a
private
key,
that
it
will
keep
secret
and-
and
that
is
how
he
is
kept
private.
So
before
you,
you
use
the
space
demand.
B
You
need
to
generate
your
key,
because
that
is
like
your
who
you
are
as
an
individual
within
the
demand.
So
if
I
do
generate
key
pair
here,
it
says
generating
the
key
pair
key
generated.
So
now
the
user
as
a
new
key,
a
new
public
and
private
key
that
and
he
can
now
start
uploading
files
that
are
encrypted.
B
So,
and
also
when
you
do
this,
this
method,
the
generic
key
pair
it-
it
also
tells
the
demon
like
okay,
now
from
now
on,
when
you
create
a
new
bucket
or
upload
files,
will
do
things
like
that.
I
want
to
do
it
with
the
key
pair
that
has
just
been
created,
so
from
now
on,
we
will
not
like
have
to
input
a
key
or
anything
like
that.
It's
going
to
be
all
managed
by
the
daemon.
B
If
I
go
to
the
index,
we
are
importing
the
client,
which
is
which
is
just
this
instead
of
the
client
that
we
initialized
earlier
and
from
there.
We
call
a
a
method
here
and
there's
a
in
in
async
is
asynchronous,
and
it
is
generic
pair
with
forks
degenerate,
the
key
pair,
and
now
we
can
actually
start
using
the
daemon.
B
So
the
first
step
is
we're
going
to
create
a
bucket.
So
you
might
wonder
what
is
a
bucket.
So
if
you
are
familiar
with
amazon
s3,
the
bucket
is
where
you
put
all
your
files
in
so
in
this
case
we
need
to
create
a
bucket
before
we
put
files
into
it.
So
I'm
going
to
hit
it
back,
yet
I'm
going
to
call
it
bucket,
I'm
going
to
do
create
bucket
now
it
says
creating
buckets
and
only
going
to
be
over.
It's
going
to
show
you
some
more
stuff
here
it
is.
B
The
name
is
called
bucket
and,
as
you
can
see
here
on
the
key-
and
here
you
see
ipfs
ashes.
That
is
because,
of
course,
everything
is
also
pushed
to
ipfs.
That's
why
there's
a
hashes
like
that
and
this
information.
I
want
to
show
you
in
the
code
where
to
get
it,
so
I'm
going
to
show
you
here
in
the
workshop
create
bucket.
B
So
it's
the
same
thing
as
before,
so
you
import
the
client,
then
you
you
call
the
create
bucket
method.
You
supply
the
method.
The
right
information
like
in
this
case,
the
flag
which,
which
is
the
name
of
the
bucket
and
then
it
returns
a
response
and
from
the
response
you
you
need
to
call
after
function.
Like
get
bucket
and
and
it
returns
an
object
and
furthermore
it
is
get
bucket.
B
If
I
go
to
docs.flick.co,
you
will
see
that
our
documentation
is
very
complete,
so
we
have
here
like
our
products.
The
first
one
is
the
hosting
product
that
our
er
talked
about
earlier,
the
storage
product
and
then
the
space
given
product
product,
which
is
what
is
interests
us
when
I
click
on
getting
started
and
from
here
we
have
a
lot
of
information
like
how
to
install
and
stuff
like
that,
but
also
we
document
every
single
method
that
is
part
of
the
daemon
like
here,
create
a
client
incent.
B
We
show
you
how
to
create
the
instance
also
print
the
bucket
at
least
buckets
open
files
to
more
auto
function
related
to
sharing
share
a
bucket
generic
public
link
backups.
So
every
method
is
documented
in
our
in
our
ducks
and
it's
very
complete
and
like
we
take
care
like
to
that.
Each
time
we
add
a
new
method,
we
also
put
it
in
the
darks
so
that
devs
that
are
building
on
the
daemon
can
easily
have
the
information
that
you
need.
B
So
I'm
going
to
click
on
the
create
buckets
here.
This
is
the
method
that
actually
you
can
delete
at
the
in
the
workshop,
and
here
we
show
you
like
how
to
use
the
response
object
to
get
all
the
information
that
you
need
like
here,
the
get
key,
the
get
name,
the
path
the
created
at
and
etc.
So,
if
you
need
to
get
some
particular
piece
of
information
with
with
the
methods
you
can
just
look
at
the
docs,
it's
gonna
tell
you
like
what
you
can.
B
The
access
to
and
each
method
is
gonna
have
their
own
methods
like
to
get
information.
So,
just
something
keep
in
mind:
you
don't
have
to
memorize
anything,
it's
all
very
well
documented,
so
I'm
gonna
go
back
to
the
workshop
and
I'm
gonna
now
create
a
folder,
so
our
in
inside
our
buckets,
it's
organized
like
a
file
system,
so
you
have
the
bucket
design
the
root,
the
root
of
the
file
system
and
inside
it
you
can
put
folder
like
a
slash.
B
My
folder
slash,
my
second
folder,
it's
like
like
in
linux,
like
you
have
your
file
system
is
very
similar
to
that,
so
it
makes
it
easier
for
you
to
like
organize
stuff.
So
I'm
gonna
put
a
folder
inside
my
newly
created
bucket,
I'm
gonna
clear
that
so
I
need
to
put
the
name
of
the
bucket.
I
call
it
bucket,
not
very
creative,
but
for
the
name,
the
path
so
in
the
root
I'm
going
to
create
a
folder
called
my
folder,
I'm
going
to
click
here.
B
It
says
folder
created,
so
the
operation
was
successful.
So,
but
now
that
we
have
indeed
created
a
folder,
how
do
we
look
into
the
packet
to
like?
Did
we
really
create
a
folder?
So,
on
the
number
three
we
got
list
directory,
so
text
is
pretty
much
you
give
it
a
folder
and
it's
going
to
look
inside
and
the
root
the
root
of
the
bucket
is
also
a
folder.
B
B
So
now
that
our
folder
is
created,
the
next
step
is
to
upload
a
file
to
the
bucket.
So
on
my
machine
before
the
presentation
I
created
an
empty
file
and
what
we're
going
to
do
is
upload
it
to
the
space
demon.
Now,
on
the
background,
what
is
going
to
happen
is
that
this
file
is
going
to
be
encrypted,
which
means
that
and
then
push
to
ipfs,
which
means
that
only
the
user,
with
his
own
key,
can
read
the
file
but
like
an
important
privacy
aspect
of
the
daemon.
B
So
if
I
want
to
upload
a
file,
what
do
I
do
well
first
step?
I
need
to
tell
the
demon
which
bucket
I'm
going
to
use
so
here
back
yet
10
the
the
path
of
the
file
on
my
machine.
So,
on
my
case,
like
I
told
you,
I
created
the
file
in
my
home,
so
I'm
going
to
put
the
path
of
my
file
this
and
I
call
it
my
file.
B
B
So
here
it's
client
that
add
items
so
the
add
items
method
is
the
one
that
we
use
in
order
to
upload
a
file
to
a
bucket.
So
it's
just
the
same
thing
that
we
we
did.
We
put
the
name
of
the
backyard,
the
third
the
target
path,
which
is
the
path
inside
the
bucket
and
the
source
paths,
which
is
the
path
on
the
machine
and,
as
you
can
notice
here,
it's
an
array.
So
it
means
that
you,
if
you
have
multiple
items
to
upload,
you
don't
have
like
to
call
this
like
10
times.
B
You
can
just
pass
in
the
array,
your
10
files
and
it's
just
gonna
get
uploaded,
and
then
it
returns
an
upload
stream,
which
is
just
a
normal
node.js
stream.
You
can
look
at
the
documentation
of
node.js
for
that.
If
you
want
to
learn,
but
it's
very
simple,
like
you
do
on
data,
and
then
it
gives
you
data
and
then
you
can
interpret
that
the
we
calling
it
results,
which
you
can
just
look
at
the
documentation
like
which
method
you
need
to
call.
B
B
B
What
you
do
you
put
the
name
of
the
bucket
as
all
the
before
then
you
give
the
path
inside
the
bucket
of
the
file.
I
want
to
decrypt.
So
it's
a
file.
You
call
my
file
and
it's
my
in
my
folder,
so
I'm
going
to
do
slash
my
folder
slash
my
file,
I'm
going
to
do
open
file
and
now
look
at
the
result
from
the
console.
I
know
it's
pretty
small
if
I
can
make
it
bigger.
B
B
So
so,
if
I
want
to
read
it,
I
can
do
chats
enter
cat
is
just
reads
the
content
of
the
file,
and
it
says
hello,
exclamation,
point
exclamation
point
which,
which
is
what
I
put
in
the
file
originally
as
we
can
verify
here.
I
do
slash
on
slash
yeah,
that's
my
file.
Indeed,
it's
the
same
thing,
so
the
file
was
correctly
uploaded.
B
Next,
I
want
to
show
you
sharing
a
bucket
now,
the
the
this
demand
pretty
much
it's
not
just
for
uploading
files.
You
can
do
a
lot
more
to
with
it
like
you
can
share
your
your
file
or
your
bucket
with
a
another
user,
and,
like
I
told
you
earlier,
the
users
are
represented
with
their
public
key,
so
it
so
just
still
respect
the
user's
privacy,
despite
being
shared
and
test
sharing.
The
other
option
that
we
have
alongside
it
is
that
we
can
share
to
a
specific
person
to
multiple
person.
B
B
So
if
I
want
to
join
the
bucket,
I
copy
this
information
over
so
like
I
put
the
name
here,
the
key
copy
that
then
I
copy
the
addresses
and
then
I
would
do
like
join
bucket
and
it
would
join
the
bucket
now.
Of
course
I
can.
I
cannot
join
my
own
bucket.
It
makes
no
sense,
but
if
it
was
another
user,
he
could
then
like
join
the
bucket,
but
this
share
bucket
until
joint
bucket
is
just
one
way
to
share
like
the
their
other
way
to
share.
B
If
you
look
at
the
documentation
like
on
sharing,
we
have
a
lot
more
functions
that
you
can
use
like
a
generic
public
link
stuff
like
that.
We
also
have
a
notification
system
that
is
related
to
that
because,
like
I
told
you
like,
we
are
developing
a
space
app
with
that
and
with
the
app
what
we
do
is
if
a
person
shared
a
person,
we
want
a
notification
to
appear,
and
so
we
just
basically
mentioned
like
all
kind
of
stuff,
like
a
notification
system
like
that
and
there's
also
more.
B
B
The
the
company
has
a
bunch
of
product
that
we
use
a
lot
in
with
the
daemon
and
pretty
much
with
all
our
fleek
products
like
buckets
threads
stuff
like
that,
and
the
power
gate
is
like
a
term
us
product
that
is
to
to
interact
with
the
falcon
network
and
it's
like
it,
bundles,
a
falcon
node,
a
lotus
node
and
an
ipfs
node,
and
in
our
case
with
our
fico
integration.
We
do
that
with
textiles
powergate.
B
But
this
this
feature
is
not
yet
fully
ready,
we're
more
at
the
stage
where
we
are
working
on
it.
So
if
you
want
to
play
with
the
part
this
this
part,
we
have
some
instructions
over
here
completely
at
the
bottom,
at
powergate
and
to
and
to
use
it.
You
need
to
go
to
the
filecoin
branch
of
the
space
demand
download.