►
From YouTube: IPFS Web and GUI Biweekly 2020-11-10
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1195/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
B
A
Welcome
to
gui
and
in
web
browsers
by
weekly
call,
which
was
over
a
month
ago.
So
this
is
a
10th
of
november
2020
and
we
will
start
with
a
really
strain.
So
I
will
quickly
share
my
screen
and
then
raphael's
slash
jessica
will
take
over.
Can
you
see
my
screen?
A
Yes,
yep?
Yes,
so
ipfs
desktop,
0.13
and
I'd,
say
0.13,
because
there's
0.132
with
fixes
for
windows,
auto
update.
However
0.13
had
a
new
web
ui
new
go
ipfs
0.7
switch
to
new
the
latest
electron
version
so
to
get
0.13
goodness
just
pick
the
latest
one,
because
that
includes
auto
updates
fixes
for
windows
users.
A
If
you
are
windows
user
and
when
you
try
to
auto
update
you
get
that
infinite
loop.
Apologies
for
that!
It's
not
fully
our
fault.
So
what
you
need
to
do
is
to
go
to
ipfs,
desktop
releases
and
download
installer
for
13.2
install
it
manually.
It's
just
this
one
release
that
you
need
to
install
manually
from
this
point
going
forward.
You
should
get
proper,
auto
updates
on
windows
platform.
A
We
also
added
chocolaty
and
snapcraft
publishing
as
a
part
of
our
pipeline.
So
if
you
prefer
to
use
those
package,
managers
or
any
other
package
manager
maintained
by
our
com,
ipfs
community
feel
free
to
do
that,
I
will
start
my
screen
sharing
now
because,
as
a
part
of
this
release,
we
improved
or
fixed,
depending
on
the
platform
native
integrations
for
mac
and
windows.
B
So
I'm
gonna
cheat
a
little
bit
and
I'm
just
gonna
share
my
screen
that
contains
an
animated
gif
of
the
action,
because
otherwise
I'd
have
to
share
my
entire
screen,
and
that
would
be
massive.
So.
B
B
So
basically,
you
can
see
my
massive
ipfs
desktop
here
in
this
window.
Wait
till
this
starts
over
see
I'm
taking
the
cat
of
the
day
and
I'm
dragging
it
up
to
my
menu
bar.
This
is
the
the
most
underrated
little
known
feature
of
ipfs
desktop
from
mac.
Is
you
can
drag
things
to
the
menu
bar
and
it
works
beautifully.
B
I
should
have
taken
longer
because
raphael
is
still
installing,
but
that
said
one
thing
we
do.
I
I
did
highlight
that
as
a
feature
a
little
bit
more
heavily
in
the
rewrite
of
ipfs
desktop
readme
and
we'll
continue
to
emphasize
that
further
in
other
places
where
we
let
people
know
about
desktops
feature
set,
because
I'm
a
bit
embarrassed
as
to
how
long
it
took
me
to
realize
that
that
was
a
feature,
because
I
didn't
read
our
own
release.
A
Yeah
and
what's
also
cool,
we
do
the
same
thing
that
ipfs
companion,
browser
extension.
Does
we,
when
you
do
that
you
we
automatically
copy
a
shareable
link
to
the
clipboard
yeah
yeah?
So
that's
a
super
fast
way
of
sharing
files,
rafael
blink
once
if
you
can
do
the
demo
or
link
twice.
A
All
right,
so
we
did
not
have
this
call
for
a
while,
and
we
had
three
releases
of
ipfs
companion,
so
I'll
go
from
the
oldest
one,
it's
a
stable
release
from
the
stable
channel.
So
if
you
just
installed
companion
from
the
add-on
or
extension
store,
you
probably
are
on
this
version.
A
Menu
item-
it's
now
not
only
faster,
but
you
are
able
to
upload
a
very
big
files
for
gigabytes
or
more
through
your
browser.
Thanks
to
the
work
by
kosala
and
akingbrain,
we
have
a
better
controls
for
obtain
and
opt
out
from
ipfs
integrations
per
website.
So
we
keep
now
when
you
toggle
this
toggle
in
menu.
A
We
store
an
explicit
record
for,
is
it
like
opt-in
or
opt-out
and
you're
able
to
edit
those
lists
from
the
preferences
screen.
However,
every
time
you
toggle
here
we
apply
this
change,
and
that
means
all
ipfs
integrations
are
disabled.
So
those
integrations
by
that
I
mean
things
that
could
change
the
website,
things
that
change
either
the
dom
or
things
that
redirect,
let's
say
redirect
from
original
http
server
to
a
local
host
node.
A
If
you
have
one
and
you
if
you
have
redirect
enabled
so
all
the
integrations
provided
by
companion
can
be
disabled
for
a
specific
website.
If
you
find
that
you
get
better
performance
either
way
or
if
you
want
to
quickly
see
how
the
behavior
changes
between
original
url
and
the
one
on
localhost,
we
also
got
support
for
ipfs
uris.
A
Those
uris
are
now
official
and
we
are
working
towards
adding
support
for
them
to
web
browsers
to
like
native
means.
For
now.
Only
ipf
only
firefox
provides
an
api
for
browser
extension
to
like
formally
register
a
handler.
That
handler
is
still
redirect-based
and
but
it
works
in
firefox.
The
problem
is
the
identifiers
in
those
uris
are
case,
sensitive
and
browser
forces
lower
case
on
them.
So
if
you
use
a
case
sensitive
identifier
such
as
cid
v0,
you
will
see
this
error
page
now,
which
is
improved
by
jessica.
A
Hopefully,
this
will
give
you
an
idea
what
went
wrong
and
how
to
fix
it
generally
when
in
doubt
just
use
cidv1.
But
if
you
need
to
use
cidv0,
this
screen
should
help
you
and
in
chromium
86,
ipfs
ipns.
I
and
I
believe,
deweb
and
a
bunch
of
other
newer
protocol
handlers
got
safe
listed.
So
we
hope
to
see
similar
level
of
integration
in
chromium
based
browsers
in
the
future,
and
we
had
two
beta
releases
recently.
A
One
had
a
switch
to
webpack
five,
which
is
not
visible
to
users,
but
decreased
bundle
size
a
little
bit
and
now,
when
there's
a
new
version
of
ipfs
companion,
you
will
see
this
eye
icon
and
when
you
click
on
it,
you
will
be
able
to
read
release
notes.
So
in
this
version
we
experimented
with
opening
errors
notes
on
in
a
new
tab,
but
that
was
kind
of
intrusive.
A
C
A
I
feel
so
bad,
so
I've
been
like
showing
you
all
those
tabs
before.
So,
let's
just
pretend
you
so
all
those
tabs
now
quickly
here
the
changes
are
around
this
toggle
and
there
is
this
nice
error
page
now
and
in
beta
releases
we
got
this.
A
I
icon,
which
tells
you
oh
there's
a
new
release
and
you
can
read
what's
new
in
this
new
release
and
in
the
latest
ipfs
component
we
moved
some
actions
to
those
buttons
and
we
now,
when
you
are
on
dns
link
website,
you
are
able
to
not
only
copy
shareable
link
to
the
canonical
address
of
a
website,
but
you
can
copy
a
link
to
a
snapshot
of
this
website
which
will
never
change
and
same
if
you
want
to
just
get
an
ipns
path.
It's
also
here
so
thanks
jessica
for
pushing
this
forward.
B
And
the
original
work
on
that
came
from
contributor
detail
fake,
so
he
deserves
the
original
credit
for
that.
A
Yep
yep,
thanks
for
to
everyone
who
pushed
this
rock
forward,
I
feel
really
bad
that
I
did
not
share
my
screen
from
the
very
very
beginning,
but
just
the
last
item
on
my
list:
rafael,
just
blink
once
or
twice,
but
after
I'm
done
with
this.
A
A
So
that
enabled
you
to
do
dna
dns
lookups,
to
know
what's
like
the
country
and
city
is
behind
that
ip
without
fetching
entire
data
set,
you
only
traverse
the
dag
and
only
fetch
nodes
that
are
relevant
to
your
specific
ip
range,
which
works
pretty
well
in
web
browsers,
and
the
problem
was
our
data
set
was
pretty
old,
so
we
spent
some
time
to
account
for
changes
in
the
input
format,
and
now
we
got
the
latest
data
set
from
october.
A
I
believe-
and
that
means
there's
no
longer
like
faster
than
light
travel
in
ipfs
in
the
past.
You
could
see
peer
in
europe
seeing
a
node
in
from
us
and
have
a
ping
around
20
milliseconds,
which
is
not
possible
that
that's
because
people
are
trading
ip
ranges
and
something
that
was
in
us
now,
maybe
in
europe
and
vice
versa.
A
So
now
this
updated
data
set
will
land
in
the
new
version
of
go
ipfs
as
well,
but
I
just
wanted
to
mention
it
because
people
been
asking
why
ipfs
is
faster
than
light,
so
I
fixed
that.
A
D
C
Let
me
share
the
screen
and
I
guess
you
can
see
my
screen
now.
Yes,
perfect,
yes,
nice.
So
what
little
one
wanted
me
to
show
is
that
when
you
have
something
you
want
to
add
to
ipfs
on
your
file
explorer,
you
can
just
right.
Click
on
it
and
click
on
the
option
called
add
to
ipfs
and
it
it
will
add
you
to
your
local
node
and
then
it
will
also
copy
a
link
to
your
clipboard.
If
you
want
to
share
it
with
someone
else
as
well.
So
there's
the
link
for
our
little
caddy,
probably
gonna.
C
A
Cool,
let's
see
what's
next,
the
next
one
is
a
quick
update
on
pinning
services.
So
let
me
try
to
share
the
right
screen.
This
time
is
the
right
screen.
Is
it
oh,
gosh,
yep,
so
pinning
services,
the
updates?
Are
we
shipped
0.1.2,
which
had
a
small
cosmetic
change
in
how
we
do
the
search
based
on
name
previously?
A
So
if
you
really
need
a
case
insensitive
or
a
partial
match,
you
need
to
specify
that
if
you
don't
specify
this
parameter,
the
search
for
your
pin
will
be
doing
the
exact
match
and
that's
something
we
wanted
to
align
due
to
the
fact
that
while
we
are,
we've
been
working
on
remote,
pinning
services
and
remote
pinning
api
in
go
ipfs,
which
is
work
in
progress
right
now.
We
realized
we.
A
We
also
want
to
improve
local
pinning
so
be
cognizant
that,
while
we
are
adding
remote
pinning
first
some
of
benefits,
some
of
additional
capabilities
introduced
in
remote
pinning
will
all
will
eventually
land
in
go
ipfs
and
be
possible
to
use
in
local
pinning
context,
namely
we
it
will
be
possible
to
attach
a
name
to
a
pin.
So
you
no
longer
will
have
a
list
of
nameless
cds.
A
You
will
be
able
to
attach
like
meaningful
name
to
a
pin
and
then
find
a
pin
at
some
point
in
the
future
when
you
want
to
get
back
to
it
and
manage
it
so
that
work
that's
its
work
in
progress
in
go
ipfs
and
also
in
js
http
client.
We
need
http
client
because
it
will
be
used
by
web
ui.
A
So
we
expect
ipfs
pin
remote
commands
to
land
in
go
ipfs,
0.8,
release
candidate
1
this
week
or
maybe
next
week,
and
then
we
will
add
those
new
commands
to
iphone's,
http,
client
and
then
rafael,
who
just
finished
stage.
One
integration
of
pinning
services
we'll
be
able
to
wire
it
up
and
start
working
on
stage.
Two.
A
A
So
that's
that's
that
yeah
and
then
there
is
exciting,
probably
for
some
folks,
it's
pretty
low
level,
but
I
mentioned
it
because
it's
gui
web
and
we
use
local
host
subdomain
gateways
for
loading
websites
from
local
ipfs
node
and
if,
in
case,
anyone
is
interested
in
low-level
details
around
host
names
for
localhost
http
gateway.
I
posted
some
updates
across
different
vendors.
We
got
intent
to
implement
secure
context
on
localhost
in
chromium
and
it's
effectively
done
because
they
mark
it
as
secure
context
for
subdomains.
A
The
problem
was
firefox
where
localhost
itself
was
secure
context,
but
subdomains
were
not
so
here
I
was
linking
to
a
bunch
of
ongoing
work.
However,
you
can
see
that
a
bunch
of
patches
landed
in
the
past
weeks
in
firefox
effectively
aligning
it
with
what
google
chrome
does
and
we
now
will
have
a
secure
context
on
localhost
subdomains
without
doing
anything
fancy
we
no
longer
need
http
proxy
and
we
get
a
secure
context
and
what's
really
exciting
about
this
work,
is
it's
not
just
about
chromium
and
firefox?
A
We
are
working
to
with
igalia
towards
creating
web
platform
tests
that
will
ensure
that
behavior
on
localhost
is
the
same
across
all
the
browsers.
So
we
we
reached,
we
are
reaching
out
to
webkit
team
as
well
to
align
the
behavior
with
what
chromium
and
firefox
do,
and
we
hope
the
web
platform
tests
will
be
a
good
way
of
kind
of,
like
softly
enforcing
the
behavior
across
different
vendors.
So
it's
been
a
long
time
in
the
works
and
I'm
super
excited
that
it
finally
landed.
A
I
believe
that's
all.
On
my
end,
the
remaining
part
are
mid,
q4
or
qr
check
like
it's
like
excuse
me
emit
q4
okr
check-in,
but
in
case
you
got
anything
else
to
add,
I'm
open
to
doing
that
before
borrowing
or
qr
checking,
which
is
not
boring.
It's
exciting,
of
course,.
A
Yeah,
just
a
teaser,
we
will
be
landing
pinning
services
soon.
We
will
have
a
improved
peer
screen
in
web
ui
at
some
point.
If
some
people
will
do
that,
so
stay
tuned,
okay
are
checking.
I
can
share
my
screen.
Yes,
please.
If
people
don't
like
spreadsheets,
that's
the
moment
when
you
need
you
can
like
switch
the
tab,
pretend
you
don't
see
the
screen.
D
A
Yeah,
so
I
I'd
say
just
very
quickly
going
over
those
our
p0
focus
was
and
is
still
pinning
services.
I'd,
say
things
like
gui
apps
ship,
with
flaws
for
interacting
with
cleaning
services.
We
are
actually.
A
B
Yeah
I'd,
say:
60..
I've
got
some
documentation,
debt
on
that
that
didn't
make
any
sense
to
hit
until
we
shipped
what's
about
to
land
like
the
joyride
help
text
and
and
how
that
gets
reflected
in
the
docs
yeah.
A
I'm
pretty
sure
we
got
to
collabs
to
implement
the
api.
However,
I
know
there
is
ongoing
integration
and
testing
work
between
go
ipfs
and
our
initial
partners,
so
I
would
put
that
like
80
percent,
because
the
remaining
part
is
integration
tests
when
go
ipfs,
0.8
rc1
and
following
one's
ship,
no
risk
here.
A
Web
ui
reports
progress
while
importing
four
gigabyte
file,
so
iraqi
fixed
imports
of
big
files.
However,
the
reporting
is
a
separate
thing.
I'm
I
checked
in
with
him
yesterday
he's
not
on
the
call,
but
I
believe
it's
like.
Let's
make
it
80,
because
it's
actually
done,
but
the
pull
request
in
in
review
and
it's
a
complicated
one
across
different
repos,
so
I'd
say
it's
safe
to
say,
20
more
to
land
it,
because
it's
never
that
easy.
A
A
A
We
mostly
focus
on
ensuring
that
our
initial
partners
work
fine,
and
I
think
we
will
then
take
those
learnings
and
create
like
generic
conformance
tests,
which
can
be
run
by
like
third
parties
or
additional
pinning
services,
but
that
did
not
that
did
not
end
up
being
a
priority
right
now
and
the
last
one
is
pinning
service
api
spec
frozen
tagged
as
1.0
I'd
say.
We
are
close
to
that.
A
I
expect
to
tag
1.0
when
go
ipfs
0.8
ships
with
pinning
service
integration.
That
would
be
kind
of
like
a
flagpole
saying.
Okay,
this
is
how
the
spec
work
works.
We
integrated
with
third-party
partners
and
we
got
gui
support.
We
got
support
in
our
jshcp
client,
so
that
will
be
a
moment
when,
with
tag
and
freeze,
the
only
change
was
the
one
which
I
described
around
search
and
it's
still
backwards
compatible.
We
had
no
braking
changes.
We
don't
expect
any
braking
changes.
So
that's
why
it's
like
80
percent.
B
Yeah,
but
I
want
to
explain
them
to
anybody
who
might
be
on
this
call
to
be
to
be
completely
honest,
we'd
included
the
item.
That's
highlighted
right
now,
as
let's
do
as
much
as
we
can
when
we
are
not
working
on
pinning
services
and
painting
services
work,
as
might
be
expected,
got
unexpectedly
large.
B
But
then
that
said,
we
have
been
pushing
through
as
many
sort
of
small
scale
improvements
as
we
can
in
the
backlog,
the
things
that
we
went
over
earlier,
the
caller
a
good
example
small,
but
very
useful
changes,
and
even
within
the
the
pinning
service
ui
setup
work,
we
have
managed
to
actually
just
make
some
improvements
to
webinar
and
desktop
overall,
so
we'll
say
that
that
is
halfway
at
the
halfway
mark,
with
completion
at
the
full
mark.
Second
item
on
that
list
is
doing
some
research
and
making
some
recommendations.
B
Some
testing
based
recommendations
on
information
architecture,
improvements
to
the
ipfs.io
website.
This
isn't
really
a
visual
design
effort,
so
I
hesitate
to
say
that
we're
redesigning
the
website,
but
we
are
trying
to
make
some
very
information,
packed
updates
and
improvements
to
that
site.
There
is
a
link
in
that
master
document
with
an
outline
as
well
as
a
wireframe
for
anybody
who's
curious
about
digging
deeper.
B
It's
probably
not
worth
going
into
right
now,
but
then
also
putting
together
sort
of
a
series
of
prd
documents
for
the
key
recommendations
that
we
want
to
make.
A
Cool
thanks.
I
think
we
are
good
on
those
yeah,
so
improving
technical
ergonomics
of
efficient
for
efficient
web
development.
It's
a
pretty
vague
term
for
a
bunch
of
work
that
iraqi
has
been
doing
and
also
we've
been
improving,
developer
nodes
across
our
different
repos
we've
being
simplifying
like
improving
ci
setups.
I
think
the
biggest
thing
here
is
adding
is
iraqis,
work
on
adding
typescript
and
then
adding
ci
setup
for
guarding
contributed
poll
requests
to
automatically
check
if
typescript
definitions
are
still
valid
for
the
project,
I'm
not
really
sure.
A
I
think
it's
yeah.
I
think
it
landed
in
js
ipfs.
So
it's
all.
It's
probably
around
eighty
percent,
because
adding
typescript
to
js
ipfs
was
a
long,
long,
ongoing
battle
for
rocklin
and
he
finally
shipped
it.
It's
also
like
not
100
percent.
A
Maybe
we
will
adjust
it
later,
but
I
feel
pretty
optimistic
about
it
being
80
percent,
not
everything
is
covered
by
typescript,
but
those
consumer
facing
apis
are
so.
I
think
it's
we
can
like
assume.
A
It
may
improve,
it
will
probably
not
be
the
end
this
quarter.
The
next
one
is
dependence
on
external
ci
is
removed.
Publishing
packaging
and
signing
is
automated,
so
we
moved
away
from
third
party
cis
and
use
github
actions
for
desktop.
I
don't
and
I
believe,
companion
we
are
still
using
circle
ci
for
web
ui,
so
I'd
say
60
percent,
given
that
gosh,
let's,
let's
call
it
16.
A
I
think
it's
fairly
to
be,
if
it's
fair,
to
be
optimistic
and
say
we
will
be
done
with
this
by
the
end
of
the
quarter,
because
moving
away
from
from
github
actions
for
web
ui
will
be
easier
than
it
was
for
desktop.
We
don't
have
any
secrets.
We
don't
have
any
like
magical,
build
pipelines
in
just
a
matter
of
replacing
the
build.
A
B
A
I
started
tracking
total,
oh
gosh,
I
started
tracking
total
downloads
for
ipfs
desktop
on
github
and
I
figured
out
that
number
may
be
useful
in
the
relative
terms.
So
the
number
right
now
is
like
700k,
but
what
I'm
looking
at
is
comparing
the
difference
between
like
each
week
how
many
new
downloads
were
occurring
each
week.
The
problem
here
is
that
those
downloads
are
downloads
of
our
installation
packages,
but
not
all
of
them,
because
a
bunch
of
them
happens
through
third-party
package
managers.
A
At
the
same
time,
github
is
counting
all
those
auto-update
checks
made
a
few
times
a
week
or
like
12
hour,
each
12
hours,
depending
how
someone,
if
someone
is
shutting
down
their
machine
or
not,
so
that's
the
kind
of
like
very
fuzzy
number
but
at
the
same
time
it's
useful
for
watching
trends.
So
if
we
see
that
the
difference
between
week
to
week
right
now,
I
believe
it's
around
10k
increase
each
week.
So
that's
like
both
downloads
and
checks.
A
But
if
we
see
that
number
like
growing
or
shrinking,
we
see
a
trend
around
ipfs
desktop
is
was
it
like
mentioned
somewhere?
Did
we
got
more
users
that
way?
But
we
did
not
do
much
here
and
I
didn't.
B
B
It
wasn't
it
wasn't
something
that
we
built
this
quarter.
I
think
I
set
up
this
reporting
last
quarter,
but
we
do
have
weekly
monitoring
and
the
metrics
that
we're
collecting
in
countley,
and
so
I've
also
been
keeping
an
eye
on
your
fatal
and
non-fatal
crash
events
on
that
weekly
report.
Just
to
see,
if
we're
anything,
we
need
to
be
extremely
aware
of.
A
Oh
yeah,
totally
like
revisiting,
currently
is
also
probably
part
of
this,
and
we
did
not
have
time
this
quarter
to
look
at
it.
I'd
say
we
probably
won't
given
the
all
the
other
stuff
happening.
B
And,
to
be
honest,
I
think
there's
a
certain
amount
of
I'm
I'm
inclined
to
wait
and
see
do
a
deeper
metrics
analysis
of
what
we
might
need
once
printing
services
lands
to
be
able
to
really
do
reporting
on
that
justice.
A
Yeah,
do
you
have
access
to
the
spreadsheet?
Can
you
like
a
note
on
grading
yeah?
Okay,
the
design
exists
for
ipfs
based
hosting
and
auto
updates
for
fpfs
desktop.
A
Did
not
nothing
happened
around
this,
but
it
was
like
p3.
However,
we
probably
I
had
some
discussions
around
that
with
dean,
ollie
and
others,
and
we
realized
it
would
not
be
something
specific
to
ipfs
desktop.
A
And
other
libraries
and
tools
that
we
have
and
ipfs
desktop
would
be
just
a
consumer
of
that,
like
a
general
purpose,
library
or
a
setup
that
we
figured
out
at
one
point
around
ipns.
The
problem
is
secret
management
right
now
the
original
publisher
needs
to
republish
a
record
ips
record
every
like
12
hours
or
something
if
it
stops,
people
won't
be
able
to
get
updates.
A
Ongoing
collapse
and
grants
are
supported.
A
bunch
of
work
happened
in
brave
we've
been
working
on
with
them
around.
Embedding
go
ipfs
around
tweaking
the
default
parameters
of
go
ipfs,
the
ui
for
onboarding
user.
When
you
first
time
visit,
ipfs
console,
slash
or
a
public
gateway,
you
are
prompted
hey.
Do
you
want
to
open
this
via
a
public
gateway?
Or
do
you
want
to
start
your
local
node
and
load
it
from
it?
A
So
a
bunch
of
discussions
we,
I
believe,
we've
passed
security
review
this
week
and
still
I
won't
give
a
date
for
shipping
this,
but
we
are
on
on
track
for
that.
So
I'd
say
it's
like
eighty
percent
done.
A
What
remains
to
be
done
is
testing
it's
behind
the
flag
in
the
brave
nightly
and
then
all
the
release,
dance
comes
and
stuff
that
needs
to
happen
either
by
in
december
or
in
january.
That's
all
I
can
say
igalia
is
helping
us
to
improve
protocol
handlers
and
local
security.
So
I
feel
really
good
about
our
progress
on
localhost
front.
A
A
So
I'm
pretty
happy
about
this.
Maybe
like
the
problem,
is
it's
a
big
win,
but
it's
just
a
single
browser,
so
I
think
it's
safe
to
say
like
not
sure
how
to
score
this,
because
it's
like
a
long
going
collaboration
at
the
same
time
it
was
p3,
so
it
was
mostly
us
supporting
igalia
does
not
really
matter
what
we've
put
here.
A
Would
I
would
keep
it
like
this
for
now
on
the
kiwi
side.
Unfortunately,
nothing
happened
when
it
comes
to
storing
zim
files
on
ipfs,
but
we've
made
some
pro
small
progress
on
making
kiwis
archives
to
be
more
useful
when
loaded
from
http
website.
A
So
that's
not
something
that
we
were
doing
as
an
ipfs
project,
but
we've
been
having
some
discussions
with
cubics
project
and
helping
them
to
make
the
format
in
which
they
store,
wikipedia
snapshots,
more
seekable
via
range
requests
or
byte
requests
in
ipfs,
and
that's
kind
of
like
preparation
for
putting
entire
snapshots
on
ipfs.
A
That's
my
quick
rambly
way
of
going
through
them.
How
do
you
feel
about
those
okrs.
E
B
A
Yep,
I
think
the
problem
with
our
qrs
was
that
we
were
super
focused
on
pinning
services
and
we've
pulled
like
we've
put
a
lot
of
priority
there
and
that's
and
given
the
fact
that
nearly
all
p0s
for
us,
even
like
brave,
was
kind
of
like
it's
expected
to
to
ship
this
year.
Maybe
I'll,
adjust
it
to
0.9
because
it
could
be
january
just
to
be
just
to
be
totally
honest.
A
But
the
problem
was
that
now
that
we
are
pretty
confident
that
we'll
be
able
to
ship
winning
services,
this
quarter,
that
impacted
our
projection
to
be
kind
of
too
high.
A
So
we
may
adjust
some
numbers
later
this
week,
but
I
feel
that's
more
or
less
how
where
we
are
now,
of
course,
like
pinning
services
is
priority
for
this
group
and
we
will
do
our
best
to
ship
it
with
core
implementations
working
group
with
go
ipfs
0.8
there
will
be
new
web
ui.
There
will
be
new
http
clients,
eventually
in
js
ipfs.
A
There
will
also
be
a
remote
spinning
service
support,
so
the
the
pin,
remote
and
namespace
will
be
part
of
core
api
and
we'll
have
pin
local
as
well,
which
will
give
people
ability
to
assign
names
to
pins.
But
I'm
not
sure
if
that
will
happen,
this
quarter,
I'm
pretty
sure
the
remote
pinning
will
happen
this
quarter.
E
A
Nothing
exciting
all
right,
thanks
so
much
for
joining
after
a
long
long
time
when
we
did
not
have
this
call
thanks
for
to
anyone
who's
actually
watching
this
sorry
for
not
being
around
and
being
betrayed,
be
trusted
when
it
comes
to
this
call
we'll
try
to
do
this.
Bi-Weekly,
especially
like
this
following
this
quarter
when
we'll
start
landing,
pinning
services
expect
some
visual
demos
that
next
time,
but
that's
it
for
now.