►
From YouTube: Core Devs Meeting
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
Today
we
have
first,
some
updates
from
sort
of
swamps,
sponsors
of
new
restructuring.
That
says
due
to
the
swamps,
essential,
swamps
and
so
teams,
as
fallback
for
responsible
groups
I
wanted
to
present,
and
then
we
have
security
list
privacy,
as
you
could
trade
offs
using
will
Safe
Browsing.
Is
there
anything
else
people
want
to
add
to
gender
before
we
get
started.
A
D
So
there's
not
much
happens.
Yes,
because
today
was
our
kickoff
call,
so
we
set
up.
So
we
are
activity
in
the
research
phase
about
how
would
we
incentivize
and
wish
use
cases,
and
why
do
we
need
it
and
things
like
that
and
essentially
there
we
set
up
that
the
deadline
for
research
phase
in
general
want
to
finish
by
the
end
of
January,
so
we
have
some
time
to
actually
implement
something
so
yeah.
So
far,
it's
more
or
less
asking
people
around
and
yesterday
was
the
first
kickoff
meeting
and
yeah
in
this
forum.
E
Yes,
the
update
would
be
pretty
much
the
same.
Actually
now
we
just
add
the
call
earlier
today
to
to
initiate
the
conversation
and
kickstart
things
a
bit
and
we
plan.
We
know
initially,
we
plan
to
have
like
one
week,
research,
but
probably
we
will
extend
it
a
bit
so
eventually,
two
weeks
and
and
yeah
just
started
so
not
much
more
to
she'll.
F
Yeah
so
I'm
gonna
do
the
chat
team
update
entirely
so
right
now.
So
what
we
plan
to
do
is
to
have
a
tribute
to
talk
as
our
hot
potater.
So
it's
the
thing
we
work
on
whenever
it's
our
turn
to
work
on
it.
So
right
now
we
have
to
check
the
contracts
and
the
designs
and
report
and
new
mismatches,
and
then
we
have.
We
are
King
on
the
list
of
top
priorities
that
the
chat
team
is
going
to
work
on
and
we
plan
to
work
on
them
as
MVPs.
F
So
the
ideas
we
will
work
on
doing
each
of
them,
like
90
percent,
that
there
is
just
some
polishing
left
to
do
to
try
to
fit
all
of
this
within
our
time
box
and
then
before
we
go
to
the
next
less
priority
items
we
do
the
polishing.
So
that's
so
far
how
we
plan
to
work
and
in
the
high-priority
features
we
put
damn
I
lost
the
page.
F
F
It's
the
in
app
notifications,
but
that's
like
its
mansions
and
we're
gonna
see
if
we
do
the
notification
design
that
is
proposed
by
chat
by
the
design
team.
So
the
idea
is
you
have
this
top
right
menu
item,
where
you
see
how
many
notifications
you
have
which
are
like
mentions
or
replies
to
your
posts,
some
kind
of
like
slack
I,
guess
you
know
this
menu
item
where
you
can
see
the
messages
that
mentioned
you.
F
It's
gonna
be
external
resources.
That's
why
I
want
to
do
it.
As
extension,
it's
like
Divi
Divi
cat,
because
I
think
to
do
image.
So
it's
it's
I
want
to
do
it
as
extension,
because
it
comes
with
the
warning.
You
know
you
cannot
now.
If
we,
if
we
do
extensions
for
a
service,
we
you
cannot
give
the
meta
data
protection
guarantees
of
whispering
on
that
stuff.
So.
C
B
A
F
B
A
E
B
A
B
B
A
D
We
just
need
to
nurture,
and
the
second
thing
that
we
were
working
on
quite
a
lot
on
its
Roman
was
working
quite
a
lot.
It's
on
slow,
sign-in
time.
I
just
hear
the
list
of
like
12
each
item,
and
there
are
only
two
left
on
it.
So
I
guess
like
today
we're
like
we
merged
like
two
or
three
pr's
and
then
yeah,
two
things
left.
A
So
we've
left
it
is
there's
been
that
two
main
things
I
mean
I.
Think
so
one
is
the
post
answer
of
introducing
a
Data
Sync
layer
on
discuss
and
Adam
s.
First,
some
sort
of
good
question
there,
some
discussed
in
there
we
go
on
this
week,
I
guess
the
general
idea
there
is
that
we
want
to
be
able
to
have
some
kind
of
rigorous
in-between
layer.
A
So
if
and
when
we
decide
to
move
away
from
whisper,
then
this
review
decouple
the
sort
of
pacing
stuff,
and
then
on
top
of
that
you
can
have
sort
of
more
interesting
semantics
and
it's
a
way
of
sort
of
distributing
State
among
your
peers
to
actually
care
about
it
and
yeah
I
mean
this
is
probably
to
go
through
the
post.
In
terms
of
how
do
we
look
like
in
sort
more
detail
now
we
can
introduce
gracefully
and
I
get
up
the
next
step.
A
There's
some
more
discussions
we
had
and
during
the
holidays,
I'll
try
to
sort
of
write
up
some
kind
of
proof,
concept
of
that
as
well
and
I.
Think
that
also
touches
on
some
into
things.
That
ego
was
talking
about
in
terms
of
all
this
state
that
exists
the
mail
service,
where
we
need
to
sync
them,
and
it's
kind
of
like
a
bit
messy.
A
So
the
message
wouldn't
just
be
lost
forever,
but
you
would
actually
keep
track
of
how
you
can
all
things
and
so
on,
and
on
top
of
that
you
can
sort
of
add,
more
performant,
sinking,
sinking,
em
effort
so,
for
example,
tribalist
dispersity
ways
of
communicate
with
blue
filters
like
what
message
you
have
available
which
she
can
provide,
and
that
happens
in
some
kind
of
group
context,
whether
it's
a
private
group
chat
or
101
or
public
fat,
and
then
you
can
sort
of
use
that
to
communicate
about
which
messes
you
want.
Yes,
that's
one
thing.
A
The
other
thing
is
we're
working
together
with
wavery
foundation
and
the
labs
and
now
more
collaborators
to
use
organize.
A
workshop
will
not
should
be
some
simpler
answer
of
this.
This,
like
this
possible
serving
mix
network,
that
we
have
stomach
research,
but
also
sort
of
trying
to
invite
people
from
need,
p2p
and
hopefully
get
some
people
from
seeker
missing
space
and
so
on
and
right
now.
The
proposal
for
that
is
end
of
January,
so
something
like
January,
9th
29th
until
February
1st
Umbra
assault
and
them.
A
A
G
Have
a
question
about
the
spate
of
May
server:
do
you
have
some
thoughts
on
how
you're
going
to
define
this?
This
is
state
because
the
message
they
you
can
tell
cannot
have
multiple
states
right
now.
Each
mail
servers
how
you
guarantee
that
all
of
them
have
the
same
state.
You
have
some
ideas
on
that.
H
State
of
my
servers
is
determined
by
just
looking
at
those
servers
had
like
pretty
much
IDs
on
the
messages,
and
so
what
we
do
right
now
is
this.
There
is
a
cross
check
between
holiday
service
that
we
have,
and
you
know
if
there,
if
we
detect
that
there
are
any
any
messages
that
we're
missing
from
one
May
server
but
available
others,
and
we
can.
We
can
sing
and
under
stay
between
them,
but.
H
More
advanced
data
structures
that
verify
the
order,
for
example,
and
the
number
of
messages,
because,
from
from
the
current
test,
it
looks
like
myself
a
super
consistent.
It's
only
happens
when
when,
for
example,
we
deploy
my
servers
and
it
happens
that
there's
a
bug
in
the
configuration
and
my
service
down
longer
than
the
TTL
for
our
messages
or
something
like
that.
Usually
when
they
are
they,
when
they
work,
they
just
make
normally
regular
without
any
interruptions.
They're
insane
click
all
the
time.
A
To
support
port-of-call
of
the
sort
of
dancing
thing
is
that
you
wouldn't
be
as
fragile
to
these
types
of
deployment
aspects,
so
you
could
abandon
that
the
Llanes
aleni
it
again
adhered
mail
service.
Hi
I
have
high
availability
in
order
for
them
to
be
useful,
so
they
would
be
more
like
normal
peers,
the
network
and
provide
themselves
at
least
I'd.
That's
idea
whether
that
works
in
practice
remains
to
be
seen.
Yeah
I.
H
Yeah
yeah,
because
the
one
reason
is
that
we
don't
still
know
if
you
want
to
keep
me
servers,
and
this
concept
seems
like
you
just
you
know
it's
just
not
really
correct
with
the
whole,
like
the
whole
principles
and
all
the
other
things
that
we
have
in
mind.
So
it's
still
not
pretty
confirmed
that
we
are
gonna,
stick
with
my
service
hosted
by
us
and
if
not,
then
we'll
just
try
to
figure
out
something
different.
So
that's
why
we
didn't
really
spend
a
lot
of
time
here
on.
H
You
know
like
figured
out
that,
like
how,
like
the
state
of
the
Mesa
service
between
all
them
and
trying,
you
know
to
figure
out
some
consensus
on
that.
So
now
that
that
was
not
in
scope,
and
that
was
just
just
small
work
to
make
sure
that
we
have
an
option
to
sing
my
servers
to
be
following
within
our
data
center.
In
case
there
are
some
issues.
G
I
I
Their
funds
have
been
allocated
among
different
pledges
and
plants
implement
you
know
who
their
different
delegates
are
among
pledges
and
just
kind
of
the
standard
sort
of
dashboard.
You
would
expect
in
order
to
be
able
to
make
better
decisions
in
a
funding
scenario,
so
that's
sort
of
where
I
stand
on
this.
A
A
This
pivotal
tracker
and
ideas
that
you
essentially
have
so
you
have
core
and
then
you
have
them
chat,
wallet,
tap
and
so
on
and
then,
for
example,
for
in
the
case
of
core,
you
track
both
sort
of
all
this
stuff,
improve
stuff
and
also
network
utilization
and
I.
Think
all
this
warm
it's
that
should
have
access
to
that.
If
you
don't
and
please
ping
ping
us
in
free
one.
B
D
B
B
A
A
But
the
idea
is
also
that
it's
you
can
get
this
in
Barca
invoke
team
has
been
using
it
very
sort
of
nicely
for
long
time
and
and
the
idea
is
I
mean
you
can
have
this-
you
certainly
sort
of
costs
and
you
estimate
how
complicated
they
are
and
and
then
you
get
some
kind
of
lost
2d
in
terms
of
estimates
and
so
on.
So
that
keeps
up
some
kind
of
global
state
and
some
awareness
of
how
long
things
are
going
in
and
try
ash
and
so
on.
D
D
B
A
Was
one
thing
you
can
do
that
we
talked
about
this
briefly?
Is
that
because
a
lot
of
people
are
going
off
on
vacation
first,
like
these
two
weeks
and
then
some
people
are
going
late
there
in
January
and
I
mean
you
can
set
this
essentially
how
much
of
the
team
is
available.
So
that's
my
somewhat
mitigated,
but
I
assumes
that
we're
updating
it
and
so
on.
Yeah
I.
A
E
So
I
guess
we
will
have
to
decide
what
we
want
to
do
with
that
and
then
in
parallel,
I
was
also
working
on
the
cable
extension
and
making
sure
that
all
the
necessary
bits
were
implemented
on
the
extension
side,
so
I'm
very
close
to
finishing
it,
but
I
still
have
something
to
fix
and
the
lower
lower
bits
are
lower
implementation,
details
of
extension,
so
I
guess
the
knob,
because
we
are
shifting
to
secure
market.
This
will
be
implemented
somehow,
but
probably
not
so
very
soon,
but
yeah
that's
pretty
much
it.
B
B
All
right
wallet
I'm
well
right
now
the
focus
is
on
on
getting
the
redesign
changes
tidied
up
and
merged.
So
you
know:
I
am
currently
working
on
wrapping
up,
basically
wallet
redesign
deaier,
necessary
items
on
the
on
the
plate
are
a
support
for
the
relevant
the
IPS,
namely
the
one
for
name,
validation
and
one
for
the
QR
codes
and
URLs.
So
yeah,
that's
that's
pretty
much
it
from
remind.
B
B
C
C
I've
also
been
talking
with
the
trail
of
its
team
to
see
what
their
security
checklist
guides
are
for
kind
of
unwrapping,
new
people
and
whatever's
not
present,
and
these
things
will
integrate
into
that
so
I'm
hoping
to
make
a
compendium
of
all
the
stuff.
So
you
can
see
and
kind
of
go
through
them
manageable
way,
so
it
doesn't
feel
a
little
too
overwhelming
right
now,
if
you
look
at
the
security
checklist
trying
to
get
through,
all
that,
you
know
in
a
short
timeframe,
seems
a
bit
overwhelming
I'm
trying
to
think
that
a
little
more
manageable.
C
A
C
Later
on
down
the
line,
I
just
want
to
make
sure
that
I
people
have
signaled
that
they
go
through
this
process,
so
that
I
have
and
I
like
more
likely.
I
might
have
to
sign
a
waiver
that
says
I've
gone
through
all
these
things
at
least
the
most
pivotal
critical
things
to
show
that
you're.
Taking
this
seriously,
we.
A
G
A
C
C
D
D
A
A
C
C
C
D
A
I
D
D
C
D
C
C
Of
that,
I
got
I,
got
some
chemical,
a
break,
oh
yeah,
I'm,
hoping
to
make
this
like
an
open
source
project.
This
is
something
that
I
talked
with
head
of
security
at
coinbase
about.
They
have
a
lot
of
internal
stuff
like
this,
based
on
the
things
they
have
to
monitor,
but
they
don't
want
open
source
it.
So
he
gave
me
some
ideas
on
how
they
make
it
and
I've
implemented
some
of
them
like
a
core
stuff.
So
far,.
C
I'm
hoping
to
build
a
simple
MVP
and
then
open
source
it
so
that
we
can
get
collaboration
across
other
people,
I'd
guarantee.
Other
people
will
want
something
like
this.
It's
just
a
matter
of
know
for
some
reason:
either.
No
one
shares
what
they're
doing
and
no
one's
built
it
they're,
just
relying
on
things
like
ether,
scans,
a
dress
watch
which
doesn't
have
very
good
resolution
on
what
you
can
watch
for.
B
J
Yep,
it
can
hear
me
great,
so
we
still
focused
on
block
Napier,
from
which
we
all
can
a
PR
firm
merge,
and
we
have
only
one
issue
left
to
be
fixed.
It
seems
it
should
be
used
by
wallet
team
and
in
order
not
to
write
for
other
possible
issues,
I'm
going
to
norge
a
pair
which
will
separate
our
known
issues
from
new
issues.
It's
not
possible
to
be
done
in
a
complete,
automated
wave
like
and
to
be
100%
sure
that
it's
not
an
issue
but
like
19%
cases
as
they
will
be
marked.
J
There
might
be
an
issue
when
new
issue
marked
as
non-issue
but
represent,
is
really
low.
So
after
emergency
spare
I
will
block
all
be
ours.
Without
with
no
past
tests
and
say
one,
you
won't
be
able
to
merge
them
and
in
order
to
merge
them,
you
will
need
to
just
run
those
failed
tests
to
run
so
no
need
to
run
whole
suite
each
time
and
the
all
the
stuff
you
did.
You
commented
purplish,
so
everyone
will
be
able
to
use
it.
J
C
G
D
G
D
B
A
D
And
for
some
reason
you,
like
you,
have
like
a
new
our
front
most
likely
force
a
mouse.
There
will
be
many
requests
to
it
at
the
same
time,
that's
one
of
the
reasons
and
the
second
one
is
that
we
also
really
request
some
stuff
when
you
minimize
their
funds,
restore
it
and
me
my
suppose,
you
can
just
go
to
task
switcher
and
go
back
to
there
and
it's
no
still
request
I
know,
but
I
guess
there
is.
C
B
A
B
D
B
C
C
C
D
C
E
E
So
yeah
I
just
wanted
to
raise
this
point
and
and
get
the
feeling
of
what
people
feel
think
about
it
and
how
we,
how
we
decide
in
general
those
things
know
if
we
want
to
to
decide
it's
kind
of
a
trade-off
between
security
and
privacy.
So
it's
not
super
clear
to
me
how
we
we
make
this
decision
as
an
organization.
D
D
Used
to
be
this
thing
that
used
to
be
loaded
images,
but
you
just
put
some
invisible
give
into
your
mail
message
and
this
points
to
it
into
your
in
this
way,
so
the
modern
male
clients
and
Gmail
just
download
this
image
separately
and
repost
it.
So
so
it's
possible
to
use
something
similar.
It
won't
be
a
decentralized
solution,
so
it's
like
you
can
always
make
a
rapper.
That's
cancel
the
headaches
from
the
API,
so
it's
not
possible
to
see
who
action
it
by
googling.
D
E
E
Yeah
so
I
mentioned
that
like
earlier
briefly,
but
essentially
with
you
pop
those
cookies
and
local
storage,
at
least
we
support
the
API.
But
then
this
information
are
not
persistent,
so
which
means,
if
you
restart
status,
you
essentially
you
your
cell
phone
from
scratch,
which
kind
of
defeats
the
world
point
of
I
guess.
But
that's
the
current
state.
G
E
G
G
E
So,
as
far
as
we
know
that
there
is
only
one
death,
at
least
from
the
depth
that
we
ship
part
of
our
catalog.
That
does
only
when
that,
let's
kind
of
rely
on
this-
and
this
is
the
one
you
that's
the
issue-
you
reported
Ricardo
and
related
to
the
ENS
manager-
that
which,
by
the
way
I
understand,
is
kind
of
deprecated
Depp,
so
yeah,
that's
kind
of
the
only
one
that
is
relying
on
that
and
breaks
because
of
this.
So
that's
kind
of
the
reason
why
we
don't
consider
it's
a
bigger
priority
here
for
now.
E
G
But
there
is
also
there's
no
I
do
not
use
it
cryptic
it
is
from
from
sometime
sometime,
but
when
I
use
it
it
every
time
I
open
the
app
I
had
to
make
a
login
again
they're
so
well
type,
my
password
to
give
a
signature
to
the
web
server
that
they
ruined
cryptokeys
I,
see
that
this
type
of
using
HRM
is
not
good
but
like
it's.
This
is
kind
of
legacy,
supported,
I,
guess.
A
A
E
Yeah
well
not
really
mostly
I,
wanted
to
raise
this
point
and
and
yeah
I'm
not
clear.
He
should
we
move
on
our
nuts
as
seen.
Yes,
you
know,
because
curry,
you
kind
of
know
is
in
favor
of
doing
that.
So
we'd
say
that
we
it
means
that
we
should
move
in
this
direction,
but
yeah.
It's
not
super
clear
to
me
just
know
how
to
decide.
There's
this
type
of
things.
A
C
E
D
Browsing
API,
there
is
version
before
then
actually,
when
you
just
download
encrypted
version
of
Safe
Browsing
lists
for
local
client
checks,
so
that
there
is
like
we
can
even
download
them
and
bundle
into
release
that
they
won't
compromise
on
security
or
privacy
because
stay
there,
local,
we
just
hash
the
URL
and
hook
up
in
the
JSON
file
or
whatever
they
provide.
So
so
it's
like
they
made.
It
promised
your
face
to
them,
because
unless
we
use
before
we
use
like
we
three
in
an.
A
One
of
the
most
important
things
is
to
document
this
document.
Enos
are
making
the
trade-off
very
explicit.
I
think
that's
that's
the
main
problem
we
had
in
the
past
because,
as
almost
Citra
it
of
is
explicit
and
and
documented,
we
can
always
sort
of
iterate
and
change
things
yeah
and
additional
research
we
can
do.
There
might
be
some
some
I'm,
not
sure
what
state
this,
but
I've
heard
some
for
some.
You
know
I'm
thinking
around
Safe
Browsing,
that's
it
more.
A
A
Would
you
go
to
see
your
questioner
on
governance?
I
mean
we
don't
have
any
super
formal
governance
model,
so
yeah
I
mean
these
course
and
I
mean
it's
like
it's.
Okay,
it's
in
the
trade-offs
page
right,
then,
if
you,
if
you
make
some
reasonable
trade-off
and
it's
documented
I
think
that's
that's
pretty
solid
right,
it's
it's
and
you
can
make
something
said
you
like
any
early
or
something
and
just
what
what
seems
right
to
you,
according
to
our
principle,
sense
of
how
you
how
you
weigh
that
I
think
that's
that
seem.
C
Think
it
should
be
documented
in
the
security
pages
of
the
docs,
so
like
I
could
maybe
make
like
a
part
of
the
section
of
the
security
page.
That
is,
you
know,
tech
decisions
we've
made
and
the
trade-offs
associated
with
them
like
have
you
know
what
we
do
and
how
and
how
we
do
them
and
the
trade-offs
associated
with
them.
So
if
you
just
start
making
these
things
that
these
documents
that
Oscar
is
talking
about,
we
can
start
just
placing
them
there.
A
So
right
now
we
have
this
and
we
have
to
swim
stuff
right,
that's
a
good
sort
of
start,
and
then
we
also
have
from
before
this
a
or
DS
I
think
they
should
probably
move.
So
a
better
place
would
be
the
dockside
where
that
could
be
like
a
dedicated
thing.
What
is
this
IKEA
decision
away?
We
talk
about
the
trade-offs
and
why
we're
choosing
security
over
privacy
in
this
specific
matter,
and
maybe
some
hit
some
link
to
research
or
whatever.
If
that's
something.
A
A
And
we
have
a
template
for
a
or
deist
I
think
we
can
use
that
I.
Don't
think
it's
too
different
from
I
mean
it's
a
soui
I
just
be
like.
This
is
a
trade-off
between
these
things,
but
in
a
sense
it's
essentially
some
index,
some
status
context,
decision
consequences
and
that's
it
and
I.
Think
just
writing.
It's
very
like
half
an
hour
writing
that
would
be
pretty
solid.
Okay,.
B
B
G
Think
that
I
was
recording
Tabuchi
talk
again
as
I
suggested,
as
that
we
could
use
a
capture
for
free
users
and
I
think
this
could
be
implemented
even
before
we
implemented
tribute
to
talk
so
captured,
don't
relies
on
any
API.
Basically,
when
the
user
doesn't
have
that
context,
it's
it's
least,
it
should
ask
the
it
for
a
capture,
so
the
culture
is
built
by
like
say
Alice
when
I
talk
with
Bob,
and
so
she
doesn't
have
Bob
a
require.
G
Probably
then
gives
a
capture
image
that
only
Bob's
know
the
solution,
so
Alice
needs
to
type
it
in
to
start
messaging.
Bob
I
think
that
this
could
go
I,
don't
know
how
it
would
be
to
implement
that
in
our
current
basic
circles,
but
I
think
this
doesn't
need
much
discussion
about
the
implications
of
valuing.
So
it's
a
more
simple
thing
to
do
is
much
straightforward.
G
G
G
G
Another
thing
while
state
OCS
is
implementing
the
integration
is
status.
They
notice
it
that
there
was
a
lot
of
lacking
lack
of
documentation
on
how
it's
how
it
works
internally,
to,
for
example,
to
our
public
chat
works
or
how
provide
chat
works,
and
this
I
think
also
would
help
with
security,
because
if
you
show
everyone
how
it
works,
people
can
easily
see
how
how
to
improve
it
and
I
also
would
know
it's
kind
of
important
because
of
stages.
Yes,
but
I
also
need
video.
C
It's
part
of
that
whole
document
section
secure
that
I
wanted,
like
you
know
this,
how
we
do
things,
what
we
do
and
how
we
do
them.
If
we
can
have
more
like
a
like
a
compendium
of
technology
that
we
use,
it
would
help
both
implementations
kind
of
understand
how
to
how
to
do
them
and
do
them
correctly.
It
work
the
same
as
well
was
show
people
the
decisions
we've
made
in
the
trade-offs
associated
with
them
and
then
essentially
how
to
fix
them.
If
there
are
issues
with
it
that
we
can't
do
that,
there's
no
documentation.
A
We
have,
we
have
a
thought
it's
nowhere
near
complete,
but
it's
the
in
terms
of
PFS
and
so
on.
So
I,
don't
know
you
guys
have
looked
at,
but
I
might
be
useful
and
maybe
I
think
it's
it's
not
completely
finished.
And
then
this
are
we
lacking
a
bunch
of
stuff,
as
you
mention
so
maybe
that's
something
that
could
talk
with
a
core
team
and
then,
as
you
Celsius
also
things
were
great
to
see,
pull
requests
to
the
doc
psych
as
well,
because
I
agree.
A
A
G
C
C
C
You
can
clearly
see
the
type
that
the
types
of
technologies
the
nation's
of
exactly
how
they
work
so
that
you
can
have
a
you
know.
You
understand
how
the
app
works
and
how
it
could
give
you
the
same
type
of
like
privacy
guarantees
that
they
that
they
give
and
I
would
like
to
do
something
similar
in
terms
of
like
these
are
the
technologies
we
use
because
how
they
work.