►
From YouTube: Manifest V3 and the road forward for IPFS browser extensions - @meandavejustice - Browsers & the Web
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everybody
just
to
do
a
little
intro
on
myself,
because
I
haven't
met
most
of
you.
I
think
now,
maybe
about
half
this
week.
My
name
is
david
justice.
I
started
contracting
in
november
with
browsers
and
platforms
team
brought
me
on
initially
just
to
try
and
convert
the
ipfs
companion
extension
to
be
compatible
with
manifest
v3.
I'm
gonna
explain
what
those
things
are
and
kind
of
like
where
we're
going
from
here
on.
A
But
the
simplest
way
I
can
say
is
like
and
like
the
most
important
feature
to
me,
is
that
if
you
go
and
you
try
and
access
like
a
gateway
and
you
have,
it
turned
on
it'll,
go
ahead
and
take
that
cid
pass
it
to
kuba
or
whatever
you're
running
like
if
you
have
a
local
node
in
brave
and
then
bring
you
back
and
navigate
it
to
your
actual
you're,
viewing
it
on
your
local
node
and
then
there's
like
a
bunch
of
other
like
little
features
added
in
you
can
see
different
things.
Go.
A
Let's
see,
I
have
another
slide
here.
Yeah
you
can
toggle
between
like
local
and
gateway.
Sometimes
you
want
to
always
have
the
gateway
for
certain
types
of
domains.
Sometimes
you
prefer
local.
You
can
toggle
that
you
can
toggle
it
like.
Overall,
you
can
get
insights
into
your
local
node
like
without
actually
digging
into
like
web
desktop
or
anything
like
that
or
ipfs
desktop.
A
So,
let's
describe
what
manifest
v3
is
manifest.
33
is
the
newest
version
spec
for
web
extension.
So
basically,
what
they're
trying
to
do
is
make
it
more.
Secure,
have
more
privacy
and
more
performance
is
what
they're
they're
stating
now
there's
it's
been
pretty
controversial.
There's
like
many
many
articles,
you
can
read
online,
which
I
won't
get
too
deep
into
of.
Why
that
like
may
or
not
be
true
for
the
users.
A
This
is
like
a
non-exhaustive
summary
of
some
of
these
changes
in
manifest
v3.
The
main
things,
the
main
two
things
that
are
affecting
me
and
a
lot
of
the
other
people
is
the
background
pages
are
switched
to
service
workers
and
the
the
biggest
one
for
us
is
that
blocking
web
request
has
been
replaced
with
declarative
net
request.
So
what
that
actually
looks
like
is
that
blocking
network
like
blocking
web
requests,
we
used
to
be
able
to
intercept
web
requests,
make
some
changes,
update
the
url
and
redirect
someone
like
immediately
now.
A
We
cannot
do
that.
What
we
have
to
do
now
is
we
get
the
request
and
we'll
kind
of
like
store
it
for
a
second
and
I'll
set
like
a
a
request
off
in
the
background,
so
to
actually
go
to
cuba,
get
the
correct
mappings
the
cid
all
that
stuff
and
then
update
it
in
our
declarative
net
request
record
so
the
next
time
the
user
goes
to
navigate
to
that
url.
It
will
update
for
them,
which
is
honestly
like
not
that
bad
of
a
ui,
it's
very
similar
to
how
brave
is
working
right.
A
Now
we
also
like
provide
on
once
that's
loaded
in
the
background.
You
can
go
ahead
and
click
to
like
refresh
and
go
to
that
page.
So
I
actually
like
that,
because
I've
had
plenty
of
like
times
working
with
companion,
where
I'm
not
totally
sure
when
it's
going
to
redirect
and
not
so
could
be
seen
as
an
improvement.
That's
one
of
our
workarounds.
A
So
there's
a
big
issue
that
happens
to
be
numbered
666.
This
was
made
before
we
got
to
it,
trying
to
deal
with
manifest
v3.
It's
got
like
a
lot.
It's
a
pretty
big
thread.
It's
been
going
on
for
years
now
you
can
see
2019.
again,
I'm
not
going
to
get
too
deep
into
manifest
v3
specifics,
because
it's
just
like
depressing.
We
don't
have
to
think
about
it
that
way.
So
I'm
trying
to
think
of
this
as
an
opportunity
to
rethink
what
we
can
do
with
companion
and
how
we
interact.
A
The
our
users
will
interact
with
it
in
the
browser.
So
we're
trying
to
rethink
this
and
we're
saying
like
what
do
we
want
ipfs
companion
to
do
now,
and
how
can
we
move?
Some
of
these
features
around
take
this
as
an
opportunity
to
just
redesign
this.
So
what
I
think
is
that
we
should
basically
just
redirect
and
allow
uploading.
A
We
want
to
keep
it
as
minimal
as
possible,
and
then
we
want
to
be
able
to
pull
out
other
features
into
ipfs
enabled
extension.
So
we
can
continue
to
build
on
that,
so
to
describe
what
an
ipfs
enabled
extension
like
the
intention
of
it
would
be
would
be
to
provide
value
to
the
users
with
a
shallow
understanding
of
ipfs.
So
they
don't
really
have
to
understand
too
much
ipfs.
They
don't
have
to
like
dig
into
diagnostics.
They
don't
have
to
really
understand
how
much
of
this
is
working.
A
Hopefully
they
just
install
something
like
dietrich
was
talking
about
before,
where
I
just
want
to
pin
something
to
wiki
like
from
wikipedia
to
ipfs.
I
just
want
to
pin
a
tweet.
I
want
to
pin
a
youtube
video
and
I
want
to
stick
it
around.
I
want
to
make
sure
like
I
can
access
it
forever
without
having
to
understand
ips.
So
I
believe
this
is
like
a
gateway
drug
to
people,
understanding
ipfs,
so
yeah
shared
single
functionality
when
possible,
shared
spec.
So
hopefully
we
can
reuse
code.
A
It's
just
maybe
a
library
that
you
can
just
include
in
your
extension
or
a
template.
It'll
be
interacting
with
kubo
or
hopefully,
some
of
the
new
like
http
specs
that
are
going
through.
That
should
be
agnostic
in
that
way
and
then
I'm
thinking
it's
very
early.
I
want
to
get
y'all's
opinion
on
it,
but
maybe
we
can
make
them
sort
of
composable.
Maybe
you
can
have
some
of
these
extensions
working
together.
A
Some
examples
of
some
of
the
ideas
we
have
like
I
just
said:
pin
tweets
ipfs
would
like
to
see
it.
Maybe
a
journaling
one
where
you
know
you
open
it.
You
click
one
click
you
get
a
full
page
like
content,
editable
web
page,
you
can
type
it
and
then
just
boom
publish
straight
to
ipfs
or
fleeq
pin
web
pin
playback,
and
then
it's
funny
move
was
talking
about
the
mutable
pinning
I
actually
had
this
down.
A
I
don't
know
how
the
hell,
I
would
do
it
as
an
extension,
but
it's
something
I
would
like
really
like
to
have
so.
Hopefully
we
can
like
work
together
on
that
eventually
get
a
spec
going
for
that,
but
yeah.
So
this
is
again
very
brief
talk,
but
I
wanted
to
just
get
the
conversation
started,
get
your
ideas
and
we'll
see
where
we're
going
from
there
there's
a
hackmd
right
here.
This
is
where
I
have
like
a
big
list
of
ideas.
Please,
like
add
anything
you
can
to
there.
A
A
A
Panel
cid
explorer
ipld
explorer
if
it
works
actually
being
able
to
get
into
that
inspecting
x,
ipfs
path,
dns
link,
there's
tons
of
stuff
we
can
do
here.
I
talked
to
russell
the
other
day
at
the
beginning
of
this
week
about
the
web,
ui
and
diagnostics
view.
I
think
that,
like
we
can
definitely
collaborate
on
that.
I
think
there's
a
whole
lot
to
be
shared
here,
but
yeah.
Additionally,
if
you
have
more
developer
experience
things,
let's
just
like
cram
it
all
into
here,
so
that's
my
ideas.
Yeah!
B
Yeah,
so
just
a
quick
question-
and
I
I
don't
mean
to
put
you
on
the
spot,
but
for
the
composability
of
the
extensions.
How
do
you
do
you
have
like
a
high
level
idea
of
how
that
would
work
and
maybe
how
we
could
compose
the
extensions
eventually
into
web
ui,
while
also
having
them
be
distinct,
separate
components.
A
I
I
don't
have
an
answer
to
that.
Yet
this
is
like
a
very
the
composable
part
was
like
a
like.
I
literally
just
added
that
this
morning
I
was
like
this
would
be
really
cool,
but
basically
I
want
to
be
able
to
just
I
I
want
to
like
I
was
thinking
when
composable,
I'm
saying,
like
maybe
an
extension
can
modify
something
like
use
web
recorder
which
we're
going
to
hear
about
next
to
pull
in
a
tweet
and
then
maybe
you
want
to
modify
that
or
duplicate
it
or
something.
A
So
maybe
another
extension
can
do
that
and
then
pin
that
also.
So
I
don't
know
if
that's
like
passing
a
cid
copying
to
your
clipboard
and
then
passing
it
over
like
the
same
way
that
you'd
like
pipe
things
in
unix.
That's
like
yeah,
that's
kind
of
what
I
was
thinking
about
for
that.
But
as
far
as
like
what
you're
talking
about,
I
was
kind
of
thinking
of
architecting.
This,
like
a
first
like
a
template.
A
A
That's
a
good
question
so
with
manifest
v3
they
like
so
chrome,
is
the
only
one
I
think
right
now.
That's
really
pushing
the
blocking
of
the
web
requests
like
they
they're.
They
were
trying
to
get
everyone
to
do
that,
but
firefox
is
not
doing
it
now.
I
think
braves
not
going
to
do
it
now
and
for
some
of
the
workarounds
we
had
to
do
for
chrome,
like
with
manifest
v3,
don't
work
in
firefox,
so
I'm
gonna
have
to
kind
of
support.
A
Both
I'm
hopefully
I'll,
be
able
to
do
some
like
feature
detection
or
like
browser
detection
in
there.
So
I
don't
have
to
like
actually
generate
separate
extensions
for
these,
but
yeah.
Definitely
like
chrome
and
firefox.
First
brave
brave
already
has
their
built-in
thing.
We
have
like
a
weekly
meeting
with
them,
so
I'll
be
like
communicating
them
with
them
more,
and
hopefully
we
can
sync
up
on
that
and
continue
to
discover
like
try
and
discover
more
of
these
like
user
interactions,
because
that's
really
what
it's
about
like
companion
is
great.