►
From YouTube: Textile Office Hours #1
Description
Have questions on Textile tech like Powergate and Buckets? Ask here!
Keep up with events for the Filecoin community by heading over to the Filecoin project on GitHub:
https://github.com/filecoin-project
Check out the Filecoin community resources:
https://github.com/filecoin-project/community
And stay connected on Filecoin Slack:
https://app.slack.com/client/TEHTVS1L6
A
Welcome
good
morning
this
is
our
first
office
hours
of
what
I
think
are
many
textile
office
hours
over
the
next
few
weeks.
So
that's
great.
I
don't
have
any
really
strong
agenda
today.
A
So
if
those
of
you
that
are
joining
have
specific
things
that
you
want
to
learn
about,
or
if
you
have
specific
questions,
technical
questions
or
you
know
idea,
questions
or
or
anything
in
general
feel
free
to
either
add
those
to
the
chat
and
I'll
just
I'll
I'll
go
through
those
and
and
answer
them
or
if
you
want,
we
can
get
you,
we
can
get
you
mic'd
and
you
can
just
ask
those
and
we
can
have
a
little
conversation.
A
So
does
it,
I
guess
so.
Does
anybody
have
a
question
that
wants
to
kick
off?
If
not,
if
I
don't
see
anything,
I
can
jump
into
just
kind
of
pointing
out
some
of
the
key
resources
that
we
have
and
get
everybody
kind
of
oriented
in
the
textile
stack
and
what's
available
for
you
to
use
yeah.
So,
okay,
I'm
happy
to
do
the
intro.
A
I
did
a
little
intro
yesterday
in
the
kickoff
in
the
kickoff
meeting,
but
I'm
happy
to
just
kind
of
go
through
that
again.
Let
me
just
bring
that
up,
and
maybe
those
of
you
that
were
there
yesterday
can
kind
of
skip,
can
kind
of
skip
this
part.
A
So
I'm
I'm
andrew,
I'm
with
textile
we're
here
to
support
teams
that
are
building
on
filecoin
generally
building
on
filecoin,
but
then
specifically
for
the
slingshot
competition
and
the
reason
that
we're
here
supporting
is
because,
for
the
last
well,
for
the
last
few
years,
textile
has
been
really
dedicated
to
building
developer
tools.
On
top
of
decentralized
networks.
A
We've
focused:
we've
focused
a
lot
of
energy
on
building
developer
tools
on
top
of
the
ipfs
ecosystems
and
stack
and
then
more
recently,
we've
put
a
lot
of
attention
into
building
new
developer
tools
on
top
of
the
filecoin
stack
and
our
objective
when
we're
building
these
tools
is
to
help
onboard
developers
faster
help.
A
You
figure
out,
if
your
idea
will
work
on
these
networks
and
move
quickly
to
the
next
idea
or
or
double
down
and
go
deeper
into
your
idea
and
so
far,
we've
seen
that
a
lot
of
technologies
built
for
decentralized
applications
and
for
applications
in
the
blockchain
and
peer-to-peer
protocol
space
are
difficult
for
developers
to
figure
out
if
their
idea
will
even
work
initially.
A
And
so
we
like
to
talk
about
internally,
we
have
a
kpi
that
might
sound
a
little
backwards,
but
we
call
it
time
to
failure,
and
so
what
we
really
want
is
developers
to
have
a
very
rapid
time
to
failure
and
that's
super
important,
because
developers
need
the
ability
to
figure
out
if
their
idea
will
even
work
before
they
can
figure
out
if
they
can
dedicate
real
time
to
making
it
a
product
or
releasing
it
to
public
releasing
to
the
public
and
so
time
to
failure
is
super
important
and
the
way
that
you
do
that
is
you
have
easy
onboarding.
A
And
so
we
teamed
up
with
protocol
labs
during
this
competition,
because
a
lot
of
these
tools
that
we've
been
building
on
the
file
coin
space
are
now
ready
for
you
to
get
your
hands
on
and
start
testing
and
start
building
with,
and
we
want
to
be
there
to
help.
A
You
do
that
and
our
reward
for
doing
this
is
that
we
get
a
ton
of
feedback
from
you
going
and
testing
things
telling
us
where
it's
not
working,
and
then
we
can
improve
those
things
before
mainnet,
and
so
your
feedback
is
super
important
and
it's
one
of
the
most
valuable
things
we
can
get
right
now.
So
also
thank
you
for
showing
up
today,
because
this
is
the
start
of
that,
and
so
you
can
think
of
textile
delivering
kind
of
four
things.
The
three
things
that
to
start
with
are
infrastructure
and
I'll.
A
Give
you
a
kind
of
a
tour
of
of
this
in
a
second
but
infrastructure
is
we
are
building
a
stack
on
top
of
the
lotus
implementation
of
of
the
filecoin
spec,
so
we're
building
a
stack
on
top
of
lotus
that
allows
application
developers
and
system
developers
to
use
filecoin
as
a
storage
as
a
storage
api
in
the
in
in
their
stack
and
that
system
is
called
powergate,
you
can
run
powergate
on
your
own.
You
can
go
to
the
github
repo.
You
can
check
it
out.
You
can
start
running
powergate.
A
You
can
connect
to
the
testnet
and
do
all
the
synchronization
synchronization
and
use
those
apis.
We
also
have
a
super
easy
to
use.
Localized
mock
of
the
network
called
localnet,
and
that's
for
that's
really
for
you
to
start.
If
you
want
to
use
powergate
go
use,
go
look
at
localnet.
It
lets
you
spin
up
the
whole
thing
and
start
using
the
entire
api
in
just
a
couple
minutes,
and
you
can
use
that
for
local
development.
You
can
use
that
for
your
continuous
integration.
A
You
can
really
see
how
your
application
will
work
on
the
network
before
you
push
it
to
a
real
running
network
with
real
miners
like
testnet.
Another
piece
of
infrastructure
we
have
is
those
powergate
instances
that
are
connected
to
testnet.
You
can
run
your
own,
but
we're
also
offering
hosted
versions
a
host
of
instances
of
those
for
teams
during
this
competition
and
so
I'll
share
with
you
how
to
get
that
we
have
api
and
access
control.
A
So
a
lot
of
applications
that
will
be
built
on
filecoin
are
going
to
need
to
think
about
who's
really
responsible
for
the
data
being
stored,
who's
paying
for
it
who
gets
access
to
these
apis
that
are
being
provisioned
and
so
powergate
doesn't
have
any
strong
opinions
about
that.
You,
it's
really
for
application
developers
and
system
developers
to
put
their
own
put
it
in
behind
their
own
systems,
but
textile
also
offers
a
system
called
the
textile
hub,
which
has
all
the
api
mechanisms
for
you
to
do
user
management
and
give
api
access
to.
B
A
And
two
applications
and
embed
in
in
mobile
and
websites,
and
and
so
we
can
talk
about
the
textile
hub
a
bit,
but
the
textile
hub
is
the
is
where
one
of
the
primary
implementations
of
textile
buckets
exist
and
you
can
think
of
textile
buckets
more
or
less
like
s3
they're,
dynamic,
folders
of
data,
but
different
than
s3.
A
When
you
push
to
a
bucket
it,
it
exists
on
ipfs,
and
so
this
is
a
way
of
managing
dynamic
folders
on
ipfs
and
since
we've
started
working
on
filecoin,
we've
added
to
the
textile
hub,
actually
a
powergate
instance,
and
so
you
won't
get
the
full
powergate
api
from
the
textile
hub.
But
you
can
do
a
lot
of
powergate,
filecoin
and
powergate.
Things
such
as.
A
If
you
have
a
bucket,
you
can
call
an
archive
command
and
that
archive
command
will
send
the
entire
current
state
of
the
bucket
to
file
coin,
create
a
deal
store
that
data
on
filecoin
and
give
you
back
the
metadata
about
that
deal
and
that's
all
that's
all
wrapped
up
together
into
a
very
comprehensive
set
of
apis.
A
And
then
the
last
thing
is
scaling.
Interoperability
docs.
These
are
all
things
that
we
work
about,
who
work
on
and
think
about
a
lot,
and
so
we're
kind
of
here
as
a
resource.
If
you
need
help
thinking
about
how
to
scale
your
app
using
our
apis
or
using
powergate.
If
you're
thinking
about
how
to
format
your
data,
how
to
get
your
data
onto
these
networks
or,
if
you're,
just
looking
to
learn
more
and
go
deeper,
we
spent
a
lot
of
time
on
documentation
and
can
point
you
in
the
right
ways.
A
So
a
little
bit
on
the
deep
dive
of
powergate
there's
a
ton,
there's
a
ton
to
unpack,
but
just
kind
of
just
kind
of
like
the
mid-level
view
here
of
the
of
the
technology.
It's
actually
a
stack
of
technologies,
so
it
takes
the
filecoin
network
and
has
an
opinion.
A
So,
whereas
say
lotus
is,
is
a
very
flexible
sort
of
sort
of
node
that
doesn't
have
any
any
opinions,
but
it
means
that
you're
going
to
have
to
build
you're
going
to
have
to
build
components
on
top
of
it
to
make
it
work
in
your
system,
textile
built
powergate
with
some
opinions
about
using
how
to
use
lotus
within
within
a
system
and.
B
A
Way
it
does,
that
is
the
every
powergate
deployment
is
a
stack
of
technologies.
It
includes
a
lotus
node.
It
includes
an
ipfs
node.
It
includes
the
powergate
sort
of
sort
of
running
system
and
state
management
and
includes
the
apis
that
it
exposes,
and
it
has
a
few
different
client
libraries
for
connecting
to
it.
A
Powergate
when
you
store
data,
it's
managing
things
like
your
wallets,
so
creating
and
managing
wallets
and
and
and
what
sort
of
deals
and
data
each
wallet
address
is
responsible
for
so
that
those
sorts
of
state
that
sort
of
state
is
managed
by
powergate.
A
It
also
does
things
like
helping
you
better,
select
and
filter
which
miners
a
deal
is
being
sent
to
it,
helps
you
manage
things
like
replication,
a
lot
of
a
lot
of
those
pieces,
and
so
we
can
kind
of
get
into
that
today
or
in
later
office
hours
as
well
I'll
go
through
these
actually
off
the
slides.
The
links
so
textile
buckets.
Alternatively,
is
it
was
really
built
ip
for
as
an
ipfs
solution,
first,
so
thinking
through
how
to
deal
with
dynamic
folders
on
ipfs.
That
was
really
the
key
motivation
of
buckets.
A
But
now
with
filecoin,
it
offers
a
really
neat
way
for
taking
entire
folders
and
snapshotting
them
to
filecoin
and
what's
really
cool
is
I'll.
Show
you
an
example
of
this
or
where
you
can,
or
you
can
watch
an
example.
This,
but
buckets
is
essentially
it
is
a
peer-to-peer
protocol
for
pushing
dynamic
folders,
and
so
you
can
actually
run
bucket
daemons
on
a
bunch
of
different
computers
or
servers
or
wherever,
and
you
can
actually
have
them
pushing
and
synchronizing
folders
with
themselves
textile.
A
We
run
sort
of
a
very
large
bucket
endpoint
on
the
hub
that
will
let
you
push
your
folders
to
the
hub.
That's
really
useful
for
an
ipfs
user,
because
you
can
build
an
application
that
is
creating
data
on
ipfs
and
then
pushing
it
to
a
remote,
ipfs
node,
which
would
be
on
the
textile
hub
and
then
that
that
source
of
the
data
could
go
away
so
like
if
it's
on
a
laptop
they
could
close
their
laptop,
but
that
data
would
still
be
live
on
the
network
because
it
would
have
been
pushed
to
the
hub.
A
But
that
sort
of
introduces
this
reliance
on
the
textile
hub.
Obviously,
as
an
api,
and
so
what
filecoin
lets
us
do
is
actually
get
back
out
of
the
way,
and
so
when
you
push
data
to
the
hub,
what
you
can
do
is
call
that
archive
command,
which
you
see
here
in
the
in
the
cli
example.
You
can
call
that
archive
command
and
it
will
take
that
take
that
data
set
store
it
to
filecoin.
A
Give
you
back
the
information
about
getting
that
data,
the
information
about
where
that
data
is
stored
in
filecoin.
You
can
take
that
information
and
leave
the
hub,
never
come
back
again
and
you
could
go
to
the
the
file
coin
network
directly
and
always
get
that
data
back
out
from
filecoin,
which
is
super
cool
because
because
now
you
don't
have
to
you,
don't
have
to
believe
in
the
hub
at
all-
and
I
I
I'd
love
you
to
believe
in
the
hub,
but
that's
the
wrong
way
to
build
an
api.
A
You
don't
have
to
believe
in
the
hub,
but
you
can
use
the
hub
to
help
scale.
Your
applications
help
onboard
users,
but
have
this?
Have
this
attack
connection
to
a
decentralized
network
for
storage,
which
is
awesome?
So
it's
super
easy.
It
takes
literally
three
commands
to
get
your
first
data
on
onto
the
filecoin
network.
You
create
a
bucket
through
the
initialization
command.
A
You
push,
whatever
data
is
in
the
folder
where
you've
created
the
bucket,
and
then
you
call
this
archive
command
and
archiving
is,
is
a
full
set
of
steps
to
get
data
on
file
coin,
so
it
may
take
time
it
does
take
time,
but
you
can
leave
and
you
can
come
back
later
and
check
the
status
of
that
and
you
could
or
you
can.
You
can
watch
it
live
and
we
can
get
into
some
examples
of
that
as
well,
but
definitely
if
you've
not
done
anything
on
filecoin.
A
But
it's
also
it's
also
a
great
tool
to
build
applications
or
build
pipelines
on,
and
so
you
can
do
that
through
through
the
command
line
tool
through
the
apis,
or
we
have
a
javascript,
client,
javascript
client,
for
example.
Then,
and
again
I'll
show
you
that
off
these
slides
so
again,
infrastructure,
api
and
access
control,
scaling
interoperability,
docs.
Those
are
all
things
you
can
lean
on
us
to
help
or
give
you
or
give
you
feedback
on
and
we'll
be
here
in
office
hours.
You
can
find
us
in
the
file
coin.
A
Slack
and
I'll.
Give
you
I'll
give
you
a
couple
places
to
find
us
there
and
but
then
the
last
thing,
that's
that,
I
think,
is
really
one
of
the
most
valuable
things
coming
from
textile.
Is
that
we're
building
a
really
strong
community
of
developers
with
a
lot
of
different
perspectives
about
how
to
build
apps,
how
to
deliver
real
value
to
end
users?
A
What
this
looks
like
to
bring
decentralized
networks
to
end
users
and
they're,
really
driving
us
to
build
better
apis
and
to
scale
the
hub
and
to
scale
each
of
these
components
and
we're
learning
from
that
every
day
and
kind
of
just
building
better
technology.
A
That
then
you
can,
then
you
can
use
and
so
definitely
share
your
ideas
if
you're,
building
on
textile
and
and
kind
of
tap
into
this
community,
because
they're
also
very,
very
active
and
and
always
seem
to
be
willing
to
give
feedback
and
help
share
the
things
that
they've
learned
so
okay,
so
that's
kind
of
the
that's
kind
of
the
intro
to
textile,
and
why
we're
here?
A
A
If
I'm
designing
a
system
to
have
an
availability
of
response
times
of
less
than
30
seconds,
what
are
the
requirements
that
are
needed
for
an
ipfs
node
to
have
approximately
10
terabytes
of
data
available?
So
it
doesn't
have
to
go
to
the
file
coin
storage
layer
to
get
that
data,
as
it
would
take
too
long
to
respond
to
the
user
request.
A
Well,
that's
a
really
interesting
question
and
okay.
So
that's
that's
not
actually
a
good
one.
For
me
to
answer.
I
am
like
the
worst
infrastructure
person
around
so
a
couple
thoughts
here,
so
it
sounds
like
you
want.
It
sounds
like
you
want
an
ipfs
node
that
can
handle
10
terabytes
of
data
or
a
series
of
ipfs
nodes
like
what's
available
in
ipfs
cluster
that
can
handle
10
terabytes
of
live
data
on
the
network.
We
are
joined
by
one
person
that
I
think
might
have
some
ideas
here.
A
B
B
To
to
give
some
numbers
the
team
at
protocol
labs
that
runs
the
the
infrastructure
that
supplies
the
proofs,
I'm
sorry,
the
proof
parameters
for
the
pipeline
network
serves
about
two
terabytes
of
data
from,
I
believe,
a
three
machine
cluster
and
those
machines
are
not
too
they're
not
like
too
out
there.
I
believe
they're,
I'm
almost
certain.
There
are
aws
instances
that
I
can
don't
quote
me
on
that.
So
what
you
would
need
to
do
something
like
this
is
basically.
B
First
of
all,
you
need
to
test
a
lot,
because
it's
not
only
the
type
of
hardware
that
needs,
but
also
what
how
your
data
is.
Chunked
and
organized,
for
example,
for
the
proofs
we
every
single
block
that
we
have
is
a
custom
one
megabyte
large
block.
I
suppose
you
know
the
host
of
ipfs,
because
we
know
that
those
are
incompressible
data
streams
that
they
cannot
be.
B
They
cannot
be
used
partially.
You
basically
need
to
download
the
entire
thing,
no
matter
what
so,
depending
on
your
data
structure
and
the
type
of
access
that
you're
interested
in,
are
you
always
going
to
be
looking
at
the
entire
thing?
Are
you
going
to
use?
Looking
for
parts
of
the
data,
you
basically
would
need
to
benchmark
this
because
we
do
not
have.
B
B
So
yeah
specific
wise.
You
don't
really
need
any
specific
resource
that
I
can
think
of
everything
scales
relatively
linearly
latest
voipfs
had
a
number
of
fixes
for
memory
usage
and
things
like
that.
So
yeah,
the
only
don't
think
would
they
be
a
fast
disks,
fast
network
and
testing
your
setup
before
you
record
the
working
product.
A
Yeah
cool
super
thanks
very
much
for
jumping
in
on
that.
I
think
so.
Fast
discs
a
lot
of
testing.
The
data
architecture
is
super
important
here
and
and
but
I
think
he
hit
on
one
thing
that
I
think
is
really
key,
especially
for
people
that
are
new
in
this
in
this
kind
of
community
and
ecosystem.
A
Is
that
if
you
try
to
build
that
and
you
do
it
in
an
open
way,
with
a
lot
of
really
good
kind
of
lessons
that
other
people
can
follow,
whether
that's
benchmarking
or
writing
up
the
progress
process
and
what
you
find
along
the
way
you'll
be
a
hero
in
this
community.
A
So
I
definitely
encourage
trying
these
things,
but
doing
it
in
a
way
that
other
people
can
learn
from,
because
I
think
a
lot
of
people
go
and
try
these
things
a
little
bit
in
a
vacuum,
and
it's
very
it's
very
impossible
for
us
to
then
answer
for
the
next
person.
What
happens
when,
when
this
occurs,
and
so
definitely
consider
that
idea
of
of
go
and
go
and
try
this?
Do
it
with
some
testing
and
and
figure
out
how
to
share
that
with
with
everybody
else,
okay,
cool.
A
So,
okay,
so
the
resources
are
pretty
straightforward
to
navigate
the
first
main
one.
That
kind
of
can
be
a
good
landing
point
to
find
all
the
rest
as
far
as
the
textile
stack
goes,
and
what
we're
making
available
is
the
doc
site
on
textile
and
I'll
just
kind
of
point
you
directly
to
a
few
key
elements
on
here.
The
first
one
is
that
if
you
want
to
give
that
three
line
command,
it
will
be
four
line
command.
Actually,
if
you've
never
used
the
hub
before,
because
you'll
have
to
create
an
account
first.
A
But
if
you
want
to
try
that
sort
of
three
line
command
for
creating
a
bucket,
pushing
the
bucket
and
and
starting
your
first
file
coin
deal
the
the
things
that
you're
going
to
do
are
are
in
the
documentation
under
the
getting
started.
So
you'll
just
basically
go
over
the
installation
and
setup
of
the
cli,
and
we
have
builds
of
the
cli
for
all
major
platforms.
A
So
you
can
go,
get
the
get
the
cll
cli
install
it
create
your
account
and
then
the
next
thing
that
you're
going
to
do
is
is
jump
down
into
the
bucket
storage
component.
A
Here-
and
you
can
read
through
this,
the
key
thing
that
you'll
want
to
to
get
to
is:
is
the
archiving
flow,
so
once
you've
created
a
bucket,
you
can
read
through
what's
happening
when
you
store
that
bucket
on
filecoin-
and
this
is
pretty
brief,
but
it
does
also
have
links
to
a
couple
of
neat
things,
one
of
which
is
is
a
isn't
actually
aging
already
things
move
so
fast,
it's
a
little
bit
of
an
aging
blog
post,
but
it
it
contains
a
lot
of
a
lot
of
things
that
are
are
really
good
insights
on
how
buckets
work,
and
so
that
might
be
very
interesting
to
you,
especially
if
you,
if
you've
been
building
on
file
coin
or
or
sorry
if
you've
been
building
on
ipfs
or
if
you
are
interested
in
building
really
interesting
data
workflows
on
ipfs,
we've
done
a
lot
in
buckets
that
you
could
leverage
or
learn
from
in
synchronizing
data
across
ipfs
nodes,
and
this
this
blog
post
goes
into
it
more
than
any
place
else.
A
But
this
sort
of
the
hidden
gem
in
this
blog
post
is
until
the
end
and
it's
about
it's
where
it
talks
about
what
happens
if
you
want
your
bucket
on
on
filecoin
and
specifically
this
archive
command
and
in
this
in
this
blog
post.
There's
this
video
and
this
video
shows
the
exact
workflow
I
mentioned
before,
which
is
creating
a
bucket
pushing
that
bucket
to
the
remote
textile
hub.
So
now
your
data
is
on
ipfs,
but
it
is
managed
on
an
on
a
node
behind
sort
of
the
textile
set
of
apis.
A
So
now
you
want
to
ensure
that
that
data
exists
on
a
decentralized
network
like
filecoin
and
so
then
you'll
archive
the
bucket
and
take
the
data
about
the
deal
and
in
this
in
this
video
he
goes
off
to
a
lotus
note.
Nothing
to
do
with
textile
takes
that
deal
and
extracts
it
back
out
of
filecoin.
So
that's
sort
of
disintermediating
textile's
own
api
from
from
your
data,
which
is
super
cool,
so
check
that
out
the
only
other
things
let's
see
to
show
so
in
in
actually
in
our
documentation.
A
We
have
pretty
good
links
here
to
to
most
other
sites.
So,
but
one
of
them
is
the
one
of
them
is
the
open
source,
so
textile
is
all
open
source.
So
if
you
go
to
our
organization,
you
can
you
can
find
a
lot
of
this
stuff,
but
just
specifically
here's
the
powergate
stack.
So
if
you
want
to
run
your
own
powergate,
this
is
where
you
can
go
dig
into
that
code
in
our
documentation.
We
also
give
you
information
on
running
your
own,
your
own
powergate.
A
We
have
docker,
we
have
docker
images
and
we
have
docker
compose
files
that
you
can
run
and
all
of
those
are
available.
I
believe
in
sort
of
make
commands,
so
you
can,
you
can
sort
of
make
you
can
make
build
you
that's
for
the
cli
you
can
make.
You
can
make
a
instance.
That's
going
to
connect
to
testnet,
but
really
cool-
and
I
mentioned
this
before-
is
the
local
net,
so
you
can
make
localnet
and
that's
going
to
give
you
the
entire
mocked
filecoin
network
running
directly
on
your
machine.
A
That's
going
to
be
great,
like
practically
no
bandwidth
requirements,
it's
going
to
set
up
in
under
five
minutes.
It's
going
to
have
the
full
set
of
apis
for
you
to
build
and
test
on,
and
so
you
don't
need
anything
else
to
get
started
actually
seeing
how
your
idea
will
flow
through
the
network.
This
way,
it
even
has
mocked
miners
that
are
going
to
run
right
on
your
network
and
accept
your
deals,
and
so
you
don't
even
need
to
hit
a
faucet
to
get
to
get
filecoin
to
use
this
network.
A
It's
all
on
your
machine,
and
so
that's
that's
a
really
great
resource.
And
so
again
the
documentation
has
the
overview
of
that.
The
repo
has
the
docker
commands
that
you'll
want
to
run,
and
so
you'll
see
it's
just
this
one
liner
to
get
the
whole
stack
running
directly
on
your
machine
and
then
once
you've
moved
through
that.
A
If,
if,
if
you've
decided
to
use
powergate
and
not
use
the
textile
hub,
but
if
you're
using
powergate
for
for
your
idea
and
you've
moved
and
you've,
you've
tried
out
the
local
net
and
you've
tested
these
apis
and
you're
you,
you
see
how
your
workflow
is
going
to
come
together
and
now
you
want
to
test
it
on
on
test
net
or
you're,
ready
to
actually
start
pushing
real
data
test
net.
You
can
run
this
all
on
your
own.
A
You
can
deploy
this
to
to
to
your
own
set
of
servers
or
on
your
own
stack
and
there's
instructions.
To
do
that.
We
also
are
offering,
like
I
mentioned,
hosted
powergate
instances
that
we
run
for
you
and
give
you
access
to
the
full
api.
And
if
you
want
to
get
one
of
those
you
can
find
you
can
find
this
link
all
over,
but
the
hosted
powergate
request
form.
A
So
I
really
recommend
getting
through
the
local
net
testing
step
before
you
apply
here
so
that
you
have
a
sense
of
what
powergate
actually
does
before
you
are
requesting
these,
because
when
you
request
one
of
these
stacks,
we
spin
up
a
fully
synced
lotus.
Node,
a
fully
capable
ipfs,
node
and
and
the
full
powergate
stack
and
give
that
to
you.
So
this
isn't
this
isn't
a
small
request.
A
So
that's
a
little
bit
more
on
the
docs
and
links
to
share,
and
I
see
a
few
more
questions
here,
I
think
about
the
performance
of
ipfs.
What
we
should
do
is
get
you
probably
connected
to.
A
I
didn't,
I
actually
didn't
show
them.
Let
me,
I
think,
yeah,
sorry,
there's
a
question
about
performance
and
finding
the
github
repo
for
ipfs
benchmarks.
I
was
going
to
say
I'm
just
the
wrong
person
to
ask
for
that
for
ipfs
benchmarks
specifically,
but
I
can
help
you
get
directed
towards
some
people
that
will
be
able
to
point
to
resources
and
existing
info,
and
so
what
I
didn't
show
is
that
we
have
two
channels
in
in
in
the
file
coin
slack.
A
This
is
really
like
where
the
community
exists
and
so
should
be
a
resource
to
most
teams,
even
if
you're
not
asking
questions
and
similarly,
if
you're
going
to
go
down
the
buckets
route
or
you're
interested
in
the
buckets
root,
there
is
a
brand
new
channel
called
buckets
users,
and
you
can
find
that
in
the
file
point
slack
as
well.
A
We
also
have
like
more
general
textile
users
in
our
own
community
slack,
but
if
you're
in
the
file
point
slack
already,
don't
feel
obligated
to
go
join
that
you
can
find
us
right
on
these
two
dedicated
rooms,
so
buckets
users,
powergate
users,
and
so
with
that.
I
think
that
this
outstanding
question
about
the
filecoin
benchmarks.
A
A
Okay,
cool
and
then
peter
mentioned.
This
is
just
for
people
watching
the
video
later
that
there
will
also
be
a
session
on
wednesday,
where
they'll
touch
on
some
of
these
topics
about
ipfs
and
ipfs
scalability
that
and
that
the
material
for
wednesday
is
still
being
prepared.
So
getting
these
questions
actually
into
into
slack
also
will
help
them.
Remember
that
these
are
the
types
of
questions
that
are
coming
up
and
make
sure
that
they
get
them
covered
next
week
cool.
A
So
if
there
are
no
more
urgent
questions,
maybe
we
can
all
go
back
to
the
async
slack
chat
world
and
I'll,
be
there
all
day.
So
people,
if
you
just
didn't,
ask
your
question
or
hasn't
popped
in
your
mind,
yet
grab
us
on
one
of
those
two
channels:
buckets
users
or
powergate
users,
and
we
can
get
you.
We
can
get
you
answers
or
we
can
or
we
can
get
you
links
or
resources
over
there.
A
Okay
and
then-
and
then
one
more
note
for
the
video
reviewers
is
that
all
upcoming
events
are
on
sleek
slingshot
dot
filecoin.io,
so
you
can
find
whatever
else
is
coming
this
week.
Next
week
I
have
some
master
classes
coming
on
using
buckets,
I'm
using
powergates,
I
have
more
office
hours
and
then
all
the
teams
at
filecoin
have
a
bunch
of
different
office
hours
and
events
that
you
can
tap
into
to
learn
more.