►
From YouTube: IPFS Web and GUI Biweekly 2020-08-25
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1173/files
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
All
right
welcome
to
guillermo
browsers
for
25th
of
oh
gosh.
What
is
it
august
2020?
We
got
lots
of
folks
today,
hi
to
all
the
usuals
and
the
new
guys
I'll
start
with
the
agenda
and
maybe
like
post
it
once
again
on
our
chat.
A
A
Faster
all
right,
so
the
first
item
is
a
quick
announcement
that
ipfs
and
ipns
uris
are
now
now
safe,
listed
to
be
used
in
register
protocol
handler
ap
web
api
in
chromium,
and
that
means
that
means
two
things.
One
is
that
you
are
now
able
to
register
redirect
based
protocol
handler
for
ipfs
or
ipns,
and
redirect
that
uri
to
url
of
your
choice
and
along
with
ipfs
and
ipns,
a
bunch
of
duo
protocols
are
there.
A
So
that's
that's
pretty
cool,
it's
a
part
of
our
work
that
we've
started
doing
with
igalia,
just
like
dietrich
mentioned.
This
is
work
instigated
and
sponsored
by
ipfs
team
at
protocol
labs,
and
we
are
very
happy
with
our
collaboration
with
igalia
that
produced
this
really
cool
patch,
which
landed
in
chromium.
A
It's
a
part
of
a
longer
work
for
having
a
full
protocol
handler
for
browser
extension.
Where
you
don't
just
redirect.
You
are
able
to
return
a
byte
array,
but
it's
the
first
very
important
step
to
have
a
support
for
those
uris
without
web
plus
prefix.
A
Was
a
thing
separately
from
ipfs
colon
slash
so
now
the
need
for
the
prefix
is
gone,
so
that's
cool
and
we
are
in
the
chromium
now.
The
second
announcement
is
also
from
me.
So
that's
just
a
quick
psa.
That's
a
new
version.
005
of
ipfs,
spinning
service
api
landed.
A
It's
not
it's
mostly
clean
up
and
upgrade
on
naming.
We
renamed
some
fields
to
ensure
they
don't
have
the
same
name
in
requests
and
response.
It's
now
much
easier
to
reason
about
them.
We've
upgraded
the
docs,
there's
more
visuals
and
we
got
a
new
field
in
the
pin
object
net
called
name.
So
you
can
it's
a
top
level
field
where
you
can
assign
a
human
readable
name,
and
then
you
can
can
filter
your
pins
by
partially
matching
that
string.
A
A
I
believe,
that's
more
more
or
less
all
the
changes.
So
this
we
don't
expect
this
api
to
change
much.
We
probably
will
promote
it
to
1.0
people
already
started
implementing
it,
so
I
just
encourage
everyone
to
familiarize
yourself
with
the
api
if
you
are
interested
in
it
from
the
client
or
server
perspective.
We
know
officially
and
in
officially
that
people
are
already
starting
implementing
clients
and
servers
of
this
api
so
expect
interesting
updates
in
the
following
weeks.
A
B
Yeah
this
is
this
is
exciting
because
it's
been
a
long
time
in
coming
and
it's
also
the
result
of
a
bounty
led
effort
from
an
external
contributor,
kevin
neaton
who
did
a
great
job.
I
do
not
have
a
local
instance
of
it
loaded,
so
I'm
afraid
I
cannot
actually
show
you
what
this
looks
like,
but
this
does
give
in
any
of
our
standard,
ipfs
directory
pages,
just
the
regular
directory
pages
there's
now
there
will
now
be
a
column
for
the
cid.
B
There
will
also
in
the
header
of
each
of
those
pages,
have
information
about
the
directory's
size,
the
one
that
you're
viewing
and
then
also
when
you're
in
a
subdirectory.
All
of
the
path
components
listed
in
that
header
will
be
links,
so
you
can
move
up
and
down
the
chain
with
ease.
B
This
is
one
of
these,
and
it
also
includes
a
couple
of
miscellaneous
fixes
for
responsiveness
that
were
in
an
earlier
an
earlier
set
of
changes
to
directory
index
html
that
we
just
didn't
get
in
because
they
were
so
small
so
and
and
so
just
other
optimizations
as
desired.
B
This
is
one
of
those
things
that
sort
of
turned
into
a
massive
rabbit
hole
in
terms
of
how
we
ended
up
like
actually
getting
it
down.
The
work
sounded
really
simple
and
then
sort
of
turned
into
this
endless
pile
of
things,
so
lots
of
cutest
to
everybody
who
who
dug
in
to
to
do
something
that
was
small
but
was
actually
really
substantial.
User-Facing
improvements.
B
I
also
added
there's
a
note:
there
cli
tutor
mode,
nearly
ready
to
ship.
This
was
another
contributor
community
contributor,
led
effort,
but
in
the
next
version
I
guess
2.11.
Hopefully
we
will
have
the
option
in
the
prefs
to
turn
on
and
off
cli
tutor
mode,
which
will
give
you
a
little
copy
code
icon
near
things
that
are
that
map
easily
from
ipf's
desktop
and
web
ui
into
the
command
line.
For
folks
who
started.
B
Thank
you,
lydol
folks,
who
started
and
and
these
these
screenshots
are
a
little
bit
outdated,
the
icon
chain
and
a
few
other
things
in
the
meantime.
But
you
you'll
see
little
little
teases.
You
click
on
those
they'll
bring
up
a
modal
with
the
thing
that
you
copy
paste
into
your
terminal.
To
do
the
thing
in
the
cli
so
should
be
good
for
new
users
as
an
onboarding
improvement
and
super
excited
that
it
ended
up
as
something
that
was
led
by
a
contributor,
a
community
member.
A
It's
super
super
cool
because,
in
general
our
gui
applications
were
like
are
not
aiming
to
be
the
the
end
user
product
with,
like
original
meaning
of
that,
it's
mostly
a
demonstration
like
visual
visualization
of
ip.
What
ipfs
can
do
and
a
vessel
for
learning
by
exploring-
and
I
feel
this
is
a
great
example
of
how
we
can
do
that
because
from
the
graphical
interface,
you
can
learn
how
to
do
the
same
thing
in
the
command
line,
which
is
super
cool.
A
Next
one
is:
is
there
anything
we
need
to
discuss
for
the
next
release
of
web
ui?
Let
me
quickly
maybe
share
that
milestone.
A
I've
added
one
thing
today
to
the
pile
of
2.11,
but
I
think
it's
it's
better
to
like
merge,
make
a
decision
to
merge
or
not,
but
I'd
say
merged
sooner
than
later,
and
it's
this
refactor
of
components
by
iraqi.
It
does
not
like
actually
change
anything.
It's
just
a
refactor
that
clean
up
stuff
and
make
it
easier
for
people
to
contribute.
A
I
think,
but
if
we
want
to
to
accept
that
change,
I
do
that
with
entrepreneurs
with
the
2.11,
mostly
because
it
changes
the
way
events
are
created,
and
we
have
this
opt-in
mechanism
for.
A
Metrics
and
we
use
currently
service
for
that.
So
if
the
it's
better,
if
there's
some
regression
regarding
the
way
we
gather
metrics
of
how
users
interactive
application
is
better
to
notice
it
sooner
than
later,
and
I'd
like
to
notice
that
before
we
integrate
pinning
services.
B
A
Yeah,
so
that's
a
that's!
That's
a
good
question.
I've
put
it
in
this
milestone,
mostly
so
that
we
don't
miss
it
and
we
don't
like
make
a
decision
to
merge
it
without
considering
exactly
that
side
effect,
so
I
I
think,
would
be
great
to
catch
either
a
hack
or
only
if
they
are
available,
because
they
are
probably
the
most
familiar
with
all
the
assumptions
done
when
countley
was
introduced.
A
Rafael
if
you
could
block
some
time
this
week
and
take
a
look
at
this
from
your
perspective
from
the
perspective
of
changes
that
you
are
doing
for
pinning
services,
that
would
also
be
useful.
I'd
say
we
should
make
a
decision
sooner
than
later,
because
it's
a
pretty
big
refi.
It's
like
a
big
refund.
B
A
Yeah,
I'm
I'm
not
yeah.
I
was
like
away
and
stuff
I'm
just
like
worrying
that
we'll
miss
it.
So
that's
why
I've
included
it
here
feel
free
to
like
the
scope
it
from
this
release,
if
it
does
not
make
sense.
A
Apart
from
that,
I
think
there
are
no
new
things.
B
The
the
last
open
question
on
tutor
mode
with
the
translations.
I
kicked
that
back
your
way
because
I
think
there's
actually
a
really
easy
fix
for
that.
B
I
rtf10
so
so,
hopefully,
hopefully,
if
I
understand
this
correctly,
it
should
immediately
take
care
of
that
problem
so
that
I
think
we
could
be.
We
could
be
done
with
okay.
A
A
Let's
I
would
have
to
take
a
look
at
this
asynchronous
after
the
call,
because
my
last
experience
was
that
it
works,
but
then,
when
you
clean
up
the
all
the
files
from
those
keys,
the
actual
fallback
turns
out
to
not
work.
So
it
may
be
a
bug
that
was
fixed
since
the
last
time
I
worked
with
i18
next
i18.
Next
is
the
library
we
use
for
localization
in
web
ui.
B
Yeah
I
did
I
made
two
commits.
They
seem
to
work
just
fine.
It
does
sort
of
open
up
future
questions
because
there
are
a
lot
of
other
duplicate
keys
in
there
and
then-
and
just
you
know
how
far
we
want
to
take
that-
and
that's
that's
for
separate
that's
for
a
separate
project
but
yeah.
I.
A
Think
that's
great.
I
think
this
should
take
care
of
it
all
right.
Let's,
let's
take
that,
oh
gosh,
do
we
have
any
question
marks
or
things
we
want
to
discuss
for
the
other
front,
I
know
rafael.
You've
been
working
on
cleaning
up
the
all
the
issues
related
to
people
connecting
to
remote
node.
C
Yeah
regarding
that
one,
let
me
just
check
real
quick.
I
just
had
it
open
here.
The
merge
request
is
ready
for
review.
I
think
you
can
see
it
now
lilo
I
just
added
just
a
few
asked
for,
and
I
just
need
to
fix
something
that
you
comment
on
recently.
C
A
Cool
yeah.
The
context
here
is
that
we
don't
want
to
invest
too
much
time,
because
most
of
people
want
will
just
lose
a
local
node.
Be
that
one
provided
by
ipfs
desktop
or
locally
running
oipfs,
but
there's
a
set
of
users
who
want
to
connect
to
remote
ip
which
by
remote
we
mean
even
mean
the
ip
in
the
ip
or
a
domain
in
the
local
network.
A
A
So
if
it's
possible
use
the
gateway
from
the
nodes
config,
if
not
just
hold
back
to
the
public
gateway,
either
user
does
not
notice
that
or
they
have
ipfs.
Companion
and
companion
will
take
care
of
redirecting
that
to
the
proper
gateway
of
users.
A
Choice-
and
I
think
that's
like
the
the
line
in
the
sound
where,
when
we
balance
the
the
convenience
of
all
the
users
with
like
the
time
we
can
spend
to
account
for
every
use
case
at
this
at
this
stage,
so
that's
will
probably
close
a
bunch
of
those
I'm
not
sure
about
supporting
api
with
when
you
enter
instead
of
multi-other
when
you
enter
uri
with
a
basic
auf
with
user
and
a
password.
A
I
know
that
it
was
a
problem
for
epiphany
companion
in
the
past
and
it
may
got
changed
with
the
change
to
the
latest
js
ipfs.
So
that's
probably
something
we'll
have
to
add
tests,
for.
I
don't
think
we
have
like
end-to-end
tests
for
this.
So
it's
possible.
We
have
a
regression
there,
but
that's
like
my
only
note
for
web
ui
2.11
the
rest
looks
fine.
I.
C
A
A
B
A
B
A
Like
animal
sacrifice
or
something
between
all
right
on
there,
a
different
topic,
we'll
start
we'll
start
experimenting
with
grooming
issues
every
week.
We
want
to
do
that
on
this
call,
because
people
would
fall
asleep
even
more,
but
we
will
be
blocking
time
each
week
to
triage
issues
on
gui,
related
and
web
related
browser
related
repos
and
try
to
ensure
nothing
is
hanging
without
a
sort
of
reply,
or
at
least
a
proper
triage.
A
B
The
do
we
just
want
to
punt
on
you
a
couple
of
weeks
ago
we've
been
working
on
active
peers
indicators
in
companion
and
possibly
in
desktop
and
I'd
sort
of
started.
Doing
some
of
that
work.
Do
we
just
want
to
hold
off
on
continuing
on
that
until
you're
done
with
the
refactor.
A
I'd
say
I
I
want
to
even
look
at
that
until
I
finish
this
fighter
and
I
I
would
make
a
better
release
with
refactor
and
then
probably
go
to
that
indicator
stuff
and
make.
A
We
some
users
use
embedded
js
in
a
browser
and
that
embedded
js
ipfs
is
in
a
super
old
version
right
now
in
companion,
and
it
will
soon
lose
ability
to
connect
to
other
peers
because
sec,
I
o,
is
deprecated
so
that
that
the
time
window
for
making
that
release
is
shrinking.
So
that's
like
my
priority
and
then
we'll
we'll
do
the
other
stuff
yep.
I
think
that's
it
on
the
agenda
and
any
topics
you
want
to
bring.
A
A
Once
twice
that
was
the
short
one
see
this
is:
what
happens
when
racket
is
not
around
all
right.
I
think
I
think
we're
good
with
half
an
hour
this
week,
let's
let's
plan
for
a
longer
one
in
two
weeks,
we'll
probably
this
time
we'll
probably
have
both
releases
and
some
interesting
announcements
that
close-up
topics
we've
mentioned
this
week,
so
I
will
start
recording.