►
From YouTube: IPFS Web and GUI Biweekly 2020-06-30
Description
Meeting notes: https://github.com/ipfs/team-mgmt/pull/1165
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
Okay,
it's
recording
welcome
to
GUI
and
in
web
browsers,
bi-weekly
call
for
the
last
of
June
2020
yep.
We
got
regular
folks.
We
got
new
old
folk,
so
it's
interesting
week.
Oli
is
our
note-taker
and
I've.
Put
some
items
on
the
agenda
and
I
will
quickly
jump
straight
to
that
feel
free
to
add
your
own
agenda
items
while
I
am
struggling
to
share
my
screen.
B
C
A
B
A
All
right,
so
it's
the
end
and
the
beginning
of
the
quarter,
and
we
are
now
a
working
group.
So,
as
each
working
group
we
prepared
some
okie
RS,
which
are
objectives
and
key
results.
We
have
limited
bandwidth
and
some
cross
working
group
priorities
which
we
had
to
include
in
our
planning.
So
there
are
two
main
topics
for
Q:
free
one
is
integrating
pinning
services
into
both
our
web
ecosystem
and
our
GUI
graphical
interfaces,
namely
IKEA
fest
desktop
and
web
UI.
A
And
then,
even
though
we
are
in
a
new
working
group
again,
we
had
a
lot
of
ongoing
collabs
and
grants
and
work
that
needs
to
continue
and
that's
a
result
of
prioritization.
So
getting
services
will
be
something
that
we
will
add
to
our
ecosystem
in
q3,
and
this
working
group
will
focus
on
implementing
user
interfaces
and
helping
to
orchestrate
entire
API
spec
to
be
finalized
and
agreed
across
all
stakeholders
and
those
stakeholders
will
be
not
just
pinning
services
themselves
but
our
core
implementations.
A
We
will
provide
lists
of
requirements
and
quality
assurance,
but
the
end
result
is
having
pinning
services
in
web
UI
and
ipfs
desktop
integrated
and
working
with,
at
least
to
collapse,
depending
how
our
partners
timelines.
We
will
have
two
or
more
pinning
services
ready
to
be
used
by
our
users,
but
everyone
will
be
capable
of
implementing
the
vendor
agnostic
pinning
service
api.
So
we
expect
that
system
growing
and
there
will
be
always
option
to
add
your
custom
pinning
service.
A
So,
even
though
it's
not
like
listed
on
those
on
the
list
of
default,
a
pinning
services,
you
will
always
be
able
to
specify
your
own
and
we
as
a
part
of
that
work.
We've
extracted
a
bunch
of
iroquois
expertise
on
web
performance
and
low
level
optimizations.
So
it's
under
maintaining
and
improving
as
bandwidth
permits.
We
I
will
ship
those
libraries
for
sharing
IP.
First
note
across
browsing
context.
However,
from
that
work,
we've
extracted
p0
to
improve
import
of
huge
files
using
web
UI.
A
Everything
else
is
on
the
best
effort
basis.
We
may
prioritize
things
related
to
a
long
backlog
of
UX
related
issues,
namely
because
it's
sort
of
related
to
supporting
falcon
lounge
and
pinning
services
as
well.
Our
GUI
applications
are
often
the
first
thing
that
people
see
when
they
Google
ipfs
and
they
want
to
try
it
so,
even
though
it's
it
might
not
sound
very
it
may
sound
vague,
but
it's
very
important
to
remove
low-level
hanging
fruits.
A
All
the
paper
cards
in
the
onboarding
of
new
users,
we
expect
an
influx
of
various
types
of
new
users
relate
in
flux.
People
will
be
related
to
integration
of
being
services,
but
also
ficon
large.
So
that's
something
we'll
probably
prioritize
here.
It's
a
p2
right
now,
but
we'll
increase
it
for
everything
else.
There
are
links
to
very
detailed
issues
on
this
column.
I'll,
probably
stop
talking
now,
if
I
missed
anything
Jessica
feel
free
to
elaborate.
You.
B
Might
as
well
might
as
well
put
the
link
in
that
issue
triage
to
ours
and
hub
board,
because
then
folks
can
can
look
through
that
and
then
the
other
note
on
that
being
like
so
super
vague
is
a
lot
of
this
is
really
just
gonna
base
on
triaging
the
highest
priority
things
in
that
backlog,
with
the
caveat
on
who
is
available,
skill
set
wise
to
be
able
to
do
that
work.
So
you
know
it
may
not
be
a
complete
priority
order.
It's
just
based
on
a
combination
of
priorities
and
availability
of
skills.
B
A
Yeah,
that's
a
good
idea.
I've
had
that
link
to
then
cut
board,
it's
not
a
link,
but
I
will
make
it
a
link
at
some
point
when
I
figure
it
out
Google
Docs
yeah.
So
that's
our
cue
ours.
Those
are
like
not
100%
finalized,
but
that's
the
general
direction
in
services,
p0,
break
integration,
p0
and
then
sharing
nodes
across
browser
context
and
the
backlog
will
be
around
p1.
If.
A
Speaking
of
meaning
services,
so
the
next
item
is
pinning
services
API
spec,
it's
something
that
I
kicked
off
quite
recently,
so
for
web
UI
to
integrate
pinning
services
into
our
interview
user
interfaces.
We
need
to
agree
on
how
that
pinning
will
happen.
That's
something
between
us
and
go
ipfs
and
jess
ipfs.
However,
the
backend
API
should
be
vendor
agnostic,
so
that
final
api,
where
you
send
the
ID
of
the
items
you
want
to,
pin
it
right
now
each
pinning
service
provide
their
own
API,
but
we
want
to
agree
on
a
universal
pinning
service.
A
A
A
A
So
we
started
discussion
in
issues
feel
free
to
participate,
feel
free
to
ask
questions
the
sooner
the
better.
We
want
this
to
the
surface
of
this
API
to
be
very,
very
small,
and
we
don't
want
to
be
too
detailed
when
it
comes
to
access
controls,
and
we
don't
want
to
force
pinning
services
to
implement
too
much.
So
it
will
be
very,
very
small,
surface,
very
small
API
that
we
all
can
agree
on,
and
then
that
will
be
like
a.
A
C
B
You
asked
Ali
I
sent.
You
I
sent
you
off
channel
on
p.m.
cuz.
Everybody
else
has
been
through
these,
but
we
can
also
walk
through
them.
Do
you
you
have
them
handy
Lytle?
Oh
no,.
B
Like
a
cooking
show,
here's
what
we
made
earlier
so
there's
there's
two
flows.
That's
one
is
in
the
settings
screen
the
other
ones
of
the
file
screen.
These
were
actually
iterated
on
and
there
were
certain
degree
in
the
pinning
summit
there
they're
real
straightforward,
though
real
real,
straightforward.
B
A
A
B
D
B
Oh
cool,
all
right,
so
this
would
be
the
settings
where
this
lives
in
settings.
As
you
see,
it's
just
another
pane
in
the
settings
explains
a
little
bit
about
pending
services
our
since
this
will
be
the
first
time
that
anybody
who
doesn't
know
this
exists
will
encounter
it.
This
will
be
the
first
point
of
contact,
so
we
want
to
give
them
a
little
bit
more
explanation
and
then
also,
obviously,
a
link
in
the
docs
that
flows
out
that
a
little
bit
harder.
B
Everybody
is
always
gonna
have
local,
pinning,
obviously,
let's
say
default,
and
then
you
can
add
more
so
you
add
services,
it's
pretty
simple.
This
is
sort
of
an
initial
state,
while
we've
only
got
a
few
pending
service
providers
on
this
boat,
so
it's
a
little
bit
like
a
logo
parade
right
now.
This
is
sort
of
an
initial
state
to
say
you
hear
the
first
couple
of
collabs
at
some
point
when
we
have
a
bazillion
of
these,
that
will
change
a
little
bit
the
the
actual
look
and
feel
of
this
logic.
B
It
might
end
up
being
a
searchable
list
or
something
like
this
you've
also
got
the
don't
see
your
pending,
a
service
provider.
Add
a
custom.
One
show
you
that
in
a
sec,
but
real
simple,
just
here's
the
service,
you
can
give
it
a
nickname
cuz,
you
might
have
say
two,
and
if
your
accounts,
you
might
call
it
zero-one
and
pura
2
or
whatever
work
and
home
or
who
even
knows
so,
you
can
give
it
a
nickname.
B
You
give
it
your
API
key,
and
then
this
guy
here
this
is
sort
of
dependent
upon
the
functionality
that
we
launched
with,
but
in
an
ideal
state.
You'd
have
some
auto
upload
parameters
right
here.
That
would
give
you
I'll,
show
you
those
in
a
sec,
also
an
escapee
to
go
to
the
pending
services
website
if
they
want
to
offer
more
one-on-one
help
specific
to
their
service.
If
you
add
a
custom
one,
it's
virtually
the
same
thing,
except
that
you
need
to
give
it
an
API
endpoint
as
well.
B
This
is
what
it
looks
like
with
a
couple
of
pinning
services
added
notice.
So
this
is.
This
is
an
example
of
all
the
permutations
of
the
auto
upload
rules.
It
would
either
be
and
again
this
this
may
or
may
not
happen
depending
on
your
pacing
and
what
users
want,
but
this
is
sort
of
a
an
ideal
situation.
Auto
upload
would
be
all
the
files,
it
might
be.
B
None
of
your
files-
or
it
might
just
be
things
that
you
pinned
to
your
local
node
only
you
can
edit
a
service
if
you
hit
the
edit
button,
it
goes
back
to
the
config
modal
I
just
showed
you,
you
can
visit
the
Services
website
or
you
can
remove
it.
Removal
and
changes
you
can.
You
can
change
the
rules
if
you
go
into
the
config
and
you
change
from
one
set
of
rules
to
the
other,
but
we
have
to
be
very
careful
by
the
language
that
you
use.
B
Here's
an
idea
saying
what,
if
you,
what
if
you
went
from
everything
to
just
pins
or
the
other
way
around,
so
if
you've
gone
from
nothing
so
say
you
went
from
nothing
to
pins.
We
want
to
ask
you
alright.
Do
you
want
to
do
you
want
to
only
pin
things
you
only
want
to
pin
do
in
Fira
or
textile
things
that
you
pin
in
the
future
to
your
local
node,
or
do
you
want
to
upload
all
of
your
local
pins?
B
Do
you
want
us
to
upload
everything
now
or
just
everything
that
you
add
in
the
future?
Yes,
so
these
are
a
couple
of
these
exceptions,
including,
if
you
disable
and
then
also
to
make
it
super
clear.
If
you
remove
the
painting
integration
entirely
from
from
your
your
desktop
or
web
UI,
you
know
we
want
to
say
removing
this
pinning
service
isn't
going
to
take
the
files
off
that
service.
You
just
won't
have
that
service
in
your
dashboard
anymore.
B
I
believe-
that's
probably
that's
probably
good
enough
for
now,
oh
and
then
just
some
status
confirmations,
the
other
half
of
this,
which
is
currently
blocked
by
the
zoom
sharing
thing
at
the
top
of
my
screen.
Let's
try
this
okay
cool
files
screen
you've
now
got
a
pin
status
column
here,
that's
going
to
tell
you:
is
it
locally
pinned
or
is
it
locally
and
cloud
pen?
There
may
be
circumstances
under
which
it
is
only
cloud
pin
such
as
you
disabled,
an
integration.
B
B
Ditto
here
for
multiple
select
files-
and
forgive
me,
I-
haven't
seen,
use
it
a
little
while
I'm
not
talking
through
these.
It's
completely
fluency
so
say
sis
a
both
from
either
this
multi
select
scenario
or
right-click
single
select
scenario,
and
you
hit
that
set
pinning
you
get
a
modal
that'll
pop
up
that
says,
select
the
services
with
which
you
wish
to
pin
these
files
so
say
this
person's,
like
a
superpower
user,
and
they
have
six
pinning
services,
including
one
that
they
made
themselves.
B
B
If
you
don't
have
that
level
of
rules,
if
it's
just
manual
pinning
or
if
it's
just
automatic,
pinning
according
to
rules.
This
is
real
easy.
This
just
goes
back
to
the
pin
on
Pinson
REO
and
then
for
visibility.
Since
you
can't
tell
by
using
that
right-click
menu
and
invoking
the
custom
pinning
rules,
we
need
to
let
somebody
know
which
services
it
is
pin
to.
So
maybe
you
had
like
a
global
rule
and
then
you
say
I'm
one
service
and
you
have
nothing
on
another.
B
So
you
might
end
up
with
this
is
pin
to
your
local
node
and
it's
pin
to
pin
Jana
and
textile,
but
it's
not
pin
to
a
tournament
in
fira.
You
would
learn
that
by
clicking
the
pin
status
in
there
in
the
the
pin
status
column
and
then
again,
some
confirmation
messages
files
can
successfully-
or
this
is
this-
is
gonna,
be
sort
of
a
very
it's.
It's
a
fairly
vague
error,
but
it's
gonna
account
for
a
lot.
It's
good,
because
most
of
the
things
that
are
going
to
go
wrong
is
there's
something
wrong
with
your
config.
E
B
I
mean
that's
a
good,
that's
a
good
question.
We
we
have
not
flushed
that
out
yet
the
question
being
whether
the
standard
you're
not
online
messaging,
that
you
get
from
the
rest
of
desktop
and
web
UI.
Is
that
going
to
be
enough
or
do
we
need
to
say
something
specific
to
you
hey?
We
can't
query
these
web
services
to
get
to
in
fear
or
whoever
it's.
E
A
Good
question
be
cognizant
that
those
mock-ups
were
created
before
we
start
a
discussion
about
scoping
between
well,
how
much
stuff
will
happen
in
web
UI
and
how
much
stuff
will
be
done
in
going
FS,
and
now
we've
agreed
that
the
actual
execution
of
the
pinning
at
the
remote
service
will
happen
in
go
ipfs.
So
it's
a
very
valid
question
that
you've
asked
what
happens
if,
like
goid
EFS
is
not
able
to
reach
the
remote
service,
I
will
expect.
A
Maybe
there
will
be
some
flexible
or
cache
of
pending
ending
actions,
but
there
will
be
also
the
pin
status
column
it
will.
Web
UI
will
ask
go
IDF
s
about
the
status
and
there
may
be
a
status
of
like
pending,
where
you
you
don't
know
if
it's
like
applied
to
remotely.
Yet
it's
like
a
super
super
effect
right
now,
we'll
talk
with
Jake
and
current
limitations.
All
the
details
in
the
following
weeks,
but
yeah
there.
B
E
Remarks
today
or
thought
I
had
was
about
the
prompt,
where
you
see
upload,
all
of
them
now
upload,
just
a
pin
snow
or
it
might
be
a
little
like
some
of
those
decisions,
sometimes
are
hard
to
make
while
serving
a
service.
So
I
was
wondering,
maybe
in
the
file
of
cui,
we
could
add
a
I
know,
line
or
something
insert
to
say
upload
all
the
existing
pins
or
based
on
options.
A
B
This
is
probably
a
good
time.
Yeah
I
mean
we're
we're
still
a
little
bit
unsure
time
frame,
wise
and
functionality
rise
exactly
how
granular,
if
at
all,
we
can
get
with
that
rulemaking,
it
might
just
be
an
everything
or
nothing
right
out
of
the
box,
but
we
are.
We
are
answering.
Oh,
and
some
of
these
are
mandatory
questions,
but
I
just
got
the
OK
to
turn
this
survey
loose
today,
which
is
also
on
the
agenda,
but
just
talking
about
hate,
giving
a
real
answer.
I
don't
live
for.
B
My
I
can
delete
this
one,
but
but
we're
talking
about
potential
pinning
features.
So
we
are,
we
are
asking:
how
important
is
it
to
manually?
Pin
a
file
whoops
come
back
type
form
automatically,
pin
everything.
That's
on
your
local
node,
automatically,
pin
everything!
That's
in
your
local
nodes,
em
FS.
B
Customize
manual
or
automatic
pinning
rules
on
a
per
service
basis
use
a
private
service,
and
you
know
would
this
change
your
life?
Also,
how
important
would
it
you
be
for
this
functionality
to
be
available
from
the
command
line?
So
definitely
we
want
to.
We
want
to
get
a
bead
on
people's
opinion
of
these
functionalities
and
their
importance
in
general.
A
C
C
Just
just
that,
like
the
level
of
granularity,
is
most
radical,
but
also
terrifying,
yeah
yeah.
This
subtree
is
pinned
to
three
of
five
services
that
subtree
is
pin
to
one
of
five
pinning
services
just
to
be
able
to
like
render
the
status
of
each
file
like
doing
call-outs
to
multiple
pinning
services
per.
B
B
A
Just
to
just
clarify
on
on
the
complexity,
we
have
like
a
working
document
where
we
try
to
identify,
translate
the
changes
from
the
front
from
the
web
UI
trying
to
translate
that
to
low-level
requirements
in
both
web
UI
and
Co
ipfs
backend,
and
we
identified
some
scopes
where
different
stuff
happens
in
a
different
place
and
we've
put
a
line
in
the
Sun
here
so
effectively.
It
may
be
here
where
we
only
have
the
manual
pinning
policy
that
out
of
my
automatic
upload
column,
that's
where
most
of
unknowns
are
right.
A
Now
the
survey
that
Jessica
a
shirt
will
give
us
data
to
know.
Is
it
worthwhile
for
us
to
invest
time
in
basically
implementing
that
column
for
MVP?
It's
not
like
we,
we
won't
have
that.
We
may
not
have
that
in
the
first
version.
We
may
have
something
much
simpler,
where
you
only
manually
mark
file
or
directory'
to
be
pinned
to
a
specific
pinning
service
and
that's
it,
and
that
would
be
already
super
useful
for
MVP
pinning
everything
in
MF
s
may
be
quite
easy.
A
So
that's
why
we've
put
a
line
after
that,
but
it's
the
line
on
the
sand
and
we'll
finalize
the
decision
after
we
got
survey
results,
yeah
I,
totally
agree.
We
given
the
time
frame,
we
probably
won't
be
able
to
implement
all
the
screens
that
Jessica
shared,
but
that's
that's.
Something
may
be
at
some
point
available.
It's
not
just
yeah
yeah.
B
This
is
mainly
just
an
effort
to
be
able
to
build
in
the
affordances
for
future
functionality,
conceptually
understanding
getting
remote
pending
services
in
desktop
and
web
UI
is
like
kind
of
a
stretch
anyway,
and
so
to
go
and
do
that
and
then
I
have
to
change
the
UI
on
folks.
Six
months
in
would've
just
been
sad.
E
So
I
remember
in
the
previous
conversations
there
were
some
issues
that
we've
been
discussing
about
the
card
interface
and
stuff,
and
there
was
a
as
I
get.
We
tend
to
ship
something
and
then
we
try
to
improve.
It
is
improvement
somewhere
in
the
pipeline
to
and
how
the
process
will
look
like.
If
it
is
this
unclear
to
me,
given
your
smells
I'm
guessing
the
answer.
A
A
Bye-Bye
go
a
PFS,
so
that's
more
or
less
not
at
this,
like
the
final
decision
or
of
what's
available,
it's
not
up
to
us,
we
will
effectively
implement
what's
exposed
in
the
HTTP
API,
and
the
final
question
would
be
where
those
additional
like
cleaning
services
are
on
the
road
map
of
go
ipfs.
Sorry,
maybe
I'll
refrain.
My
question.
E
So
my
question
would
mean:
are
there
opportunities
to
rethink
the
user
experience
of
this
in
the
future,
and
if
there
is
how
that
process
looks
like
of
trying
to
improve
it
from
the
mock-ups
that
we
were
given
or
or
like?
Is
that
saying
they're
all
is
that
kind
of
being
pipeline?
Is
it
something
that
needs
to
be
I
just.
A
We
are
not
like
anchoring
us,
or
we
are
not
anchoring
the
user
interface
around
the
code
that
we
wrote
in
the
user
land.
There
would
be
a
bit
more
generic
api,
exposing
the
HTTP
api,
and
that
means
it
will
be
easier
if
we
decide
to
change
the
user
interface
or
the
user
experiences,
it
will
be
easier
if
we
now
that
we
will
have
this
generic
API,
then
if
we
like
tightly
coupled
everything
in
web
UI
that
just
like
my
subjective
opinion,
Jessica.
B
E
Because
I
think
that
they
call
with
Molly,
we
all
had
some
ideas,
how
things
could
be
better
and
the
feedback
I
got
that.
Well,
we
want
to
do
something
really
quick
and
then,
as
a
start-up,
we're
gonna
eat
right
over
it
all
right
over
so
I'm
trying
to
understand
how
this
iteration
over
is
happening.
Innovation
and.
B
E
B
E
One
of
the
examples
I
can
remember
so
one
things
that
I
brought
up
during
that
conversation
is
instead
of
showing
the
cloud
with
the
P
in
there
and
then
clicking
add
robot
it
to
see
that
dialogue
with
all
the
things
that
you've
pinned
we
were
I
suggest.
Maybe
we
can
have
something
like
what
Google
Docs
is
doing
where
at
the
top,
you
see
kind
of
will
I
construct
to
see
who
you
shared
the
document
with
or
who
was
on
the
document.
E
E
I'm
trying
to
find
where
oh
yeah,
yes,
so
I
proposed
a
meeting
at
the
current
limitations
or
asked
for
the
design
review
meeting
and
I'll
try
to
schedule,
sometimes
this
week
or
actually,
depending
on
people's
availability.
Mostly,
there
needs
to
be
some
decisions
made
around
how
we
go
about
it.
Well,
one
option
would
be
to
do
everything
in
the
browsers,
but
that
would
mean
we
will
be
doing
more
six
or
the
other
option
would
be
to
slightly
modify
the
HTTP
API
in
non
backwards
compatible
way,
but
that
would
endure.
E
It
was
to
just
use
Web
API,
rather
than
try
to
do
the
custom
stuff
sudden
problems.
Few
other
things
in
the
meantime,
I
started
working
on
a
patch
that
assumes
that
we
were
not
gonna,
be
doing
the
HTTP
API
changes,
but
if
you
do
send
it
like
that
will
be
just
simplified,
so
I'm
working
on
a
couple
of
patches.
Actually,
so
the
problem
is
ipfs,
add
functionality
in
Jess,
IPS
does
bunch
of
normalizations
and
through
those
normalization,
some
of
the
car
abilities
are
lost.
So
we
end
up
buffering
because
of
that.
E
However,
there's
also
peculiarity
or
I
could
have
said
where
it
takes
I
think
iterator,
reversing
iterators,
which
creates
this
double
I,
think
loop,
that
is
hard
to
kraid's
and
specialized
escape
patches
or
hutches,
to
avoid
some
of
the
normalization.
So
it's
becoming
kinda
like
I,
have
a
patch
for
that,
but
it's
huge
and
massive
and
I
don't
know
if
it's
helpful
at
all
so
I
have
another
implementation,
just
just
just
add.
Without
any
of
that
sings,
which
is
a
lot
simpler,
so
I
hope
you
have
by
the
meeting
two
versions
and
try
to
guide
towards.
E
Can
we
have
a
simpler
one
without
necessarily
integrating
into
the
ad
and
see
how
it
goes?
This
kind
of
had
been
my
ongoing
conversations,
because
I
find
that
some
of
the
api's
are
very
generic
to
address
all
kind
of
use
cases,
but
that
also
harms
us
when
we
are
trying
to
not
do
all
of
those
cases
in
browsers.
E
Anything
else
I
think
that's
all
for
now,
so
I
have
a
little
trouble
with
web
UI
patch
right
now,
if
anyone's
available
later
can
help
would
be
helpful.
I
for
some
reason,
bundle
arising
he's
not
picking
out
a
dependency
edit,
but
if
you
are
available
later,
that
would
help,
if
not
I'm,
sure
I
can
figure
it
out.
C
E
C
E
A
A
A
E
A
Also,
like
a
ruffle
he's
back
tomorrow-
and
he
probably
has
fresher
look
at
web
UI
than
I
did
yeah
all
right
we're
at
the
end
of
our
list.
If
there's
anything
else
feel
free
to
add,
I
will
quickly
go
over.
Our
highlights,
I
think
I'm,
mature,
probably
mention
it
on
other
calls,
but
I'll
just
go
quickly
over
them.
Oh
gosh,
this
zoom
sharing
thing
right,
so
Raphael
released
web
UI
2.10
and
it
had
a
significant
improvements
for
accessibility.
A
So
when
you
are
using
screen
reader,
if
you
are
like
visually
impaired
or
something
you
can
just
tab
the
screen
now
in
this
starting
from
this
version,
and
you
will
get
a
pretty
good
user
experience.
Raphel
also
like
streamed
this
on
Twitch,
which
is
interesting
tidbit
of
information.
So,
if
really
cool,
to
see
how
he
struggled
to
write
entire
user
interface
and
if
I
did
not
tell
you
this,
you
probably
would
not
notice
because
he
did
such
a
good
job
of
making.
Everything
look
the
same.
A
So
he
spent
a
lot
of
time
on
improving
experience
of
people
with
various
disabilities,
but
it
should
not
impact
the
regular
workflow
and
a
bunch
of
other
stuff.
We
kind
of
stabilized
end
to
end
test
a
little
bit
and
there
was
additional
partial
ease
where
a
small
artifact
in
electron
was
fixed
and
we
have
companion
release
which
now
lets
you
obtain
into
the
latest
web
UI.
A
So,
instead
of
using
the
hard-coded
CID
that
ships
with
Co,
ipfs
or
JSP
files
of
your
choice,
you
now
are
able
to
obtain
into
a
version
at
web
UI
that
idea
of
SEO,
which
is
it's
not
the
latest
comet
from
master.
It's
the
latest
release
as
far
as
I
know,
so
it
should
be
fairly
safe
to
opt
in,
but
we
we
made
it
opt-in.
A
We
want
people
to
use
the
version
that
was
tested
with
the
node
by
default
and
there
is
Arabic
locale
in
case
there
are
people
speaking
and
reading
Arabic
and
you
find
anything
dodgy
or
will
Tina
be
of
his
companion.
Please
reach
out,
fill
the
initial
inactive.
His
companion
report
is
the
first
language
that's
from
right
to
left
not
from
left
to
right,
so
we
probably
did
not
account
for
that
in
our
user
interfaces.
So
if
anything
looks
wonky,
please.