►
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
B
Yeah
I
guess:
I'm
definitely
heard
that
that
that
sounds
good.
But
when
we
discussed
this
before
I
didn't
get
that
that
wasn't
the
part
that
I
remember
the
bridging
I
think
I.
Think
cap.
So
I'm
he's.
C
B
C
C
C
C
When
group
products
he
went
into
luminous,
but
but
not
remote
groups
well
did
they
actually
did
it?
I
got
something:
I've
got
somebody
in
confused,
but
bucket
policy.
We
had
I,
guess
now,
I
guess
I
guess.
Group
policy
is
I'm.
Sorry,
forgive
me
group,
I,
guess.
Group
policy
is
not
a
not
his
a
is
not
in
any
of
these
utterly
it's
not
way.
It's
a
weird
term.
It's
lightly
other
right,
Sally!
Oh.
C
B
A
F
E
F
E
A
F
E
F
A
F
They're
linked
in
the
sense
that
the
resulting
multi-site
is
not
a
knot
of
like
the
problem
that
we
see
now
wouldn't
happen,
they're
there,
because
it
the
way
it
would
work
right.
What
we
what
happens
now
is
yeah.
If
we
need
to
stop
the
sink
and
then
start
you
know,
do
their
free
shot
and
then
we
start
the
same
battle
in
the
per
bucket
replication.
You
you
have
able
to
to
I
same
thing:
fetch
data
from
multiple
instances
in
the
bucket
yeah.
A
C
And
then
consider
making
Anderson's
making
dynamic,
making
both
site
were
compatible
or
started
with
returning
is
kind
of
as
a
blocker
for
people
with
all
the
site,
as
it
is
now.
It's
a
it's
a
critical
feature
there.
So
we're
not
gonna
solve
it
and
write
Oh
pipe
just
by
passing
the
problem
to
them
to
the
next
level
over.
C
F
B
Sorry,
anyway,
what
I
was,
but
it's
going
to
suggest
is
that
it
maybe
makes
sense
to
take
and
pick
out
the
items
here
that
are
sort
of
some
orthogonal
future
work.
Things
like
were
monestery,
select
and
I,
don't
know
what
else
a
group
or
something
it's
yes
and
and
flag
those
ones,
and
then,
after
those
are,
should
have
organized
pivot
to
a
discussion
around
the
metadata
changes
and
back-end
changes
that
we're
planning
and
see.
C
But
I
mean
ones
that
are
in
there
like
well,
we're
missed
were
missed
in
Nautilus.
The
s3
select
is
totally
orthogonal,
but
it's
not
probably
not
Australia
or
anywhere
miss
and
not
octopus,
but
I
mean
but
I,
don't
think
I,
don't
think
I
serious
life
is
likely
to
be
an
octopus.
It's
gonna
be
work
done
and
octopus
timeframe,
but
I
think
it's
too
novel
to
expect
much
of
it.
There.
C
Romer
group
I,
don't
think
it's
I,
think
I,
don't
think
it's
likely
that
they'll
be
on
a
work.
An
effort
started
on
that
I.
Think
new
bucket
in
neck
started,
using
STS
will
be
an
octopus
whether
that's
already
is,
but
to
keep
other.
Whether
you
put
the
water
than
in
the
off
will
be
there.
Keystone
already
is
in
in
Nautilus.
C
H
I
can
alter
the
bucket
log
one.
There
was
a
cloud
PR
from
couple
of
years
ago
that
they
submitted
that
we
never
merged.
It
definitely
needs
clean
up,
but
the
implements
access
a
lot
reactive
loves.
It
had
issues
yeah.
B
There's
that
I
think
the
reason
why
we
created
this
cart
also,
why
I
had
this
card
yeah
twenty
second
twenty
eighteen
was
because
we
had
a
backup
user.
We
wanted
a
way
to
get
incremental
backups
when
their
vacuums
or
s3
buckets,
but
I,
wonder
if,
because
I
wonder
if
the
event
stream
from
the
Surrealists
whatever
stuff,
it's
that
well
not
capture
that
pops
up
on
earth.
That
would
capture
the
IDs
case.