►
From YouTube: IPFS Web and GUI Biweekly 2020-09-08
Description
No new releases this week, but we give a quick status update on ongoing efforts. Meeting notes: https://github.com/ipfs/team-mgmt/pull/1174
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
This
week
we
got
a
pretty
cool
announcement,
so
maybe
I'll
share
my
screen
feel
free
to
add
any
agenda
items
which
I
missed.
A
The
cool
cool
development
is
that
part
of
work
we
do
with
igalia
on
improving
the
way
protocol
handlers
work
on
the
web
platform.
Initially,
the
goal
was
to
improve
browser
extension
context,
but
since
then
the
work
pivoted
a
little
bit
and
we
are
improving
the
way
the
generic
navigator
api
looks
like
so
in
chrome,
86,
which
shipped
on
the
3rd
of
september.
A
There's
this
update
that
ipfs
ipns
and
a
bunch
of
other
distributed
web
uri
schemes
are
now
safe
listed,
which
means
everyone
can
use,
use
them
in
with
register
protocol
handler
api.
It's
a
basic
api
which
just
enable
you
to
redirect
specific
requests
to
some
arbitrary
website,
but
it's
pretty
cool
that
we
are
now
site
listed,
safe,
listing
means
our
protocol
scheme
does
not
need
to
be
prefixed
by
web
plus
prefix.
A
So
you
know,
are
it's
much
easier
to
use
ipfs
console
slash
protocols
in
in
websites
and
in
general
across
your
system?
That's
the
first
step.
Ideally,
we
want
to
get
to
the
point
where
we
are
able
to
return
arbitrary,
bytes
fetched
from
ipfs
without
redirecting
to
some
other
url,
but
it's
pretty
cool
that
registration
at
ayana
and
now
we
can
see
it
happened
some
time
ago
and
now
chrome
86,
safe,
listed
ipfs
ipns,
which
will
make
all
make
it
to
all
the
other
chromium
based
browser
vendors
sooner
or
later.
A
As
a
side
note,
we
got
this
website.
Are
we
distributed
yet.com?
It
was
mentioned
on
the
chrome,
chromium
team,
blog
post.
Unfortunately,
that
website
is
bit
outdated
and
the
deployment
does
not
work.
So
my
proposal
was
to
switch
to
flick,
so
we
don't
need
to
figure
it
out
how
to
do
circle.
Ci
deep
bass
deployments
across
the
orgs,
because
this
website
is
under
are
we
distributed
yet.org
and
there's
a
bunch
of
stuff
that
does
not
work
across
orgs,
but
that's
something
we
probably
will
discuss
asking
outside
of
this
call.
A
There
are
upcoming
releases.
I
try
to
like
compile
a
list
of
stuff
that
will
land
sooner
or
later
we
did
not
ship
ipfs
web
ui
to
11
yet,
but
there's
a
milestone
which
is
nearly
completed.
We
got
just
two
or
three
issues
or
pull
requests
waiting
for
a
review
and
merge,
and
then
we
are
good
to
go
to
to
do
it.
A
The
plan
is
to
do
it
either
tomorrow
or
thursday,
depending
how
profile
it
feels
and
our
reviews
goes,
but
this
will
be
a
pretty
cool
release
where
changes
made
by
iraqi
on
removing
the
need
for
removing
the
buffering
of
big
files
that
will
land,
if
I'm
not
mistaken,
breadcrumbs
breadcrumbs
by
rafael,
improved
support
for
remote
apis.
So
it
would
be
possible
to
use
things
like
basic
alf
or
a
custom
configuration
of
http
client
yeah
and
a
bunch
of
improvements
around
the
way
we
handle
translations.
A
The
duplication
of
code
of
key
is
made
by
jessica
there's
like
a
long
long
list
on
the
milestone.
I
believe
I
don't
think
I'm
sharing
my
screen,
but
the
link
is
in
the
notes,
we're.
A
Yeah,
I
think
we
should
aim
for
like
a
smaller
milestones,
we
already
scoped
a
bunch
of
stuff
to
to
12
and
we
will
probably
refine
this
process
the
this.
When
this
release
happens,
we
will
ship
new
ipfs
desktop,
I
believe,
go
ipfs.
0.7
will
be
released,
probably
next
week
at
the
beginning
of
the
next
week
or
at
the
end
of
this
week.
A
So
when
we
have
this
new
web
ui,
we
will
bump
the
version
of
both
web
ui
and
go
apfs
in
ipfs,
desktop
and
ship
that
to
our
end
users,
so
all
those
new
web
ui
features
will
land
in
ipfs
desktop
and
ipvs
companion
with
post
secio
refactor
got
kind
of
deprioritized,
because
our
infrastructure
will
still
maintain
those
bootstrap
nodes
which
talk
only
with
which
will
enable
js
ipfs
running
in
the
browser
context,
js
ipfs
in
an
older
version,
which
does
not
support
anything
other
than
sekio.
A
Those
notes
will
continue
working
properly.
So
it's
no
longer
a
super
high
priority
to
learn
this
so
that
sound
good
news
is
that
alex
landed.
I
I
mentioned
it
a
little
bit
lower.
So
there's
this
javascript
epic
of
replacing
node
buffers
with
uint
arrays,
and
the
good
news
is
that
I
believe
the
latest
version
of
jsapfs
is
mostly
unifying.
A
The
behavior
between
jsipfs
and
jsipfshtp
client,
so
the
same
types
are
accepted
in
both
which
will
make
a
refactor
of
ipfs
companion
easier
because
in
ipfs
companion
we
have
both
http
client
for
talking
to
a
remote
node
over
http
and
there's
also
ability
to
run
embedded
node
and
so
far
we
had
to
created
two
code
paths
for
each
and
now
it
will
be
greatly
unified.
So
I
think
that
will
unblock
this
refactor
as
well.
Oh
gosh,
I
believe
that's
it.
A
On
on
upcoming
releases.
Did
I
miss
anything?
Ipfs
go
ip
jessica,
updated
names
of
bunch
of
countries
which
were.
A
It
was
like
all
over
the
place,
but
yeah
that
will
also
be
in
web
ui
to
point
eleven.
So
it's
pretty
fat
release
we'll
try
to
cut
a
bit
more
lean
releases
going
further
further
in
the
future.
B
And
am
my
right,
you
can
see
you
can
see
the
country
edits
already
in
the
public
gateway
tracker,
because
they're
already.
A
Public
yeah,
so
I
I
believe
I
switched
this
static
website.
It's
it's
using
the
ipfs
go
ip
and
it's
using
the
pre-built
browser
bundle,
http
client,
which
is
pretty
funny.
So
if
you
hover
on
the
flag
of
the
usa
in
the
past,
it
was
united
states.
Now,
it's
usa,
that's
how
we
know
the
name
updates
got
applied.
A
All
right
pinning
services
gosh.
Oh
every,
why
every
item
is
mine?
I
should
randomize
this
stuff
all
right,
so
pinning
services,
api
spec.
The
good
news
is
that
there
are
no
no
news.
So
that's
a
good
news.
A
It's
good
news,
because
we
are
pretty
stable
and
pretty
happy
with
the
api
there.
There
is
just
a
bunch
of
final
touch
touches
on
on
the
topic
of
documentation,
so
we
are
specifying
that
the
pin
name
filter
should
be
case,
insensitive
to
improve
user
experience,
and
we
are.
A
A
We
do
not
control
every
error
that
will
be
returned
by
reverse
proxies
and
also
pinning
services
may
decide
to
create
their
own
custom
error
codes,
but
there's
a
an
error
structure
that
we
suggest
to
use,
which
makes
it
easier
for
both
machines
humans
and
make
it
possible
to
figure
out
what
went
wrong
without
relying
on
http
semantics.
So
that's
mostly
improving
docs
and
clarifying
stuff
that
was
not
specified
in
the
spec.
A
I
also
believe
we
now
have
a
go
library
for
a
client
site
and,
and
you
made
pins
on
rails-
I'm
not
sure
if
I
mentioned
it
like
the
last
time
we
we
talked
so
pins
on
rails
are
a
server
implementation
of
pinning
service
api
that
you
can
like
run
locally
or
run
remotely
and
use
it
for
self-hosting
and
stuff.
Like
that
yep,
I
believe,
that's
my
list
of
stuff.
A
I
was
supposed
to
run
through
very
quick
yeah,
so
the
the
the
links
to
both
client
and
andrew's,
pinning
service
app
will
be
added
to
the
rhythmy
of
pinning
service
apis
back.
I
believe,
there's
an
open
pr.
B
C
Today,
question
title
about
foul
coin
and
pinning
things
are
we,
assuming
that
the
file
coin
stuff
will
be
transparent
to
the
user
or
deal
out
of
band
like?
Is
that
something.
A
C
A
Is
something
that
will
get
flung
so
it
was
like
a
conscious
decision
to
not
include
anything
file
coins
related
in
the
spec,
so
it's
purely
ipfs
there's
you
you
can
implement
it
with
sql
database,
whatever
you
want
as
a
back-end,
you
may
use
whatever
you
want
for
the
storage.
The
idea
is
that
it
should
be
possible
to
use
this
api
in
a
pinning
service
that
is
file
coin
backed,
and
it
should
be
possible
for
pinning
service
to
come
up
with
additional.
A
The
pinning
service
that
is
implementing
this
api
spec
should
be
able
to
leverage
info
and
meta
fields
which
are
like
free
form,
dictionaries
right
now
and
come
up
with
a
convention
for
supporting
this
additional
file
coin
specific
or
way
of
storing
files.
But
we
did
not.
We
did
not
include
that
in
the
spec
just
to
make
a
spec
small
and
like
backhand
agnostic,
and
also
we
did
not
had
many
pin,
we
had
a
small
num.
A
We
have
a
small
number
of
pinning
services
which
will
implement
this
spec
out
of
the
box,
so
we
don't
want
to
be
prescribed
prescriptive
too
early,
and
the
idea
is
that
spinning
services
that
are
using
file
coin
on
the
back
and
then
they
will
eventually
come
up
with
a
set
of
conventions
which
are
common
to
them
and
we
either
agree
or
like
everyone,
will
follow
the
same
set
of
conventions
or
we
will
promote
those
meta
or
info
fields
to
the
higher
level.
A
Just
like
we
did
with
creation
date
or
a
name
of
a
pin,
but
that
just
like
where
things
are
right
now
the
spec
is
just.
C
C
That
makes
sense.
I
thought
the
spec
on
the
whole
was
very
easy
to
implement.
There's
a
few
bits
that
you
have
to
make
sure
you
focus
if
you're,
if
you're
implementing
it
like,
I
did
by
hand
rather
than
using
the
like
something
that
generates
something
else
from
the
yaml
file,
but
the
only
thing
that
I
found.
That
was
weird.
C
That's
still
there
is,
when
you
do
an
update,
you're,
not
actually
doing
an
update,
you're
deleting
the
thing
and
returning
a
brand
new
thing
which
hurt
my
brain
a
little
bit
to
like
do
that,
I
kind
of
re-implement
it
three
times
until
I
ended
up
with
like
okay,
fine,
I'm
gonna
forget
what
I
know
and
I'm
just
gonna
do
exactly
what
this
says,
but
that
might
end
up
being
a
gotcha
for
some
other
people
as
well.
C
Maybe
it's
just
a
messaging
around
it
to
be
like
it's
not
really
an
update
at
all.
You
don't
touch.
A
A
A
Both
post
and
this
concern
about
like
get
posting
something
and
getting
something
new
is
because
the
general
idea
behind
this
api
is
that
the
pin
object
is
immutable.
So
you
effectively
can
think
that
you,
if
you
use
ipfs
for
storing
those
pins
right.
So
you
have
this
pin
object
and
you
put
it
on
the
ipfs
and
you
get
an
immutable
cid,
and
then
you
can
use
that
immutable
cid
as
an
id
of
id
in
a
pin
status
right
right
and
that's
if
you
think
about
things
that
way.
A
That
explains
why
you
are
not
able
to
like
actually
update
the
pin
when
you
post
a
pin
to
replace
it.
You
posted
a
new
thing
that
new
thing
got
added
to
ipfs
and
you
got
a
different,
unique
identifier
and
that's
why
you
got
this
different
identifier
back
yeah.
C
C
A
A
I'm
at
the
end
of
agenda.
We
are
a
bit
short
stuff
this
week.
Is
there
anything
you
want
to
discuss
talk
about.