►
From YouTube: IPFS GUI and Browsers Biweekly 2020-05-19
Description
Meeting Notes: https://github.com/ipfs/team-mgmt/pull/1157
About IPFS GUI and Browsers Biweekly: https://github.com/ipfs/team-mgmt/issues/790
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
A
B
B
Countly
does
fire
off
every
Wednesday,
a
very
abbreviated
version
of
the
latest
stats
it
does
it
in
an
email
is
like
a
giant
image,
it's
so
so
what
you're
seeing
is
actually
only
some
of
the
stats
because
I'm
the
giant
image
with
all
the
stats
was
just
like
completely
unreadable.
If
you
are
not
receiving
this
Wednesday
email.
I
think
everybody
on
this
call
should
have
received
one
last
Wednesday.
If
you
don't,
let
me
know,
and
I
will
make
sure
that
you
get
added
to
that
distro
list.
There's
nothing
like
totally
totally
surprising
in
there.
B
As
of
yet.
The
one
thing
that
it
does
point
out
is
that
upgrade
pace
is
very
different.
If
you
look
at
it
a
number
of
installs
versus
number
of
sessions.
So
it's
really
about
you
know
the
people
who
are
frequent
users
have
upgraded
like
most
of
them
have
upgraded
I.
Didn't
I
didn't
check
it
this
morning,
but
the
upgrade
rate
is
huge,
and
then
you
got
all
these
people
who
you
know
downloaded
desktop
later
with
a
couple
of
times
and
never
ran
it
again.
B
So
it's
a
very
different
view
of
those
metrics,
depending
on
the
parameter
that
you
look
at
it
and
but
take
a
look
at
the
countly
there's
a
lot
of
interesting
stuff
in
there.
B
So
a
small
tweak
to
that
I,
don't
suspect,
I,
don't
expect
to
see
a
big
change
in
retention
metrics,
but
did
change
the
language
on
the
install
section
of
ipfs
thought
IO
just
to
make
it
clearer
what
does
what
or
who
might
want
to
download
what
so
would
be
interesting
to
see
if
that
makes
any
done
in
anything,
but
it
was
time
those
are
mine,
I,
don't
know
who's,
doing
the
design,
meaning
I.
Think.
A
A
A
Okay,
so
I
will
be
very
brief.
We
introduced
subdomain
gateways
in
go
active
as
0.5
and
for
the
next
release
we've
been
thinking
about
switching,
go
ipfs
to
new
key
format,
which
is
EDD,
I,
think
to
255
19.
Yes,
so
problem
is
the
key
is
much
smaller.
It's
so
small.
It
can
fit
in
the
CID,
so
we
would
start
in
line
in
keys.
The
problem
is
that
in
line
key
is
2
characters
over
the
limits
of
a
single
label
in
DNS.
A
So
that's
like
a
hard
limitation
of
DNS
spec
and
a
lot
of
places
actually
implement
that
spec,
which
means
you
are
not
able
to
ping
domain,
which
is
which
has
like
two
long
segments.
So
there
will
be
a
design
meeting
to
figure
it
out.
What's
the
best
way
to
handle
that
we
probe
like,
we
probably
could
find
a
custom
representation.
Just
for
this
specific
kid,
the
gist
here
is
that
we
want
the
default
IP
and
s
keys,
work
pretty
well
with
subdomains,
but
at
the
same
time
we
don't
want
to
introduce
anything.
A
A
That's
it
on
this
front
and
another
one
is
also
from
me.
So
a
bunch
of
develop
uri
schemes
got
approved
by
IANA.
It's
a
part
of
our
work
on
with
agalya
on
getting
protocol
handlers
for
browser
extensions
to
the
point
where
they
are
much
more
useful
than
what
we
already
have
in
Firefox
in
chromium.
We
don't
have
anything
so
we
want
to
push
boundaries
across
vendors
in
a
like,
a
generic
way
that
can
be
used
by
not
just
IP
affairs,
but
all
the
projects.
So
the
cool
thing
here
and
I
okay
did
I
broke.
It.
D
E
A
Think
yeah
multiple
times.
Yes,
so
that's
cool.
It
means
it's
formal,
its
formalized
and
you
can
use
those
protocol
handlers
in
places
when
it
was
expected
to
be
registered
by
Ayana
and
it's
a
part
of
our
work,
because
if
someone
wants
to
follow
up
the
next
step,
it's
white
listing
those
key
new
protocol
schemes
in
the
Web
API
called
registered
protocol
handler.
A
So,
for
example
like
because
companion
would
be
able
to
use
it
to
register
handler
in
chromium
and
at
some
point
in
the
future,
we
want
to
have
a
protocol
handler
in
which
browser
extension
or
maybe
a
page,
is
able
to
inject
arbitrary
byte
byte
responses
similar
to
like
how
serviceworker
works
or
we'll
see.
But
that's
general
direction
of
this
work
and
registering
your
eyes
is
the
first
step.
I
think
that's
it
for
this
psi.
F
Shipped
yeah,
so
basically
pierced
are
related
almost
shipped
thing,
so
basically
that
pierced,
our
initial
endeavor
is
completely
done
in
terms
of
coding
just
a
bit.
We
everything
is
done
and
merged
in
the
just
between
0.28
branch.
This
basically
includes
the
address
book
proto
work
and
also
something
that
it
was
initial
endoscope,
which
is
the
meta
metadata
boot
and
including
also
data
persistence
for
all
of
them.
So
basically
now
Oh
another
thing.
F
Basically,
we
talked
earlier
about
having
metrics
to
for
these
improvements
on
storing
the
peers
data
and
then
restart
and
see
how
long
more
along
less
would
be
to
be
connected
to
all
of
the
peers.
This
is
not
done
yet
because,
basically,
we
want
to
use
the
test
ground
for
this,
and
otherwise
it
would
be
just
a
key
tests
in
my
laptop,
but
we
are
still
waiting
on
the
support
for
Jason
browser
notes
for
that,
so
basically
I'm
kind
of
postponing
that
until
Google
as
the
support,
so
this
will
come
in
I
would.
D
F
Okay,
so
I
will
make
sure
we
we
have
before
the
Phillies,
so
this
will
come
in
the
lipid
to
be
0.28
release,
as
I
said,
so
we
merged
all
these
and
also
other
stuff.
Regarding
this
release
last
week
as
well,
Jacob
is
out
this
week,
so
we
are
planning
on
doing
the
release
candidate
in
the
beginning
of
the
next
week.
F
Meanwhile,
we
are
losing
this
in
the
energy
in
the
lipid
side
of
things,
I'm,
mostly
integrating
it
in
jessup
FS.
Basically,
it's
almost
done.
There
is
a
block
around
the
bit
swap
update
that
Alex
is
working
on
and
I,
don't
don't
foresee
any
further
blockers,
so
hopefully
we'll
get
these
in
the
next
gen
first
release
and
that's
it
for
the
beer
store.
Then
I
also
added
another
points
which
is
the
following
and
there
is
no
fee.
Never
so.
Basically,
the
initial
plan
for
my
quarter
would
be
there.
F
I
would
work
on
this
initial
endeavor
of
the
piercer,
which
is
done
no
and
then
I
would
work
on
the
specs
for
the
multi
other
confidence
in
here
scoring,
which
basically
would
be
the
next
step
in
their
store
in
which
we
name
in
a
lipid
to
be
as
a
piercer
v2,
which
also
go
once
to
have
in
their
side.
This
would
improve
a
lot
the
dial
performance
of
in
connectivity
in
general
of
the
beers.
F
However,
this
would
take
a
long
time
until
we
get
to
the
finish
line
and
consensus
with
the
go
team
and
considering
that
Jacob
is
with
low
available
in
the
browser
context.
Now,
basically,
I
talked
with
him
and
I
suggested
that
I
should
probably
focus
on
something
more.
We
did
more
immediate
value
in
the
Rosewood
context,
and
so
basically
we
got
aligned
there.
I
should
just
work
on
the
honeypot
protocol
for
now
and
basically
I
linked
the
notes
on
the
issue
about
where
is
the
a
little
bit
behind
info?
F
We
basically
just
went
to
uniform
all
of
these
and
used
the
rely
protocol
and
secret
relay
to
achieve
connectivity
and
with
this
I
also
hope
to
create
proper
documentation
for
browser
users,
so
that
we
can
finally
move
on
with
all
this
confusion,
about
star
servers
and
now
these
words.
Now
we
set
up
this
and
basically
have
a
more
friendly
environment
for
browser
users
and
yeah.
That's
it.
A
F
Yet
there
is
a
working
progress
PR
from
visa
for
a
while
ago,
but
I
think
that
then
you
shift
to
something
else
and
basically
it
has
been
stalling
for
like
a
year
or
something
so
I
think
Jess
will
be
the
first
implementation
of
that
spec
and
if
it
updates
it
will
be
according
to
the
work
that
we
are
doing
and
if
something
needs
to
be
changed,
we
will
discuss
with
Visio
and
will
update,
but
for
now
I
see
the
best
source
of
truth.
Yeah.
D
A
I
think
it's
also
like
work
in
Reichle
rating
in
some
in
case
someone
is
watching
what
is
and
I
think
he's
about.
I
think
if
I
mentioned
that,
but
there's
a
link
in
the
notes
about
the
plan
to
sunset
star
servers.
So
it's
like
super
long
arc
from
the
probably
the
beginning
of
the
aquifers
project
when
we
had
those
like
temporary
measures
for
running
hi
professing
web
browser
and
we
still
are
using
them.
So
this
is
the
plan.
To
finally
do
the
right
thing.
A
E
H
I
I
H
I
Priority
that
could
be
to
potentially
the
updating
feature
and
try
to
make
it
working
100%
and
also
increase
the
amount
of
log
and
error
logging
we
have
in
the
plate
feature.
We
can
pray,
how
many
other
exactly
ablative,
how
many
others
are
still
being
prompt,
updating
but
haven't
chosen
complete
yet
and
all
that
information
that
could
be.
I
I
I
H
H
I
Think
it's
the
I,
really
need
to
figure
out
where
the
problem
is
and
thank
you
for
helping
with
it.
I
think
the
problem
is
in
both
the
radix
bundler,
which
doesn't
directly
provide
feedback
when
this
or
changes.
So
when
we
have
a
lot
of
changes
like
this
progress
is
being
changed
a
lot
of
times
there.
It
explained
blur
like
bundles
all
the
teams
and
just
provides
feedback
later
so
when
we
actually
want
to
tell
the
progress
we're
growing
there.
I
We
cannot
do
it
because
it's
having
too
many
changes
and
the
other
one
is
also
the
file
upload
memory
and
accredit
directly
showed.
So
we
need
to
change
that
will
make
working,
but
nonetheless,
it
says
how
many
files
are
imported.
I
think
it's
starting
to
collapse
because
I
already
collapse
it
before
do
them,
and
now
it
keeps
the
record
here.
I
I
H
I
I
B
A
quick,
quick
straw
poll
for
all
you
guys,
because
we
had
a
discussion
in
the
thread
about
whether
it
was
worth
the
amount
of
work
like
if
you
notice
manuals
word
I
can't
pronounce.
No,
these
all
have
like
well.
That
should
be
the
generic
file
icon,
the
one
without
any
like
word
lines
in
it.
It's
just
a
little
sheet
of
paper.
B
The
we
discussed
the
amount
of
effort
required
and
trying
to
attach
the
correct
file
icon
I
at
this
stage,
I'm
leaning
toward
just
having
the
generic
blank
sheet
of
paper
for
everything
inside
of
that
dialogue.
For
the
sake
of
getting
this
in
the
hands
of
people.
But
since
there's
a
large
number
of
us
in
the
room,
I
thought
I
would
see
if
anybody
in
this
room
objected
to
that
I'm
gonna.
Take
that
as
a
no
it's.
D
B
Yeah,
that's
what
I
figure
I
mean
like
eventually
like.
If
we
were.
If
we
were
focused
at
that
level
of
detail,
it
would
be
super
cool
if
it
matched
the
correct
icon,
but
yeah
I
think
just
the
generic
folder
or
the
generic
file
icon.
I'll
make
a
note
of
that
in
the
in
the
issues.
Thanks
Raphael.
B
B
C
B
A
What
I
did
there
are
like
huge
size
reduction
like
Firefox?
Is?
It
was
10
and
now
is
2
megabytes,
which
is
ridiculous.
Basically,
I
checked,
which
types
of
phones
are
supported
by
Firefox
and
chromium
and
I
removed
everything.
That's
that,
like
I,
think
just
like
the
best
type
I
like
I
already
merged
this
work
on
companion
preferences
that
you
did
and
I
will
cut
a
better
today
and
probably
a
stable,
later
changes
suite.
B
There
doesn't
seem
to
be
much
point
in
doing
that
if
the
URLs
are
all
gonna
change
like
two
days
after
we
do
it,
though
so
I'll
at
least
I'll
at
least
get
a
PR
and
there
so
that
we
can.
We
can
talk
over
what
goes
in
the
welcome
screen,
but
we
may
not
want
to
merge
that
if
Doc's
betta
hasn't
officially
launched
by
the
time
you
cut
your
release
might
be
a
good.
Oh,
that's,
okay,
Iraq
Lee!
It's
all
you.
C
Yes,
so
I
did
look
into
their
large
file
upload
memory,
growth
issue
partially,
because
that
is
something
related
to
the
work
I'm
also
gonna
be
facing
with
the
moving
stuff
like
Rosa
workers.
Good
news
is
web
platform
is
actually
is
able
to
handle
that
and
do
the
streaming.
Venues
is
currently
Jerris
IKEA
pairs
doing
through
all
the
normalization
that
happens
in
a
pipeline
kind
of
do
this
some
of
the
properties
and
that's
why
it
end
up
survey
days,
but
it's
solvable
so
we
can
do
it.
C
One
thing's
for
this
experiment,
I
noticed
that
I
think
might
be
worth
emphasizing,
although
I'm
not
sure
how
common
that
would
be
said.
As
I
was
uploading,
huge
files
I
know,
there's
that
whole
size
versus
whole
library,
like
I,
think
in
the
web
UI
we
show
two
sizes,
one
is
for
the
total
size
and
one
of
the
specific
thing
you're
looking
at
and
I
end
up
with
specific
Singh
being
smaller
than
their
full
size,
which
I
don't
think
it's
about
these
things.
That
makes
sense
because
of
deduplication,
but
I
felt
like.
C
Maybe
this
is
something
we
can
more
emphasize
better
in
the
UI
and
explain.
Why
is
there
might
be
a
case
since
it's
a
positive
I
wrote
a
proposal
for
no
cheering
at
Rose
browser
context
that
I
talked
about
last
week,
I
think
or
two
weeks
ago?
I
guess
it's
in
a
notes
which
you
can
provide
feedback.
You
should
because
it
would
be
very
helpful.
I
posted
that
to
the
discussion
group
to
ask
feedback
from
community.
C
C
C
That
means
two
things
would
have
to
agree
on.
The
configuration
I
think
this
is
a
problem.
Actually
is
that
is
beyond
the
browser.
Once
browser
start
shipping
in
natively,
then
users
of
my
PFS
won't
be
able
to
say
what
the
configurations
they
want
to
use.
It
will
be
proud,
they're
shipping,
with
a
specific
configuration,
so
he's
also
the
issues
that
came
up
before
with
textile
desktop
and
radical
and
web
UI
certain
on
web
UI,
I
preserve
some
all
shippings
are
all
on
ipfs
notes.
C
We
just
can't
just
your
battery
life
and
it
makes
sense
to
have
one
configuration
that
is
best
for
this,
your
environment
and
have
that
so,
hopefully
we
can
get
there.
Probably
incremental
II
I
did
a
preliminary
analysis
of
the
configuration
options
that
they
have
I.
Think
some
of
those
could
be
maybe
hosted
out
into
specific
API
calls
others,
maybe
not,
but
we
need
to
figure
out
something
I
think
there's
also.
C
One
thing
said:
who
is
in
charge
is
the
important
is
I,
am
better
supposed
to
be
deciding
some
of
this
configuration
options
or
is
it
a
user?
This
decision
and
treating
them
differently
would
be
important
saying.
So,
if
you
care
about
this
and
want
to
help,
please
go
to
the
issues
that
I
linked
to,
and
that
would
be
a
way
to
help
and.
A
Thank
you.
That's
super
useful,
I'm
I
think
you
are
aware,
but
some
time
ago
we
disabled
window
ipfs
experiment
for
multiple
reasons,
one
of
them
being
changed
of
API
and,
like
we've,
been
injecting
the
new
version,
and/or,
the
old
version
and
people
been
expecting
the
new.
The
other
one
long
story
short.
Is
that
I
think
we,
if
we
like
reintroduce
window
ipfs
in
some
form,
that
would
probably
need
to
be
aligned
with
this,
like
no,
that
duplication
work
that
you
do,
the
like
note
in
companion
like
either
embedded
JSF,
EFS
or
the
HTTP
client.
A
A
That's
a
really
cool
and
an
example
of
we
have
like
a
custom
configuration
that's
specific
for
that
environment,
but
that's
just
like
there's,
probably
like
multiple
namespaces
within
the
config
like
we
right
now
have
a
single
config,
and
it's
like
everything
there
from
the
data
store
network
transports
and
even
like
my
own
addresses,
which
I
will
announce
myself,
we
may
want
to
get
some
luck
more
gradual
control.
That
would
be
interesting,
especially
like
for
embedded
J's
ipfs
in
brave,
so
I
just
wanted
to
mention
yeah.
So.
C
A
So
that's
that's
a
very
good
question
like
right
now
it's
an
experiment
and
if
you
basically
have
a
input
for
the
json
configuration
of
your
node
and
it's
not
one
had
100%
under
control
of
the
user
like
things
like
which
tcp
port
is
picked,
it's
automatically
like
we
find
a
free
one,
so
user
does
not
need
to
like
do
anything.
So
it's
like
a
hybrid
mixture,
but
that's
that
that's
interesting.
H
Yes,
just
briefly
so
I'm
kind
of
looking
into
where
why
people
might
not
be
upgrading
to
the
latest
versions
of
ipfs
beer
go
ipfs
as
a
library
or
the
demon
Jaya
Jaya
ipfs,
mostly
used
as
a
library
and
desktop
and
to
a
lesser
extent,
web
UI,
but
it
kind
of
ends
up
being
a
little
bit
messy
but
seems
like
the
analytics
is
broken
down
by
at
least
like
what's
the
desktop
version
and
what's
the
web
UI
version,
but
it
doesn't
look
like
we
currently
store
anything
about
the
go,
slash,
Jas,
IPS
version.
H
We
don't
record
that
in
analytics,
which
I'm
currently
making
the
most
horrendous
matrix
of
what
versions
of
web
UI
were
shipped
in,
what
versions
of
go
IPs
and
desktop
so
that
I
can
then
go
like
because
it
looks
like
go.
Ipfs
went
from
two
point.
Four
point
four
of
web
UI
to
two
point:
seven
point
two:
so
you
know
that
anything
in
between
didn't
ship
with
your
IP
of
s.
So
it's
a
desktop
version
which
then
allows
you
to
work
out.
Oh
this
person
desktop
for
this
version
ago.
H
Ipfs
maybe
gets
a
bit
hairy,
so
that
would
be
good
to
record
that
so
we
can
work
out
like
what
are
people
actually
running
inside
of
these
things,
rather
than
me
have
to
jump
through
many
hoops
and
web
UI
is
recorded
as
a
hash
of
the
like
the
cid
in
all
the
source
code.
It
and
no
source
code
anywhere
says
the
version
of
web
UI,
it's
shipping,
which
is
very
frustrating.
You
can't
search
our
source
repositories.
You
have
to
look
at
commits
for
something
that
looks
like
the
word
web
UI.
H
A
comment
next
to
those
C
IDs
would
be
super
helpful
for
people
to
work
out
what
version
is
going
on
it
or
even
shipping
web
UI
as
a
NPM
dependency,
doesn't
sound
crazy
to
me,
but
maybe
there's
some
history
there
that
I'm
missing
the
other
thing
I
noticed
poking
around
in
County
is
there's
a
lot
of
errors
and
I.
Don't
know
if
anyone
has
noticed
this
and
gone
like
it's.
Actually,
it's
not
a
problem
and
there's
specifically,
let
me
share
my
screen
briefly.
H
H
H
I
was
looking
at
in
it's
the
over
30
days,
ipfs
in
it
failed
five
half
a
million
times,
whereas
like
move
a
file
or
write
a
file
a
thousand
times,
this
number
is
gigantic
compared
to
everything
else,
which
makes
me
think
there's
something
going
on
like
is
probably
not
causing
most
people
to
have
a
bad
time,
but
there's
something
happening
either.
Weird
logging
stuff
the
week
yeah.
A
B
H
So
maybe
I
shouldn't
look
too
much
into
that
I'm,
mostly
interested
in
seeing
like.
Is
there
what's
the
kind
of
like
uptake
on
desktop
for
shipping,
0.5
and
above
which
I
think
I
can
work
out,
but
also
making
it
easier
to
do
that
in
the
future,
so
that
we
have
a
good
idea
of
like?
Is
there
stop
driving
any
adoption,
or
is
it
just
a
very
small
piece
compared
to
other
things
and
then
webui
shipped
in
more
things?
H
A
A
Yeah
III
think
Hui
to
make
sense
to
open
an
issue
in
web
UI
repo,
because
my
understanding
is
like
actually
the
most
of
metrics
that
we
gather
from
web
UI.
The
desktop
just
had
a
few
additional
labels,
but
still
the
most
of
metrics
are
gathered
in
web
UI
and
let
whether
I
itself
could
like
detect
the
note
type
which
it
is
connected
to
and
report
out.
So
that's
will
be
pretty
useful
to
find
the
gaps
that
we
like
our
like
blind
spots
right
now.
H
Yeah
I
can
see
that
in
the
in
one
of
the
dashboards,
the
the
kind
of
the
other
thing
that
I
was
looking
at
I've
lost.
My
own
page
I
was
on
I
was
trying
to
kind
of
work
out
where
so
we
have
web
UI
dot
ipfs
to
I
have
which
is
like
it's
there.
You
can
go
to
it
and
arbitrary
run
that
and
it
will
fail.
Oh
we
do.
We
have
analytics
on
that
hosted
version
of
the
web.
You
some.
C
H
B
And
if
you're
gonna
open,
if
you're
gonna
open
a
sort
of
amend,
countly
collecting
stuff
ticket
I,
would
I
would
vote
that
as
far
as
I
can
tell,
we
do
not
have
an
ad
via
desktop
event
in
web
UI,
which
I'd
like
to
I'd
like
to
start
tracking
and
then
I.
Don't
see
any
events
for
pinning
and
now
it
also
that's
gonna
get
more
and
more
important
as
we
start
thinking
about
integrating
a.
H
B
A
Something
probably
kind
kind
of
related
is
the
fact
that,
right
now,
when
we
ship
web
UI
with
ipfs
go
ipfs
or
JSF
GFS,
we
like
hard-coded
that
version
that
Angie
mentioned
that
knowing
to
track,
and
that
means
those
sort
of
like
every
go
idea.
Festinger's
ipfs
release
ships,
we've
hard-coded
web
UI,
which
cannot
be
effectively
upgraded
unless
you
upgrade
go
ipfs
or
jess
ipfs
itself.
If
you
run
active,
has
desktop
it
bundles
web
UI
inside.
A
A
Steven
was
not
comfortable
with
going
ahead
with
that,
because
it
relies
on
the
assumption
that
the
DNS
link
from
the
DNS
points
at
the
reel
web
UI,
not
like
someone
could
the
man
in
the
middle
at
the
DNS
level
and
inject
a
different
version
of
web
UI.
That's
why
we
don't
have
this
like
rolling
release,
cause
right
now,
when
we
I
believe
which
we
managed
to
master
their
web
UI
ipfs
IO
is
updated
and
if
you
will
merge
to
release
or
something
like
that,
the
web
UI
is
updated
or
the
other
way
around.
A
So
we
like,
we
could
have
a
rolling
release
of
web
UI.
The
problem
is,
we
don't
want
to
do
that
as
default,
because
we
want
to
ship,
like
the
version
that's
tested
with
against
a
specific
goal.
Pfs
version,
but
I
want
to
figure
out
a
way
to
provide
an
easier
way
for
people
to
opt
in
to
the
latest
web
UI
and
I.
Think
like
in
companion
at
least,
we
could
historically,
we've
been
playing
with.
A
Modifying
the
original
header
to
pretend
that
we
loaded
web
UI
from
the
API
port
and
that
removed
the
manual
step
of
setting
course
headers
on
go
ipfs
daemon
to
allow
logging
web
UI.
It
will
allow
accessing
api
from
a
gateway
port
I'm
just
like
interested
if
we,
because
we
also
are
planning
to
like
not
planning.
But
we
are
discussing
to
stop
bundling
web
UI
inside
of
electron
browser
and
instead
ipfs
desktop
just
having
like
a
menu
item
for
status
and
files,
and
that
link
would
open
in
a
browser
which
the
which
the
surveys
seemed
to.
A
So
it's
like
actually
I
hope
to
have
a
like
short
description,
but
it's
actually
like
a
lot
of
moving
pieces
right
here
and
long
story
short.
Is
that
we,
we
probably
will
have
to
figure
it
out
a
way
of
making
it
easier
for
people
to
opt-in
to
the
latest
web
UI
really
cycle
of
go
ipfs,
which
is
like
six
weeks
unless
we
are
a
lot
comfortable
with
aligning
with
that
release
cycle.
Maybe
that's
a
good
way
moving
forward.
A
But
to
me
it's
like
an
open
question:
either
we
align
ourselves
with
recycles
of
go
FS,
maybe
J's
ipfs
will
follow
or
we
may
need
to
find
a
way
B
that
with
companion
or
not
of
letting
users
to
opt
in
to
the
latest
version,
I,
don't
think
it's
possible
without
companion.
Actually
so
yeah,
that's
a
hard
cookie.
C
Ask
a
question
so
I
think
one
problem
that
you
mentioned:
work
or
setters,
and
that's
something
that
came
up
before
as
well.
It
seems
that
maybe
solving
the
core
setter
might
unlock
many
opportunities
here
specifically
like
these
are
reason
why
webview
it
can't
be
just
in
web
app
set
users,
IP
FS
internally
sideways,
and
you
could
go
to
the
actually
code
load
with
a
hash
of
the
web.
Ui
relates
or
it
could
go
to
the
web
UI.
The
write
has
that
command
it
will
automatically
make
when
to
the
various
hash,
but
it
could
like.
A
H
A
Then
you
need
leg,
add
those
course
headers,
and
this
is
like
just
a
problem
of
user
experience.
It's
not
like
we
would
like
if
someone
opens
click
a
link
in
web
UI
inactive
as
desktop.
We
don't
want
to
ask
people,
we
don't
want
to
greet
people
with
that
error.
You
need
to
type
this
stuff
in
console
to
make.
A
C
A
That's
that's.
What
I
would
love
to
figure
out
how
to
remove
that
manual
step,
at
least
for
desktop
I?
Think
it's
possible
if
we
pass
the
address
the
potential
small
problem
is
that
in
go
I
give
s
if
you
update
configuration
it's
not
like
a
live
reload.
Not
everything
is
life
reload
that
you
need
to
stop
and
start
node
and
that's
like
pretty
big
requires
some
refactoring
bingo
80
of
us.