►
From YouTube: IPFS GUI and Browsers Biweekly 2020-05-05
Description
Meeting Notes: https://github.com/ipfs/team-mgmt/pull/1155
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
A
A
The
and
welcome
directly
here
as
Quezada
who
will
be
joining
us
with
browser
endeavors
and
trying
to
figure
it
out.
How
can
we
do
placate
I,
give
us
notes
across
hubs,
origins
and
also
reuse
like
leverage,
the
local
ironic
note,
I,
think
that's
the
more
or
less
description,
but
exactly
feel
free
to
say
a
few
words.
A
B
Yeah
sure
so,
I
think
today,
if
you
run
ipfs
Jess
I
care,
that's
in
your
browser.
That
means
every
time
you
open
a
new
tab.
We
spawn
a
new
IP
first
node.
It
has
to
reconnect
to
the
same
peers
and
do
all
of
those
things
over
and
over
again,
that's
true
for
the
same
origin
tab.
So
the
same
site
would
do
the
same.
If
you
do
they're
different
origins,
it
would
be
the
same.
B
Furthermore,
if
you
have
idea
paths
of
running
a
side
by
side
to
your
browsers
that
use
ipfs,
there
is
no
sharing
happening
between
those
two,
which
also
means
that
you
might
have
a
data.
You
know
look
like
if
I
snow,
it
on
a
desktop
and
your
app
might
be
trying
to
get
the
same
data
and
while
you
may
be
offline-
and
you
won't
be
able
to
succeed
to
do
that
same
across
the
tabs.
A
A
C
C
Like
the
number
of
times
I
started
accidentally
running
multiple
nodes
and
then
get
real
confused.
You
know
I
can't
be
the
only
one
right
so
so
I
would
love
anybody's
thoughts
on
that
I
will
I'll
get
a
sort
of
quick,
probably
probably
just
a
Google
Form
I
can't
really
think
of
any
about
a
better
way
to
do
it,
but
I
get
that
up
and
running
and
then
see
see
all
y'all
and
see.
If
you
have
any
other
thoughts
on
comments.
C
B
C
C
C
D
But
I
like
I,
like
your
initial
approach,
though
first
asking
why,
like
with
that,
because
I
feel
like
if
you,
if
you
ask
that
question
to
the
people
that
will
affect
people's
answers,
I,
really
like
that.
Your
first
question
is:
why
do
you
use
desktop
now
and
then
we
can
follow
along
with
what?
What
should
desktop
do?
Yeah
yeah.
C
D
C
D
One
thought
I
had,
though
too
is
is
actually
asking
this
question
inside
desktop
because
I
feel
like
if
we
ask
in
our
channels
we're
not
going
to
get
the
full
audience.
Molly
said
we're
like
sixty
thousand
desktop
users,
or
something
like
that.
Maybe
so
no
I
feel
like
if
we
ask
people
if
we
ask
people
a
question
and
we
actually
shift
that
question
in
desktop.
Not
only
do
we
have
a
little
bit
of
a
better
idea
of
who's
using
desktop
we'll
reach
audiences
that
aren't
hanging
out
in
our
forums,
which
is
probably
like
audience,
yeah.
C
Yeah
I
mean
I
think
the
weekly
is
gonna,
get
us
a
whole
lot
of
folks.
I
agree:
the
forum
is
pretty
self-selected
vital.
Are
we?
What
do
we
have
plans?
I
mean
we
could
have
it
as
a
first
launch.
We
get
I
was
like
a
snack
bar
on
first
launch,
the
next
time
we
but
are
we?
Are
we
shipping
and
upgrade
I,
don't
want
to
ship
an
upgrade
that
just
asks
people
a
question.
C
Time
we
ship
a
desktop
update,
yeah
yeah,
because
I
think
this
is
kind
of
you
know
a
song
if
weekly
turns
out
to
be
a
representative
group
of
people
and
and
we'll
want
to
tweak
that
by
a
that'll
that'll
be
like
B.
What
do
you
use
desktop
for
word?
Not
use
desktop
for
question.
If
that
starts
feeling
representative
I
think
we
can
get
the
data
we
need
on
like
25
people,
so
can.
B
I
saw
one
more
idea,
so
one
things
that
we've
been
doing
at
Mozilla
is
templating
part
of
the
users
for
the
new
ideas
before
we
actually
go
ahead
and
do
it,
one
of
the
things
we
could
do
is
if
I
know,
if
anything
is
measured
like
how
many
times
people
open,
UI
or
anything
like
that.
But
if
we
can
sample
some
segments
of
you
and
instead
of
opening
the
UI
just
popping
the
browser
tab.
This
is
the.
C
Yeah
and
we
do
have
the
other
thing-
the
other
thing
I
do
know
is
we've
got
gonna,
say
roughly
about
50
people
who
have
responded
to
prompt
within
Docs
to
be
beta
testers
in
general,
read
sort
of
phrase
that
is
like
being
a
beta
tester.
The
docs,
but
I
see
no
reason
why
we
can't
see
coop
that
audience
if
we
need
to
as
well.
You
bring
up
some
very
interesting
points
about
a/b
testing
and
there's.
There
is
something
to
be
said.
You
know
if
we
start
moving
this
thing
into
exclusively
into
web
UI.
C
A
Just
like
a
closing
thought
here
is
that,
like
historically,
the
way
that
stop
started,
I
believe
hack
remembers
it
better,
but
it
had
like
a
panel
which
you
was
mainly
used
for
drag
and
drop
and
I
feel
like
the
drag
and
drop
story
still
remains.
If
someone
is
like
using
it
and
it's
like
bounce
to
the
web
UI
and
files,
it's
probably
the
drag
and
dropping
stuff
and
so
having
a
question
around
drag
and
drop.
Use.
C
C
A
Speaking
of
like
fixes,
when
we
fix
something,
we
make
a
new
release
of
web
UI
and
desktop
so
right
now
we
are
bundling
web
UI
with
desktop
and
we
are
able
to
like
ship
fixes
if
the
stop
itself,
if
we
start
opening
web
UI
in
a
web
browser,
then
you
get
into
that
tricky
situation
of
access
controls
to
the
API
wizard,
which
is
like
not
UX
problem,
is
like
technical
problem
with
our
stock,
but
it's
something
to
be
aware
of.
If
we
start
opening
in
a
web
browser,
we
need
to
figure
it
out.
A
A
F
Married
address
book
in
proto
book
was
March
in
this
year,
28
release,
which
was
cool
so
basically
forgiving,
United
States
about
the
next
release,
obviously
will
be.
We
are
now
missing
the
cue
book,
which
I
already
implemented
as
well
and
Jacob,
will
review
it
this
week
and
also
the
big
key
chain
integration
which
I'm
currently
working
on.
They
are
the
two
missing
pieces
regarding
the
piercer
and
we
are
still
blocked
on
some
other
stuff.
Regarding
the
interoperability
we'd
go,
we
would
be
in
the
noise
and
Shake
and
also
in
the
in
another
case,
with
sharp.
F
Maybe
blocking
is
the
release
for
the
next
week.
We
you
need
to
shake
it
out,
because
basically,
we
are
pending
on
PRS
to
get
merged
in
bitumen
so
that
we
can
des
interrupts
with
Jess
so
that
we
can
after
that,
really
is
the
new
release,
but
yeah
we
need
to
think
we'd
also
grab
the
FS
and
go
a
bit
B,
and
that's
also,
while
is
thinking
a
longer
time,
two
things
important
to
point
about
the
Pearce,
our
persistence.
This
is
mostly
related
with
paper,
it's
important,
so
we
will
have
in
wicked
beside
the
persistence.
F
The
disabled,
by
default
for
now,
for
one
specific
reason,
which
is
since
we
don't
have
like
Jessica
fest,
a
way
of
immediate,
will
detecting
the
environment
that
we
are
running
if
we're
running
browser
or
nodes.
Basically,
the
only
data
store
that
we
would
have
that
it's
comparable
with
all
of
them
is
the
memory
data
store
in
the
memory.
Data
start
its
kind
of
useless
when
you
want
to
persist
something
and
they
start.
F
The
node
in
Jessica's
do
not
be
the
problem,
because
there
is
already
a
set
up
with
the
browser
in
node
and
we
can
set
up
enable
by
default
in
the
browser
and
from
the
start,
but
in
which
P
will
need
to
wait
for
the
next
release.
Before
we
work
on
improving
the
lipids
piconfig,
which
is
also
another
of
my
hairs
there.
F
Hopefully
I
will
work
on
this
work
and
with
that
we
end
to
also
the
same
thing
else,
are
the
fastest
and
have
the
configuration
immediately
providing
it
with
send
defaults
for
the
environment
that
we
are
running,
which
currently
is
not
the
case.
This
is
one
thing
and
the
other
issue
is
the
threshold
parameter
that
we
added
for
the
piercer
persistence.
So
basically
we
want.
We
don't
want
to
every
single
atomic
change
to
the
piercer
to
be
persistent,
because
this
would
not
be
really
performance
and
so
avoiding
trying
to
avoid
it.
F
We
added
the
threshold
parameter,
which
basically
says
the
number
of
dirty
peers
that
you
can
have
in
the
peer
star.
Before
persisting.
So,
let's
say:
if
we
have
the
threshold
or
five,
we
will
keep
a
list
of
the
of
tears
that
are
dirty
and
when
we
reach
this
threshold.
Okay,
so
let's
now
apply
to
all
these
five
years
that
we
have,
and
we
just
persist
like
a
batch
of
all
the
operations
instead
of
doing
one
and
one
and
one.
F
However,
this
also
might
have
some
bad
consequences
for
the
browser
and
we
will
be
recommending
for
browser
users,
the
threshold
of
client
for
now,
because
we
don't
have
a
clear
way
of
of
stopping
the
node,
because
with
the
threshold
in
if
we
are
in
the
node.js
environment,
when
we
stopped
the
nodes,
basically,
we
call
the
persist
anyway.
Even
if
we
have
230
peers,
we
will
guarantee
that
in
stock
we
will
persist
that
data
or
in
the
in
a
browser
environment.
F
F
Unless
will
we
think
on
other
alternatives
like
we
I
initially
talked
about
having
an
interval
of
time
where
we
just
persist
anyway,
even
if
we
don't
achieve
the
threshold,
but
then,
even
with
that,
we
can
end
up
with
data
being
lost,
so
I
would
say
for
us
to
go
with
the
threshold
for
one
right
now,
and
then
we
can
discuss
any
threat
on
top
of
that
and
yeah.
That's
it
for
me,
I
know.
If
anyone
of
you
have
comments,
I.
A
F
That's
that's
one
of
the
things
yeah
I
want
to
eventually
add,
but
in
the
next
release
to
Liberty
pay
like
strategies
of
the
peer
discovery
from
the
beginning,
we
can
like
configure
configuration
that
says.
Okay,
if
you
have
n
number
of
beers
already
in
the
beer
store,
you
might
start
trying
to
dial
them
instead
of
going
to
the
bootstrap
nodes,
but
that's
a
thing
that
we
will
probably
target
to
work
in
parallel
with
the
config
improvements,
because
it
will
be
like
a
lot
of
different
stuff
that
we'll
need
to
endow
in
the
configuration
can.
B
I
ask
one
question
you
mentioned
about
persisting
before
unload
I.
Don't
know
what
you're
persisting.
So
it's
not
exactly
there
for
me,
but
there's
hooks
that
you
hope
you
can
hook
into
on
before
clothes
to
do
the
things
that
you
can
do
synchronously.
So
it
may
not
give
you
the
a
sink
rate
right,
but
you
could
persist
local
storage
or
something
unless
it's
a
huge
amount
of
data.
F
We
are
basically
storing
the
multi
others
of
the
beer
that
appears
that
we
know
and
the
protocols
that
they
are
running,
and
this
allows
us
to
imagine.
You
start
appear
from
a
fresh
beer
and
you
will
discover
the
bootstrap
beers
and
another
beers
from
those
beers,
and
then
you
will
keep
a
record
of
all
these
peers
for
so
that
in
the
next
time
you
start
your
nodes,
you
will
not
need
to
reach
to
them
again
and
you
can
to
discover
them
because
you
already
know
them.
You
can
immediately
try
to
connect
to
them.
F
If
you
want,
and
with
that,
we
can,
as
light
over
saying,
not
keep
a
big
load
on
the
bootstrap
nodes
and
we
can
distinguish
which
beers
we
want
to
dial
from
the
beginning,
instead
of
going
directly
to
the
bootstrap
nodes
and
regarding
the
the
roots.
Basically,
what
we
do
it's
that
this
threshold
thing
where
we
once
in
a
while
start
a
batch
of
operations
instead
of
being
continuously
storing
everything.
F
D
My
periodic
keyboard
paws
block
it
by
keyboard.
Yes,
so
Galle
assigned,
we
have
a
mailing
list
and
they're
gonna
send
weekly
updates.
Let
me
know
I
think
I
might
just
forward
those
dump
those
those
weekly
updates
into
the
browser's
channel,
so
everybody
can
follow
along
if
anything,
it's
very
interesting
to
be
able
to
see
what
these
set
of
activities
are.
D
When
you
have
somebody
solely
focused
on
making
a
set
of
changes
to
the
address
or
browsers
themselves,
and
then
all
the
places
that
they
need
to
communicate
various
mailing
lists
and
web
boards
and
who
they
need
to
file
issues
with
and
where
and
what
the
different
players
involved
think
about
the
changes,
that's
fascinating.
So
even
this
first
up
table
and
shared
by
frederique
is
pretty
cool
to
watch.
That
work
will
be
ongoing.
It's
basically
a
six-week
contract
over
12
weeks.
D
So
some
of
these
frederique
foreman
values
work
half
time
on
this,
because
the
nature
of
the
of
the
work
is
a
lot
of
times
just
send
a
message
to
a
list
and
they're
waiting
for
a
reply
and
driving
a
decision
on
a
given
thing,
not
necessarily
just
sitting
and
coding.
Nothing
out
so
that
was
the
only
update
there
is
that
we
have
now
signed
the
contracts
and
I
officially
kicked
that
work
off.
A
A
One
of
concerns
were
those
were
not
registered
or
IIA
and
a
Ayana,
and
we
may
spend
some
time
just
to
like
close
that
gap.
On
the
idea.
First
sight
I
reach
out
to
secure
staccato,
but
I
feel
I
think
he
got
reached
out
to
the
dot
people
already,
so
if
they
would
be
the
best
if
they
register
like
submit
for
registering
your
eyes
on
their
own.
But
if
we
get
blocked
too
much,
we
probably
may
be
like
submitting
it
on
our
or
our.
On
our
end,
that's
small
small
new
ones.
A
If
anyone
is
interested,
are
you
talking
about
chill
DS,
no
I'm
talking
about
URI
protocol
schemes
so
like
ipfs,
colon,
slash,
slash
right
so
IP
fsip,
NSD,
web
dot
and
SSB,
where
some
time
ago,
white
listed
in
firefox,
but
there
is
like
a
lot
of
movements,
switching
from
white
list
to
black
lists
and
stuff
like
that,
and
now
when
we
want
to
introduce
a
feature.
Parity
in
chromium,
we
hit
that
again
by
not
having
those
like
officially
registered.
Yet
alright
local
discovering
brave,
kicked
off.
It's
a
separate
that
grant
now.
A
A
Mind
them
so
that
the
work
on
active,
the
local
discovery
in
brave
started.
The
goal
was
mostly
to
dog
food,
our
mdns
implementation,
with
something
else
than
go
idea
fess.
So
we
got
support
for
in
JSI
PFS
we
ran
and
by
the
GSI
PFS
in
brave.
That
brave
note
has
access
to
more
powerful
api's
which
enable
us
to
listen
and
broadcast
on
tcp
and
UDP
sockets,
so
just
work.
A
This
is
a
dev
grant
to
close
the
gap,
make
it
possible
for
brave
node
to
announce
itself
on
mdns
and,
if
not,
try
to
figure
it
out
alternative
way
of
local
discovery
in
a
network.
So
if
you
have
or
in
under
airplane
two
people,
we
pray
she'll
be
able
to
exchange
files
with
each
other
and
that's
progressing
pretty
pretty
nicely
Ranger
who's
leading
this
work
identified
problem
with
chromium
code
base.
Basically,
it's
not
possible
to
the
way
chromium
API
exposed
to
a
browser
extension.
A
Like
grabs,
the
UDP
ports
is
not
compatible
with
more
than
one
listener
on
the
OS,
it's
basically
grabbing
it
just
for
its
own
use
and
does
not
support
port.
We
use
and
there's
like
old
peer
patch,
which
fix
that
and
so
Ranger
is
like
testing
if
it's
actually
fix
and
if
so
porting
the
patch
to
the
latest
version
of
chromium
and
will
plan
to
submit
that
patch
to
a
brave.
A
But
just
like,
I
think,
ii
ii,
don't
know
to
the
note
see
if
someone
is
interested
in
a
way
it's
implemented
without
shooting
full
ET
room,
blockchain,
client,
so
long
story
short,
it's
making
requests
to
third-party
HTTP
api
at
in
pure
and
click.
I
had
some
initial
concerns
on
that.
It
at
least
should
ask
user
for
permission
before
sending
any
information
about
the
browsing
habits
to
some
third
party
API.
So
if
you
are
interested
in
that
discussion,
links
to
the
pr
is
in
the
notes.
Next
one
is
desktop
migration
and
upgrade
bug.
A
E
That
could
be
a
problem
for
a
migration
path
like
from
a
user
experience,
point
of
view,
because,
instead
of
a
click
and
it's
upgraded,
they
need
to
check
out
to
the
latest
release
and
manually,
build
it
again,
which
cannot,
which
can
also
be
no
issue,
since
we
already
have
advanced
users,
they'd
like
to
see
the
code
first
before
they
have
the
product
bill.
So
maybe
they
would
also
like
to
see
what
changed
between
the
versions
and
decide
if
they
want
to
upgrade
or
not.
E
But
nonetheless,
every
time
we
start
desktop,
it
gives
a
warning
to
the
user,
forcing
them
to
update.
So
that
could
be
an
issue
as
well.
I
don't
know
if
we
should
change
that
approach,
just
like
inform
the
user
as
an
applet
not
required,
or
if
we
should
force
people
to
update.
Maybe
we
can
discussed
a
bit
around
that
because
that's
a
struggle
point
I
found
because
the
the
app
really
forces
me
to
update
right
kind
of
blocks
well
when
I
open
it
for
the
first
time
you.
A
Had
a
very
good
point
with
the
fact
that,
like
more
advanced
users,
don't
trust
pre-built
packages
and
they
want
to
build
them
on
their
own
and
I,
say
it's
not
a
bug,
it's
a
feature,
but
the
auto-update
does
not,
because
if
I
build
something
from
source,
I
don't
want
it
to
like
update
to
add
some
binary
blood
and
the
next
day,
so
I
don't
believe
we
actually
need
to.
We
don't
have
actual
back
here.
A
So
it's
just
a
matter
of
how
much
time
do
we
work
in
bandwidth?
Do
we
want
to
spend
in
like
improving
experience
for
those
like
very
technical
users,
who
probably
don't
really
care
that
much
about
UX
of
automatic
updates
might
like?
My
only
concern
was
that
the
users
who
are
using
those
pre-built
packages,
like
the
concern,
was,
is
there
an
issue
and
I,
don't
believe
there
is.
A
If
you
install
the
official
package
of
like
o0
10-4
and
you
click
like
check
check
for
updates,
you
will
get
updated
to
the
latest
version
and
that's
what
was
like.
The
main
concern
of
before
molly
was:
are
those
like
regular
users,
get
update
and
I
believe
they
will?
If,
if
we
are
able
to
like
reproduce
it
with
like
regular
packages,
then
we
have
a
problem,
but
I
don't
know
if
we
confirm
that
we
have
this
problem.
Yeah.
E
A
Trying
like
trying
had
created
that
package
for
was
it
like
ipfs
or
gateway,
which
is
trying
to
fetch
from
ipfs,
and
if
you
don't
have
running
node
locally,
it's
falling
back
to
the
public
gateway.
That's
like
a
separate,
separate
discussion.
I
feel
we
are
pretty
great
with
this
this
bug.
If
anyone
has
any
issues
with
upgrading
and
they
believe
they
are
on
the
official
channel,
please
fill
an
issue
that
would
be
useful
data
point,
but
so
far
we're
not
able
to
reproduce
the
vision,
issues.
D
Thanks
for
digging
into
this,
these,
these
are
often
really
thorny
and
difficult
to
test
scenarios.
Some
conditions
but
I
appreciate
you
digging
into
it
it's
if
we
can
get
independent
third-party
verification
of
it,
I'd
be
worried,
but
it's
old
Molly
and
the
thread
like
it's
I
I,
don't
trust
anyone
on
our
team,
because
especially
people
years
and
years
and
years
of
working
with
desktop
software.
A
Here
exactly
because
he
reported
as
similar,
but
not
really
issue
with
migrations
and
notarization,
and
that's
like
what's
a
good
example
of
someone
who's
in
the
community
and
like
over
time,
installs
various
things
and
stuff.
That's
like
three
years
just
hanging
around
now
when
my
co
has
introduced
mandatory
notarization.
Suddenly
that
introduces
this
problem.
So
it's
always
always
important
to
either
like
do
a
total
purge
in
virtual
machine
or
or
ask
someone
who
did
not
develop
anything
yeah.
E
A
Just
like
on
the
notarization
topic,
I
commented
that
we
could
notarization
for
those
binaries
on
the
dist
ipfs.
Our
website,
like
we
have
go.
Ipfs
is
just
one
of
them.
There's
a
lot
of
very
various
tools
and
people
may
download
them
using
the
browser
and
they
will
get
an
authorization
problem
on
Mac
res,
but
that
needs
to
be
addressed
upstream
in
the
repo
of
each
project
to
produce
a
binary
which
is
already
notarized
and
stuff
old,
because
the
this
ipfs
our
website
itself
is
create.
A
It's
like
creating
hash
for
each
file,
not
just
ipfs
cars,
but
also
like
I,
believe
that's
Chauhan,
or
shall
2250
yeah
56
for
people
who
use
like
scripts
and
other
tools
for
automated
updates
package
manager
maintain
errors.
So
we,
if
we
add
notarization
for
my
class,
we
need
to
do
that
in
the
upstream
of
the
project.
Not
in
the
least
I
PFS
our
webs.
D
Already
hopped
in
there
and
drop
this
repo
down,
not
necessarily
a
browser,
but
it
kind
of
interesting
that
it's
somebody
else's
playing
around
with
different
ways
to
be
able
to
get
a
full
node
running
on
on
android.
Just
thought:
it'd
be
interesting!
Note
to
drop
here.
I
the
next
one
after
that
Oh.
D
C
That
was
sort
of
like
a
first
sort
of
a
triage
bash
at
it.
I
have
a
PR
open
right
now
that
makes
it
responsive
on
pretty
much
any
standard.
Smartphone
also
I'm,
not
quite
sure
what
the
sort
of
like
legacy
of
that
of
that
code
is,
but
there's
like
just
a
bunch
of
extraneous
CSS
I've
I've
been
off,
and
on
the
last
couple
of
days
it's
like
totally
refactoring
it.
So
hopefully
that's
happen
to
review
right
now.
C
D
C
C
Been
shipping
everything
everything
with
the
old
teal
we've
been
shipping
for
quite
some
time,
and
just
doesn't
just
just
passed
away
it
does.
It
does
mute
out
like
it
does
wash
out
the
color
palette
a
little
bit,
and
you
know
if
you're
not
used
to
seeing
it
it
it's
something
that
you
may
notice
I
would
I
personally
would
suggest
that
we
that
we
turn
this
into
sort
of
a
separate
discussion.
C
D
D
C
C
D
C
C
B
A
C
Not
it's
not
the
the
issue
is
not
the
bar,
the
top.
The
page.
The
issue
is
that
the
excessive,
when
we,
when
we
pushed
the
the
saturated
teal
to
ipfs
CSS,
one
of
the
things
in
this
round
of
changes
to
director
index.html,
was
to
bring
the
colors
in
line
with
ipfs
CSS,
which
they
never
were
so
and
the
reviewer
objects
to
you.
The
dissatisfaction
of
directory
index.html
I
have
been
specifically
directed
to
regress,
desktop
or
web
UI.
However,.
A
D
Yeah
yeah,
so
this
was
just.
This
is
a
project
that
somebody
just
dropped
in
the
channel
for
the
the
mobile
design
guidelines,
work
which
I
am
not
familiar
with.
What
this
run
Linux
on
Android
solution
is
that
they
were
using
I
realize,
like
I,
wouldn't
lift
it
up
and
I
was
it
go?
Yeah
I
am
I'm
actually
following
along
in
that
reddit,
and
that
Twitter
account.
D
Difficult
for
me
to
imagine
that
it's
super
performance,
but
as
far
as
like
a
fast
path
for
getting
a
form
that
running
kind
of
kind
of
interesting
heck,
they
were
maybe
worth
looking
at
the
other
item
there
I
and
on
on
the
weekend,
push
some
nice
changes
to
the
browser
sandbox
so
worth
pulling
and
rebuilding
that
taking.
You
know.
D
I
actually
pointed
this
person,
two
birdies
work
and
birdie
actually
recently
moved
their
migration
in
their
gum
about
stuff
into
the
AFS,
or
so
it's
kind
of
officially
now
and
then
I'm
kind
of
curious.
We've
talked
a
little
bit
like
what
what
next
steps
there
might
be
like
if
we
actually
like
I
think
would
be
great
to
be
able
to
just
release
a
ipfs
node,
an
official
IP,
this
node
for
mobile
for
people
that
want
to
run
it.
D
D
D
Brady
did
it
so
I
think
we
have
to.
We
have
to
have
a
library
from
a
from
developer
and
builder
inclusion
pathway,
but
also
just
having
a
ipfs
noted
that
people
can
run,
maybe
that
he
did
awesome
and
you
know
a
minor.
You
know
functionality,
all
I
do
either
a
share
handler
and
things
like
that.
That
might
be
nice
innovations.
A
Some
highlights-
maybe
there
have
been
some
releases
I,
think
I
missed
some
of
them,
but
there's
a
new
it's
ipfs
release,
which
is
a
tiny
library
for
detecting.
If
is
this
URL
ipfs
resource,
actually
it's
part
of
who
goes
endeavor
to
remove
use
of
global
of
nodes,
global
such
as
like
buffer
and
things
like
that.
But
it
may
be
useful
to
know
for
people
who
stumble
upon
that,
because
some
build
some
like
Banderas
stopped
stopped,
injecting
those
node
Global's.
A
So
it
may
be
useful
to
switch
to
the
latest
version,
they're
saying
new
ipfs
provider
version,
which
is
a
very
small
library
for
adding
ipfs
to
your
application
in
a
way
that
has
like
a
progressive
fallback.
So
it
tries
to
find
the
best
node
available.
It's
very
crude
library,
but
it
works,
so
it
tries
to
is
the
window.
Ipfs
object
is
the
HTTP
api
on
localhost?
A
A
Each
one,
but
if
someone
use
that
they
will
immediately
know
what
I'm
talking
about
so
it
one
of
requests
were
to
like
stop
pounding
J's
idea.
First,
abandoning
HTTP,
client
and
lazy
load
them.
So
this
new
release
does
that
and
I
believe
that
plug-in
already
switched
to
ideas
provider,
so
they
no
longer
need
to
run
like
write
their
own
code
for
doing
that,
and
this
was
like
some
time
ago,
but
it
was
it
happened
since
we
had
this
call
last
time,
ipfs
web
UI,
shipped
with
peer
screen
updates
by
Raphael.
A
A
B
B
While
there
is
a
dns
SD
standard
and
I
think
there
were
some
discussions
for
switching
to
the
standard
of
those
reasons
to
use
a
standard
other
than
he'd
been
a
standard
actually
on
many
routers,
pure
and
DNS
is
banned
and
DNS
SD
is
not
because
that's
what
printers
and
other
things
used,
so
I
was
wondering
if
I
could
has
actually
switched
to
it
or
not,
and
if
not,
it
might
be
worth
thinking
about
it.
Now
that
prairies
actively
developing
this
stuff,
oh
yeah,.