►
From YouTube: Web Browsers and GUI WG Weekly Sync - 2018-03-19
Description
Tracking the Path to getting IPFS and other Decentralized Protocols Natively Supported in Web Browsers:
https://github.com/ipfs/in-web-browsers
A
A
A
A
So
a
couple
of
like
pre
points,
I
am
sort
of
currently
the
de
facto
champion
of
a
working
group
that
has
no
working
group
in
that
we've
got
this
PM
GUI
slash
in
web
browsers,
crossover
so
in
lieu
of
anyone
else
wanting
to
write
lots
of
github
issues.
I
am
putting
myself
forward
as
the
schmuck
who
will
lead
the
github
issue
charge
to
great
glorious
gooey
future.
A
But
the
idea
is
that
maybe
we
should
there
was
some
chewing
of
throwing
right
at
the
beginning
of
this
in
web
browsers,
GUI
working
group
existence
and
over
everyone
from
core
was
like.
Don't
have
weekly
meetings
because
then
you'll
have
a
hundred
weekly
meetings
and
then
you
you,
you
won't
get
anything
done.
I
think
we're
at
the
other
end
of
the
spectrum,
where
we
don't
have
enough
face
time,
yeah
and
we're
not
really
a
team
and
I
would
like
to
see
more
of
your
faces,
so
I
kind
of
pestered
David.
A
C
A
Good
all
right,
it's
the
water
good,
so
just
just
as
a
preamble
I
would
really
like
to
check
in
with
you
all
Lydell
I
want
I
want
people
to
tell
me
how
they're
feeling
I
want
people
to
tell
me
what
their
workload
is.
I
don't
want
it
to
take
very
long
like
two
sentences
on
where
your
head
is
at
right.
Now,
Lytle.
Can
you
kick
us
off
yeah.
B
So
like
the
first
quarter
is
nearing
its
end
and
obviously
I
am
far
behind
with
my
okie
arse,
like
mostly
the
number
one
okay
like
he
result,
I
hoped
from
this
quarter
was
this:
addressing
from
the
distributed
web.
Yep
I
tried
to
start
it
like
like
last
week,
but
I
failed
to
synchronize
with
flowers.
Okay,
we
realized
that
we
have
nearly
the
same
item,
and
so
we
just
I
just
want
to
coordinate
with
flowers
so
that
there's
no
duplicate
data
fault,
especially
that
he
created
the
outline
and
I
suspect
he
already
had
some
text.
B
B
That's
like
my
only
concern,
but
it
has
the
highest
priority
and
what
not
addressed
apart
from
the
odds,
the
ipfs
compile
it's
quite
well.
I
am
bit
skittish
when
it
comes
to
making
care
final
release.
Iii,
like
III
I'm,
not
able
to
put
my
finger
what's
wrong,
but
I
think
there
is
like
something
like
regression,
maybe
may
be
related
to
my
local
machine,
but
I
suspect
the
user
interface
works
faster
in
the
last
stable
release.
B
So
before
I
make
final
release,
I'll
probably
do
a
release
candidate
this
week,
okay,
just
and
suggest
encourage
others,
probably
today
on
their
own
hands,
quickly,
encourage
others
to
yeah
test
it
before
we
push
it
and
before
I
make
a
blog
post
advertising.
How
wonderful
it
is,
you
probably
should
be
sure
it
is,
and
we
may
decide
to
push
the
blog
post
one
release
later.
B
Okay,
that's
fun
like
my
idea
is
that
we,
if
we
deliver
a
better
sharing,
that
we
discussed
recently,
that
might
be
a
much
better
experience
and
but
much
better
reason
to
advertise.
However,
like
this
release
was
very
technical
way
about
that
window,
ipfs
object
and
but
that
is
ipfs,
so
I'm
a
little
bit
torn
between
advertising.
This
like
release
for
developers-
and
maybe
we
want
to
make
the
actual
stable
release
when
we
have
those
sharing,
can't
upload,
UX
provements,
sorry
for
like
rambling,
but
just
like
those
are
two
things.
I
am
constant
right
now.
A
And
fair
enough,
it's
not
all
on
your
shoulders.
I
think
the
thing
to
do
is
is
make
yourself
a
release
checklist
which
includes
beta
testing
from
the
rest
of
us
and
if
we
all
give
it
the
thumbs
up,
you
know
it's
not.
You
don't
have
to
feel
like
you're,
the
sole
gatekeeper
of
the
integrity
of
the
project,
yeah
I
think
like
I,.
B
A
That's,
okay,
but
my
check-in
was
gonna,
be
a
bit
more
like
I'm
feeling
pretty
positive,
because
I
I
started
off
on
the
research
for
the
gooey
stuff,
thinking
that
it
might
have
been
a
waste
of
time
and
I
now
I'm
pretty
confident
that
it
was
very
much
needed.
At
least
it's
helped
me
figure
out
a
bunch
of
stuff
that
is
missing
in
my
head
and
I
hope.
It's
useful
for
you
guys
to
see.
A
C
E
D
C
Nice
microphone
I
forgot
the
plug
for
it.
You
know,
USB
sees
a
difficult
anyway,
let's
see
I
so
this
week,
I
was
happened
to
be
done
in
Austin
and
I
talked
with
something
on
the
dot
project
about
you
know:
hey,
you
know.
If
you
wanted
web
browser
integration,
what
would
what
would
you
want
right,
like
the
idea
was
to
sort
of
like
find
the
sort
of
like
common
ground
for
like
what
everyone
in
the
space
needs
to
do?
C
You
know
distributed
web
implementations
inside
web
browsers
and
after
I
got
their
notes.
I
went
over
to
Portland
and
I
visited
with
two
people
at
Mozilla,
Gazala
and
Dietrich,
and
talked
with
them
a
little
bit
about
that
and
the
consensus
that
we
sort
of
put
together.
It
was
that
we
should
definitely
get
everyone
on
some
kind
of
a
mailing
list,
or
something
and
and
and
since
that
we
can
have
a
place
to
collaborate
on
these
issues.
C
C
Like
you
know,
like
you
know
the
secure
spell
about
people-
and
you
know
anyone
else
that
you
know
the
what
new
for
us
right,
but
anyone
that
needs
this
stuff
because
we're
all
kind
of
trying
to
build
the
same
thing,
which
is
a
peer-to-peer
stuff
in
browsers
right,
and
so
that's
what
I
did
this
week
and
yeah
and
also
as
far
as
I,
quickly
examine
see
you
guys
in
a
while
you've
done
really
amazing
work
on
the
desktop
stuff.
It's
really
nice.
You
know
yeah
I,
love
that
you're.
C
Looking
at
the
GUI
side
of
things,
because
to
me
like
graphical
interfaces,
are
like
the
way
forward,
eventually
like
I
see.
This
fundamentally
is
going
to
eventually
has
to
become
an
interface
problem,
and
so
you
know
the
better
interfaces
are
the
closer
I
think
you'll
get
to
something
that
people
will
start
using
on
a
regular
basis.
So.
A
Very
cool
one
of
the
other
okay
ours
that
is
sat
very
unfinished
in
my
on
my
laptop,
is
the
jumping-off
point
for
the
conversations
with
multiple
browser,
vendors
and
peer
to
peer
stakeholders.
The
are
we
distributed
yet
calm.
Web
site,
which
is
I,
think,
was
going
to
be
a
bit
of
a
eye
candy,
initially
a
record
just
an
eye,
candy
kind
of
make
the
point
in
a
pleasing
way
and
link
to
the
most
relevant
pressing
issues
like,
as
you
said,
there's
some
easy
ones
like
if
web
RTC
bugs
were
fixed.
C
To
take
a
look
at
that
site
because,
like
my
and
I
talked
to
goes
all
a
little
bit
about
this
about
the
idea
of
like
us,
making
a
sort
of
manifesto
site
right,
this
sort
of
like
opening
idea
as
a
public
discussion
and
as
in
like
there's
a
web
page,
it's
like
hey
are
we
distributed
yet
yeah.
This
is
what
we
need
in
browsers.
Oh
yeah,.
C
A
The
pitch
for
oh,
we
disagree
yet
I'll
come
right
now,
there's
no
reason
why
it
can't
be
that
it
I
think
it
was
the
way
I'm
thinking
about
it
at
the
minute
is
to
be
something
like
is
service
workers,
ready,
calm,
but
slightly
I'm
or
hey
and
Rick,
and
but
so
that
was
very
focused
on
some
explicit
specs
that
already
exist,
and
then
issues
to
various
browser
manufacturers
to
say,
like
either
they're
enthusiastic
about
building
is
they've
already
committed.
So
that
kind
of
that,
but
we
can.
C
The
beginning,
that's
beautiful,
keep
doing
that.
That's
absolutely
perfect
and,
like
the
whole,
you
know
I
was
kind
of
half
joking
with
the
manifesto
thing,
but
you
know
just
you
know
like
a
little
copy
stuff
that
maybe
here
and
there
but
I'm,
definitely
so
how
far
away
through
our
far
are
you
with
the
should
I
take
a
look
at
it.
A
I
not
very
far
tool
beyond
I've
got
a
I
got
a
sense
if
it's
gonna
fit
together.
I've
I've
got
a
skeleton
there,
but
the
hardest
part
honestly
for
me
right
now
is
wording
is
the
precise
sure
but
approachable
wording
for
each
issue.
Yeah,
because
the
we've
got
screeds
all
over
the
place
about
all
the
things
we
need,
but
trying
to
do
it
in
a
way.
A
A
What
it's
gonna
be
right
now,
yeah
it
may
get
fancier
and
get
driven
from
github
issues
at
some
point,
but
not
just
make
it
sounds
perfect,
exactly
say,
bomb
I,
but
so
yeah
definitely
playing
us.
When
you
get
a
chance
to
write
up
any
other
stuff,
you
found
out
I.
Well,
thank
you
so
and
reek.
How
are
you
doing
you?
You
missed
a
quick
check-in
from
everyone.
A
D
D
D
A
Super
cool
you
forget
that
you're
talking
to
the
ipfs
in
web
browsers
and
GUI
team.
This
is
exactly
what
we
want
to
hear
know
what
one
other
question
for
you
I'm
aware
that
you
also
have
other
things
pressing
on
your
time,
what
kind
of
availability,
if
you
got
kind
of
for
the
next
couple
of
weeks,
you
50%
on
IPA
finesse
percent,
free,
because
this
is
nice,
don't
forget,
don't
forget
to
read
your
books,
yeah.
D
A
A
Break
it
well,
I
hope
you
enjoy
so
and
if
anyone
has
any
other
issues
they
want
to
discuss
on
this
call.
I
will
happily
divert
everyone's
time
and
attention
to
the
discussion
of
scoping
the
existing
ipfs
GUI
apps.
Are
we
happy
with
the
existing
scoping?
Does
anyone
share
my
enthusiasm
for
or
reviewing
the
existing
scoping,
so
I
think
you've
all
seen
and
I've
said
it
enough
times?
There's
a
bunch
issues
on
the
PM
ipfs
key
website
that
was
my
take
on
the
existing
feature
set
that
seems
to
be
important.
A
There's
like
the,
if
anyone
thinks,
if
anyone
any
specific
questions
now
would
be
a
good
time
to
raise
them
before
I
get
a
bit
more
abstract
about
app
scoping
anybody,
nope,
okay
right!
So
what
it
strikes
me.
The
thing
that
I
was
saying
we're
at
the
beginning
of
the
call
is
I'm
concerned
that
we're
reviewing
the
scope
of
the
IP,
invest,
GUI
apps,
and
just
to
confirm
that
I'd
be
less
desktop
like
putting
ipfs
as
a
native
integration
to
your
operating
system.
A
A
C
C
One
of
the
things
that
sort
of
been
interesting
to
me
personally
is
that
the
desktop
is
sort
of
a
potential
jumping-off
point
for
doing
sorts
of
like
interesting
things
related
to
like
demoing,
like
security,
origin
level
like
Windows,
that,
like
load
web
pages
and
stuff
like
that
right
and
you
know
using
the
lucky
uses
electron
as
I
and
and
and
and
and
electrons
just
a
chrome
window,
and
so
like
it's
a
pretty
short
step
to
do.
Things
like
you
know,
be
able
to
load
like
ipfs.
C
You
know
content
like
in
a
security
origin
in
a
in
a
window.
That's
like
similar
to
the
way
browsers
work,
I
mean
it
I'm.
Just
not
not
saying
this
is
a
web
browser,
but
like
I'm,
saying
that
you
could
put
something
like
this
into
I,
see
it
as
desktop
right.
Some
flavor
of
this
R
you
can
like
load
web
pages
or
something
like
that.
C
It
might
be
kind
of
interesting
to
see
if
you
could
like
use
it
that
way
or
not,
but
I
don't
know
if
there's
like
the
will
or
the
interest
in
that
idea
or
not
to
do
that,
but
it
just
seems
like
an
interesting
branching
off
point.
You
know
we
can
do
things
like
IP
FS,
colon,
slash,
slash,
which
we
can't
do
with
regular
browsers
right,
yep,
the.
A
A
So
I
really
want
to
I
really
want
to
commit
to
one
path
or
the
other
for
desktop
like
it
should
we
should
either
be
building
like
a
Dropbox
alike,
minimal
drop-down,
menus
that
then
hands
off
major
functionality
to
a
web.
Ui,
that's
separate
or
desktops
should
be
a
proper
desktop,
app
and
screen
real
estate
shouldn't
be
a
pressing
concern,
but
at
the
moment,
with
the
design
feedback
that
we
were
getting,
people
seem
to
want
it
to
be
both
to
do
both
things,
and
that
seemed
like
an
unrealistic
expectation
to
me.
A
C
Yeah
I
mean
deaf
from
my
from
my
perspective.
Like
the
ipfs,
you
know,
desktop
app
is
going
to
become
VIP
at
best
app
at
some
point
in
X
like
to
you
know
a
few
years
or
something
like
to
me
like
right,
I,
don't
think
I,
don't
think
it's
practical
for
like
people
to
like
download
a
UNIX
daemon
that,
like
is
like
running
like
kind
of
command-line
and
like
if
we
want
to
start
getting
like
mask
ins
mass
adoption.
You
know
at
some
point.
C
We
have
to
have
a
graphical
interface
that
works
well
for
them
or
integrate
into
things
that
they
use
everyday,
then,
and
so,
like
you
know,
the
neat
thing
about
desktop
is
that
it
lets
us
get
that
that
massive,
more
users
like
on
a
non
super
professional
basis
before
that
happens
before
we
start
integrating
in
browsers
and
stuff
like
that,
right
and-
and
so
it's
I
mean
to
me
like
I
I-
would
like
it.
When
people
go
to
IP
festivai,
oh
there's
a
button,
they
click
and
they
installs
an
application
that
they
can.
C
That
mom
you
know
like
and
and
that
works
right
now
for
UNIX
programmers.
You
know
it's
great
for
everyone
down
here
in
Silicon
Valley,
but
you
know
I'd
love
to
see
I'd
love
to
see
like
you
know,
everyone
else
be
able
to
use
this
technology
to
and
so
like.
That's
why
I'm
so
interested
in
the
browser
stuff
and
why
I'm
so
interested
in
the
desktop
guys.
C
They've
done
amazing
work
on
it's
gotten
so
much
better
and
and
and
so
that's
sort
of
my
thought
right
and
yeah
me
I
guess
in
that
dichotomy
of
like
should
be
minimal
versus
desktop
application.
I
think
it's
just
I
think
it
should
be
a
desktop
application.
You
know
I
think
it
should
have
like
a
GUI
I,
think
it's
just
have
like
controls
and
like
browsers
and
I
think
that
it
should
be
able
to
pop
up
in
the
web
page,
and
you
know
that
whole
thing
right,
like
yeah.
That's.
A
A
But
this
is
the
kind
of
thing
that,
if
you
have
strong
opinions
about
it-
or
if
you
have
questions
about
it
or
you
don't
kind
of
understand
what
it
is
I'm
trying
to
get
out,
then
the
call
is
a
good
place
to
ask.
If
you
have
strong
opinions
about
it,
you
can
state
them
now
or
feel
free
to
drop
them
on
the
scoping
issue,
because
this
is
exactly
what
I
want
to
bottom
out
until
we
as
a
group,
decide
this.
We
can't
make
useful
progress.
Jared
did
you
have
your
hand
up
different
yeah
I
did.
F
So
I
guess
it's
kind
of
opinions
that
lead
to
questions
potentially,
but
just
general
I'm
kind
of
new
to
everything.
So
stop
me
if
I'm
saying
something
wrong
by
different
I,
see
ipfs
in
general,
as
you
know,
trying
to
develop
the
new
distributed
web,
it's
kind
of
in
some
sense
replacing
the
web,
but
keeping
all
the
good
stuff.
E
C
Yeah,
okay,
so
Mike
I
think
that
yeah
a
little
bit
so
just
quickly
I
mean
the
idea
of
long
term
is
that
we
want
to
be
in
web
browsers
like
that's.
The
general
approach
is,
like
you
know,
get
into
Firefox
get
into
Chrome.
The
the
problem
is
that
the
interfaces
that
we
require
and
are
from
the
browser
manufacturers
in
order
to
do
that
are
not
currently
available.
C
For
example,
socket
support
doesn't
exist,
which
means
you
have
to
use
WebRTC,
which
is
not
designed
for
hundreds
of
connections
with
your
networks,
everyone's
having
the
same
problems
with
that
mr.
beauty,
web
space.
The
other
thing
so
there's
just
like
a
few
things
like
that,
like
security
origins,
like
is
an
issue
when
you
have
like
pathogen
security
problem.
You
know
that
which
doesn't
exist
yet
it's
suspect
but
nobody's
implanted
it,
and
so
the
idea
is
just
sort
of
that.
This
could
be
sort
of
a
demo
of
like
things.
C
A
You
could
do
so.
I
was
more
railing
about
the
the
question
of
the
day.
For
me,
is
we've
been
tasked
with
reviewing
and
improving
the
implementation
of
the
existing
IP
FS
apps
themselves.
So
this
is
a
slightly
separate
question
to
how
do
people
make
apps
that
make
use
of
ipfs,
but
it's
all
relevant
just
just
to
get
back
to
the
question
of
the
scope
of
the
existing
IP
FS
desktop
app.
The
question
on
the
table
is:
should
it
be
minimal
menu
tray?
A
Should
it
be
maximal,
I
think
there's
some
leaning
towards
it
being
maximal
it
the
reason
why
the
scoping
isn't
limited
to?
What
should
we
do
to
desktop,
though,
is
there
is
also
the
open
question
of
what
should
happen
to
the
ipfs
web
UI
implementation.
So
this
is
the
question
of
that.
There
was
a
right
at
the
start
of
this
projects
life.
There
was
an
issue
raised
that
someone
said
my
shoes.
We
just
abandon
web
UI.
So
there's
a
there's
been
a
slight.
A
If
the
studies
exist,
I
don't
haven't
seen
them,
and
what
I
want
to
see
is
a
bit
more
kind
of
who
at
these
apps
for
and
as
like
my
feeling
right
now
is
web
UI
is
trying
to
trying
to
serve
everyone
and
not
succeeding
particular,
whether
that's
serving
anyone
not
to
denigrate
the
work
done,
they're
just
that
it
needs
a
lot
of
love
and
attention,
and
it
seems
to
be
given
that
it's
bundled
with
go
idea.
Fess.
A
It
seems
to
be
positioned
as
a
dashboard
manager
app
for
for
controlling
an
IP
FS
note,
but
at
quite
a
low
level,
but
then
it
includes
high
level
fancy
features
like
a
spinning
3d
globe.
That
suggests
where
peers
are-
and
things
like
that.
So
if
we
start
making
desktop
and
more
maximal
at
what
what
should
we
be
doing
with
web
UI?
What's
the
scope
of
web
UI?
Does
it
still
have
a
place?
Does
it
still
exist?
A
Current
feeling
is
yes,
it
should
still
exist.
It's
kind
of
nice
to
have
a
easy
to
playable
admin.
Visual
admin
console
for
a
gateway
for
an
IP
FS
mode,
but
it'd
be
interesting
to
kind
of
pin
a
primary
user
story
to
each
app
like
who
are
we
trying
to
serve
so
I?
Think,
as
Kyle
was
suggesting
for
the
everyman
for
most
people,
the
desktop
app
should
be
the
go-to
thing,
and
it
should
be
super
easy
to
use
and
have
a
bunch
of
baked
in
expectations
about
your
use
cases,
and
it
should
make
those
super
easy.
A
B
Was
for
Jared's
questions
like
I
had
a
depression
that
we
can
work
around
limitations
that
are
currently
in
web
browsers
regarding,
like
local
data
storage,
that
or
distributed
application
can
use
you.
You
just
cannot
rely
on
the
local
storage
provided
by
the
browser,
because,
because
of
the
security
parameter,
which
does
not
exist
right
and
if
you
use
window
ipfs
object
instead
on
your
distributed
up,
then
you
can
like
rely
on
scoping
and
security
parameter
that
we
provide
in
browser
extension
like
that.
A
C
And
I
just
wanna
say
quickly
that
in
the
context
of
I'm
actually
kind
of
indifferent
to
like
whether
it's
a
desktop
application
or
it's
the
browser,
plugins
or
something
but
just
like
when
I
got
IP
I
said
I,
oh,
but
peoples
have
the
ability
to
install
this
stuff
right,
like
this
bill
install
like
an
ad
ipfs
web
browser
like
add
print
and
install
the
desktop.
It's
nothing
right
like
that
whole
idea
right,
it
just
happens.
A
So
as
a
tiny,
tiny,
quick
win,
Lydell
posted
an
issue
that
is,
we
can
now.
We
can
now
instruct
chrome
to
recommend
installing
a
chrome
add
on
from
any
arbitrary
web
page,
so
we
can
have
a
kind
of
click
button
on
our
give
us,
though,
that's
like
you
should
get
you're
using
Chrome.
You
should
hit
this
button
and
install
the
Chrome
Matalin,
and
that
is
like
you
know.
That's
like
a
couple
of
hours.
A
And
then
we
can
update
the
website
to
instruct
people
on
how
to
install
the
plug-in
but
I
think
as
we're
all
kind
of
aware,
there's
bigger
problems
than
just
getting
people
to
install
the
plug-in
at
the
moment,
because
we
still
don't
quite
the
plug-in
is
like
pointing
to
web
UI
and
things
like
that
and
can't
be
used
without
also
going
to
install
a
binary.
So
right,
yeah.
C
A
C
B
A
B
A
A
Not
it
shouldn't
pretend
to
be
a
menu
tray
anymore,
and
we
need
to
review
the
designs
for
desktop
if
that,
if
that
but
I'd
like
to
see
people
fill
out
their
their
thoughts
or
at
least
just
+1
existing
thoughts
on
the
scoping
issue,
if
that
is
the
will
of
the
group,
because
it
is
a
change
from
the
direction
that
desktop
is
going
in
at
the
moment
at
the
moment,
desktop
is
trying
very
hard
to
be
as
small
as
possible,
but
isn't
it's
not
tiny?
It's
just
a
very
weird
small
desktop
app.
F
Thanks
portal
to
address
titles
question
earlier
and
what
you
just
actually
asked
about,
so
my
sort
of
mental
gateway
model
of
the
browser
being
the
gateway
into
new
life,
EFS
stuff
that
could
be
easily
applied
and
some
of
the
browser
limitations
workaround
by
having
it.
The
browser
essentially
be
what
web
UI
is
kind
of.
A
Yes,
that
that's
the
other
route
that
we
can
examines
there's
there
was
a
call
for
potentially
considering
removing
web
UI
or
replacing
it
and
something
else
there's
a
problem
with
deploying
web
UI
with
go
ipfs,
which
makes
it
harder
for
us
to
improve
web
UI
outside
of
the
go
ipfs
release
schedule.
So
that's
not
very
good.
A
Lytle
has
repeatedly
mentioned
that
bundling
a
web
UI
with
the
go
demon
has
led
to
an
unlimited
security
issues
with
other
people's
deployments,
because
they
immediately
try
and
open
the
api
ports
and
to
make
the
web
UI
available
to
them
on
other
notes.
So
like
bundling
this,
if
HTML
viewer
with
go
seems
to
set
a
bad
precedent,
or
at
least
would
need
a
lot
of
it
needs
reconsidered.
From
an
author
point
of
view,
it
needs
a
definition
of
what
its
primary
use
case
is
like.
A
A
A
My
bigger
concern
is
that
I
don't
have
a
clear
sense
of
which,
what
user
story,
what
user
goal
each
app
is
intended
to
mostly
fulfill.
So
we're
reaching
consensus
on
the
idea
that
desktop
is.
It
would
be
of
highest
value
if
it
was
the
one
true
place
to
point
all
casual
users,
you
know,
and
it
included,
introductory
material
that
seems
to
be
coming
across
and
no
one
has
spoken
against
that
which
would
which
solves
a
few
design
questions.
You
know
we
don't
we
don't
have
to
make
it
as
small
as
possible.
A
A
So
then
the
net,
the
other
side
of
scoping,
is
what
what
is
web
UI
purpose
and
how
does
it
relate
to
a
maximal,
desktop
map
and
a
minimal
ipfs
companion
browser
plug-in
I'm,
deliberately
not
really
discussing
the
purpose
of
the
browser
plug-in
because
it
seems
pretty
obvious
and
not
really
worth
debating
like
it's.
Its
purpose
is
to
handle
ipfs
links
in
the
browser
and
get
you
to
ipfs
functionality
in
your
normal
browsing
routine
as
quickly
as
possible,
but
we
are
left
with
this
like
what
is
web
UI
purpose
versus
desktops
purpose?
G
A
G
F
G
Conversation
was
always
like
that,
and
so
I
can
see
your
point.
I
don't
know
when
to
I
I
I'm,
not
sure
exactly
if
that
will
leads
to
them
almost
like
dropping
the
web
UI
entirely.
Just
focusing
on
desktop
I
still
think
it.
There
is
some
value
to
have
like
something
that
can
chip
with
the
demon
right.
The
desktop
will
always
be
separating
so
and
the
web
UI
can
always
shift,
even
because
it's
a
web,
app
and
and
one
of
the
selling
points
in
the
past
was
also
see.
G
I
can
even
the
dashboard
or
like
the
FS,
it's
an
application
on
my
PFS
and
can
be
divided
in
pieces
and
for
multiple
places,
and
so
there
is
like
all
of
those
bits
of
conversation
that
we
had
in
the
past,
which
we
haven't
have
in
the
last
year
like
we
now
do
other
demos
like
fear
path
and
so
on.
If
you
amazed
people
so
I,
yeah,
yeah,
I,.
A
C
So
we
need
to
have
like
away
for
like
people
to
manipulate
like
dag
objects
and
stuff
like
that
right,
some
sort
of
a
in
a
manipulation
interface.
You
know
for
more
like
a
database
level,
style
interface
and
then
for
people
that
want
to
use.
You
know,
I,
believe
s
for
distributed
web
for
web
browsers.
You
know
like
they
have
some
kind
of
a
window
that
comes
up
that
like
loads,
that
web
pages
or
something
like
that
and
that
the
security
origin.
A
Do
we
do
this
point
about
ease
of
deployment
like
if
we
can,
we
can
deploy
all
these
things
as
web
applications.
Should
they
just
should
we
just
rebuild
web
UI
to
be
a
lot
better,
but
stick
to
that
fundamental
deployment
target,
but
then
the
trade-off
it
again
is
well
with
a
desktop
app.
We
have
control
of.
We
have
more
control.
The
browser
does.
If
the
browser
gave
us
all
the
api's,
we
need
to
build
a
really
powerful
web
UI
right
now.
A
So
there's
a
strong
argument
for
making
desktop
the
all-singing,
all-dancing
vision
of
what
web
UI
was
supposed
to
be.
But
if
you
go
far
enough
down
that
line,
you
end
up
building
a
kind
of
workbench
thing
that
you
could
point
to
any
remote
ipfs
node
and
manage
it
as
well,
and
then
it's
like
well
doing,
which
do
we
have
enough
energy
to
also
build
a
web
UI.
A
C
C
A
F
F
On
top
up
to
some
degree,
he
could
it
essentially
release
IP
NS,
manifest
for
a
stable
version
of
the
application
set
and
then
update
dynamically
over
time,
utilizing
that
to
allow
all
the
clients
to
pull
as
they
feel
ready
to
update,
and
then
that
would
go
with
the
web
UI
implementation
allowing
that
to
update,
rather
than
it
being
bundled
with
a
daemon
and
completely
static,
based
on
that
fun
way.
I.
A
Think
I
think
people
were
talking
perhaps
about
bundling
echo
ipfs
teaming
with
a
with
an
interface
but
I'd,
say
I.
Take
your
point
without
guiness
that
there
is
some
mechanism
for
updating
things.
You
know
we
can.
We
can
launch
updates
and
that
wasn't
I
wasn't.
Quite
there.
I
was
interested
in
vitals
thoughts
on.
A
B
The
problem
with
with
web
UI
is
that
people
like
to
put
it
behind
nginx
and
expose
it
to
the
public
Internet.
That
is
why
it's
hard
coded
to
only
work
on
the
local
host,
which
in
turn
means
that
we
have
at
least
one
topic
about
this
a
week
on
bread
under
discuss.
So
that's
that's
the
UX
problem,
or
maybe
that's
a
communication
documentation
problem.
B
Maybe
it
would
be
solved
by
web
UI,
detecting
it's
running
not
from
the
local
host
and
displaying
some
kind
of
part
time
right,
and
that
way
we
would
just
not
have
this
question
I
think
asks
over
and
over
again
going
back
to
this
sculpting
I
think
the
the
the
main
problem
with
defining
what
IP
first
the
desktop
is,
is
that
a
lot
of
people
have
a
preference
to
have
a
small
application
that
just
controls
the
daemon
and
shows
the
current
notes.
That
status
is
it?
B
The
HD
server
I
think
those
things
compound
and
may
scare
people
away
and
no
matter
how
nice
you
you
I
will
be.
We
no
one
will
care
because
people
will
like
shut
it
down,
want
enable
it
to
running
in
the
background
and
I.
Think
that's
the
main
sentiment
behind
keeping
I.
Give
us
desktop
small,
but
my
opinion
personally
is
that
it
does
not
need
to
be
small
it's
just
by
default.
B
When
it
starts
with
your
system,
it
should
be
an
icon
in
the
tray
on
menu
bar
and
when
you
press
on
that
icon
that
initial
smallest
status
should
be
small
anything
else.
All
the
icons
like
icon
for
file
browser
icons
for
Pierre
Pierre
list
and
like
stuff
with
map,
all
those
things
and
configuration
screen.
Those
things
can
be
maybe
not
full
screen,
but
you
can
take
a
lot
more
screen
estate.
B
It's
just
like
I
kinda
Indic
between
those
two
approaches,
because
I
understand
that
the
initial
UI
should
be
compact
and
I
understand
why
people
have
a
strong
opinion
why
it
should
be
compact.
It's
just
a
pure
aesthetics
and
it's
a
lot
of
internalized,
like
interface
aesthetics,
that
people
have
and
people
just
don't.
B
A
Super
good
I
think
this
is
my
fundamental
point:
is
that
there
isn't
an
easy
answer
to
this
and
we're
gonna
have
to
make
some
trade-offs
and
I
want
us
to
make
them
as
a
group
and
I
want
us
to
decide
them
really
soon
and
we
don't
have
to
commit
to
them
forever.
But
we
have
to
commit
to
them
for
one
like
product
iteration
life
cycle,
so
that
we
can
release
some
really
good
apps.
A
G
G
What
each
app
should
do
web
UI
station
and
companion
it's
more.
How
can
we
converge
the
interfaces
and
make
it
pluggable
so
that
we
can
add
more
features?
For
example,
I
know
the
technique
when
he
designed
or
when
he
redesign
ipfs
desktop.
He
made
it
very
easy
for
someone
to
go
there
and
add
another
pane
and
like
so,
you
can
add
another
pane
add
another
like
initially.
G
Did
that
too,
that
in
the
web,
UI
will
be
extremely
beneficial
as
well,
because
then
people
can
customize
it
as
they
want,
and
then
when,
once
we
have
all
those
modules
like
all
of
those
features
that
you
can
plug
and
play
into
your
web
UI
session
or
companion,
then
we
can
decide
which
modules
stay
in
which
version
in
and
with
the
user
research
with
user
feedback,
then
we
can
decide
exactly
which
ones
should
stay
in
each
part.
Go
ahead.
Howie,
I,.
A
Respectfully,
disagree,
I
think
I,
think
that
sounds
good
I
think
clickability
always
sounds
great
I
think
we
will
make.
We
can
make
some
really
good,
simple
apps
if
we
know
who
we're
building
apps
for
this
is
why
I'm
not
looking
for
lots
and
lots
of
user
research
at
this
stage,
but
I
am
looking
for
us
as
a
group
to
own
a
set
of
user
stories
for
each
app
where
we
say
you
know
we're
gonna
build
this
app
for
Gateway
admins
and
we're
gonna
build
that
app
before
new
users.
A
If
you
want
a
desktop
experience
and
from
there
like
just
come
up
with
a
short
list
of
features
that
each
ones
needs
to
do,
a
really
like
seamless,
ipfs
experience
and
not
just
invent
a
bunch
of
features
that
are
plug-and-play
but
like
just
make
a
good,
simple
experience
for
each
use
case
and
then
go
from
there.
Okay,.
A
G
That
the
users
now
I
used
to
have
the
web
UI
by
default
on
their
IP
Testament,
and
they
are
used
at
least
suprem
admin
control
on
their
demon.
If
we
decide
to
design
like
a
new
dashboard
for
knelled
admins,
which
I
think
then
my
data
fest
cluster
team
would
be
also
super
interested
on
that,
then
almost
like
I,
don't
know,
call
it
the
admin,
dashboard
or
the
cluster
dashboard.
Something
like
that,
so
that
that
keeps
clear
the
intention,
all
that
dashboard
and.
E
A
Point
my
point,
my
simply
just
am
we
shouldn't
leave
it
to
other
people
to
like
if
we
make
everything
really
pluggable
and
modular,
and
then
it's
like
go
make
your
own
dashboard,
like
I'm,
happy
to
get
to
that
utopian
future,
but
we
won't
get
there
unless
we
present
some
really
coherent,
simple
apps.
First.
G
A
A
A
So
the
only
other
thing
on
my
mind
is
okay,
ours
and
we
can
very
quickly
say
we
all
feel
slightly
behind
on
them
and
that's
totally
alright
we're
in
the
same
boat
but
more
pressingly.
We
also
need
to
starts
pecking
out
our
okay
ours
for
the
next
quarter,
hooray,
but
if
we
are
all
behind
on
our
existing
okay,
as
that
makes
pecking
the
next
court
as
okay
I
was
really
easy,
cuz,
it's
probably
gonna,
look
somewhat
similar
to
the
existing
ones.
So
we
don't
need
to
chat
about
that.
A
A
huge
amount
now,
apart
from
to
all
like
emotionally
bond
over
our
shared
mild
panic
and
instead
like
let's
have
another
call
at
this
time
next
week
and
the
subject
of
that
call,
will
largely
be
around.
Let's
come
up
with
the
scope
of
our
okay
ours
for
the
next
quarter,
so
that
we
can
be
ahead,
and
so
matza
won't
bless
off
in
like
four
weeks
time
when
we
haven't
done
it
quickly.
When
is
the
end
of
the
okay
ours,
just
right,
I
was
assuming
at
the
end
of
the
month
that,
as
a
total
assumption,
yeah.