►
From YouTube: IPFS Web and GUI Biweekly 2020-09-22
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1176/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:
https://eepurl.com/gL2Pi5
A
We
finally
released
ipfs
web
ui,
so
this
this
will
be
a
quick
show
and
tell
of
what's
new
in
the
new
releases
we
had
to
release
this
one
was
like
the
domain
with
features
and
then
was
a
quick
bug
fix
release.
That's
followed
shortly
after
that
this
web
ui
will
land
in
before
we
go
to
the
show
and
tell
this
web
ui
will
land
in
go
ipfs
0.7
and
the
next
version
of
iphone's
desktop.
A
We
we
got
ipfs
desktop
and
ipvs
companion
releases
scheduled
to
release
soon.
So
probably
the
next
time
on
this
call
we'll
discuss
those
jessica.
Do
you
want
to
like
make
a
quick
chantel
of
the
ui
changes?
I
can
put
a
later
demo
the
remote
api,
because
I
gotta
call
setup.
A
Yeah
so
like
the
change
list
is
pretty
massive.
A
The
thing
that
we,
I
think
we
would
like
to
highlight
is
cli
tutor
mode
and
probably
the
changes
around
super
brand
crams
breadcrumbs,
the
welcome
page,
the
continuity
and
I
can
demo
the
remote
api
with
basic
auth,
because
I
got
because.
B
All
right
so
here
we
have
ourselves
a
beautiful
web
ui
with
its
streamlined,
sidebar
menu
there,
including
this
guy
here,
so
we
were
realizing
that
we
had
thanks
to
a
contributor
to
andrew's
contributor
who
said
the
welcome
messaging
is
kind
of
hidden
because
we
weren't
really
showing
that
any
time
other
than.
If
you
had
a
blank
file
screen,
you
didn't
have
any
files
yet
so
we
have
ourselves
a
nice
little
status
menu.
B
The
nice
thing
is,
if
you
drop
drop
your
connection,
it
will
also
reflect
that
right
there
in
that
status
screen
and
give
you
some
things
that
you
can
do
right
away
because
you
probably
don't
have
cores
figured
out
or
your
api
is
on
the
wrong
port
or
something
like
that
or
you
just
did
like
me,
and
you've
stopped
your
daemon
for
a
second.
But
so
then
you
successfully
reconnect
and
you
get
that
which
is
wonderful
settings.
This
is
super
cool.
B
This
came
from,
oh,
and
also
we
rearranged
things
a
little
bit
more
here,
so
that
api
address
is
easier
to
change.
Should
you
wish
to
reconfigure
your
api
address
there,
but
this
is
the
really
cool
part.
Cli
tutor
mode
oink,
you
turn
that
on
you
notice,
underneath
the
ips
config
fps
config,
you
get
this
little
icon.
That
little
icon
appears
all
over
the
place.
B
So
like
say
here
right,
they're
all
over
here,
so
you
could
pin
delete
whatever
whatever
whatever
or
you
could
invoke
this
cli
tutor
mode-
and
here
it
says,
paste
this
into
your
terminal
to
do
this
thing
in
the
command
line.
So
if
you
have
just
downloaded
desktop
or
you're
just
using
web
ui,
because
it's
easier,
it's
a
good
way
to
get
started
in
the
terminal
commands.
B
We
also
have
new
and
exciting
and
shiny
super
breadcrumbs.
So,
oh
good,
I
do
have
things
making
some
nested
files
to
demo
all
right
to
say:
we've
got
like
all
of
these,
like
cats,
more
cats,
even
more
cats.
I
could
take
like
this
guy
here,
who's
sitting
in
three
directors,
deep,
even
more
cats-
and
I
can
do
that
and
now
it's
gone
but
cubecat's
in
here
now
super
shiny
lots
of
other
small
improvements,
but
those
are
the
major
ones.
I
would
you
like
lytle
to
demo
the
remote
api
authy
stuff.
A
Yeah,
let
me
quickly
share
my
screen
yeah,
so
this
is
like
the
default
view
when
you
are
connected
to
ipfs
nodes,
and
you
can
click
on
advanced,
to
see
like
more
details.
The
api
here
has
this
edit
button
and
when
you
click
on
it,
you
got
moved
to
this
screen,
which
is
casual
before
what's
interesting.
Here
is
that
we
in
this
input
field,
you
can
like
of
course
enter
multi-others.
A
You
can
enter
it
as
regular
url
as
well,
and
when
you
check
it
will
use
url
which
you've
passed,
but,
what's
probably
them
even
more
useful,
is
that
now,
if
you
have
a
remote
api
which
is
guarded
by
basic
auf
or
some
custom
tokens
or
any
other
http
based.
A
Authorization
mechanism,
we
made
it
possible
for
people
to
specify
custom
headers
and
just
connect
to
it.
The
easiest
way
is,
of
course,
using
basic,
auf
and
in
basic
alph
is
pretty
easy
because
you
can
like
inline,
user
and
password
as
a
part
of
url,
and
if
you
connect
to
that,
I
got
a
proxy
which
is
adding
a
basic
alph,
but
it's
effectively
connected
to
the
same
node.
You
can
see
there's
a
different
port.
A
So
if
I
connect
it
to
that
now
I
no
longer
see
the
address
here,
because
the
address
itself
includes
sensitive
credentials
and
we
don't
want
to
link
them
with
like
status
screenshots
that
people
may
use
for
debugging.
So
you
have
this
message
that
it's
a
custom
json
configuration
and
why
does
it
say
it's
custom
json
configuration.
A
So
when
you
go
to
settings
page,
you
can
see
that
that
inline
basic
of
cred,
those
inline
basic
out
credentials,
got
converted
into
a
json,
that's
accepted
by
hdb
client,
and
it's
pretty
handy
because
it
not
only
supports
basic
health.
So
basic
off
part
is
this:
here:
you
can
see
that
every
request
made
by
web
ui
will
have
this
additional
authorization
header,
which
is
just
a
user
and
password
hashed
encode.
That
is
based,
not
hashed.
A
Api
path
can
also
be
customized,
so
this
is
a
json
with
acp
client
configuration
and
we
don't
announce
it,
but
it's
if
you,
if
someone
needs
it,
it's
supported
out
of
the
box
and
of
course
you
can
like
revert
back
to
just
a
multi-other.
At
any
point,
I've
we
had
like
a
multiple
requests
for
various
use
cases
and
I
believe
now
anyone
can
just
implement
whatever
they
use
without
implementing
that
in
web
ui
itself.
A
A
B
Yeah
and
there's
a
little
bit
of
a
background
to
that,
we
did
add
some
extra
translation
burden.
With
this
release,
I
went
through.
We
had
a
lot
of
duplicate
internationalization
strings
and
really
things
that
were
appearing
in
multiple
files
that
were
very,
very
very
similar,
so
I
did
go
through
and
clean
all
of
those
up.
We
do
have
a
standard
app.json.
That's
now
got
sort
of
like
the
master
strings
that
appear
in
multiple
places,
so
that
should
help
a
lot
with
consistency.
B
It'll
also
help
us
with
writing
more
consistently,
as
we
add
features
going
forward,
making
sure
that
that
they
appear
in
the
same
voice
and
the
same
methodology
same
sort
of
overall
mental
models
we've
got,
but
what
that
does
mean
is
that
we
did
move
a
lot
of
internationalization
strings
around
in
ways
that
you
know.
Transfex
does
do
some
of
this
in
like
automatic
mode,
but
not
everything.
So
apologies
if
you
are
tuned
in
on
this
call
and
are
one
of
our
active
translators
and
you're
like
wait.
B
A
Something
that
may
like
is
the
pain
is
that
on
transfex
we
got
a
feature
enabled
called
translation
memory,
which
is
kind
of
like
a
safety
net.
In
case
we
messed
something
up,
no
translation
is
ever
missed
or
like
ever
forgotten,
or
it
does,
even
if
it
like
disappears,
because
we
messed
up
keys
and
your
translation
disappeared.
It's
still
in
the
like
shared
memory
between
projects.
So
if
the
same
source
string
appears
under
different
key,
it
should
be
picked
up
automatically,
or
at
least
you
should
be
you.
B
Think
a
lot
of
that,
I
think
I
think
that
should
that
robot
should
take
care
of
most
of
it,
but
there
are
going
to
be
a
few
things
that
are
going
to
need
to
be
retranslated
by
hand
yeah.
A
Just
just
to
close,
like
the
show
and
tell
the
section,
maybe
I'll
quickly
give
a
sneak
peek
of
a
new
release
of
desktop.
We
will
be
shipping
go
ipfs.
0.7
may
probably
this
week,
maybe
next
week,
and
it
will
include
this
new
web
ui
as
well,
so
stay
tuned
companion.
A
Easy
yeah,
it
jokes
aside:
I've
successfully
made
embedded
js
ipfs
run
in
brave
after
this
assing
iterables
refactor,
so
that
was
like
a
huge
time
sync,
but
now
it
should
go
much
more
smoother
yeah.
So
also
like
expect
release
this
or
next
week
and
yep.
I
think
that's
it.
The
next
section
is
just
a
quick
psa
about
pinning
services,
because
why
not?
It
would
not
be
a
week
without
pinning
services
with
shipped
0.1.
A
This
is
a
hopefully
in
the
last
release.
Ideally,
we
would
just
tag
1.0
from
the
same
revision
without
any
changes.
The
plan
is
to
tag
1.0
when
go
ipfs
0.8
ships
with
a
built-in
client
for
this
api,
so
it
will
be.
The
idea
is
that
go
ipfs
itself
will
give
an
opt-in
capability
for
people
to
add
a
remote
service
and
have
a
ability
to
pin
specific
cids,
with
additional
name
and
to
to
that
remote
service,
and
when
go
up
so
0.8
ships,
we'll
freeze
the
spec
so
to
speak.
A
In
this
release
we
got
two
braking
changes
because
we
renamed
fields
or
we
introduced
more
strict
structures
for
error
responses.
A
But
apart
from,
but
apart
from
that
there
were
no
revolutionary
changes,
just
slow
stabilization
and
clarification,
we
will
be
refactoring
the
epic
for
pinning
services
branch
in
the
following
weeks
and
switching
to
the
new
js
http
client
that
uses
those
new
p
remote
commands
so
expect
interesting
updates
in
the
next
time
we
are
on
this
call,
I
think
that's
it
for
for
now,
on
my
ends
directly,
do
you
want
to
mention
the
big
refactor
that
landed
in
webui.
D
Yeah
it
landed
yesterday.
There
were
a
lot
of
changes
in
terms
of
how
we
use
react.
Sorry,
redux
bundler.
D
A
Yeah
cool,
I
believe,
like
rafael,
was
waiting
for
that
without
with
before
he
started
final
appealing
services.
Integration
work
on
the
file
screen,
I
believe.
B
A
Oh
also,
we
will
have
a
progress
reporting.
A
I
did
not
mention
that
before,
because
it
was
not
not
on
the
not
in
realist
notes,
but
right
now,
what's
not
like
visual,
but
the
one
of
main
improvements
in
this
new
web
ui
that
will
ship
to
everywhere
soon
is
that
you
can
just
import
very
big
files
like
two
gigabytes,
five,
four
gigabytes,
it
will
take
a
moment,
but
they
will
import
and
will
not
kill
your
browser,
which
is
very
good.
A
The
problem
is
like
for
now
it
just
takes
a
few
seconds
and
nothing
happens
and
we
want
to
add
the
progress
reporting.
So
I
think
that
will
also
be
landing
soon.
A
So
that's
really
cool
news
that
it
landed
and
we
can
move
forward
with
that
all
right.
Folks,
any
topics
you
want
to
that
hog
andrew.
How
do
you
feel
about
your
pinning
services?
I
promise
to
not
release
new
spec
anytime
soon,.
E
God,
it
seems
fine
on
my
end,
there's
definitely
some
optimization
for
that.
I
can
imagine
clients
wanting,
but
from
from
a
base
level,
it's
it's
good
enough
to
get
you
there.
E
The
thing
I
jump
to
straight
away
is,
I
want,
like
the
web
ring
of
pinning
services
so
that
you
can
as
a
client
just
bounce
and
be
like
I'll,
just
send
out
to
a
number
of
pinning
services
that
all
offer
free
things
so
that
I
get
a
nice
distribution
around
the
internet,
but
obviously
that
stuff
doesn't
come
for
free
forever
and
people
will
take
advantage
of
it.
So
it's
it's
not
perfect.
E
A
E
E
It'd
be
good
to
have
a
the
js
client
as
well,
so
that
you
can
do
that
from
the
browser
and
then
the
the
next
thing.
I
guess
that
people
will
reach
is
the
authorization
kind
of
thing
and
then
they'll
want
some
standardization
there
to
be
able
to
like
get
your
access.
Token,
and
I
mean
the
access
taken,
should
can
be
anything
but
they've
got
to
be
a
string
right
and
they
can
come
from
anywhere.
So
you
might.
B
E
A
A
Something
that's
pretty
cool
is
that
when,
like
this,
api
includes
additional
metadata
about
providers
in
request
and
response.
However,
when
the
client
is
implemented
in
go
ipfs,
it
will
be
kind
of
like
hidden
behind
the
curtain.
So
when
you
like,
pin
remotely
the
go,
ipfs
itself
will
ensure
it
shares
its
multi-other
directly
with
pinning
service
and
then,
when
pinning
service
responds
with
multi-others
of
their
own
nodes
go
ipfs,
which
will
ensure
that
local
node
is
connected
to
a
pinning
service.
So
that's
all.
A
I
mentioned
it
because
it's
important
for
desktop
users,
who
are
usually
behind
nuts
in
networks
that
have
strange
topology
and
this
additional
metadata
dance
that
we
do
with
pinning
service
api,
ensures
that
you
don't
need
to
ask
dht
which
may
be
slow
or
not
all,
and
even
if
you
get
the
address,
you
may
not
be
able
to
connect
to
to
it
and
by
ensuring
that
we
both
sides
try
to
proactively
connect
to
each
other.
That
closes
the
gap
with
strange
network
topologies.
E
Eventually,
if
you
can
just
punch
through
palgate
to
talk
to
ipfs
on
0.1,
then
you'll
be
able
to
use
that,
but
to
be
able
to
say
like
can
I
have
a
nice
api
that
pins
to
filecoin
as
and
the
powergate
hot
storage
for
built
into
the
command
line,
for
that
particular
instance
would
be
great.
If
you
get
like
the
same
kind
of
api,
then
you
can
use
your
whatever
pinning
client.
E
You
have
to
talk
to
a
power
gate
instance
and
have
all
of
that
stuff
happen
automatically,
rather
than
having
to
configure
it
all
yourself,
which
currently
is
painful
or
using
third-party
service.
But
then
you're
like
I
have
to
upload
all
my
files
over
there
and
then
they
get
sent
over
there
and
then
they
get
put
in
ipfs
and
then
they
go
into
file
coin.
And
then
they
go
into
another
file.
Coin
storage
node
over
there-
and
it's
it's
very,
very
slow
and
painful,
and
I
want
to
be
able
to
not
think
about
it
anymore.
A
Yeah,
it's
still
unclear
if
it
will
be
a
part
of
powergate
or
maybe
someone
will
create
a
kind
of
like
a
middleware
that
sits
in
front
of
it.
But
definitely
that's
a
that's
not
like
on
that
checklist.
I
would
like
to
see
personally
also
the
the
js
client
is
something
we
may
we
may
want
to
create.
Just
like
we
created
the
go
client
for
pinning
services
api
and
you,
namely,
use
the
js1
for
quick,
like
regression
test
or
compliance
tests.