►
From YouTube: IPFS Desktop v0.10.3, Browsers & Connectivity Q1 OKRs - IPFS GUI and Browsers Weekly 2020-02-05
Description
About IPFS GUI and Browsers Weekly: https://github.com/ipfs/team-mgmt/issues/790
IPFS Mirror: https://ipfs.io/ipfs/bafybeifhtwecjyazfkzcsodyl6ice34kcaxoquysgqtxvwd72ajlgindeq
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
A
So
the
first
item
on
the
agenda
is
ipfs
desktop,
if
feel
free.
To
add,
add
your
items
where
I
cover
this
one.
It's
mostly
a
public
service
announcement.
We've
released
a
new
version,
a
patch
back
Vic
parent
version
of
aquifers
desktop.
There
are
no
functional
changes
compared
to
the
previous
one,
apart
from
adding
three
new
locales
for
new
languages
and
bumping
up
versions
of
web
UI
and
go
a
TFS
which
ship
with
activist
desktop.
A
A
Fixes,
especially
in
web
UI,
the
peer
screen
should
work
much
better
now
and
related
to
IP.
First
desktop,
there's
an
ongoing
problem
on
Mac
OS
Catalina,
where
the
notarization
process
there's
an
authorization
process
where
a
developer,
uploads
binary
or
like
this
image
with
the
and
that
specific
blob
gets
blessed
by
Apple
and
in
the
future,
when
a
mock
machine
is
trying
to
install
a
run
that
blob
it
either
has
additional
manifest
stubbled
on
top
of
that
binary
or
the
Mac
OS
itself
is
probably
Halleck,
hashing
it
and
sending
that
to
home.
A
Asking
is
this
okay
to
run
that's
my
understanding,
I'm,
not
a
Mac
user.
So,
however,
I
feel
that's
more
or
less
how
it
works,
and
that
problem
is
so
far.
It
was
optional.
However,
in
Mac
OS
Catalina
it
became
a
mandatory.
So
there
that's
why
people
get
this
warning
that
Apple
can
not
check
it
for
malicious
software.
That
means
it's
not
like
notarized
and
I
sort
of
did
some
research
on
what
we
could
do
to
plug
an
authorization
into
existing.
A
Continuous
integration
infrastructure
we
already
use
for
releases
and
there
is
a
way
of
manually,
notarizing,
already
released
versions,
so
I
believe
we
could
try
that.
However,
I
was
not
able
to
track
who
is
the
owner
of
like
protocol
labs,
keys,
I,
believe
that's
more
or
less
where
we
are
with
this
right
now.
If
anyone
music
mike
has
more
anything
to
add
on
top
of
that,
I
would
appreciate
it.
B
Desktop,
the
icon
in
your
in
the
finder
and
you
double-click
on
it.
Then
it
pops
up
a
different
one.
It
says
like:
oh,
do
you
still
want
to
open
this,
but
if
you
try
and
open
it
from
like
using
spotlight
that
search,
then
it
just
goes.
Nope
can't
open
this.
You
need
to
update
it,
which
is
where
the
confusing
part
comes
in,
because
it's
the
latest
version.
It's
just
that.
What
Apple
means
is
you
need
to
get
a
notarized
version
of
it.
So.
A
B
Need
to
try
and
open
it
directly
from
the
finder
by
double-clicking
on
the
icon.
You
can't
open
it
like
from
the
disk
image
or
from
search
or
from
the
the
bar
at
the
bottom,
which
I
forget
what
they
call
it,
but
for
most
regular
people
you
can
turn
the
whole
thing
off
for
Catalina,
but
you
have
to
go
in
the
terminal
and
type
some
stuff.
It's
not
gonna
work
for
regular
humans
and
it
it's
not
exactly
clear
how
it
like
Mac
OS,
doesn't
make
it
clear.
C
I
think
that
the
only
thing
to
do
here
is
try
to
close
this
as
soon
as
possible
to
reduce
the
window
and
time
regular
people
who's
the
target,
witness
Desktop
non-technical
users,
let's
reduce
the
window
in
time
with
both
screens.
This
sounds
like
little.
You
have
it
most
of
the
way
there
automating.
It
would
be
great
if
you
know
I'm
sure
electric
could
probably
help
just
ask
electric
for
the
go.
Get
the
keys
to
the
Apple
account
I
want
to
tell
you
at
least
who
has
them.
C
A
C
A
Right,
I
only
have
one
additional
side
note
around
that
the
first
desktop
while
I
was
like
doing
regression.
Tests
I
noticed
that
drag-and-drop
uploads
in
into
web
UI
of
a
folder
so
like
multiple
files
in
a
directory
tree,
that's
been
broken,
not
in
not
only
in
this
release
but
also
in
previous
one.
So
I
did
not
like
block
release
due
to
that,
but
it's
a
problematic
space,
because
it's
I
think
there
are
multiple
bugs
around
that
and
also
the
product.
A
It's
the
only
thing
that
we
don't
have
end-to-end
tests
for
like
for
drag
and
drop
and
for
like
directory
uploads,
because
the
orchestration
API
is
for
puppet
puppeteer
like
the
api's
are
not
just
there.
We
test
multiple
files
on
the
flat
structure.
However,
if
you
like,
drag
and
want
to
upload,
drag
and
drag
and
drop
directory
tree,
we
did
not.
We
don't
have
a
test
for
that,
so
that
that's
that's
a
tricky
space
and
going
to
the
final
end
to
end
test.
Oh
gosh,
don't
do
that
to
me.
Oh.
A
Yeah
and
to
end
test
landed
in
Goa
PFS.
The
the
PR
in
Jai's
ipfs
is
green
I
believe
it's
not
March
to
Jace
ipfs
only
because
they
are
finalizing
the
refactor
stuff
and
probably
that
would
like
introduce
some
noise.
Maybe
we
need
to
tweak
this
a
little
bit,
but
yeah
as
I
said
and
problem,
is
that
the
dose
drag
and
drop
is
specific
to
electron
running
in
an
unmarked
and
there's
a
separate
bag,
I
believe
in
web
UI,
which
will
also
don't
have
tests
for
because
we
don't
have
orchestration
for
that.
This.
C
Might
be
something
where
we
had
a
whole
bunch
of
stuff
like
this
in
Firefox
that
we
just
had
manual
test
cases
set
up
for
and
then
we
just
had
a
web
page
where
people
could
go
and
check
whether
they
ran
those
manual
test
cases
on
each
one
of
the
tier
one
operating
systems
that
we
supported.
So
this
might
be
a
thing
where
we
can
actually
just
set
something
up
and
then
drop
it
and
ipfs
IRC
channel
on
freenode
be
like
new
bit
of
desktops
out.
C
A
C
Before
we
move
on
for
the
end
end
test
bit,
I
knows
actually
I
was
just
asking
about
whether
those
in
test
exercise
the
with
the
web
UI
in
absolute,
like
absence
of
a
deployment
channel
or
if
they
actually
run
electron.
I
know
we
talked
about
puppeteer
for
running
in
browser,
but
if,
if
we
can
because
I
knew,
we
have
CI
4
electron
tests
right.
C
A
We
have
entered
and
tests
in
ipfs
desktop
repo,
but
those
tests
are
specific
to
like
GUI
a
big
desktop
application.
So
it's
like
you
started.
You
confirmed
like
the
window
when
you
click
on
the
icon.
You
confirm
the
window
with
a
blue
eye,
shone
and
stuff
like
that,
and
we
don't
run
the
query,
UI
and
plugging
in
those
web.
A
web
UI
and
20s
into
this
is
tricky
because
we
would
not
be
testing
web
UI
running
in
electron.
We
would
be
testing
it
over
HTTP
API
right.
So
it's.
C
D
C
A
Yeah,
that's
that's
the
problem
we
like
right
now
we
are
using
github
for
like
the
distribution,
we
could
switch
to
self
hosted
solution
which
could
in
turn,
give
us
a
better
insight,
but
yeah.
Then
we
have
to
do
anyway
for
other
reasons.
For
yes
but
that's
like
yet
another
thing
that
would
be
on
a
plate
of
that
feature:
material,
new
hack,
yeah,
exactly.
C
A
Cash
next
registering
URI,
and
it's
also
like
a
PSA
from
me,
just
indicate
that
there's
some
going
work
on
preparing
the
docs
and.
A
A
A
Pages
and
separate
registration
processes,
but
yeah
I
I,
agree,
and
it
will
probably
is
some
adoption
in
in
in
some
places
where
they
are
already
using
your
ends
for
identifying
content
like
semantic
web
like
solutions.
So
it's
good
to
give
people
that
option.
I
believe
I
touch
it
on
this.
One
I'll
link
issue
on
the
notes.
A
So
I
start
cuz,
I
wrote
for
so
the
p0
for
me
in
this
quarter
is
delivering
some
domain
gateways
to
ipfs
ecosystem,
and
that
means
I,
on
my
in
gateways
being
natively
supported
by
go
active
as
j
sacrifice,
activist
companion,
updating
dogs
making,
sure
the
all
tests
are
in
place
figuring
out
the
migration
path
like
representing
existing
dogs,
guidelines
and
stuff.
Like
that,
so
that's
a
p0.
This
needs
to
happen.
This
quarter
and
remaining
ones
are
t1
and
t2
s--.
A
Instead
provide
end-to-end
answers
for
people
who
want
to
run
their
own
right.
Now,
it's
either
scattered
around
different
places
or
not
existing
at
all,
and
then
the
final
one
is
consolidate.
All
the
specs
related
to
addressing
this
is
like
also
probably
will
be
related,
like
partially
partially
will
be
done
as
a
part
of
this
URI
registration
scheme.
Ideally,
we
would
clean
up
our
specs
before
like
submitting.
That
would
be
much
better
if
we
linked
to
the
one
place
and
that's
more
or
less
from
me.
C
You
can
look
real,
quick
and
I
have
a
couple
of
questions
before
we
move
forward.
I
wonder
if
the
updating,
the
specs,
who
are
the
stakeholders
for
updated,
addressing
specs,
is
that
for
browser
implementers
is
that
for
is
that
for
specific
work
or
just
making?
What
ongoing
work
that
you
know
needs
to
happen
at
some
point.
A
However,
like
people
been
using
those
specs
which
were
designed
for
web
browsers
in
other
places,
for
example
like
et
rien
immaterial
Microsystems,
some
of
their
specs
are
referring
our
specs
for
web
browsers
and
it
gets
messy
pretty
fast
and
also
we've
been
revisiting
our
approaches
over
time
due
to
lack
of
original
subdomains
long
story,
short
I,
think
it
probably
just
give
us
addressing
not
ipfs
addressing
in
web
browsers.
It
needs
to
be
like
one
document
and
there
could
be
like
a
section.
The
this
type
of
addressing
is
usually
seen
in
web
browsers,
but
overall
it.
A
It
just
needs
to
be
like
a
generic
addressing
thing.
So
the
work
here
is
to
like
just
take
everything
into
one
document
and
then
and
then
move
it
to
the
actual
specs
repo
and
then
in
that
PR.
All
the
stakeholders
from
like
go
ideas.
Jessica
first,
like
like
leads
from
of
those
projects,
would
know
what
are
possible
stakeholders
on
the
user
base
yeah,
and
then
we
would
gather
feedback
in
that
single
peer,
because
otherwise
I
don't
see
how
we
can
like
time.
This.
A
C
A
C
A
E
Alright,
so,
regarding
the
first
one
on
the
spreadsheet,
the
appears
RV
to
basically,
we
started
to
make
some
improvements
on
this
during
the
famous
a
single
factor.
Basically,
during
the
refactor,
we
renamed
old
pearbook
into
a
pure
start
to
match
what
go
ahead
before,
and
we
also
moved
that
into
the
gesso
PHP
code
base
and
started
adding
some
new
functionalities.
E
But
now,
as
this
was
kind
of
the
groundwork
to
reach
the
peer
star
v2,
which
will
probably
have
persistence,
we
might
also
consider
rewriting
among
other
things,
but
for
this
I
will
also
need
to
push
this
back
forward
as
the
note
in
the
spreadsheet.
Basically,
there
is
currently
issue
with
some
discussions
around
this
with
also
the
the
go
team,
as
the
go
team
will
also
go
to
implement.
E
Basically,
I
already
also
started
working
on
this
in
the
key
shine.
Basically,
we
want
to
move
it
under
the
code
base
in
the
API,
with
supporting
of
the
peer
IDs
persistence
from
the
piercer
v2.
So,
basically
now
the
lipid
petition
is
used
by
Jessup
FS,
but
it's
completely
external
to
Jessup
HP,
in
a
way
that
it's
just
a
professor
controls
and
does
everything
in
the
kitchen
and
basically
it
is
called
to
limit
vacation.
E
Basically,
we
aim
to
sunset
the
websocket
star,
which
we
already
didn't
refactor
to
the
cigarette
stuff.
So
basically
we
need
an
alternative
to
the
WebRTC
star
transport
as
soon
as
possible,
and
it's
the
Stardust
will
be
this
piece
and
then
we
will
try
to
do
other
stuff
like
Jacob
will
will
be
working
on,
is
routed
signal
and
that's
it
I.
C
E
We
are
not
doing
that,
but
the
goal
would
be
to
do
something
like
that.
Yes,
because
we
ideally,
we
would
probably
want
to
persist.
Beer
addresses
and
eventually
get
White's,
for
which
were
the
beers
that
we
were
connected
before
that
were
more
important
for
us
and
try
to
establish
metrics
that
make
us
able
to
initially
discover
more
beers
and
the
beers
that
are
really
meaningful
for
us
and.
F
C
F
We
didn't
significantly
update
that
when
we
were
doing
the
refactor
is
just
enough
to
get
it
working
with
the
refactor,
so
this
will
do
an
overhaul
and
hopefully
make
that
more
efficient
as
well.
The
big
thing
here
is
getting
us
direct
browser
to
browser
connections
over
any
intermediary
peer,
so
an
in
theory.
As
long
as
you
are
mutually
connected
to
appear,
you
would
be
able
to
use
them
as
a
signaler.
So
in
theory,
three
browser
nodes
could
browser
node
cause
you'd.
Another
browser
note
that
they're
mutually
connected
to
to
connect
to
one
another.
A
C
All
right,
thank
you.
So
much
I
really
appreciate
you
all
taking
the
time
to
write
these
up
and
put
these
in
here
and
be
patient
with
my
many
questions
about
how
this
stuff
works
and
I'm
super
excited
to
see
more
progress
on
our
connectivity,
stuff
I
think
that
connectivity
map
to
Lionel's
can
really
help.
We
just
had
a
conversation
with
with
Microsoft
yesterday
about
their
use
of
JSI
PFS,
and
there
really
is
just
a
lot
of
kind
of
big
confusion
around
which
connection
types
are
used
in
their
what
situations
and
why?
C
What
our
defaults
mean,
how
to
optimize,
how
to
optimize
for
specific
types
of
clients
and
connection
types.
So
this
works
to
both
like
collapse
and
and
make
more
cohesive
how
what
the
connection
is
and
its
boundaries
between
I
profess
says.
Yes,
the
p2p
will
help,
but
also
the
work
that
you're
doing
light
all
around
what
what
the
the
map
of
what
those
connection
types
are
when
they're
used
how
they're
used
under
what
situations?
This
really
helps
as
well
like
they
were
like.
Sometimes
the
connection
is
faster.
We
don't
know
why,
and
sometimes
it's
slow.
C
We
don't
know
why,
and
they
don't
even
know
what
what
route
was
used.
If
somebody
asks
for
a
CID
from
the
Gateway
that
they
got
from
the
Bitcoin
blockchain
and
they
asked
the
Gateway
but
they're
reading
notes
they're,
like
sometimes
it
works
instantly
and
other
times
it
takes
these,
but
and-
and
we
have
answers
to
that
if
we
know
how
all
that
stuff
works,
but
for
Saudis
just
an
I
profess
user.
This
deploying
some
nodes.
They
don't
have
great
visibility
to
all
that
stuff,
yeah
and.
C
C
But
at
this
point
you
know
we,
you
know,
especially
in
this
group
I'm,
trusting
that
you
all
know
what
the
most
important
thing
that
you
have
talked
and
in
this
meeting
or
other
places
around
making
sure
that
that
the
this
priority
order
is
right
and
I.
Think
from
the
work
that
you
and
I
did
Lydell
with
Hugo
last
year
or
from
a
browsers
perspective.
C
We
like
kind
of
stack,
ranked
every
possible
thing
that
we
knew
we
wanted
to
do
with
regard
to
browsers
and
all
of
the
connectivity
stuff
bumped
up
to
the
top,
which
is
part
of
what
prompted
this
closer
alignment
between
a
slim,
p2p
and
and
the
browser
work
so
I
think
all
this
seems
to
align
directly
with
what
what
we
did
in
that
prioritization
exercise
and
whenever
that
was
last
fall.
So
so
that
seems
generally
right
and
then
I
know
part
of
it.
You
know,
I
brought
this
up
with
the
IP
us
leads
meeting.
C
Yesterday,
too,
is
that
we
have
to
do
that
with
an
understanding
that
Jacob
Moscow
also
have
other
things
that
might
trade
off
against
it
for
their
limb
p2p
work
that
might
be
higher
priority
than
our
longer-term
browser
stuff.
This
is
a
ten
accelerating
some
of
that
stuff,
but
also
with
an
understanding
that
you
also
have
loyalty
into
a
whole
different
area
of
consumers.
Let
p2p
stack
I.
C
Awesome
so
I
think
you
like
what
we
talked
about
before
earlier
this
week
about
just
marking
your
my
current
marking
the
priorities.
If
it's
p
0,
then
we
know
to
expect
it
from
you
this
quarter,
if
it's
not
p
0,
and
then
we
know
that
it's
going
to
trade
off
against
other
stuff
and
and
and
that
it's
a
maybe
for
this
quarter,
yeah.
F
C
We
will
talk
more
as
a
group
about
how
wait
where,
where
we
share
this
information
and
how
we
kind
of
formalize
this
as
a
special
interest
groups
and
special
interest
groups,
are
still
kind
of
new
I
think
I've
merged
part
way
through
last
year,
as
a
alternative
form
of
working
group
that,
if
you
have
any
input
in
thoughts
on
on
that
stuff,
let
me
know
I
also
added
that
last
agenda
item
Lyle
and
I
met
with
a
Galia.
We
talked
about
kind
of
like
what
the
long
slow
pathway
to
Native
chromium
plantation
would
be.
C
They
do
their
consultancy
that
they
do
work
and
they
have
commit
rights
on
WebKit,
HECO
and
chromium
repos.
They
do
a
lot
of
stuff
around
the
bedding
for
people,
they've
built
features
like
CSS
grid
and
added
them
to
browsers,
so
the
and
and
math
ml
things
like
that.
So
we're
talking
with
them
about
what
some
type
of
longer-term
project
would
look
like,
but
in
the
shorter
term
a
smaller
scope
project
we
looked
at
was
well.
C
If
that's
something
that
maybe
we
just
want
to
talk
about
it
at
teen
week
to
wear
together
for
an
hour
if
you're,
gonna
spin
up
at
some
point,
a
draft
of
that
for
I
think
is:
if
we
even
just
get
a
couple
of
paragraphs
like
a
one-page
draft
of
that
and
get
it
into
a
Gallia's
hands
and
that'll
be
enough
for
them
to
start
estimating
what
the
cost
would
be.
We
don't
we
want
to
the
point
there
is
to
avoid
doing
that
work
and
have
them
do
that
work.
C
So
if
we
could
just
spec
out
either
an
API
or
point
to
previous
examples
and
what
the
outcomes
that
we
want
to
be
are,
and
specifically
in
which
browser
Nick
chromium
is
probably
first,
is
what
we
discussed
and
just
ignore
the
others
for
now,
because
the
the
browsers
that
were
work
with
most
closely
that
wants
to
be
able
to
implement
something
like
this
for
ipfs,
are
all
coming
based.
It's
mine,
yep,.
B
A
C
Sounds
great
I
think
targeted
grant
is
probably
best,
because
this
isn't
something
that
we
want.
Some
the
the
ability
to
have
having
commit
rights
and
already
meeting
anger
integrated
in
the
rendering
engine
communities
is
the
superpower
and
that
expertise
and
experience
of
somebody
like
regalia,
so
I,
don't
think
we
want
Rando
proposals
for
something
like
this,
and
this
really
isn't
going
to
be
a
targeted
grant.
Just
for
the.
A
Context,
if
someone's
watching
this
and
it's
wondering
what
our
dev
grants
there
is
a
cliff
I,
slash
their
grants,
repo,
it's
an
experimental
grant
platform
where
we
state
problems
like
ipfs
project
states,
problems
which
could
be
solved
and
you
could
apply
for
solving
those
problems
or
you
could
there's
a
mechanism
for
open
grounds.
And
now
we
are
experimenting
with
targeted
grants
where
you
can
propose
your
own
grant
I,
also
like
smaller
chunks,
like
bounties
adoption
micro
grants.
If
you
want
to
include
like
I,
think
I
give
us
support
for
your
into
your
project.
C
A
C
Might
be
a
good
team
week,
activity
is
everybody's,
got
like
I
know,
I
have
a
huge
list
of
ipfs
backburner
I
just
had
a
few
some
weeks.
I
can
push
out
some
of
these
things
then
just
put
a
file
them
all
as
adoption
micro
grants
like
stuff
that
people
get
four
hundred
thousand
bucks
or
take
on
or
bounties
or
whatever
I'm.
A
Pretty
sure
we
have
like
an
issues
which
are
detailed
enough
to
spend
some
time,
then
move
them
to
a
template
of
a
grant.
Maybe
someone
will
just
just
live
yep
I
believe
we
are
at
the
end
of
the
agenda.
We
are
getting
better
and
better
at
this.
Are
there
any
ad
hoc
topics
anyone
wants
to
discuss
questions
concerns.
D
Hi
hi
everyone,
so
my
name
is
Homer.
Dean
I'm
from
Moxie
I
recently
got
employed
by
Moxie
as
a
TPM
to
work
with
with
protocol.
My
background
is
full-stack
developer
for
almost
four
years
and
I
decided
to
go
with
the
career
of
project
manager,
because
I
love
the
interaction
between
people
and
communication
between
teams
and
and
think
and
try
to
help
the
team
members
improve
their
work
and
see
if
what
we
are
developing
makes
sense
in
the
user
perspective.
D
So
that's
it-
and
this
is
a
bigger
challenge
for
me,
because
it's
the
first
time
that
I
work
as
a
project
manager
for
a
remote
team,
a
complete
remote
team.
So
it
will
be
a
big
challenge
for
me,
but
I'm
really
excited
for
new
Disney
opportunity,
and
so
this
is
why
I'm
I'm
here
in
this
call
is
because
I'm
I'm
trying
to
learn
as
much
as
I
can
in
these
first
weeks.