►
Description
Browsers 3000 is a six-week virtual event to explore and accelerate the development of web3 in the browser through experimentation and challenge prizes of up to $20,000 worth of Filecoin (FIL). Learn more at https://events.protocol.ai/2021/browsers3000.
Like all IPFS Community events, Browsers 3000 expects all speakers and participants to follow the IPFS Community Code of Conduct (https://github.com/ipfs/community/blob/master/code-of-conduct.md).
A
My
name
is
jeff
griffiths.
I
work
at
a
company
called
phishing.
Phishing.Codes
is
the
url,
because
we
have
cool
tlds
now
and
I'm
super
excited
for
efficiently
part
browser.
3000,
hackathon,
I've
known
g
trick
for
a
long
time
and
I
think
ipfs
is
cool.
So
what
is
fission
well
efficient
today?
What
we've
done
is
we've
got
a
cli
and
we've
got
a
cli
driven
web
publishing
platform
on
ipfs.
So
when
you
build
a
web
app,
you
publish
it
to
phishing
system,
it
gets
propagated
out
into
ipfs.
A
You
can
check
out
the
sids
and
see
the
content
addressing
all
work
and
we
also
gateway
that
to
the
web,
and
we
also
have
a
decentralized
authentication
system.
That's
passwordless
I'll
show
that
in
a
bit,
hopefully
it
works
and
we
have
a
simple
security
in
browser
storage.
By
what
we
call
the
web
native
file
system,
I'm
going
to
show
a
stack
diagram
of
how
all
this
works
or
will
work
in
the
future.
A
So
you
can
see
the
orange
block
is
your
application.
We've
got
some
platform
abstractions
there,
which
is
our
web
native
sdk,
and
we
have
some
blocks
in
there
that
aren't
built.
Yet,
like
collaboration
chat
and
instant
sync,
and
in
the
middle,
we
have
this
gerbil
structured
store,
which
is
a
web
native
database,
which
is
something
that's
on
a
roadmap
they're
really
excited
to
see.
But
beneath
it
all
is
this
durable
file
store,
which
is
the
web
native
file
system
and
so
in
the
browser
as
a
web
developer.
A
You're
just
writing,
javascript
and
fetching
files
from
this
thing,
and
it
gets
synced
out
from
the
browser
and
and
published
onto
ipfs
and
there's
two
sides
to
that,
which
is
a
really
important
part
of
this.
One
side
is
public,
it's
a
public
on
the
web
and
anybody
can
go
to
it
and
there's
a
private
side
where
we
use
our
distributed
identification
system.
A
There
did
system
and
you
sign
up
for
an
account
and
we
encrypt
your
private
data
for
you
and
then
publish
it
encrypted
at
rest
to
ipfs,
which
is
super
cool
because
it
builds
privacy
into
the
basic
layer
of
the
system,
and
so
on
this
identity
side.
We
have
password
login.
I
said
that
in
decentralized
auth
you
get
a
personal
subdomain
and
we
carry
private
keys
in
the
browser
using
the
web.
Crypto
apis
we're
end-to-end
encrypted.
A
We
have
versioning,
so
it's
like
a
think
of
it
as
like
git
in
the
browser
for
storage
of
personal
data,
and
you
know
you
get
these
permanent
archive
links
with
ipfs
of
every
known
state
of
your
your
previous
state
of
your
data
and
this
because
it
leverages
ipfs
it
automatically
syncs
between
devices.
The
building
blocks
of
all
this
ipfs.
Of
course,
a
bunch
of
pretty
cool
browser
apis
that
we
now
have
in
browsers.
A
That
seemed
like
a
would
have
been
impossible
10
years
ago,
but
a
ton
of
people
have
put
a
ton
of
work
into
the
web
platform,
the
last
10
years
and
we're
really
building
on
the
shoulders
of
those
those
giant
features
that
have
been
added
to
web
browsers
in
in
chrome
and
firefox
and
and
and
brave,
etc.
A
We
use
decentralized
identifiers
and
we're
working
actively
with
partners
like
microsoft,
to
standardize
some
of
these
things
and
also
people
in
sort
of
the
blockchain
world
around
how
did
should
work.
We
have
a
decentralized
authentication
specification
called
ucan.
A
We
have
our
web
native
file
system
and
one
thing
I'm
really
excited
about
getting
our
system
to
look
a
little
bit
more
like
a
traditional
web
2
app
system
having
a
more
database
abstraction
on
top
of
the
data.
So
how
does
sufficient
use
ipfs
well,
ipfs
content?
Addressing
is
extremely
important
to
us.
A
Everything
needs
to
be
portable,
and
so
we've
just
built
this
web
native
api
again,
and
so
everything
is
synced
around
to
different
browsers
that
are
logged
into
the
phishing
system
and
the
data
goes
from
browser
to
ipfs
infrastructure,
the
ipfs
sort
of
constellation
system
and
then
back
into
a
browser
when
you
log
into
a
different
browser
again
so
so
getting
started
with
phishing,
it's
pretty
easy.
We're
gonna
try.
It
today
live
here.
So
what
we
need
to
do
is
install
the
cli,
create
link
your
phishing
account
and
create
and
publish
an
app.
A
So
I've
cheated
a
little
bit.
I've
already
installed
fishing,
that's
not
gonna
work
for
that
and
it's
got
help
stuff,
and
so
the
first
thing
we
do
is
run
fish
and
setup.
A
A
A
A
And
see
those
numbers
there,
we
switch
back.
Those
are
the
same
numbers,
one
zero,
two,
five,
three
five,
and
so
we
verify
that
and
its
second
factor
and
we
grant
access
and
we
log
in
on
the
other
device
now
to
successful.
So
that
was
super,
easy
right
and
it
actually
it
worked.
Thank
the
demo
gods.
A
And
then
I'm
sitting
here
in
a
demo
directory
and
you'll
notice
when
I
list
this
directory,
it
has
a
fission.yaml
file.
We
are
going
to
temp
the
demo
gods
again
and
just
remove
that
and
we're
going
to
run.
A
And
I'm
sorry
for
the
amount
of
text
that
this
is
going
to
punch
into
your
terminal
into
your
screen
here
through
the
terminal
I'm
doing
it
in
verbose
mode.
Just
so,
I
can
show
you
kind
of
under
the
hood
how
this
works.
A
We
have
like
a
local
version
of
go
ipfs
that
we
run
and
we
try
to
connect
to,
and
so
it
takes
a
little
while
to
check
and
make
sure
that
that's
running
and
normally
what
you
would
see
if
you
didn't
do
dash
v
is
just
a
little
spinning
clock,
but
this
is
much
more
matrixy
just
to
check
how
old
I
actually
am.
I
remember
the
matrix.
A
A
Again:
apologies
for
the
sheer
amount
of
text.
That's
going
to
go
whizzing
by
we're
going
to
publish
this
to
the
web
on
a
new
brand
new
domain
which
we
we
do
auto
generate
these
domains.
So
this
app
is
called
skinny
petite
round
gnome,
which
is
interesting.
We
have
like
some
sort
of
markov
chain,
esque,
url
generator
that
somebody
wrote
last
year,
that's
very
clever,
and
so
it's
sort
of
doing
the
same
dance
of
getting
the
cli
working
and
running
with
go
ipfs
here
and
then.
A
Were
generous,
probably
because
I've
been
praying
to
them
a
lot,
so
next
steps
for
fishing
for
this
hackathon,
so
we've
got
the
efficient
guide.
I've
got
a
url
here.
A
What
you
would
do
with
this
app
next
is,
you
would
hook
it
up
with
the
efficient
authentication
system
so
that
someone
who
comes
to
your
app
can
sign
up
for
efficient,
distributed
id
account
and
use
your
app
and
store
their
data
for
themselves
in
their
browser
and
ipfs
without
you
having
to
run
storage
or
in
an
aws
account
or
anything
like
that,
and
everything
gets
stored
in
web
native
on
behalf
of
the
user.
A
It
gets
encrypted
at
rest
and
then
and
you
don't
have
to
run
a
database
with
a
million
users
in
it,
which
is
pretty
cool.
What's
next
for
the
hackathon,
we've
got
fabulous
prizes,
we've
got
a
sticker
sheet,
we've
got
t-shirts
and
they
look
pretty
cool
and
so
best
you
sufficient
we're
actually
going
to
ship
someone.
One
liter
of
maple
syrup
fishing
is
a
distributed
company.
It's
located
around
the
world,
but
there
is
a
bunch
of
canadians
and
we
like
maple
syrup,
plus
a
t-shirt
and
sticker
sheet.
A
A
runner-up
for
best
use
of
fishing
web
native
t-shirt,
plus
sticker
sheet
and
honorable
mentions
you've
got.
Is
it
sticker
sheets?
That's
a
link
to
the
the
swag
shop
that
we
have,
but
this
will
be
for
the
winners
shipped
free
of
charge
worldwide
and
come
talk
to
us
during
the
browsers
3000
hackathon
we've
got
a
hashtag
browser's
3000
channel
on
our
discord.
Server
just
go
to
efficient.code
discarder
it'll.
Get
you
to
the
right
part.
Tell
us
what
you're
trying
to
build
talk
to
us.
We're
going
to
be
manning
that
channel.