►
From YouTube: DNSLink URLs, connection state in UI, new ipfs.io - IPFS GUI and In Web Browsers Weekly, 2019-07-31
Description
IPFS Mirror: https://ipfs.io/ipfs/bafybeibv7qadap3x3iujtf433bhxavwnhm7usbr4srnkfyfifdihdhf73m
A
A
Should
I
PFS
and
domain
name
be
a
canonical
representation,
or
should
that
be
IP
NS
and
initially
this
PR
started
as
a
proposal
to
support
DNS
link
above
and
an
open
question
was
should
which
way
we
should
redirect,
because
we
don't
want
to
like
people
get
confused
by
having
the
same
website
on
both
namespaces
the
at
least
at
the
browser
level.
It
should
converge
at
one
address
and
there's
a
long
discussion,
but
I
got
a
short
summary
here
from
a
call
we
had
before
to
unboard
you
on
some
latest
decisions
and
concerns.
A
A
People
have
around
ipfs,
addressing
where
all
ipfs
paths
and
ipfs
addresses
were
always
immutable,
which
meant
you
can
fetch
something
today
and
if
you
fetch
something
from
the
same
address
20
years
in
the
future,
it
should
give
you
the
same
bytes
and
if
we
allow
the
NS
link
on
like
ipfs
namespace,
that
introduces
some
confusion,
because
people
think
it's
immutable
and
it's
no
longer
at
the
same
time,
IP
and
s
it's
a
problem.
A
problem
has
problems
on
it
on
its
own.
A
You
can
have
IP,
only
p2p
keys
there
and
have
that
as
a
mutable
pointer
to
something
you
can
also
have
the
NS
link,
which
acts
as
a
mutable
pointer
to
any
content
path.
But
still
there
is
understanding
in
the
community
that
I
TNS
namespace
is
about
mutable
naming
for
ipfs,
so
sort
of.
At
this
point,
we
agreed
to
support
the
nesting
on
ipfs
protocol
handler,
with
a
small
caveat
that
it
will
for
now
it
will
redirect
to
IP
NS
protocol
handler
so
in
the
location
bar.
What
will
persist?
A
That's
all
those
are
some
harder
discussions
and
designing
in
the
short
term,
but
in
the
law
we
can
always
change
the
way
this
redirect
behaves
and
what
it
unlocks
is
allows
people
to
just
type
ipfs
colon,
slash,
slash
and
domain
name
in
location
bar
and
as
soon
as
active
as
companion
supports
this
change.
It
will
work,
so
people
can
start
using
this
URL
and
also
this
one
I
believe.
That's
it
for
this
topic.
If
there
are
any
questions
or
the
celica
chat,
stop
sharing
now.
A
B
I
had
a
couple
of
questions
about
the
so
that
it
seems
like
the
main
blocker
for
doing
this
would
be
the
understanding
in
the
community
around
me
immutability,
a
that
is
in
anyway,
assumed
to
be
an
IP
FS
resource.
But
if
you
have
the
resolution
of
that
name
to
see
ID,
then
that
isn't
necessarily
trustable
as
immutable,
because
that
could
potentially
change
two
points
to
something
else
is
so
my
question
was
really
around.
Who
is
doing
this
now?
Who
are
the
parties
that
are
actually
shipping
ipfs
colon,
slash,
slash
so
here?
A
B
Call
yeah
the
the
way
to
because
it's
hard
to
start
the
reason
about
what
the
impact
of
changing
that
understanding
in
the
community
is.
If
we're
just
talking
about
the
community
as
a
you
know,
ambiguous
blob
of
activity
where
people
some.
So
it
really
helps
that
conversation.
If
we
talk
about
the
people
that
are
impacted
by
that
potential
change,
very
specifically,
which
who
are
the
projects
whose
shipping
code,
who
are
the
communities
or
ecosystems
that
have
dependencies
on
this
understanding
of
the
immutability
of
active,
has
:
/
/,
specifically.
A
So
that's
more
or
less
the
current
situation.
With
this
we
will
land
support
for
aquifers,
colon,
slash,
slash,
DNS,
link
in
aquifers
companion,
just
like
a
UX
feature,
so
people
can
price
links,
even
though
it's
not
canonical
one
won't
be
present,
persistent
in
location
bar.
It
makes
it
easier
for
people
and
at
the
same
time
it
does
not
pollute
ipfs
namespace
with
mutable
mutable
identifiers,
because
it
will
explicitly
redirect
user
to
IP
Ana's
namespace.
B
To
some
extent,
because
by
shipping
that
you're
also
training
people
you're
training
users
to
expect
that
I
give
s
:,
/
/
name
to
be
something
that
it's
usable
and
familiar
and
understandable,
so
I
feel
like
you
are.
We
are
now
if
we
ship
that
feature,
even
though
it
is
a
redirect
what
people
are
able
to
share
between
each
other
is
ipfs
colon,
slash,
slash,
URLs,
and
that
builds
a
community
and
an
ecosystem
around
an
understanding
of
that
functioning
in
that
way
in
a
but
not
mutable,
it
way.
A
B
We're
making
impact
our
broader
adoption
strategy
moving
forward,
as
we
start
shipping
in
more
browsers
I
think
is-
is
important
and
I.
Don't
think
we
fully
understand
that
yet,
but
I'll
see
if
I'll
see
if
there's
some
research
around
how
how
we
end
users
think
about
these
things,
because
again,
my
god,
a
given
that
where
our
project
is
0.4
and
we're
the
you
know,
nascent
beginning
of
a
potential
adoption
growth
trajectory
there's
any
time
to
kind
of
change.
B
A
A
It's
like
a
sec,
something
too,
we
will
probably
feel
an
issue
later
today
is
if
we
want
to
have
a
universal
name
like
universal
protocol
handler
for
all
those
multiple
namespaces.
We
could
have
something
like
the
web,
then
you
have
your
name
or
your
identifier
and
then
at
the
very
end,
you
stick
the
protocol
like
the
actual
protocol
namespace,
and
that
gives
you
a
region
per
protocol.
But
that's
just
like
a
cute
hug
for
to
think
about.
In
case
we
don't
end
up
with
I,
TNS
or
ipfs
permanently
in
location
bar.
B
Hey
I
guess
when
one
thing
to
think
about
is
that
I
mean
one
lesson
we
learned
in
browser
landis
that
most
users
don't
really
understand
any
of
it
at
all,
no
matter
how
hard
you
try
in
the
URL
bar
and
that's
why
Google
keeps
trying
to
basically
hide
the
URL.
This
has
hiding
the
URL
reduces
confusion,
and
it
actually
opens
up
new
doors
to
how
to
visually
communicate.
These
things
yeah.
A
A
So
it's
from
a
pragmatic
point
of
view,
it's
mostly
making
sure
in
case
someone
writes
URL
that
or
clicks
a
ul
or
like
types,
the
URL
that
looks
like
that
in
location
bar
will
it
return
error
or
it
will
it
with
a
redirect
user
to
a
valid
place.
They
wanted
to
load
in
the
first
place,
I
think
that's
more
or
less
on
this
topic.
Anyone
wants
to
add
something.
C
A
A
We
are
like
discussing
some
prototypes
around
indicating
connectivity
by
showing
those
like
connection
points
protruding
from
the
cube
and
some
through
some
mock-ups,
how
it
would
look
like
in
a
black
and
white
scheme
and
how
it
looks
on
Mac
how
it
looks
on
Windows.
Some
scaling
issues
and
I
also
played
a
little
bit
with
IP
first
companion
to
see
how
those
icons
would
look
in
the
browser
context
and
I
I
realized
that
the
proposed
protruding
circles
make
a
nice
animation.
If
you,
if
you
make
it
animate,
so
that
more
or
less
on
on
Dennis.
C
My
only
addition
would
be
that
holy
smokes
there's
a
lot
of
different
places
where
these
icons
are
gonna
appear
and
yes
of
airing.
On
the
side
of
you
know,
simplicity
and
attempting
to
follow
the
guidelines
established
by
folks,
like
Apple,
is
probably
a
good.
You
know
like
that,
for
example,
not
you
know
using
only
the
the
template,
the
you
know,
pure
black
and
white,
for
for
the
basic
tray
icon
is,
is
preferable
to
using
you
know,
Jason
color,
most
most
of
those
icons,
don't
really
use
color,
except
sometimes
to
indicate
like
an
active
state.
C
C
Additionally,
the
the
old
one
you
know
uses
color
or
tone
as
like
the
primary
indicator,
and
that's
not
just
you
know,
that's
not
necessarily
the
the
most.
The
the
best
indicator
I
mean
some
people
can't
really
tell
the
difference
between
shades
and
yeah.
And
additionally,
you
know
just
the
high.
The
higher
contrast
is
going
to
be
is
is
going
to
be
something
that's
not
based
in
color
I
mean
you
usually
color
is
used
as
as
it's
best
used
as
a
supporting
communicator,
as
opposed
to
the
sole
way
of
communicating
a
state,
for
example.
C
So
so
something
with
the
dots,
for
example,
literally
changing
like
the
dots
starting
in
a
hover
at
hovering
around
the
orbiting
around
the
box.
It
helps
to
make
the
box
itself
a
little
the
whole
graphic
itself
a
little
bit
bigger
without
actually
enlarging
the
box,
because
that
that
gets
to
be
a
little
bit
too
dominant
and
clunky
in
it.
The
box
needs
a
little
space
to
breathe.
A
A
A
Stuff
cool,
so
if
anyone
has
opinions
or
ideas
on
how
to
indicate
connected
connecting
an
offline
state
or
are
there
any
other
opportunities
of
states
that
we
missed?
Please
comment
on
that
issue,
I
believe
now
we
can
move
to
the
next
one
unless
someone
wants
to
follow
up
on
UI
and
indicators.
Yes,
no,
yes,
no!
No!
Okay,
three
I,
believe
text.
D
Matrix-Like
as
a
general
concept,
this
idea
of
the
state
like
this
is
something
we
talked
about
in
off,
like
a
looks
like
the
UI
of
these
states
being
different
than
you're
used
to
like
safe
here,
it's
somewhere,
but
not
on
my
machine.
All
of
that
stuff
that
happens
in
traditional
web
applications
with
some
weird
statuses
that
people
aren't
used
to
symbol
as
far
as
definitely
definitely
the
problem
extends
beyond
the
project,
so
it's
cool
to
see
it
being
treated
and
we
might
get
in
I.
D
B
I
so
I
should
document
here
it
started
as
part
of
the
q3
work
to
make
sure
that
we
are
not
being
regressed
in
desktop
GUI
companion,
then
probably
other
places
to
around
faster
and
cadence
changes
in
cords.
Yes
and
ipfs
implementations
started
looking
at
kind
of
the
overview,
the
eye
level
view
of
what's
tested
and
what's
not
tested
and
whether
something
is
tested
automatically
when
core
things
in
core
change,
trying
to
get
a
kind
of
what
the
big
picture
is
around,
where
our
testing
and
regression
vector
gaps
are.
Is
there,
for
example,
a
question
like?
B
Is
there
a
place
where,
if
something
breaks,
we
would
have
no
way
to
new,
it
know
it
until
we
either
ship
it,
and
somebody
tells
us
or
we're
doing
manual
testing,
and
we
have
to
try
and
hope
that
we
find
it.
If
you
have
any
idea
this
around
with
there
are
issues
or
repos
that
track.
This
kind
of
work
now
be
great
to
add
it
to
this
table.
B
If
there
are
other
scenarios
that
you
know
of
that
in
in
these
three
given
parts
of
the
project
that
should
be
tested
or
other
types
of
I
just
drafted
this
list
off
the
top
of
my
head
I,
don't
really
know
how
much
of
this
already
exists.
If
none
of
this
exists,
but
it
seems
like
things
that
we
probably
want
to
exist
at
some
point
to
make
sure
that
we're
not
breaking
ourselves
without
knowing
it.
That's
fine
trying
to
break
ourselves.
That's
normal
part
of
iterative
development.
B
We
just
want
to
know
when
we
break
ourselves,
so
we
can
unbreak
or
pour
back
out
I've
changes
that
are
breaking.
So
if
you
have
any
thoughts
about
this
kind
of
work,
this
probably
actually
should
be,
and
then
maybe
the
testing
and
infer
a
group
as
well,
so
maybe
I'll
stop
by
there
meeting
next
week
and
share
this.
A
E
We're
on
to
the
next
one,
which
is
mine,
I'm,
going
to
keep
this
short,
so
there's
an
issue
on
the
piers
tab
in
the
web,
UI
I.
Once
you
get
past
like
a
hundred
piers,
it
starts
to
get
kind
of
slow
and
it's
actually
already
noticeable
with
a
lower
number
of
piers.
If
you
scroll
through
the
table,
you'll
notice
that
the
table
appears
and
dissapears
while
you're
scrolling
and
the
reason
it's
doing.
E
So
after
looking
at
it,
I
think
we've
got
a
few
choices
there,
one
of
the
things
that
I
initially
thought
was.
Maybe
we
have
a
component
inside
of
the
table
that
handles
the
resolution
rather
than
so
that,
rather
than
rendering
the
whole
table,
we
just
re
render
unknown
to
whatever
the
location.
It
is
that
we
find,
and
that
way
we
don't
have
to
worry
about
re,
rendering
a
whole
table.
E
The
other
option
is
to
use
something
like
rxjs
or
a
reducer,
some
kind
of
transducer
to
take
the
massive
amount
of
data
and
then
debounce
it
I
guess
so
that
it
it
doesn't
rerender
every
time
up
here
gets
resolved.
Instead,
it's
only
rear-ending.
You
know
every
minute
or
something
or
not
every
minute,
every
second
or
something
like
that,
so
that
it's
not
every
10
milliseconds.
However
often
it's
happening
right
now,
I
just
wanted
to
see,
if
you
guys
have
any
opinions
on
that.
E
I
couldn't
tell
you
the
exact
number
I
had
it
set
up
to
log
every
time
it
was
rendering,
and
it
was
enough
that
it
was
scrolling
faster
than
I
could
keep
up
with
and
I
can
get
stats
for
that.
If
that
would
be
helpful,
but
it's
it's
really
often
at
the
very
beginning,
and
then
after
that,
it's
it's
much
slower
as
it's.
You
know
resolving
fewer
and
fewer
peers.
Since
it's
already
tried
to
go
through
the
majority
on
the
list,
so
yeah
I
can't
tell
you.
E
E
So
once
you
stay
on
that
page
for
a
while,
then
it's
not
an
issue,
but
if
you've
got
you
know,
I
think
the
issue
came
up
when
one
had
like
26,000
peers
connected,
which
is
insane
and
obviously
that's
not
gonna.
Go
that's
not
going
to
end
after
a
minute.
You're
gonna
be
resolving
peers
for
as
long
as
you're
on
that
page
so
definitely
noticeable.
There.
A
E
They
actually
have
that
in
place
now
for
the
resolution
of
the
locations.
They
have
a
queue
set
up
with
concurrency
and
all
of
that,
so
it's
it's
getting
throttled
already,
but
it's
still
happening
too
often
for
the
rendering
phase.
So
it's
almost
like
there
needs
to
be
another
throttle
outside
of
the
resolution.
That's
happening
to
prevent
over
rendering
as
well,
because
it's
resolving
fat
really
fast,
but
we
don't
want
to
render
out
all
of
that
as
soon
as
it
comes
through
just
because
it
could
be
problematic
for
large
data
sets.
A
Go
with
with
the
bouncing
it
goes
like
it's
probably
safer,
but
to
decrease
the
right
will
refresh
like
it
does
not
need
to
be
that
fast.
It
does
not
need
to
be
that
exact,
honestly,
I,
don't
think
people
would
be
worried
if
it
like
refreshed
once
a
second
yeah
you
won't
have,
even
if
you
occur
about
like
latency
:,
if
you
like,
refresh
faster
than
like
half
a
second,
it
loses
its
meaning.
Yes,.
F
A
C
C
One
of
the
tactics
that
we
thought
might
be
interesting,
useful
towards
improving
the
you
know.
The
overall
docks
experience,
making
the
docks
more
effective
is
to
put
a
little
quiz
or
a
little
sort
of
a
little
menu
encapsulated
menu
of
listing
the
kinds
of
things
that
I
might
want
to
do,
or
with
ipfs
or
get
out
of
ipfs.
Basically,
why
I
am
visiting
ipfs
dot
IO
the
two
possible
improvements
that
could
come
out
of
creating
a
little
utility
like
this?
C
Are
you
know
we
kind
of
get
a
better
idea
of
what
people
are
visiting
the
site,
what
they
want
from
the
site
so
that
can
inform
personas
or
whatever
you
know,
we've
got
developers
who
got
researchers.
We
have
all
sorts
of
people
in
theory
who
are
coming
to
ipfs,
that
IO
and
then,
additionally,
we
could
be
channeling
people,
maybe
those
people
more
effectively
into
the
content.
C
That's
in
the
content
that
we
have,
whether
that's
the
helpful
content,
that's
in
Doc's,
maybe
or
it's
in
proto
school
or
you
know-
maybe
it's
in
a
thread
somewhere,
but
currently
the
the
layout
of
Doc's.
You
know
the
organization
of
Doc's,
you
know,
needs
a
little
bit
of
information
architecture
work
anyway,
and
also
it's
not
all
on
Doc's
right,
and
so
we
have
actually,
why
don't
I
just
go
to
the.
C
If
you
check
out
this
the
lint
issue,
maybe
you
already
have
theirs?
It's
it's
interesting
to
see
where
all
these
links
actually
go.
When
you
are
in
an
IPF
sto,
just
as
a
sidebar,
you
know
they.
They
click
to
places
that
are,
you
know
disparate
and
some
of
them
look
similar.
Some
of
them
don't
look
similar,
they
click
it
or
you,
and
even
the
structure
of
the
of
the
site
is
modified
a
little
bit
when
you
click
in
some
into
it,
such
as
the
the
blog
section
when
you
click
into
the
blog.
C
All
of
a
sudden,
the
top
nav
gets
an
additional
item
added,
which
is
media
and
that's
the
only
place
I
could
find
the
media
in
the
top.
Now,
if
and
secretly
like
so,
if
you're
very
good
I
have
a
very
good
eye
for
detail,
you
might
be
able
to
find
our
media,
my
PFS
dot
IO,
and
this
is
a
proposed
reflow.
C
So
currently
it
says,
try
it,
we
have
try
it
and
then
what
does
it?
Learn
more
or
something
I've
already
forgotten,
watched
Anna,
so
watch
demo
links
to
a
video
from
2015,
which
has
which
is
vintage.
You
know,
and
people
like
vintage
stuff,
so
that's
valuable,
maybe,
but
it's
also
and
it's
in
Aswan,
you
know
and
it's
well-informed
and
whatnot,
but
it's
maybe
not
the
best
thing
to
be
to
have
right
at
the
top
of
the
page
right
now
and
try
it
which
scrolls
you
down
the
page
to
the
implementations.
C
There
are
multiple
issues
going
on
here
and
hopefully
what
we're
proposing
as
a
really
quick
test
to
implement
within
a
couple
days
will
actually
also
maybe
you'll
alleviate
or
give
us
a
window
into
how
we
might
alleviate
some
of
these
extra
issues
like
the
fact
that
implementations
and
install-
or
you
know
it's
kind
of
a
conflation
going
on
there.
If
you
click
in
to
install
it,
brings
you
to
the
you
know
the
CLI
install
ipfs
and
implementations
down
here
it
goes
to
you
has
go.
C
Javascript
best
does
not
have
the
other
link
to
the
other
way
of
installing.
So,
there's
a
little
bit
of
confusion
in
my
mind,
I
reckon
there
is
some
people
have
some
confusion
so
here
instead,
what
if
we
had
a
simple
button
which
was
I,
don't
know
if
it
was
get
started,
just
simple,
simple
call
to
action,
which
would
lead
people
either
further
down
on
the
page
or
to
another
page
and
actually,
when
I
jump
in
be
in
vision
demo
have
you
all
actually
already
found
the
envision
prototype?
C
C
Roughly
these,
these
for
questions
or
needs
are
where
we've
landed.
I
need
to
learn.
I
want
to
learn
about
the
distributed
web.
I
want
to
store
and
share
files.
I
want
to
do
a
manage
large
amounts
of
data.
This
might
be.
You
know.
Each
of
these
implies
a
certain
user
group.
So
without
coming
right
out
and
saying
it,
I
am
an
individual.
I
am
I'm
an
individual
and
I
want
to
short
store
and
share
files.
You
know
we
can.
We
can
figure
out,
make
a
good
guess
of
what
kind
of
people
those
are
so
yeah.
C
We
might
do
these
simple
accordions
that
then
drive
drive
people
to
some
of
this
sort
of
curated
links
right.
So
maybe
some
of
the
content
we
have
in
Doc's
right
now
is
useful
if
you're
like
really
hardcore
and
drilling
drilling
drilling
and
your
very
specific
problem,
but
perhaps
the
lion's
share
of
them
are
the
most
useful.
10Th
is
a
lot
smaller
of
a
list.
C
You
know
it's
a
lot
more
manageable,
a
collection
and
some
people
currently
might
have
trouble
finding
discovering
what
those
are,
and
so
this
is
a
way
to
to
lead
them
there
more
efficiently
and
of
course,
all
of
this
would
be
measured.
We'd
have
metrics
for
all
this,
so
we
can
get
a
good
idea
like
oh
pretty
much.
Everyone
wants
to
implement.
Ipfs
wants
to
use
ipfs,
so
we
need
to
prioritize
the
devs,
as
our
you
know,
a
primary
use
case,
which
is
actually
probably
the
truth
and
and
the
catch-all
as
well.
C
C
In
a
and-
and
it's
just
a
really,
you
know
we're
putting
so
much
attention
into
making
this,
not
just
you
know
not
a
beginners
per
se
in
application,
so
much
as
a
handy
and
super
easy
to
use
at
handy
utility
that
helps
everyone
understand
what
the
nuts
and
bolts
are
of
ipfs.
You
know,
and
it
helps
developers
understand
more
about
how
it
works,
and
it's
it's
visual.
So
then
just
haven't
have
the
rest
of
the
of
the
various
app
some
of
the
apps.
D
Have
a
question
about
this
extra
bution
page
visit:
do
people
who
know
more
than
me
feel
really
strongly
that
it
should
say
distributions
not
downloads
like
you
go
there,
and
it
says
this
is
the
Downloads
website
to
people.
Everybody
else
know
what
the
word
distribution
means
and
that
you
click
it
and
go
to
downloads.
D
B
B
I
I
think
we
agreed
it's
a
problem.
I
do
that's
why
I
brought
it
up?
Okay,
yeah
it
also.
It
only
has
a
subset
of
things
we
actually
ship
and
that
has
the
same
visual
uniformity.
I
can
feel
problems
that
Eric
was
trying
to
address
here.
It's
I
brought
it
up
as
a
great
exhibit
of
all
of
the
problems,
disconnected
visual
uniformity,
lack
and
not
even
actually
accurate
and
late
language
specific
to
it
to
its
specific
domain
and.
H
C
A
F
Basically,
when
we
want
to
connect
one
package
to
another,
let's
say
we
have
a
package
full
of
tests
and
we
have
gsm
FS
and
just
a
bit
of
s,
imports
the
tests
to
run
so
sometimes
when
we
are
developing,
we
need
to
change
the
tests
in
one
place
and
then
run
it
in
another
place.
Let's
say
the
test
and
JSF
FS.
F
When
we
have
this
situation,
you
need
to
link
them
locally
in
our
machine
to
be
able
to
develop
fast,
or
else
we
would
need
to
change
here
into
our
ways
and
then
pull
the
rulli's
on
this
side
and
run
tests,
which
is
very
awesome.
So
we
link
and
yarn
and
npm
have
this
functionality,
which
is
link
one
package
to
another,
but
basically
link
has
a
big
big
problem.
That's
what
I'm
going
to
show
you
and
how
connect
that
this
new
package
that
builds
the
solves
that
problem.
F
F
F
It's
only
these
ones,
and
this
happens,
because
when
you
install
NPM,
there's
a
bunch
of
stuff
and
basically
the
duplicates
a
bunch
of
dependencies
and
arrange
them,
so
we
don't
have
like
a
million
of
them
and
if
and
only
one
version,
so
the
dependencies
are
quite
small.
Then,
if
you
want
to,
if
you
want
to
do,
if
you
link
directly
as
I'm
doing
here
in
the
the
console
I'm
using
yarn,
because
I'm
gonna
use
yarns,
it's
the
same
thing
at
the
end
game,
we
are,
if
you
link
Asia
what
happens
it's.
F
Basically,
this
the
folder
becomes
like
stupidly,
big
because
it's
basically
doing
symlink
from
one
folder
to
the
other.
So
what
the
problem,
the
big
problem
here,
what
is
that
dependency
tree
is
not
the
same.
If
we
do
a
clean,
install,
you
get
the
first
version
that
you
saw.
If
you
link
you
get
this
version,
so
it's
not.
It's
basically
not
the
same
codebase
and
that
sometimes
gets
us
into
big
troubles,
because
we
find
some
error
and
we
don't
know
where
it
comes
from
and
probably
is
from
this
specific
problem.
F
F
So
it's
we
go
back
one
folder,
and
then
we
have
Asia
here,
and
this
gives
us
some
little
extra
files
here
so
just
to
keep
track
of
things.
And
then
we
want
to
connect
easier
or
just
connect
connect,
and
this
is
packing
easier
and
installing
the
asia
on
JSP
FS,
directly
from
the
zip
file
or
the
tar
file,
and
when
these
hands
this
normal
is
faster.
When
zoom
is
not
running.
F
So
when
you
reject
everything,
gets
clean
and
gets
reverted
to
the
previous
site
and
you
get
clean
a
clean
ripple
with
no
changes
at
all.
As
you
can
see,
my
editor
is
telling
me
there
is
no
change
at
all
in
this
ripple,
so
it
reverted
correctly.
So,
basically,
this
is
our
connect.
Apps
words
just
wanted
to
show
you
this,
because
if
you
are
a
developer,
this
might
be
useful
free
that
that's
it.
F
A
Awesome
honestly,
at
least
one
one
guy
will
totally
appreciate
it,
because
in
ipfs
companion,
when
I
work
on
Jes
ipfs
with
those
polyfills
on
top
of
chrome
sockets,
that
we
need
to
like
to
get
it
like
nodes,
net
module
and
stuff
like
that,
and
we
also
run
happy
Jas
in
web
browser
and
happy
Jaya
has
slowed
some
from
it.
Some
like
server-side
modules,
so
long
story
short.
A
F
You
can
connect
multiple
packages
at
the
same
time
and
you
all.
You
also
have
a
watch
mode
which
basically
watches
for
changes
and
does
everything
automatically.
So
you
don't
need
to
worry
about
it
just
code,
it's
a
it's
a
little
bit
slower
or
much
slower,
because
young
link
doesn't
take
any
time
at
all,
because
it's
just
a
link,
but
at
least
it's
correct
and
doesn't
give
you
problems.
Yep.