►
Description
This week we hear from Fission about building native web apps and their use for front end coding
https://fission.codes/
Fission Drive is here:
https://drive.fission.codes/
Get involved with Fission:
https://events.fission.name/2020/ipfs-community-call
https://fission.codes/discord
https://talk.fission.codes
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
B
All
right,
hi,
everyone
welcome
to
the
ipfs
weekly
cool
is
here.
It
is
this
this
thing
you're
here
it
is
the
9th
of
March.
Today
we
have
fishin
who
are
going
to
talk
about
how
how
they
are
using
ipfs
and
how
they're,
integrating
with
will
you
said
web,
that's
the
old
web
from
where
with
we're
standing
so
that
will
be
super
interesting.
B
C
This
is
the
talking
head
over
here,
Brooklyn,
depending
on
where
you
are,
has
a
lovely
Illustrated
face,
and
we've
got
some
other
folks
from
the
fission
team
on
as
well
Steven
and
styling
infirm,
ganked,
Belgium,
Brooke
and
I
are
in
the
Vancouver
area.
We
are
a
distributed
team,
and
now
you
should
once
again
see
a
participation,
yeah
amazing,
thank
you.
C
I
am
the
non
technical
hand
waver
the
rest
of
my
team
are
engineers,
I
mean
theoretically,
I
am
as
well,
but
I
tend
to
just
break
things.
That's
what
testing
is
for,
and
you
know
love
thank
you
so
much
for
having
us
and
love
to
get
feedback
on
what
we're
working
on.
So
what?
If
front-end
code
was
all
you
needed
because
front
end
is
really
the
part
that
humans
interact
with
it's
not
gonna,
go
away,
browsers,
keep
getting
more
powerful.
C
We've
got
a
bunch
of
what
we're
starting
to
call
public
infrastructure,
so
we
see
ipfs
and
the
global
and
interplanetary
network
as
being
public
infrastructure,
and
then
the
other
thing
is
sort
of
the
rise
of
edge
computing
server
list
kind
of
edge
kind
of
portable
compute.
We
use
a
couple
of
different
words
for
this
and
I
think
we're
just
starting
to
see
this
come
into
focus
I
mean
really
all
apps
are
hard,
but
in
particular,
we've
been
building
lamp
stack
apps
for
30
years,
and
you
have
to
do
a
front
end.
C
You
have
to
do
a
back
end
and
fun
times.
You
have
to
add
a
sprinkling
of
DevOps
to
make
this
stuff
work
and
we
have
breaches
all
the
time
and
and
we've
got
a
really
great
sort
of
local
development
environment.
But
basically,
as
soon
as
you
get
to
deployment
other
than
you
know,
localhost
colon
4000.
C
C
So
we
really
think
that
what
we
can
do
is
build
web
native
apps.
So
vision
is
building
a
framework
for
self-contained
web
native
apps.
We're
still
ear,
quoting
this
because
we're
kind
of
you
know
what
does
that
even
mean
we're
also
building
a
hosted
services
so
that
all
of
this
stuff
will
just
kind
of
work
and
support.
But
all
the
stuff
should
run
locally
convenience
features
deployment.
It
should
just
work
user
accounts
with
data
privacy
password
with
login
and
authentication
app
hosting
DNS.
Yes,
web
DNS
is
kind
of
like
a
thing.
C
A
Web
apps
more
like
native
desktop
or
mobile
phone
apps,
so
on
the
web
you
have
to
go
and
upload.
You
know
files
to
every
individual
service
and
large
target
for
personal
information,
and
you
know
all
the
problems
associated
with
that
on,
say:
iOS,
you
have
your
photos
and
you
grant
access
your
photos
to
different
different
applications.
You
have
storage
and
authentication
and
compute
all
in
a
single
SDK.
A
A
You
know
both
JavaScript,
the
AIT's
webassembly
and
a
bunch
of
web
standards
on
top
of
IP
FS
to
to
make
that
work
and
to
also
give
nice
experiences
with
not
having
to
worry
about
it's
not
on
this
slide
per
se,
but
not
have
to
worry
about
DevOps,
because
now
your
production
server
quote-unquote,
is
the
network
which
is
provided
by
ipfs.
Also.
C
I'm,
not
gonna
totally
go
into
this,
but
this
is
a
diagram
that
Brooke
has
made
in
thinking
about
the
kind
of
pieces
of
the
stack
and
there's
a
lot
of
words.
There
Brookes
example
always
is.
You
should
be
able
to
build
an
entire
app
while
offline
on
a
plane
create
the
first
user
account
locally,
and
it's
running
it's
in
production
on
your
laptop
and
then
you
deploy
by
connecting
and
syncing
to
the
rest
of
the
network.
C
The
other
constraint
that
we
put
on
ourselves
in
deciding
how
to
put
these
pieces
together
is
that
everything
that
we
build
in
deploy
and
put
into
the
hands
of
front-end
developers
to
build
apps
with
should
work
in
all
browsers,
including
mobile
without
plugins.
So
you
know
Allen
and
team
JSI
PFS
and
some
of
the
work
being
done
there
definitely
a
key
piece
we're
where
we
want
to
be
injecting
a
JSI,
PFS
node
into
into
browsers
and
work
with
service
workers
to
make
a
bunch
of
that
stuff.
Just
work.
C
C
So
what
have
we
built
so
far?
We
have
built
a
web
api,
so
it's
a
restful
api
for
our
PFS,
as
you
may
have
seen
in
various
kind
of
pinning
services.
We
very
much
don't
think
of
ourselves
as
a
pinning
services,
we
think
of
ourselves
more
as
posting,
in
that
we
do
a
bunch
of
other
things
and
that
pinning
is
kind
of
the
least
interesting
thing
that
gets
done.
We
think
that's
gonna
be
pretty
commodified
and
that
people
will
be
able
to
bring
their
own
storage
and
in
different
interesting
ways.
C
The
first
thing
we
actually
did
was
build
a
Heroku
add-on.
So
that's
in
part
for
the
way
the
web
to
stuff
is
so.
We
made
a
little
add-on
in
the
in
a
roku
marketplace
that
you
can
programmatically
add
to
apps
and
do
one-click
deploys
and
get
access
type.
If
that's
that
way,
by
connecting
to
our
servers,
we've
also
built
in
dns
automation.
C
The
fission
CLI
tool
sign
up
log
in
all
that
stuff
can
be
done
directly
through
the
CLI
and
kind
of
the
main
command
that
you're
gonna
do
is
fission
up
and
that
just
takes
the
current
directly
directory
works
with
your
local
node
uploads
it
to
ipfs
or
rather
puts
it
on
ipfs,
and
then
our
server
reaches
out
and
pins
the
dag,
and
we
we
rely
on
ipfs
to
do
that.
Syncing
and
I've
just
got
a
little
video
here.
Let's
see
if
it
plays.
D
C
We
grabbed
a
gift
from
somewhere
edited
the
index.html
we
type
in
vision,
register
we've
registered
type
in
vision,
watch,
which
is
basically
you
can
have
your
and
there
you
go
so
probably
not
something
that
this
team
hasn't
had
before,
and
we've
really
integrated
this
all-in-one
in
one
tool
where,
in
this
case,
vision
watch
is
actually
running
in
the
CLI.
So
if
you're
typing
in
your
editor
and
you're
live
reloading
and
you've
got
vision,
watch
running
on
that
directory
it'll
constantly
be
uploading.
C
C
Next
up
public
and
private
key
based
accounts,
so
this
is
really
how
we
make
accounts
portable
using
cryptography
crypto
as
in
cryptography
on
our
system.
Accounts
are
gonna,
be
able
to
add
apps
apps
can
have
domains.
We've
got
this
sort
of
single
account
system
right
now
that
we
give
you
a
subdomain
for,
and
this
lets
people
add
multiple
apps
and
so
you'll
have
sort
of
app
fission
dot.
App
that
you
can,
you
can
add
through
one
account.
C
A
Think
so,
Brooke
yeah
sure
so
basically,
identity
or
the
way
we're
using
it.
It's
almost
like
a
just
below
identity
based
very
loosely
on
the
ideas,
verifiable
credentials,
so
we
generate
a
public/private
key
pair
directly
on
the
clients,
with
an
onyx,
portable,
private
key
and
then
use
the
public
key
as
identity
for
and
that's
authentication
for
authorization.
So
you
now
have
a
root
account
and
you
can
delegate
access
to
other
accounts
or
to
other,
because
this
is
then
scoped
to
a
single
domain
name.
A
So
you
can
go
cross
domain
by
signing,
essentially
a
certificate
that
says
another
account.
Your
account
on
the
other
domain
has
some
subsets
of
your
rights,
so
it
might
be
they're
allowed
to
write
into
my
storage
for
the
next
24
hours
so
in
a
lot
of
ways
very
similar
to
how
things
work
with
OAuth
and
JWT
today,
but
in
a
totally
decentralized
manner,
based
largely
on
google's
macaroons.
D
C
A
Sure
I
mean
not
not
too
much
to
to
see
here
beyond
you
know
today
you
can
store
our
public
files
and
we're
making
it
so
that
you
can
do
private
files
in
a
way
where
you
can
share
subdirectories
again
in
a
totally
decentralized
way.
So
each
file
in
each
directory
comes
along
with
the
header
that
contains
a
symmetric
key
for
everything
at
its
level
and
then,
as
we
go
up
this
tree,
it's
also
including
all
of
the
keys
below
it.
A
So
every
file
at
the
directory
has
a
unique
key
for
it
and
then,
if
it
contains
other
keys
that
helps
you
go
go
further
down
the
tree.
So
now
you
can
take
some
subtree
and
share
that
with
somebody
by
sharing
a
key
with
them
doing
key
rotation
is
pretty
straightforward.
We
rotate
the
keys
on
on
index
and
then
do
new
key
exchange
because
we
have
these
nice
asymmetric
keys,
RSA
keys
or
Edward's
keys
kicking
around.
So
we
can
do
key
exchange
for
this
symmetric
key
to
to
view
things.
A
C
A
lot
of
stuff
going
on
we're,
going
to
be
documenting
all
this
and
trying
as
much
as
possible
to
stick
with
with
standards
and
other
emerging
things
that
are
that
are
happening,
and
our
primary
goal
is
kind
of
put
this
all
together,
so
that
it
just
works
because
obviously
there's
a
lot
of
stuff
going
on
here.
I.
A
C
Vision
dries,
go,
try
it
I.
Will
you
you
you
you?
Can
you
can
try
it
right
now,
you're
gonna
see
this
bowl
of
duck.
Ramen
I'm!
Sorry,
if
there's
any
vegetarians
quite
a
bit,
because
it
ended
up
being
one
of
the
the
demo
images
that
I
use
in
a
lot-
and
this
is
me
especially
experimenting
as
I
have
for
the
last
four
months,
with
our
system
using
IP,
FS
directly
to
share
and
and
sync
files.
C
This
just
got
launched
in
what
we
call
preview
mode
in
February
and
our
in
our
team
retreat.
So
basically,
this
is
us
building
an
app
on
top
of
our
own
framework
for
early
adopter,
end
users
and
obviously
developers
who
are
going
to
be
using
this
one
of
the
things
that
we're
thinking
about
as
I
explore.
C
The
the
model
is,
each
user
will
have
one
of
these
things
controlled
by
a
key
you'll,
get
a
convenience
name
like
Boris,
dot,
fission,
dot,
name
and
then
per
app
storage.
So,
just
like
you
have
on
your
phone
today
where
you're
saying
you're,
giving
photos
access
or
a
gif
maker
access
per
app
storage,
and
then
that's
all
happening.
Client-Side.
C
Works
with
any
public
IP,
FS
files,
private
files
and
password,
let's
login
coming
here,
is
a
gorgeous
screenshot
of
image.
Previews.
Yes,
it
works
on
mobile
as
well.
It's
pretty
zippy,
that's
one
of
the
things
that
people
tell
us
quite
a
bit
and
we're
obviously
tinkering
a
lot
with
the
interface.
All
of
this
was
built
by
Steven
Steven.
Are
you
on
the
call?
Yes.
D
C
D
Sure
we
built
fission,
driver,
town
and
element
C
is
this.
We
chose
L
mainly
for
the
great
developer,
experience
the
functional
program
aspect,
and
it
also
allows
us
to
like
quickly
iterate
on
app,
because
it's
really
easy
to
reflector
and
next
to
that
we
have
our
get
ipfs
library
and
we
also
use
render
media
from
the
web
torrent
folks
to
stream
media
files.
C
Yeah,
so
we're
we're
trying
to
showcase
a
bunch
of
things
and
make
it
really
zippy.
You
know
service
workers,
a
bunch
of
other
stuff
in
here
as
well,
and
we
look
forward
to
to
releasing
releasing
that
as
open
source
as
well,
so
that
other
people
can
see
how
we
built
it
and
and
hack
on
it.
I
don't
want
to
spend
a
bunch
more
time,
so
I'll
zip
through
some
of
the
rest
of
these
things,
so
Steven
mentioned
get
ipfs.
C
So
this
is
like
ipfs
provider
but
and
it
was
kind
of
built
around
the
same
time.
In
October
we
met
some
of
the
ipfs,
the
p2p
team,
and
they
told
us
about
a
PFS
provider,
we're
using
es6
syntax
for
this
and
we'll
maintain
this
and
keep
getting
this
working
and
see
if
we
can
merge
at
the
FS
or
what
that
works,
but
that's
available
in
our
github.
We
use
Haskell
on
the
back
end,
you
heard
Steven
mentioning
elm
and
functional
programming.
That
would
be
Brooks
wheelhouse.
C
C
We
are
we're
not
doing
any
NGO
stuff
in-house
right
now,
so
we
ended
up
hiring
a
developer
to
add
a
feature
to
go
out.
Give
us
ipfs
ignore,
so
we
thought
it
was
very
important
for
our
users
to
not
accidentally
upload
private
files.
So
we
implemented
that
in
the
CLI,
but
ideally
we'd
like
that
directly
in
ipfs.
So
there's
a
PR
and
progress
and
ideally
fingers
crossed
I'll,
send
links
around
to
that.
C
C
We
find
a
lot
of
time
explaining
why,
how
and
why
this
could
be
useful
and
we
think
there's
interesting
things
around
sync.
You
know
I'd
love
to
have
an
interface
where
we
have
Drive
on
the
desktop,
but
you're
managing
your
attachments
in
ghost
or
Drupal
or
discourse,
and
that's
all
reflected
in
a
local
desktop
interface
and
kind
of
make
it
available
in
in
both
directions.
C
You
can
try
this
as
a
one-click
action,
so
I,
bundled
together,
Heroku,
the
ghost
blogging
system
and
our
ipfs
adapter.
So
what
this
basically
does
is
on
Heroku,
which
doesn't
have
a
file
system.
You're
uploading
your
files,
your
images
typically
directly
to
ipfs.
So
this
is
then
serving
directly
through
our
gateway
and
has
two
pieces.
This
is
the
little
one
click
deploy
and
then
the
the
the
ghost
storage
adapter
that
we
built
as
well.
We've
done
the
same
thing
for
discourse.
This
is
running
kind
of
in
beta
testing
on
our
own
talk
forum.
C
A
B
Developer
experience
that
you
just
described
there
is
it's
really.
This
is
something
that
I
feel
that
I
profess
really
needs
for
application
building
on
top
of
IP,
FS
and
I'm.
Just
super
excited
to
see
this
is
there?
Are
people
actually
using?
Like?
Has
people
built
apps
on
this
other
than
yourselves
yeah?
We
I
mean
we.
C
D
C
Just
static
front
front
ends:
we
are
only
going
to
be
pushing
this
more
broadly
and
that's
really
been
our
focus
when
we
get
the
building
blocks
of
identity
and
private
files,
and
that's
where
things
get
really
really
interesting
that
then
we
believe
we've
got
a
minimal
stack
where
people
can
build
completely
client-side
nice
right.
So
lots
of
experimentation
and
we're
just
ramping
up
now
to
be
like
yes
use
it.
Try
it
out,
use
these
components
works
today,
nice.
B
C
We'd
love
feedback,
we'd,
love
collaborators,
stuff
we're
doing
on
the
front
end
is
all
a
GPL.
We
are
doing
a
hosted
service.
We've
got
this
crazy
model.
We're
gonna
ask
people
to
pay
for
services
like
with
regular
money.
That's
our
plan
right
now,
although
we
think
there's
some
really
interesting
opportunities
to
work
with
our
customers
and
possibly
other
budgeting
partners
with
file
coin
as
well-
and
you
know,
would
love
feedback,
collaborators
or
anything
come
chat
with
us.
B
D
B
Want
this
and
I'm
really
excited
for
it:
yeah
yeah!
That's
that's,
really
cool!
Thank
you
so
much
for
coming
today,
both
Brooklyn
and
Boris,
and
thank
you
for
presenting
about
fishing
them.
It's
been
really
exciting
and
we
are
pretty
much
out
of
time
so
I'm
gonna,
I'm
gonna
end
it
here.
It's
please
do
get
in
touch
with
them.
If
you're
at
all
interested
in
it,
it
sounds
super
cool
and
exciting.