►
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
A
So
Chatfield
is
a
web
OS
that
is
based
on
web
Technologies.
So
it's
kind
of
the
continuation
of
work.
We
did
at
Mozilla
for
Firefox
OS
and
it's
we
are
a
few
years
later,
so
things
have
changed.
We
can
experiment
with.
We
have
interesting
new
things,
and
so
that's
that's
a
very
experimental
project
which
gives
us
a
lot
of
opportunity
to
try
new
things
and
also
because
we
have
control
over
the
full
stack.
We
can
do
stuff
that
is
not
subject
to
limitations.
A
Like
many
people
have
when
they
try
to
well,
it's
not
a
criticism,
but
when
you
have
to
Target
existing
browsers
or
existing
oscs,
you
have
a
lot
of
barriers
and
a
lot
of
impedance
Mitch,
Match
and
with
capital.
We
we
don't
have
that
we
we
maybe
we
need
to
build
a
bit
more,
but
at
least
we
we
know
that
we
we
can
do
it
and
we
have
the
choice
to
make
it
so
yeah
we've
been
playing
with
ipfs
so
like
ipfs
and
ipns
protocol
Anglers
I'm
planning
gecko.
A
So
here
you
can
see,
for
instance,
it's
a
real
ipfs
URL.
So
we
understand
it's
using
a
Gateway,
but
from
the
web
page
and
all
the
Dom
apis.
What
they
see
is
an
ipfs
URL.
So
everything
like
relative
URLs
resolution
course
ESP
rules
and
everything
applies
directly
to
that
ipfs
URL
that
that
works
pretty
well,
it's
not
using
the
trustless
Gateway.
Yet
that's
gonna
come
later,
and
once
we
have
trustless
gateways,
support
I
think
will
be
in
a
fairly
okay
situation
to
even
try
to
push
that
Upstream.
A
That's
gonna
be
a
fun
description
with
some
Mercury's
but
yeah.
That
would
be
reasonable.
You
don't
need
to
bring
whole
ipfs
stack
for
that,
so
that
that
makes
things
a
bit
more
reasonable
yeah.
So
we
can
also
easily
publish
to
ipfs.
So
it's
not
done
the
same
way
as
that
move
short
with
students
doing
fetch.
Here.
We
we
can
push
any
local
resource.
That
means
any
blob
to
ipfs
using
Estuary,
so
yeah.
A
It's
a
picture
that
took
this
morning
during
the
session
you
you
can
see
progress
and
you
end
up
with
a
nice
URL
that
you
can
share
with
a
QR
code
copy
to
your
clipboard.
Whatever
we
have,
you
can
support
that.
We
started
to
use
to
get
the
permissions
and
capabilities
for
some
of
the
apis
that
we
added,
so
you
can
choose
whatever
identity.
A
You
have
it's
a
local
did
that
is
created
for
users
and
you
can
choose
what
capability
you
ground
and
for
how
long
and
and
yeah
that's
it's
fairly
basic
but
use
a
few
cans,
but
I
think
it's
a
it's
a
nice
way
to
show
how
that
could
differ
from
the
regular
permission
schemes
that
web
browsers
are
using
and
how
that
that
fits
with
the
model
of
of
yeah
the
web
model
in
terms
of
security
and
permissions.
So
we
identified
some
interesting
points
around.
A
Oh,
so
when
I
talk
about
Capital
people,
very
often
they
ask
me,
oh
okay,
so
you
need
an
app
store
because
where
are
people
gonna
find
interesting
content
and
apps?
And
my
answer
is
always
the
same:
it's
it's
like!
No,
no
I'm,
not
gonna
beat
an
app
store.
I!
Absolutely
don't
want
to
do
that.
That's
and
so
once
I
say
that
I
need
to
explain
why
and
I
think.
A
That's
pretty
interesting
to
dig
a
little
bit
deeper
into
that,
because
App
Store
are
not
just
a
regular
just
another
app
that
you
put
on
an
OS,
we'll
see
with
iOS
Android,
it's
a
very
fundamental
building
block
of
this
osis
and
that's
because
they
they
have
multiple
roles.
It
looks
like
just
an
app,
but
it's
doing
a
lot
of
things
boost
for
users
and
developers,
but
so
they
yeah
it's
it's
a
gatekeeper
of
what
you
can
run
on
your
device.
Yeah,
it's
your
device,
but
actually
it's
Apple.
A
That
decides
what
you
can
do
with
it.
So
I
mean.
Maybe
that's
not
really
yours
I,
don't
know
that
provides
application.
Discovery,
yeah
you'd
have
no
other
way
to
find
apps,
basically,
except
going
to
your
app
store
at
our
supply
distribution
for
developers
and
that's
a
revenue
channel
for
the
OS
vendor
and
Developers.
A
A
So
I
will
go
through
all
this
point,
one
by
one
and
see
how
it's
done
in
yeah,
Native
voices
kind
of
and
how
that
applies
to
the
current
web
and
and
what
we
can
do
with
this
centralized
web
and
what
that
would
mean
in
a
projected
Capital.
What
can
we
try?
What?
Where
are
we?
What
What's
missing
so
yeah
native
star
get
get
keepers
of
apps?
It's
I
mean
I'm,
always
very
surprised
by
how
people
are
happy.
People
are
to
write
new
apps
for
this
devices.
A
While
you
know
that
is
very
arbitrary,
how
you
can
get
accepted
or
rejected
in
this
app
stores.
There
are
countless
people
that
that
got
just
updates
rejected,
while
the
previous
version
was
fine.
So
it's
it's
a
big
single
point
of
failure.
I
I
mean
it
looks
like
a
very
High
business
risk
honestly
and
also
limiting
Innovation,
even
if
they
will
claim
that
it's
not
the
case
apple
and
also
kind
of
Google.
They
always
claim
that
they
need
that
to
ensure
a
very
high
quality
and
security
of
the
apps.
A
A
A
Of
course
that's
going
to
be
used
for
that,
but
from
a
technical
perspective,
one
one
reason
for
that
is
that
all
these
platforms
are
coming
from
a
fairly
old
application
model,
which
is
just
like
processes
that
are
pretty
unfettered
access
to
the
platforms
they
run
on
and
and
they're
not
designed
to
run
on
trusted
code
in
in
a
very
nicely
sandbox
way
like
like
a
web
browser
or
web
runtime
can
do
so.
They
don't
really
have
in
some
ways.
A
So
if
you
contrast
that,
with
the
HTTP
level,
where
your
application
layer
is
about
the
well,
you
don't
have
to
ask
permission
to
Mozilla
or
Google
or
the
webkit
team
to
put
up
a
new
website.
Yes,
there's
no
earlier
list
of
websites
that
that
can
be
built,
you
just
give
them
a
URL
and
the
RPD
will
will
try
to
render
it
and
and
that
just
works.
A
You
can
update
it
as
often
as
you
want.
No,
no
need
to
to
ask
anyone
for
updates
and
so
on
one
one
thing
that
I
think
during
yeah
the
holidays
of
the
web.
The
focus
was
very
much
about
hey,
let's
create
this
capability
of
linking
documents
and
that's
going
to
be
great,
but
they
didn't
force
you
that
some
people
will
create
silos.
That
will
cause
so
big
that
they
will
just
succeed
using
out
of
the
room
and
and
bring
everyone
in
one
single
place,
creating
their
own
closed
networks.
A
We
still
have
links,
so
we
can
still
do
the
same
thing
where
you
can
just
pass
away
urls
the
browser
will
still
appear
under
anything,
and
the
big
difference
here
is
that
now
we
can
own
our
data
in
a
much
better
way,
because
whatever
it
is,
I
can
just
access
this
to
some
content,
addressing
scheme
and
I
can
I
can
decouple
the
computation
from
my
data
and
bringing
back
in
in
different
way.
So
to
me,
that's
a
very
interesting
thing
about
hosting
stuff
on
ipfs
right
now
and
in
capitoon.
A
I
didn't
show
anything
because
the
UI
is
not
great,
but
I
have
a
feature
where
you
can
install
wazam
plugins
and
they
are
totally
interested.
The
the
because
the
API
that
is
exposed
by
the
plugins
can
be
checked
so
I
can
I
have
a
demo
where
I
can
do
just
image.
Processing
on
on
pictures,
and-
and
this
is
all
coming
from
wherever
and
that's
I
think
it's
nice
to
think
that
it
brings
everyone
to
the
same
level
like
you
could
Adobe
could
could
provide
Photoshop
features
like
that.
A
A
Yeah,
so
Discovery
are
next,
so
this
this
screenshot
I
just
took
it
from
when
I
opened
the
Play
Store
on
my
Android
device
yesterday.
So
look
at
this
is
from
Google
masters
of
search.
Okay,
so
the
first
thing
they
try
to
sell
me
Tick
Tock
Avatar,
and
then
they
realize
I
don't
have
the
talking
story,
it's
like
how
does
it
make
sense,
in
fact
they're
supposed
to
to
be
the
best
in
search?
A
It's
like
it's
like
Amazon,
trying
to
sell
you
10
fridges,
because
you
already
bought
one
and
it's
I,
don't
know
it's
mind-boggling,
so
yeah
I
think
they
totally
lost
the
track
of
what
what
good
Discovery
less
organic.
They
just
pick
and
choose
whatever
they
want
to
promote
and
so
on
and
and
yeah
relevance
is
done.
The
drain.
A
A
Our
research
engines
directories
like
like
Yahoo
and
demos,
and
then
one
day
you
can
Google
the
first
version
of
Google,
the
one
that
was
really
really
good,
that
that
totally
destroyed
the
competition
just
because
they
were
already
so
much
better
and
then
Google
started
to
be,
plays
good
and
started
to
add
a
lot
more
like
info
boxes
and
trying
to
keep
you
in
their
result
page
instead
of
finding
new
destinations
for
you.
That's
that's
Google
of
today
and
that's
been
like,
like
that.
A
Maybe
since
almost
10
years
now
it's
been
going
done
in
quality
and
thankfully
I
think
we
we've
seen
a
few
actors
recently
that
are
starting
to
give
a
run
for
their
money
at
Google.
There's
yeah
that
go
quite
the
historical
one,
but
other
such
changes
like
like
Niva,
wife,
search,
you.com
ke.
They
are
trying
new
things.
They
they
are
not
there
yet,
but
at
least
they're
trying
it's
good
to
see.
New
competition,
I
personally
I
use,
live
search
and
honestly
in
English,
it's
pretty
good.
A
Other
language
is
not
so
much,
but
for
English
I,
almost
Maybe
one
out
of
20
requests.
I,
come
I
switch
back
to
the
Google,
but
it's
not
that
much.
Overall,
it's
pretty
good
yeah,
so
yeah,
that's
just
kind
of
the
landscape
of
search
today
on
the
distance
right
is
a
search
web
search.
What
what
can?
What
can
we
do
like
it's?
A
We
still
have
links,
so
we
know
that
we
can
crawl.
It
is
immutable.
It's
a
nice
property
for
search
engines.
It
means
that
once
you,
you
get
the
data
once
you,
you
will
never
have
to
refetch
it
to
check
what
has
changed.
You
know
it's
it.
It
didn't
change.
So
that's!
Maybe
that's
a
nice
property
actually
and
we
see
new
Innovations
in
in
search
engines
that
maybe
can
help
us
build
something
for
ipfs
ipns
at
a
relatively
low
cost.
So
I
I
tried
something
Brave
as
a
new
feature
or
a
fairly
recent
feature.
A
Is
it
called
Google's
Googles
and
that
allows
you
to
describe
rules
that
they
will
use
to
rank
the
search
results
for
for
request
differently
according
to
your
own
preferences?
So
you
can
you
can
execute
site
or
boost
some
some
sites
based
on
URL
patterns?
It's
equal.
It's
really
innovative,
typically
is
kind
of
thing
that
Google
won't
do
because
you
they
don't
want
you
to
reorder
your
searches.
Clearly
they
don't
want
that
so
I
I
wrote
a
very
simple
one
to
just
get.
A
I
was
trying
to
get
URLs
from
the
ipfs
gateways,
basically,
and
only
these
ones
so
I
push
that
to
to
Brave
search
and
I
searched
for
Vanguard,
because
I
know,
that's
one
I
just
showed
it
before
the
Wikipedia
one
and,
oh,
my
goodness,
we're
not
there.
Yet
that
was
actually
what
happened
it,
but
I
didn't
find
anything.
A
I
tried
the
URL
and,
and
it
failed
and
I
think
that's
a
prerequisite
that
we
need
like
if
you
want
the
ipfs
web
to
be
callable
and
indexable
by
these
guys
who
have
all
the
coal
farms
and
the
indexing
power
and
all
that
stuff.
We
need
the
gateways
to
be
up
to
to
to
the
task,
and
that's
I
mean
that
has
been
a
frustration
point
for
me:
the
Gateway
performance
in
general,
but
yeah.
A
It's
really
like
it's
sad
I
saw
that
I
could
do
a
nice
demo
of
showing
finding
ipfs
content,
but
but
I
could
not
even
fetch
this
so
right
so
after
discovery,
a
distribution
distribution
is,
is
an
a
Very,
relatively
simple
topic.
You
write
your
app.
You
want
someone
to
be
able
to
bring
it
to
your
end
users
in
Native,
app
stores.
A
You
create
your
app,
you
upload
it.
You
don't
have
to
think
about
it.
It's
very
nice,
especially
if
you're
successful,
because
you
don't
have
to
deal
with
a
lot
of
traffic
and
all
that
on
the
HTTP
web.
It's
a
bit
less
nice,
you
and
actually
you
need
to
get
a
domain
or
subdomain
or
whatever
some
of
us
pay
for
HTTP
server
or
manage
it
yourself.
It
comes
with
all
kind
of
I
know
your
sister
will
say
it's
not
that
simple.
We
technical
people
tend
to
say.
Oh,
it's
easy.
A
You
just
put
it
on
some
HTTP
server.
For
many
people,
I
mean
there
are
many
people
that
can
write
apps
that
don't
want
to
have
to
deal
with
that.
So
it's
it's
actually
a
friction
Point
and
we
when
we
we're
working
on
Firefox
OS.
We
we
found
that,
where
I
discovered
that
in
a
kind
of
in
direct
way,
so
Firefox
wide
are
the
other
way
to
package
apps
and
initially
that
was
done
because
we
wanted
to
be
to
have
some
code
that
was
assigned
to
allow
this
code
to
use
apis.
A
That
will
be
consider
downloads,
but
some
people
were
using
the
same
capability
not
for
these
apis.
They
were
just
using
that
to
bring
us
packages
that
we
will
host
ourselves,
and
so
they
don't
have
to
do
anything
on
their
side,
and
this
is
where,
like
I
I
realized
that
oh
yeah.
Actually
people
are
fine
with
writing
web
apps,
but
they
don't
want
to
have
to
deal
with
the
hosting,
because
that's
that's
the
burden
and
that's
that's
absolutely
correct,
I
think,
but
on
the
decentralized
web,
it's
we
are
fine.
A
A
Yeah
Revenue
channels,
clearly
we
all
know
as
a
wonderful
way
for
apple
and
on
Google
to
to
get
billions,
the
cut
they
take
from
other
developers.
It's
it's
just
crazy,
like
30
percent
or
something
like
that.
I
am
pretty
sure
that
prevents
some
apps
from
just
existing
because
when,
when
they
got
so
deep
in
your
margins,
something
just
cannot
happen,
and
we
don't
hear
about
that
because
they
just
that
just
cannot
happen.
A
They
also
yeah
prevent
uses
of
property
payment
system
for
in-apps.
That
was
the
topic
of
a
lawsuit
between
epic
and
Apple.
That,
if
you
look
at
what
the
conclusion
was,
it's
kind
of
interesting
Apple
won
in
curved
in
the
way
that
they
said
yeah,
it's
not
a
monopoly,
but
still
it's
something
competitive
Behavior.
A
So
it's
like
you're
bad,
but
not
too
bad-
that
the
good
news
is
that
at
least
in
the
U
EU
policy
makers
are
starting
to
wake
up
and
dma
and
DSA
have
been
approved,
which
means
that
the
EU
will
enforce
some
policy
and
and
some
sanctions
to
prevent
anti-competitive
Behavior.
So
we'll
see
exactly
how
that
ends
up.
It's
cut.
It's
not
directly
related
to
to
broader
choice,
for
instance,
it's
it's
like
even
like
payment
stuff
and
so
on.
A
B
A
A
If
the
UI
of
the
border
is
good,
oh
yeah,
this
one
should
have
removed
on
a
decentralized
word,
it's
kind
of
a
yeah,
a
new
space,
and-
and
there
are
things
that
we
can
see
coming
around
around,
where
it's
with
like
stuff,
like
with
the
mass
stages
of
some
others.
I-
think
that
interesting
project
that
try
to
provide
a
nice
way
to
do
subscriptions.
This
one
is
unblocked
that
probably
some
others
but
I
think
maybe
that
will
solve
the
issue
with
micro
payments
and
yeah
getting
subscription
for
for
websites.
A
I,
don't
know
if
who's
looking
at
cleaning
up
the
the
store,
but
at
the
it
it's
I
think
it's
important
also
to
to
get
that
cleaned
up
a
bit
yeah
at
yeah,
it's
so
in
in
another
chair,
well
how
we
with
dweb
right
now,
I
think
we're
very
good
on
not
gatekeeping
it's.
It's
really
gonna
open
new
opportunities
for
app
developers.
In
that
sense,
a
lot
more
cross-pollination
between
projects
will
be
possible
and
so
on.
A
When
you
see
what
you
can
do,
if
you
can
I
mean
I,
can
I've
I've
been
talking
with
work
about
how
we
could
like
just
use
the
winfs
stuff
with
what
we
have
been
capture
doing
and
so
on?
So
that's
that's
a
lot
of
interesting
use.
Cases
that
will
pop
up
distribution
is
to
me
it's
solved
kind
of
you
just
push
your
stuff.
A
The
only
maybe
think
is
that
we
may
still
have
a
need
for
sign
code,
and
that
means
that
we
need
some
kind
of
signature
and
Trust
chain
around
that
I'm,
not
sure
how
we
can.
We
should
do,
but
that's
something
to
think
about
the
the
payments
yeah
it's
in
flux,
so
many
people
are
interested
in
getting
money.
I'm
sure
something
will
happen.
A
And
and
the
yeah
the
the
part
that
is
I
think
this
work
is
discovering,
mostly
because
of
the
the
Gateway
issues
but
I
from
infra
about
the
work
on
indexes
and
so
on.
To
improve
the
situation
there
so
there's
hope
to
yeah
and
that's
that's
it
right,
yeah.
Just
one.
One
last
point
is
that
so
it's
all
about
what
can
we
do
with
high
PA
fat,
but
I
don't
think
like
ipfs
will
replace
the
HTTP
web.
A
C
So
you
you
mentioned
and
I
think
we
all
like
this,
that
you
know
the
web
just
keeps
working.
Http
requests
just
keep
working
in
ipfs
and
I.
Think
in
my
mind,
until
you
said
that
I
was
always
imagining
a
world
where
ipfs
kind
of
consumes
HTTP
and
like
dissolves
it.
But
are
you
imagining,
then
a
world
where
ipfs
then,
like
a
an
ipfs
user,
could
host
a
web
2
within
themselves
or
like
it
exists
within
the
d-web,
or
something
like
that?
What
are
your
thoughts
on
where
that
future
is.
A
Yeah
that
future
looks
like
I
mean
thanks
for
us.
I
think
it
is
going
to
take
some
time
and
I
don't
want
to
wait
that
long.
So
it's
it's
important
to
to
have
an
incremental
path
towards
that.
Then
it
if
you
need,
you
mostly
need
motivity
for
for
what
you
describe
to
work,
I
think
to
to
work
well,
because
people
people
want
to
update
their
websites
and
they
won't
just
make
me
sometimes
a
code,
sometimes
a
Content.
So
we
need
a
good
story
around
that
and
what
move
was
saying
about?
A
D
I
think
we
do
need
to
do
some
Discovery
and
reputation
and
there's
some
thinking
in
more
of
the
blockchain
land
about
you
know,
allow
listing
or
thumbs
upping
good
stuff
and
down
voting
bad
stuff,
so
I
think
there's
some
marketing
pieces
there
that
we
should
not
forget
about
so
on
the
flip
side
of
that,
like
do
you
think
that
there
are
have
you
thought
about
new
business
models
that
aren't
buy
my
app
or
subscribe
to
my
app
or
you
know
some
of
those
nuances.
Oh.
A
Well
so
so
one
thing
one
so
I've
been
in
the
mobile
web
voice
for
a
while
and
what
what
we
can
see
is
that
the
whole
ecosystem
is
a
big
dysfunctional
because
there's
no
points
it's
a
long
chain.
There's
the
hardware
provider
there's
the
OS
vendor
there
are
Service,
Partners
or
whatever,
and
all
these
people
have
kind
of
designed
incentives
at
some
point.
A
It's
when
you
get
your
device
that
everything
starts
and
examples
for
the
for
the
service
providers.
So
if
you
want
that
to
work
a
bit
better,
I
think
it
would
be
nice
to
have
a
some
financing
model
where
we
can
install
type
also
find
some
the
other
way
around
or
to
keep
to
stay
in
the
loop.
So
let's
say,
if
you
add
a
subscription
model
for
your
device.
A
Well,
you
say:
I
pay,
I,
don't
know
15
dollars
per
month,
and
some
of
that
goes
to
us
as
a
Founder,
someone
that
goes
to
the
hardware
vendors
when
sometimes
they
need
to
provide
better
support
and
long-term
updates
and
all
that
stuff
and
some
can
go
to
some
Partners
like
say,
I
want
to
use
fission
to
push
all
the
user
data
and
and
save
it,
there's
no
reason
you
should
not
get
a
cut
and
so
on,
so
maybe
bringing
a
full
ecosystem
like
that.
Would
work
a
bit
better.
D
F
A
We
are
looking
at
what
kind
of
Good
device
we
can
use
for
the
end
of
year
and
a
few
years
later,
so
maybe
the
new
pixel
6A
will
be
a
good
Target,
we'll
do
a
full
pattern
and
so
on
yeah
and
we
we
also
have
a
kind
of
report
to
Linux
mobile
devices
like
the
pine
phone
and
the
ribeye
M5,
but
we
don't
have
all
the
alloy
apis
on
this
one.
So
it's
a
bit
different.