►
From YouTube: Browsers 3000: Agregore Learning Session
Description
Join us in our second learning session, where we are joined by Mauve from Agregore. Mauve's hackmd file with useful links from the session:
https://hackmd.io/bELcuKrBThecW-XsiUXyQw?edit
https://blog.mauve.moe/slides/agregore-blog-workshop/#1
Join the hackathon at:
https://events.protocol.ai/2021/browsers3000/
To get builders ready, we’re gathering web builders, browser makers, and the dweb ecosystem together to grow both the vision of a decentralized browser and the community creating it.
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).
We believe that our mission is best served in an environment that is friendly, safe, and accepting, and free from intimidation or harassment. Towards this end, certain behaviors and practices will not be tolerated. We're here to help: abuse@ipfs.io
A
A
We're
gonna
see
a
number
of
different
projects,
some
building
extensions,
some
building
wallets
some
building
web
apis.
But
today
we
have
a
special
guest
move
will
talk
to
us
about
their
project
agrigore,
I
think.
Maybe
we
met
for
the
first
time
in
person
at
d
webb
camp
a
few
years
ago
we
got
to
hang
out
and
talk
about
vr
stuff
for
a
while,
which
was
fantastic.
It's
great
to
get
to
know
you,
then
I'm
really
glad
that
you're
coming
and
joining
us
for
projects
like
this
today.
B
B
So
today
we're
going
to
be
making
our
first
peer-to-peer
website
with
aggregor
and
to
do
this,
we're
going
to
learn
a
little
bit
about
the
peer-to-peer
web,
how
it
works,
we're
going
to
learn
some
basic
html
and
css
skills,
and
some
chrome
dev
tools,
skills
for
modifying
stuff.
On
our
page,
then
we're
gonna
put
together
our
websites
and
we're
gonna
show
them
off
to
each
other
by
sharing
links
to
our
peer-to-peer
websites
in
a
hackmd.
B
So,
regardless
of
whether
you're
using
the
notes
or
not,
I
suggest
you
follow
along
with
the
slides,
so
you
can
copy
and
paste
code
snippets
where
appropriate
and
backtrack
to
previous
slides.
If
you
missed
anything
so
as
dietrich
said,
I
move
or
at
ranger
move
anywhere
on
the
internets,
my
pronouns
are
they
them
and
I
do
consulting
through
my
company
mobe
software
inc
as
well.
I
am
high
key
obsessed
with
peer-to-peer
and
local
first
software,
so
before
we
get
into
agriware,
let's
take
a
quick
overview
of
how
the
peer-to-peer
web
works.
B
This
means
that
if
I
am
editing
my
website,
I
don't
need
to
be
connected
to
anything
in
order
to
loads
and
updates
data
as
well.
If
I've
already
downloaded
some
data,
I
can
just
view
it
and
as
well.
If
I
am
on
a
local
network
with
somebody,
even
if
we
don't
have
internet,
we
can
just
kind
of
connect
to
each
other
and
exchange
data.
So
imagine
you're
out,
camping
somewhere,
and
I
can
share
an
image
with
a
friend
or
even
share
an
entire
application
just
by
our
computers
connecting
to
each
other
and
loading
a
hyperlink.
B
So
let's
take
a
look
at
some
of
the
peer-to-peer
protocols
that
are
supported
in
agricore,
so,
firstly,
we
have
ipfs,
which
you
know
we
all
know
and
love,
and
it's
probably
the
one
everyone
is
most
familiar
with
here.
So
it's
really
great
for
data
that
gets
reused
between
websites
and
data
that
doesn't
change
too
often.
This
is
because
it
is
content.
Addressable
and
content
is
deduplicate
deduplicated
across
all
the
peers
on
the
network
and
is
immutable.
B
B
Another
protocol
that
agriculture,
another
protocol
that
agrigore
supports,
is
called
hypercore
protocol.
So,
unlike
ipfs,
it's
not
immutable
or
content
addressable
and
instead
uses
public
private
key
pairs
to
identify
groups
of
files.
So
it's
good
for
data
that
changes
pretty
often
or
is
private
by
default.
However,
it's
not
really
good
for
deduplicating
contents
and
the
ecosystem
is
not
as
far
advanced
as
filecoin.
B
With
regards
to
pinata
and
sorry,
did
I
say
filecoin
I'm
at
ipfs,
because
ipfs
has
these
cool
things
like
pinata,
filecoin,
ipfs
cluster,
all
these
cool
things
hypercore
doesn't
really
have
them.
Yet,
however,
for
today's
session
I'm
going
to
be
using
hypermore
because
we're
going
to
be
doing
a
lot
of
updating
of
our
websites.
However,
the
apis
to
use
ipfs
are
essentially
the
same,
so
if
afterwards
you're
interested
in
using
ipfs
only,
I
suggest
looking
at
the
aggregor
website
and
the
documentation.
B
So
I'd
just
like
to
take
a
moment
to
make
sure
we're
all
on
the
same
page,
and
while
I
keep
talking,
let's
go
to
this
slide
and
go
to
the
download
link
for
agricore
so
as
well,
you're
going
to
want
to
go
to
the
releases
page
and
download
an
installer
that
works
for
your
system.
So
right
now
we
support
windows,
mac
and
linux.
B
So
if
you're
on
one
of
those
os's,
you
should
be
good
to
go
if
you're
using
32-bit
windows
xp
sorry,
I
can't
really
do
much
there
anyway.
So
while
I
keep
going
I'd
like
you
all
to
install
agricore,
if
you
haven't
yet
so
agrigore
lets,
you
talk
to
different
peer-to-peer
protocols
using
custom
protocol
schemes
and
get
and
post
methods
using
the
browser's
fetch
api.
So
what
this
means
is
that
for
those
of
you
that
have
done
web
development
with
http
servers,
the
transition
to
peer-to-peer
is
pretty
smooth.
B
B
Instead,
now
I
do
a
get
to
a
ipfs
url
or
a
hypercore
url,
or
an
ipns
url
or
whatever
else,
and
the
browser
can
handle
the
exact
same
mechanisms
for
loading
stuff
so
anywhere
where
you
can
use
an
http
url.
You
can
basically
use
an
ipfs,
url
or
whatever
else
as
well
with
servers.
If
you
want
to
upload
data,
you
do
a
post
with
some
content
and
with
the
peer-to-peer
stuff
you
do
the
exact
same
thing.
I
can
post
to
ipfs
to
upload
some
content
to
the
peer-to-peer
network
and
that'll
get
distributed.
B
B
This
probably
won't
be
super
interesting,
but
for
those
that
are
new
to
developments,
this
will
just
kind
of
give
you
a
brief
overview.
So
all
websites
are
made
out
of
three
basic
parts:
html
for
the
general
structure
and
textual
content,
css
for
styling
that
structure
and
javascript
for
making
these
websites
interactive.
B
However,
javascript
is
mostly
optional
if
you
just
want
to
put
something
static
on
the
web,
so
we're
gonna
pretty
much
gloss
over
it.
We're
gonna
do
a
little
bit
of
javascript
just
to
save
our
pages,
but
mostly
we're
gonna
focus
on
the
html
and
css,
because,
honestly,
I
think
that's
the
most
fun
with
regards
to
just
putting
content
on
the
web.
B
B
All
web
pages
are
just
text
under
the
hood.
There's
no
fancy
file
formats
like
binary
file
formats.
It's
not
like
an
image.
You
can
open
any
web
page
and
pretty
much
read
it
with
your
eyes
unless
it's
super
messy,
which
it
often
is,
so
let's
go
over
this
line
by
line
and
see
what
everything
means.
So
the
first
line
here
is:
what's
called
the
doctype.
B
This
is
kind
of
a
holdover
from
some
legacy,
things
that
got
to
the
web,
where
it
is
now
and
before
this
line
of
text
was
actually
very,
very
long
and
very
complicated.
So
luckily
it's
not
anymore.
You
don't
have
to
care
next.
The
most
important
part
I
think
of
any
web
page
is
actually
the
title,
so
titles
on
a
web
page
is
what
helps
you
kind
of
differentiate
between
them.
B
This
is
what
makes
it
easy
for
you
to
recall
them
in
your
history
to
differentiate
them
in
your
browser
tabs
to
just
kind
of
like
to
help
with
search
engines.
If
you
don't
want
to
do
any
other
seo,
and
so
it's
really
good
to
have
a
title
that
makes
sense
for
what
your
content
is.
That'll,
be
memorable
and
kind
of
usable.
B
B
B
We're
not
going
to
go
too
deep
into
that,
but
if
you
look
in
the
hackmd,
I've
linked
to
the
mozilla
developer
center,
documentation
for
learning
html
and
so
there's
some
useful
resources
there.
If
you're
interested
in
more
details
over
here,
we
have
our
first
visual
elements,
so
the
doctype
is
something
that
just
lets
the
browser
know
what
it's
parsing.
This
title
is
also
metadata
that
lets
the
browser
know
what
the
title
for
the
page
is.
B
B
But
here
it
defines
all
the
different
stylings
that
we
want
for
this
element,
so
we
want
it
to
be
position
fixed.
That
means
fixed
relative
to
the
entire
page.
We
want
it
to
be
10
units
from
the
top
and
10
units
from
the
left
as
well.
We
want
to
give
it
a
height
of
eighty
percent
of
the
screen
and
a
width
of
eighty
percent
and
background
of
red.
B
So
that's
a
lot
of
stuff,
but
the
format
of
css.
Is
this
general
thing
where
you
have
a
key,
which
is
some
sort
of
name
for
this
style,
and
you
have
a
value
which
is
the
actual
thing
you
want
that
style
to
be
so
here
we
have
an
example
of
css
units,
so
there's
a
bunch
of
different
ways.
You
can
specify
sizes
and
distances
on
a
screen.
B
One
of
them
is
pixels,
another
one
is
font
size,
which
is
a
em,
but
I
like
to
use
this
one
called
v-min,
which
basically
says
a
percentage
of
either
the
width
or
the
height,
whichever
one
is
smallest,
so
it
might
sound
a
little
complicated,
but
once
we
get
into
the
visuals
it
should
be
easy
enough
to
understand
and
as
well,
colors
can
be
represented
in
different
ways.
We'll
go
over
them
in
a
bit.
B
But
if
you
want
to
make
a
color-
and
you
want
to
don't
want
to
think
too
much
about
it,
you
can
type
most
things
like
say,
move
or
purple
or
green
and
they'll
just
accept
them
again.
I
linked
to
the
css
reference
in
the
hackmd,
which
here
let
me
just
repost,
that
in
the
chats
and
there's
more
information
there,
but
we'll
go
over
some
basics
in
a
sec,
cool,
so
question
so
far.
Is
anybody
having
trouble
installing
aggregor?
B
B
Oh
yes,
useful
comment
from
dietrich
for
mac
os.
You
need
to
approve
running
it
in
the
security
and
privacy
settings
pane,
so
agrigore
is
currently
a
one-person
operation
and
getting
all
the
signing,
certificates
and
making
corporations
happy
is
a
bunch
of
effort.
So
sadly,
you're
gonna
have
to
trust
me
and
mitigate
or
work
around
some
security.
B
Stuff,
okay,
cool,
so
I'm
going
to
assume
that
everyone
that
wants
to
install
aggregor
has
installed
it
now
and
oh
yeah.
There's
a
question
in
the
chat:
is
it
electron
based
so
yeah
agrigore
is
actually
built
on
top
of
the
electron
js
framework,
and
that's
because
electron
gives
us
a
lot
of
power
that
is
hard
to
get
in
different
places.
So,
for
example,
it
gives
us,
of
course,
the
framework
to
create
browser
windows
and
to
control
content
in
it.
B
B
B
I
am
looking
into
alternatives,
particularly,
I
think
there's
this
one
rust
framework,
where
they're
kind
of
like
making
progress,
which
should
improve
performance,
but
right
now
electron
is
just
kind
of
the
easiest
way
to
go.
Okay,
cool,
oh
wondering
how
the
protocols
work
actually
and
are
there
special
browser
apis?
B
Also,
so
we're
actually
going
to
get
into
that
in
detail
in
just
a
second,
but
the
tldr
is
that
everywhere,
where
you
can
use
fetch
and
get
for
an
http
server,
you
can
instead
use
ipfs
and
the
apis
for
interaction
interacting
with
the
different
protocols,
are
all
inside
theirs.
There's
no
custom
javascript
apis
being
injected
into
the
page.
It's
all
just
existing
web
apis
and
a
lot
of
your
tools
that
already
work
with
http
and
fetch
should
actually
translate
really
well
to
ipfs
and
the
such
cool.
B
So
now
that
we
have
our
browser
installed,
let's
create
our
first
peer-to-peer
website.
So
making
a
website
in
agrigore
is
super
simple:
we're
going
to
open
up
a
new
window
and
we're
going
to
navigate
to
hyper
colon,
slash
blog.
In
fact,
if
you
click
this
link
in
the
slides,
it
should
go
right
to
it,
so
I'm
gonna
click
the
link
and
bam.
I
just
made
a
new
peer-to-peer
website
in
this
case
using
the
hypercore
protocol.
So
what
happens
here?
B
So,
oh,
so,
as
I
mentioned,
our
next
step
is
going
to
be
opening
up
chrome,
dev
tools,
so
if
you're
working
with
the
web,
this
is
kind
of
like
the
most
invaluable
tool.
In
my
opinion,
you
know
a
lot
of
people
like
their
ides
with
like
their
visual
studios
and
their
emacs
or
whatever
it
is
the
cool
kids
use.
But
if
you
want
to
actually
debug
stuff
on
a
web,
page
devtools
is
kind
of
the
way
to
go,
and
so
one
way
to
open
it
is
to
hit
control
shift.
B
B
So
what
that'll
do
is
open
these
dev
tools
down
here,
and
this
is
what
we're
going
to
be
using
to
actually
interact
with
our
webpage.
So
we're
not
going
to
be
installing
any
extra
software,
any
ex
extra
ids
we're
going
to
be
doing
everything
in
dev
tools
cool,
so
the
first
thing
we're
gonna
do
is
actually
see
how
do
we
interact
with
these
apis?
B
So
if
you
wanna
load
a
file,
you
can
just
use
the
browser's
fetch
api
with
a
particular
url.
So
what
we're
gonna
do
is
copy
all
of
this
text
open
the
dev
tools
and
I'm
gonna
just
clear
all
that
stuff
and
we're
gonna
paste
it
and
bam.
If
everything
worked
out,
you
should
be
getting
a
copy
of
my
blog's
homepage
on
your
terminal,
and
so
what
we're
doing
here
is
we're
fetching
from
the
url
and
we're
getting
the
text
out
of
the
response
and
logging
it
to
the
console.
B
B
Live
demos
and
workshops
are
a
thing
all
right,
excellent,
so
what
we
can
do
is
actually,
instead
of
using
the
hyperurl,
we
can
use
ipns
and
we
can
actually
get
the
homepage
of
ipfs,
so
it
might
take
a
little
bit
longer
to
execute
because
we
need
to
do
the
lookup
for
ipns,
but
here
we
have
the
home
page
and
so
with
this
any
ipfs
ipns
or
hyperurl
they're
all
available
through
the
same
interface.
So
that
means
anywhere
where
you're
trying
to
load
content
on
the
web.
B
It
doesn't
matter
where
that
content
is
coming
from
anymore
and
you
don't
need
to
do
any
extra
coercing
to
make
it
work
so
say:
you're
loading,
3d
models
or
videos
or
say
you're
loading
code
from
the
web
rather
than
having
to
inject
a
bunch
of
javascript
apis
and
like
use
these
like
globals
that
are
coming
out
of
nowhere
to
fetch
the
data
and
like
having
con
custom
logic
everywhere.
You
can
just
use
fetch
or
anything
that
uses
fetch
cool,
so
that
was
downloading
a
file.
B
B
So
I
want
to
add
a
file
called
index.html
to
my
blog
and
I
want
it
to
have
the
following
content
so
to
do
that,
we're
going
to
change
the
http
method
to
put
and
we're
going
to
set
a
body
for
the
request
for
some
sort
of
content.
Again
we're
going
to
have
the
doctype
and
here's
where
I'm
going
to
want
you
folks
to
customize
stuff
a
little
bit
we're
going
to
want
to
change
the
title
to
be
something
that
reflects
us.
B
B
This
is
just
going
to
inject
some
useful
code
onto
your
pages
so
that,
rather
than
having
to
do
this
dance
of
opening
the
console
and
like
uploading
files
individually
you'll
be
able
to
just
drag
and
drop
files
into
the
blog
and
that'll
just
automatically
upload
them
to
it.
This
will
just
make
life
a
little
bit
easier
as
well.
It'll
inject
some
global
functions,
that'll.
B
B
In
fact,
let's
do
a
bunch
all
right
cool,
so
once
you're
happy
with
the
content
of
your
website,
we're
gonna
hit,
enter
and
bam.
We
just
created
our
first
web
page,
so
we're
going
to
copy
that
url
from
fetch
and
we're
going
to
paste
it
in
our
browser.
So,
as
you
can
see,
here
is
my
webpage
page,
here's
all
of
my
like
snake
emojis,
and
if
we
open
up
the
dev
tools,
we
can
actually
see
the
html.
B
So,
for
example,
if
I
want
to
change
the
text,
I
can
click
on
the
text
and
change
it
to
whatever
else
I
want
and
so
we'll
get
into
how
to
save
how
we
save
the
changes
in
a
sec,
but
there
we
go.
That
should
be
the
start.
So
before
we
keep
going
has
anyone
had
trouble
getting
up
to
here
is
everyone
on
their
first
page,
I'm
gonna
give
it
a
few
seconds.
B
B
So
when
we
use
hyper,
we
aren't
creating
a
public
web
page,
it's
just
private,
pretty
much
yes!
So
when
you
use
hyper
by
default,
it's
private
in
that
nobody
can
access
it,
but
you
can
make
it
public
by
sharing
it
with
people.
So
in
the
haccmd
that
I
pasted
in
the
chat
earlier,
which
I
shall
re-paste
in
case,
anyone
is
missing
it.
B
We
have
a
section
called
websites
and,
at
the
end,
we're
going
to
be
pasting
our
websites
there
if
we
want
and
doing
a
little
showcase-
and
so
that's
how
you
share
things.
Ipfs
is
similar
in
that,
even
though
technically
people
could
like
scrape
for
content
hashes
and
like
all
this
hacker
stuff
generally,
if
you
don't
share
your
content,
hash
with
people,
it's
gonna
be
pretty
much
private,
but
it's
like
a
subtle
distinction.
B
The
main
thing
is
the
mutability
is
going
to
be
easier
right
now
I
love
ipfs,
okay,
cool.
I
don't
see
any
questions
about
the
the
fetch
stuff
so
far,
so
what
we're
gonna
do
now
is
make
our
blog
actually
interesting
by
getting
some
gifs
onto
it.
So
we're
gonna
go
to
gift
cities,
which
is
a
thing
made
by
the
internet
archive,
and
so
what
this
is
gonna
give
us
is
a
vast
repository
of
super
cool
bling
which
we're
gonna
be
making
use
of.
So
I'm
just
going
to
change.
B
B
This
is
a
bit
of
a
workaround.
We
need
to
do
because
browser
security.
Doesn't
let
me
download
a
gif
directly
from
website
into
another,
sadly
yet
anyways,
so
I've
searched
for
cats,
and
now
I'm
gonna
go
and
look
through
and
find
some
cool
chunkers.
So
I
really
like
this
cat,
I'm
just
gonna,
drag
it
into
my
finder
there.
I
really
like
this
cat,
and
I
think
this
one
is
pretty
neat
so
once
you
have
your
cats
you're
going
to
want
to
open
up
your
website
again.
B
B
B
If
you
go
back
to
the
assets
folder,
we
should
see
all
of
our
cats
here.
So
I'm
just
gonna
go
back
to
my
console
and
show
the
blog
and
I'm
gonna
be
showing
you
how
to
edit
the
html
on
your
website
to
actually
show
your
cats.
So
first
thing
we're
going
to
want
to
do
is
right,
click,
one
of
these
gifs
and
copy
the
link
address.
B
B
Life
is
hard,
so
what
we're
going
to
want
to
do
is
click
on
our
image,
attributes
that
should
have
been
added
and
we're
going
to
click
on,
add
attribute.
So
that's
going
to
let
us
edit
some
stuff
we're
going
to
want
to
paste
src
equals
and
then
that
link
we
had
before,
and
so
that's
going
to
give
us
our
cat.
B
B
B
B
B
So
another
question
in
the
chat:
what
is
the
host
for
the
gif?
Is
it
your
local
machine,
and
the
answer
is
yes,
so
what's
happening?
Is
you
have
a
hypercore
protocol
or
ipfs
node
running
directly
on
your
machine
and
when
you
upload
files
to
it
it's
being
uploaded
to
the
to
the
protocol
on
your
machine?
So
it's
advertising.
B
Excuse
me
on
the
network
if
someone
wants
to
actually
download
it
peer-to-peer,
but
as
I
mentioned
every
as
I
mentioned
before,
with
the
peer-to-peer
web,
everything
is
local,
first
and
offline
first.
So
any
changes
you
do
are
local,
but
then
they
can
be
exchanged
peer-to-peer,
which
we'll
be
doing
soon
and
speaking
of
things
I
mentioned
earlier.
B
I
said
that
you
can
just
kind
of
edit
the
src
and
add
a
cat
in
there,
but
I
actually
for
neglected
to
mention
another
part,
which
is
that,
even
though
we
can
add
the
image,
if
we
refresh
suddenly
it's
not
there,
and
so
what?
Oh
sorry
before
I
go
on
that
there's
another
question
in
the
chat.
Is
that
true,
even
if
your
src
points
to
an
image
hosted
elsewhere
in
that
case,
no,
so
the
only
time
it's
actually
using
the
peer-to-peer
protocols
is,
if
you're,
using
a
peer-to-peer
url.
B
So
if
you
you're
using
an
ipfs
url,
it's
loading
it
locally.
If
you're
uploading
to
ipfs,
it's
also
loading
it
locally
and
if
you're
pointing
to
an
http,
url
or
an
https,
url
or
gemini
or
whatever
else,
that's
actually
going
to
be
loaded
over
those
protocols
from
the
internet.
So
that's
going
to
be
cached
in
your
browser
as
it
normally
would
be,
but
it's
not
going
to
be
offline
first,
because
only
the
peer-to-peer
protocols
themselves
are
offline
first,
so
just
to
go
back
to
the
slides.
B
B
B
B
B
B
Bam
and
so
I'm
going
to
save
that,
so
you
can
also
play
around
with
this
like
say
you
want
it
to
be
50
from
the
right.
You
can
specify
50
v
w,
which
is
width
or
you
can
have
a
specific
number
of
pixels
like
say,
420
px
from
the
right,
and
so
this
will
be
responsive
as
your
viewport
changes
cool.
So
I'm
going
to
save
that
as
well
as
well.
B
So
if
you
have
any
questions
about
what
we
have
so
far,
post
them
in
the
chat
and
in
the
meantime
I
suggest
we
all
take
a
few
minutes
just
to
add
some
cats
on
our
page
or
add
some
content.
If
you
are
already
pretty
well
versed
in
css
and
html,
you
can
probably
do
some
fancier
things
than
I
can
cover:
okay
cool.
So
we're
going
to
take
a
few
minutes
just
to
customize
our
websites
and
feel
free
to
post
questions
in
the
chat.
B
So
I'm
going
to
first
of
all
change
the
color
of
my
whole
web
page.
Because
green
is
not
my
favorite.
I'm
gonna
go
into
this
little
color
wheel,
picker
make
it
a
nice
purple.
Color,
I'm
gonna,
save
that
and
I'm
gonna
go
back
to
my
assets.
Folder
and
I'm
gonna
copy
another
cat
and
just
add
it
to
the
screen.
B
B
B
B
B
All
right
so
we're
getting
towards
the
end,
so
hopefully
y'all
have
put
at
least
something
on
your
screen
to
start
and
we're
gonna
get
to
the
next
part,
which
is
actually
sharing
our
websites
with
each
other.
So
what
we're
going
to
do
is
we're
going
to
get
the
public
url
of
our
browser
or
of
our
website.
B
B
So
first
you're
going
to
want
to
go
back
to
your
blog
and
then
open
up
the
dev
tools
using
control
shift.
I
so
I
added
some
helper
scripts
to
make
life
easier.
So
if
you
use
the
await,
gets
public
url
function,
I'm
just
gonna.
You
can
copy
paste
that
either
from
the
slides
or
I'm
pasting
it
in
the
zoom
chat
or
you
can
copy
it
from
my
screen.
B
If
you
invoke
that
you're
actually
going
to
get
back
this
long
string
and
so
what
we're
going
to
do
is
copy
that
link
address
and
paste
it,
and
so
now
this
is
using
the
full
url
so
in
if
you're,
using
ipfs,
this
will
be
the
multi-hash
of
the
or
sorry
the
cid
content
id
of
your
web
page
or
the
cid
of
the
public
key
of
your
ipns
domain,
whatever
else
and
in
hypercore
protocol.
This
is
the
32
bits
or
a
32
byte
hex
encoded
public
key.
B
B
So
I'm
going
to
open
up
one
of
the
ones
here
on
this
stream,
I'm
just
going
to
paste
it
right
into
agricore
and
bam.
Hey!
It's
sticky
keys,
hey
sticky
keys,
so
we
can
see
your
html
here.
I
see
you
linked
directly
to
an
image
which
is
totally
valid
and
we
can
kind
of
see
how
they've
just
got
this
basic
html
page
with
the
stuff
we
had
before.
B
So
as
you
can
see
that
loaded
super
fast
and
that
was
all
without
any
central
servers
or
any
caching
servers
or
anything
else
in
between
us
and
we
didn't
need
to
register
for
a
donate
domain
name.
We
didn't
really
need
to
do
anything,
just
kind
of
exchange
urls
with
each
other,
and
so
our
computers
found
each
other
over
the
peer-to-peer
network
and
we
connected
directly
to
each
other
and
I
downloaded
their
website.
B
B
Not
found,
I
don't
know
why
it's
404,
as
you
can
see,
not
everything
works
all
the
time,
but
hopefully
some
folks
were
able
to
load
my
website
as
well,
and
I
think
that's
all
the
folks
that
wanted
to
share
their
websites
for
today,
but
that's
kind
of
how
it
works.
You
can
just
edit
stuff
directly
in
agricore.
You
can
add
code,
you
can
link
to
things
you
can
link
to
each
other.
B
So
with
this,
we
can
actually
link
between
protocols,
mixing
http,
ipfs,
hyper
gemini
bittorrent,
everything
that
you
can
think
of
and
using
whatever
makes
sense
in
whatever
situations
or
whatever
people
feel
like
using
yeah.
So
hopefully
that
was
useful
and
we're
just
gonna
do
some
last
thoughts
and
then
we'll
talk
about
the
rest.
B
So
hopefully
this
was
a
fun
introduction
to
the
peer-to-peer
web
and
making
your
first
website,
hopefully
folks
that
are
following
the
recording
after
the
fact
will
be
able
to
use
this
to
also
experiment
feel
free
to
ping
me
on
the
ipfs
discord
in
the
browser's
3000
chat.
If
you
are
building
something
with
aggregor
or
want
to,
or
have
questions
it'd
be
cool
if
even
after
this
people
could
tweet
some
of
their
urls
at
me,
so
that
I
could
save
them
or
re-share
them
with
folks.
B
And
seeing
how
it
all
works,
it's
it
should
be
pretty
similar
to
other
web
stuff,
you've
done
in
the
past
and
honestly.
I
hope
this
will
inspire
some
folks
to
try
to
make
stuff
and
to
think
about
alternative
ways.
We
can
interact
with
the
web,
that's
more
local,
more
resilient
and
more
accessible
to
people
accessible
in
terms
of
easier
to
use,
but
also
accessible,
because
you
gotta
remember,
accessibility,
all
right.
So
I'm
gonna
answer
some
of
the
questions
in
the
chats.
B
B
B
B
So
one
thing
I'm
working
on
this
summer
is
to
actually
replace
js
ipfs
with
go
ipfs
in
agricore,
and
so
that
should
support
all
of
the
subdomains
and
all
that
stuff
better.
So
at
the
moment,
dns
dns
link
mostly
works
ipns
using
public
keys,
mostly
works.
It
all
works
better.
If
you
have
ipfs
companion,
companion
loaded
locally,
but
it
can
be
a
little
iffy
just
because
ipns
is
it
works
a
little
differently
between
javascript
and
go
cool
yeah.
B
A
B
B
You've
got
the
pinning
services
api
so
that
you
can
talk
to
things
like
pinata
or
stuff
in
the
cloud
and
you've
got
filecoin
which
lets
you
just
like
use
this
distributed
network
to
keep
stuff
online,
which
is
great.
However,
for
hyper,
it's
a
little
more
obscure
and
we
don't
have
as
many
fancy
things.
So
personally,
I
use
this
thing
called
dat
store,
which
is
a
a
command
line
utility
that
I
use
to
keep
stuff
online.
B
So
I
usually
just
launch
this
in
a
digital
ocean
droplets,
and
this
also
comes
with
a
cli.
That
lets
me
talk
to
either
a
local
instance
or
a
remote
one,
and
so
this
lets
me
either
sync
folders
to
hypercore
or
just
keep
hypercoarse
pinned
either
in
the
cloud
or
locally.
So
this
is
what
I
usually
use:
it's
not
as
fancy,
but
it
works.
B
All
right
cool,
I
think
that's
probably
all
the
questions.
Thank
you
all
so
much
for
coming
and
yeah
again.
Hopefully
you
can
make
something
cool
with
this.
If
you
have
any
comments
or
want
to
follow
up
or
whatever
else,
I'm
going
to
be,
I'm
pretty
online,
so
you
can
either
tweet
at
me
on
the
tweeters
or
mention
me
in
the
ipfs
discord
or
join
the
agricore
discord.
If
you
want
to
kind
of
keep
in
touch,
so
thank
you
and
I
guess
I'll
pass
it
off
to
dietrich.
A
No
thank
you
that
was
awesome.
It
was
great
to
be
able
to
see
the
how
aggro
works
and
how
a
multi-protocol
browser
can
work,
which
I,
like
aside
from
just
http
right.
So
it's
very
cool
and
also
a
great
view
into
the
differences
between
some
of
the
protocols
and
relative
links
strike
again
being
the
bane
of
every
decentralized
web
developer's
life
we'll
get
there
eventually,
hopefully,
but
thanks
for
joining
and
like
like
mo
said,
ask
questions
in
the
channel.