►
From YouTube: IPFS Web and GUI Biweekly 2020-10-06
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1178/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
A
A
A
Soon
to
be
shipped
and
even
improved
with
ipv6
desktop,
but
for
now
it
restores
context
menus
on
directories
and
breadcrumbs.
So
here
you
can
right
click
and
you
got
the
full
context
menu
here
same
here
on
the
directory.
A
The
context
menu
is
here
and
I
believe
the
the
kind
of
cool
thing
is
that
we've
improved
text
file
preview.
So
there
was
a
bug
where
you
are
not
able
to
preview
file.
You
have
to
download
it
through
this
button
and
now
you
can
see
entire
file
if
it's
small
enough
right.
So
this
is
a
small
text
file
and
you
can
see
the
entire
file.
A
However,
here
I
got
one
of
works
of
toy
story
and
it's
a
three
megabyte
of
plain
text
and
you
can
see
by
the
scroll
bar
like
it's
long,
but
then
it's
not
even
like
entire
thing.
So
this
is
the
improvement
we've
did.
A
You
may
have
really
really
big
text
files,
and
this
has
it's
a
practical,
practical
use
because
people
may
store
or
share
log
files
or
other
stuff
type
of
text
up
and
only
data
where
it's
really
really
big,
like
hundreds
of
megabytes
of
gigabytes,
and
we
don't
want
to
load
the
entire
text
file
to
the
browser
to
preview
it
in
in
a
web
ui.
So
now
we
fetch
only
the
first
block,
which
is
256
kilobytes.
A
I
believe,
and
then
you
have
this
option
to
either
load
more
or
download
entire
thing.
So
if
you
you
initially
download,
then
you
download
it
and
save
it
to
the
disk.
You
can
also
load
the
next
block
and
it
will
load
the
next
block
and
you
can
resume
and
do
that
until
you
read
the
entire
file.
So
that's
the
main
improvement.
The
the
key
and
the
key
idea
here
is
to
avoid
loading
too
much
into
the
browser.
B
Sorry,
you
can
drag
and
drop
the
images
as
well
now
and
json
text
will
not
be
oh.
A
Right,
yeah
yeah,
so
this
is
a
yet
another
thing.
So,
like
the
drag
and
drop
works
before
you
can
like
drag
to
pads,
go
to
pets,
and
then
the
file
is
here
right
and
you
can
drag
like
this.
The
improvement
now
is
that
you
can,
I
believe,
drag
this
image
right,
yes
into
like
pets
and
it
it
works
yeah.
So
that's
also
cool.
So
like
a
bunch
of
small.
A
Make
it
more
intuitive
to
work
with
stuff?
I
guess
that's
the
highlight
for
this.
There
is
an
upcoming
improvement
for
the
way
http
gateways
present
directories
in
html
form,
so
maybe
I
will
maybe
I'll
just
kind
of
like
show.
This
is
a
directory
listing
for
our
this
ipfs
io
website,
which
has
a
dns
link,
it's
loaded
from
a
local
gateway,
but
if
you
use
dns
link
the
address
would
look
like
this
without
the
gateway
suffix.
A
So
the
improvements
which
we
landed
previously
were
the
breadcrumbs
and
the
cid
column
and
upcoming
fixes
are
that
those
breadcrumbs
will
work,
even
if
you
use
dns
link.
So
even
if
you
have
the
root
at
the
url
root,
those
links
will
work
fine
and
the
cid
column.
In
the
past.
It
just
pointed
at
the
row
row
cid
now
it
will
have
a
file
name
preserved.
A
So
if
you
download
it,
the
file
name
will
be
previewed
in
save
as
dialog
in
your
system
and
if
you
are
displaying
this
screen
on
dns
link
website,
which
probably
does
not
have
a
public
gateway
mounted.
If
you
are
using
your
own
domain,
you
generally
don't
want
to
have
people
being
able
to
load
arbitrary
content
under
your
own
origin.
So
in
that
context
we
kind
of
changed
the
behavior
of
cid
column
instead
of
pointing
at
the
public
gateway.
We
did
not
want
to
favoritize
some
one
canonical
gateways,
a
gateway.
A
We
decided
to
point
at
cid,
ipfs,
io
utility,
which
explains
the
meaning
behind
cid.
So
that's
an
ux
improvement
on
this
front
and
the
third
item,
which
oh
it's
also
mine,
so
I
can
probably
show
it
as
well,
and
we
we
did.
A
We
did
a
overhaul
of
how
ipfs,
desktops,
ci
and
cd
works
and
long
story
short
is
that
we've
switched
to
github
actions
for
both
mac,
os
and
windows,
and
linux
builds
and
now
there's
a
single
ci
pipeline
which
builds
artifacts
for
every
or
every
push
and
every
pr,
and
when
it's
a
release,
it
also
attaches
those
build
and
signed
and
notarized
in
the
case
of
apple
packages,
to
github
release.
A
So
maybe,
as
an
illustration,
if
we
want
to
see
the
latest
build
for
the
master
branch,
you
can
see
it
run
for
first
it
runs
tests
against
mac,
linux
and
windows,
and
if
tests
pass,
then
it
and
only
then
it
will
build
the
packages
because
that's
expensive-
and
here
everything
is
green,
so
packages
were
built
and
after
successful
build
packages
are
attached
to
the
job.
So
it's
pretty
useful
for
testing.
We
are
no
longer
you.
We
no
longer
need
to
check
out
the
the
branch
and
build
locally.
A
We
have
a
built
for
a
specific
commit
attached
to
the
github
action
that
was
responsible
for
testing
and
building
stuff.
Those
are
zip
files,
that's
the
limitation
of
github,
it
zips
all
the
artifacts.
So
even
if
I
created
a
zip
per
file,
it
would
still
be
zipped.
So
it's
a
single
zip
for
windows,
for
linux
and
for
mac
os
for
now,
but
it's
pretty
useful
to
be
able
to
a
quickly
test
installation
package
for
a
comet.
A
So
that's
something
to
be
aware:
if
there's
an
error
like
a
mac
security
error
or
a
windows
error
when
you
test
a
pr
from
a
contributor,
that
means
it's
fine,
it's
just
like
we
don't
expose
secrets
for
builds
that
were
triggered
by
people
other
than
internal
collaborators.
A
So
I
think
that's
a
pretty
good
trade-off
between
what
we
had
before
and
what
we
have.
What
we
want
to
have
with
like
with
addressing
the
security
concern
of
signing
a
code
that
we
did
not
approve,
so
the
value
here.
The
main
value
here
is
that
we
see
if
a
build
breaks,
we
are
able
to
detect-
let's
say,
windows
problems
sooner
than
on
the
release
date
in
the
past.
A
A
I
think
that's
it.
On
my
end,
it's
pretty
exciting
that
we
removed
dependency
of
external
ci
providers
and
now,
like
at
least,
we
are
relying
on
github,
which
is
like
one
external
company
instead
of
four,
which
is
pretty
pretty
pretty
good
security
wise.
A
I
plan
to
do
similar
thing
for
companion.
This
quarter
we'll
see
how
it
goes
later.
This
week
we
should
be
releasing
ipfs
desktop
0.13
with
go
ipfs
0.7
and
the
new
web
ui,
which
has
a
fix
that
was
not
present
in
in
the
latest
release,
but
we'll
also
release
that
later
this
week
it's
improved
file,
import
feedback,
which
also
has
a
bug
fix,
but
I'm
mostly
excited
about
file
import
feedback.
C
A
A
I
totally
have
this
prepared,
so
I
want
to
import
it
and
you
can
see
I
had
this
short
spinner
here
which
told
me
that
something's
happening-
and
it
was
bothering
me
before
because
my
like,
I
have
a
very
slow
laptop
and
it
takes
time
for
importing
even
smaller
files
and
nothing
happened.
And
now
something
happens
and
after
things
happens,
we
see
that
we've
imported
one
item.
A
I
believe,
that's
more
or
less
it.
There
was
a
bug
when,
instead
of
a
number
here,
we
had
and
not
a
number
error
which
will
which
blocked
a
iqs
desktop
release,
but
that
will
land
this
week.
So
I'm
pretty
excited
on
that
and
I
believe
the
web
ui,
which
I
was
showing
you
all
this
time
already
has
this
fixed
by
jessica,
to
accommodate
smaller
viewports
and
on
the
status
yeah.
We
got
the
version.
C
Yeah
there's
an
easter
egg.
That
is
thanks
to
contributor
bertrand.
You
cannot
blame
me
for
wanting
to.
He
raised
both
the
issues
and
pr
and
an
initial
fix
to
include
the
ui
version.
It's
also
in
not
only
in
the
status
screen.
If
you
look
at
the
very
bottom
of
the
left
nav
it's
there
as
well.
A
See
that's
what
I
get
for
having
a
working
copy
of
what
do
I
I
need
to
demo
all
this
stuff,
all
right.
Folks,
that's
the
stuff
I
had
on
the
agenda.
Are
there
any
topics
you
want
to
bring
up
perhaps
or
it's
just
top
secret
that
we
need
to
discuss
after
I
ended
this
recording
right.
It's
just
top
secret
stuff.
Okay,.
A
All
right
folks,
I
was
hoping
we
will
demo
it
fast
desktop,
but
we
got
derailed
and
it
happened
probably
later
today,
but
that
means
I
will
demo
that
in
two
weeks
so
this
week's
one-
it
was
pretty
short
but
stay
tuned,
see
you
in
two
weeks.