►
From YouTube: S3E20 | Anonymization and Pseudonymization
Description
We can't pronounce it at all, but we sure can talk about it. We've had anonymization around for a while, but pseudonymization is a mouth-full and a fairly new topic. In fact, it is so new we brought a guest on today's episode to help slaughter the word, while bringing light to the subject. Help reduce the clutter of your data while securing your patron's privacy. All this and Rogan Hamby. Whoops! I should have encrypted his name!!!
Contents:
0:00 - Title
0:27 - Intros
4:45 - Confidentiality
5:32 - Anonymization
13:51 - GDPR
23:56 - Pseudonymization
31:48 - Cleaning up Data
37:28 - Report to Find Old Data
Additional Resources:
https://github.com/northeast-kansas-library-system/nextkansas.sql/blob/master/R.003559.sql
Music: https://bensound.com/
Text -to-speech: https://wideo.co/text-to-speech/
Audio Effects: https://zapsplat.com/
Visual Effects: https://flexclip.com/
A
A
And
today
we
are
including
a
special
guest
Rogan
Hamby
from
Equinox
and
Rogan
is
going
to
talk
a
little
bit
about
anonymization
and
data
privacy
in
koha,
and
this
kind
of
grew
out
of
a
you
know:
I
met
Rogan
and
Christopher
Matt
Rogan
for
the
first
time
at
the
kohai
US
conference
in
Lawrence,
Kansas
last
fall
and
we
had
dinner
the
three
of
us
at
a
restaurant
here
and
we
talked
about
you
know
what
kind
of
things
we
could
get
Rogan
on.
This
show
to
talk
about
and
the
issue
of
anonymization
came
up.
A
C
Video
is
sponsored
by
koha
us
your
place
to
look
for
all
things
Quahog,
whether
you're,
just
starting
out
with
koha
or
you've,
been
with
Quahog
for
a
while
koha
us
is
a
great
place
to
find
resources,
learn
new
tips
and
techniques
or
connect
with
other
users
and
libraries.
Koha
us
provides
excellent
information,
both
original
and
curated
from
around
the
internet,
including
the
terrific
every
other
day
training.
Videos
you'll
also
find
several
special
interest
groups
to
connect
with,
as
well
as
our
general
monthly
meeting
Where
We
Gather.
To
talk
about
the
latest
poha
news.
C
You
should
also
check
out
the
koha
U.S
annual
conference
held
at
various
locations
around
the
U.S.
This
is
a
great
opportunity
to
meet
with
other
users
face
to
face
and
build
your
Kohan
Network,
as
well
as
new
friendships
and,
of
course,
don't
forget
about
the
great
presentations
koha.
Us
is
also
actively
involved
in
the
koha
community
by
contributing
towards
new
developments.
If
you
are
interested
in
contributing
towards
koha
U.S
funded
developments
join
the
Kohan
U.S
memberships.
C
Your
annual
membership
builds
the
funds
to
sponsor
new
developments
in
the
community
and,
as
a
member,
you
also
help
shape
koha
us
with
your
membership
votes
and
receive
a
discount
on
the
annual
conference.
You
can
also
contribute
towards
developments
through
a
direct
donation
or
by
purchasing
some
great
koha
us
merchandise,
through
our
threadless
accounts
visit
us
at
kohaus.org
to
find
out
more.
B
You
know
speaking
of
conferences
before
you,
you
continue
on
okay,
I
just
want
to
point
out.
We
have
a
conference
coming
up
in
September
and
we
opened
up
call
for
presentations.
So
if
you
have
great
ideas
for
presentations
for
the
conference
or
just
want
to
come
to
the
conference,
please
prepare
for
that
check
out
the
website.
The
kohaus.org
website
for
more
information
on
the
conference
we're
looking
forward
to
seeing
everybody.
Where
is
that
this.
A
A
B
A
E
A
A
Mostly
what
we
do
is
we
run
a
script
in
koha
that
deletes
data
I,
think
it's
called
clean
database
or
Purge
database
and
we
run
it
regularly
on
a
bunch
of
tables
and
I
actually
did
a
presentation
at
the
McKinney
conference
about
you
know
how
to
find
out
how
how
long
your
dad
is
being
stored
and
all
that
stuff,
but
there's
been
some
new
stuff
added
in
cohosh,
so
I
think
we'll
just
let
Rogan
talk
now
and
you
know
the
question
I
have.
Is
you
know
what
are
some
good?
E
E
E
If
you
don't
need
it,
and
so
what
are
the
first
things
I
find
that
when
people
start
talking
about
Anonymous
data
and
cohawk,
is
that
for
good
or
bad
koha
has
had
some
options
aimed
at
Patron
privacy
for
a
very
long
time,
but
they
were
not
truly
Anonymous
right
and
newer
features
that
are
really
nice
have
not
been
able
to
remove
those
because
of
the
need
to
maintain
backwards
compatibility.
So
there
can
be
a
lot
to
kind
of
piece
apart
and
deconstruct
in
that.
D
E
Id
absolutely
and
maintains
the
link
and
statistics
to
the
circulation
right
right.
So
you,
regardless
of
using
that
Anonymous
Patron,
which
will,
as
you
said,
anonymize
check-ins
as
well
as
suggestions
right
made
through
the
OPAC
you'd,
never
really
lose
that
information
and
it's
still
available
to
anybody
with
access
to
the
reporter.
So
it's
it
sounds
great,
but
it
from
a
from
an
actual
privacy
standpoint.
It's
not
very
useful,
and
it
also
has
some
behaviors
that
people
have
to
step
through
when
they
think
about
it.
E
When
you
set
up
your
Patron
categories,
you
can
set
their
defaults
for,
do
they
always
retain
it
do
does
it
become
Anonymous
on
check-in
or
another
one,
another
option
which
is
to
let
it
be
cleaned
up
by
a
Cron
job
that
can
be
sent
right
and
you
tell
it
what
interval.
But
then,
if
you
choose
I'm
trying
to
remember
the
option,
name
I
think
it's
OPAC
privacy.
E
A
E
E
I'll
also
throw
out
I
just
want
to
mention
that
opac's,
robust
ability
to
customize
through
JavaScript
and
CSS
is
really
nice
for
being
able
to
modify
the
intranet.
If
you
want
to
hide
certain
pieces
of
information
to
allow
say
certain
staff
less
access
to
Patron
information,
even
if
they
need
to
do
some
search
functions
right.
E
A
E
A
A
E
To
tell
anybody
to
do
anything,
yeah
I
will
also
mention
some
relatively
recent
changes
that
went
in
for
borrower
relationships.
There
are
system
preferences
that
allow
you
to
set
check
out
visibility
for
a
guarantor,
seeing
the
circulations
for
who
they
are
the
guarantor
for
for
and
to
see
the
fines
for
right
and
I.
Think
that's
really
nice
yeah.
A
The
laws
are
different
and
the
rules
are
different
and
the
library's
policies
are
all
over
the
place,
and
so
I've
got
some
libraries
that
use
I.
I.
Think
most
of
my
libraries
use
the
guarantor
guaranteed
relationships
here
and
we
have
them
set
up
so
that
they
can
optionally
choose.
If
the
adults
can
see.
You
know
what
is
what
is
with
the
guarantee
so,
but
I've
worked
at
a
library
in
the
past,
where
that
would
be
absolutely
100
forbidden
right
to
set
up
those
relationships
so.
E
Oh
good
idea,
you
read
my
mind:
I
was
gonna.
I
was
gonna
tangent
on
that
anyway,
the
gdpr
has
become
thrown
around
as
in
a
initialism
a
bunch,
and
it
stands
for
the
general
data
protection
regulation
if
I
ever
accidentally
say
General
data
privacy
regulation
some
for
some
reason
that
is
stuck
in
my
head.
But
that
is
wrong.
It
is
the
protection
regulation.
E
Now,
when
I
say
untested,
it's
well
tested
in
the
EU
people
comply
it
with
it,
they're
very
serious
about
it.
I'm
not
aware
of
a
EU
government,
suing
say
an
American
institution
or
Canadian
over
it
yet,
but
they
assert
that
they
have
the
right
to
so.
It
is
something
that
everybody
in
the
world
should
consider
and
they're,
not
alone.
China
has
laws
to
this
effect
as
well.
A
I,
actually,
you
know
I
wasn't
thinking
of
the
question.
What
is
the
gdpr?
Because
there
was
a
long
story
this
morning
on
NPR
when
I
was
taking
the
kids
to
school
about.
You
know
when,
when
this
airs,
when
this
shows
up
on
Youtube
it'll,
be
a
couple
weeks
in
the
past,
but
you
know
meta.
The
Facebook's
parent
company
was
just
living
a
huge
fine
this
morning
by
the
EU
for
violating
some
gdpr
issues.
So.
E
Yeah
and
you
bring
up
a
great
point-
I
didn't
think
of
that,
but
certainly
institutions
like
meta
Apple
Microsoft,
these
large
multinational
yeah
Global
entities
have
been
leveraged
fines
under
it,
which
is
fairly
straightforward
for
them,
since
they
also
have
operating
presences
within
the
right
yeah.
Now
our
local
library.
Obviously
you
know,
doesn't
my
local
library
here
in
Atlanta
Georgia
doesn't
have
a
branch
in
France,
so
that
limits
their
exposure.
But
in
theory
the
EU
says
that
they
must
comply
by
it.
E
But
that
is
untested
to
this
point
right
and
I
and
I.
Don't
want
to
go
into
detail
about
all
of
what
the
gdpr
says,
but
it
is
often
cited
as
one
of
the
most
comprehensive
sets
of
laws
for
personal
privacy
online,
and
it
is
something
that
in
the
United,
States
I
know
as
more
and
more
state
governments
are
beginning
to
look
at
privacy
concerns.
They
are
looking
at
the
gdpr
as
a
template
for
what
they
need
to
address.
E
B
E
According
to
the
gdpr,
it
does
now,
I
am
not
a
lawyer
I'm,
not
an
expert
on
international
law.
My
guess
would
be.
That
would
be
difficult
to
enforce,
but
I
am
assuming
that
with
all
the
minds
that
went
into
it
with
their
knowledge
of
international
law
that
they
would
not
have
put
that
language
in
if
they
didn't
think
they
could
for
something
important
enough.
E
E
A
E
A
E
A
E
Blocker
and
something
I
would
be
curious
to
see
if
a
library
is
done
if
anybody's
watching
this
has
done.
This
I'd
be
curious
to
hear
about
your
experience,
I've
always
kind
of
imagined
that
people
might
set
it
to
a
permissive
mode
for
an
interim
period
as
they're
moving
to
it
with
an
intention
of
then
moving
to
enforced
at
a
later
date.
E
E
And
then
obviously,
there's
an
option
for
linking
to
an
external
privacy
policy
right
which
just
nice
to
have
but
not
critical
for
the
software
operation,
and
then
you
have
the
subscription
options
now
something
that
people
have
to
understand
that
as
part
of
the
gdpr,
it
is
very
much
an
opt-in
set
of
regulations.
You
have
to
opt
in
to
allow
other
people
to
use
your
data
and
that's
what
these
bottom.
This
bottom
option
is
about
that
once
this
is
enforced
as
a
software
option.
E
A
E
A
E
A
D
A
Good
six
months
investigating
it
and
figuring
out
how
to
how
to
do
it,
what
they
wanted
to
do
and
how
they
wanted
to
word
their
policy.
It
was
not
the
kind
of
thing
that
they
just
slapped
something
together
and
stuck
it
on
there
overnight,
and
they
really
made
a
there's
a
group
effort
to
sit
down
as
an
organization
and
figure
out
how
they
wanted
their
privacy
policy
to
read.
A
E
Think
sometimes
libraries
get
blindsided.
You
know
some
level
of
governance
over
them,
whether
it's
a
municipality
or
a
county
or
a
state
suddenly
passes
a
law
that
they
didn't
know
was
heading
through
to
approval
and
then
they're
suddenly
informed
by
somebody
that
they
have
to
comply
with
these
privacy
rules
and
they
weren't
prepared
for
it,
and
then
things
happen
very
quickly
because
they
have
to.
But
it
creates
chaos
because
they
have
not
had
time
to
do
that
six-month
process
of
sit
down
and
evaluate
what
do
they
want
to
keep?
E
E
E
The
truth
is
that
the
Anonymous
patrons
stuff
still
leaves
outside
of
the
circulation
history
table
all
that
information
and
other
places.
Like
statistics,
you
can
delete
patrons,
but
they
still
exist
in
another
part
of
the
database.
So
while
the
anonymous
stuff
helps
at
least
sort
of
at
a
superficial
level,
it
doesn't
actually
make
anything
Anonymous
now,
pseudo-anonymization
yeah
I
want
to
talk
about
briefly,
and
that
is
in
another
section
of
the
system.
Preferences
I
believe
under
security
and
I
will
warn
up
front
that
this
pseudo-anonymization
is
additive.
E
E
E
E
So
it
is
a
very
strong
good
form
of
security
and
the
reason
they
do
pseudo-anonymization
of
some
of
that
data,
like
the
borrower
number
to
identify
who
did
a
circulation,
is
so
that
you
can
still
tell
things
like
distinct
borrowers
who
checked
the
materials
out
the
count
of
them
find
patterns
in
the
data.
How
many
borrowers
of
a
certain
Patron
category
checked
out
certain
kinds
of
materials?
You
can
still
do
that
analysis
without
actually
being
able
to
say
hey.
Bob
Smith
checked
out
this
book
on
this
topic.
E
E
B
So
in
pseudonym,
anonymization
boy,
I'm,
gonna
Slaughter
pronouncing
pronouncing
this,
does
it
retain
necessary
links
for
things
like
fines
and
Patron
history
that
patrons
want
to
retain?
Does
it
maintain
that
last
borrower
link
for
libraries
that
need
to
be
able
to
go
back
at
least
a
patron
when
necessary
for
a
certain
amount
of
time?
Does
it
does
that
function
still
exist.
E
Not
in
those
status
the
this
data
that
pseudo-anonymized
is
going
to
be
useful
for
creating
aggregate
information
for
reports
to
governing
entities
for
annual
reports
to
the
to
say,
imls
collection
development.
But
it's
not
going
to
be
useful
for
identifying
who
did
what
now
there
are
some
options
for
what
information
you
retain
and
there
is
information
about,
there's
a
whole
sort
of
checklist
under
that
system:
preference
that
kind
of
pops
up
when
you
activate
it
and
says.
Okay
here
are
some
check
boxes
and.
E
The
following
fields
for
patrons
and
for
transactions-
and
this
is
where
those
initial
questions
I
said:
what
data
do
you
need
to
keep?
That's
where
that
discussion
becomes
useful
here
now
on
the
transaction
itself,
there's
not
a
whole
lot.
That
I
would
consider
dangerous
to
keep
I
think
you
could
keep
pretty
much
all
of
that
and
there's
not
a
concern.
E
But
when
you
look
at
the
patron
information,
especially
things
like
gender
Library,
I'm,
actually
kind
of
surprised
to
see
gender
here,
I
thought
that
was
removed
from
default
from
koha
a
while
ago,
but
it
information
like
City
ZIP
code
information
like
gender.
It
is
shockingly
easy
to
identify
people
by
those
sets
of
information.
E
A
B
A
I
can
see
that
if
you
can
save
this
data
separately
and
Purge
it
at
a
different
rate
than
you
can
statistics,
then
what
you
can
do
is
you
can
start
purchasing
yours
right
now,
I
think
we
have
our
statistics
I.
Think
we
keep
that
data
for
25
months
so
that
we
have
two
years
of
data
yeah
and
then,
but
then
with
this.
A
D
E
Which
runs
in
cron
now,
a
lot
of
cohort
mins
are
going
to
be
very
familiar
with
this.
Maybe
cohort
administrators
don't
think
about
it.
So
much
administrators,
in
this
case,
meaning
administrators
of
cohort
libraries,
not
of
the
software
Library
directors
and
heads
of
Public
Service
things
like
that,
but
the
just
to
kind
of
give
a
brief
overview
of
what
it
does
for
those
folks
is.
E
So
you
can
say:
hey
I
want
messages
more
than
this
many
days,
purged
I
want
to
delete
transactions
more
than
x
number
of
months
old
I
want
to
remove
logs,
which
is
another
source
of
privacy
that
people
often
forget
I
want
to
remove
these
particular
logs
after
X
amount
of
time.
It
has
a
whole
bunch
of
options,
I'm
not
even
going
to
try
to
go
through
them,
we'd
be
here
a
while,
and
it
does
break
out
pseudo-anonymizations
into
a
separate
category.
E
Now,
if
you've
really
tightened
down
on
pseudo-anonymizations.
Well,
it's
probably
not
dangerous
to
retain
them
for
a
very
long
time,
but
you
can
absolutely
set
them
up
to
remove
on
a
different
schedule
than
the
other
things.
And
it's
really
through
this
cleanup
database
script
and
removing
old
entries
from
statistics
from
Circ
transactions,
and
things
like
that.
A
B
So
I
would
assume
like,
for
example,
George
you've.
You
said
that
you
hold
on
to
statistical
information
for
25
months.
I
would
assume
that
when
you
turn
the
pseudo
Nana,
the
pseudonym
on
that
that
you
would
probably
wait
for
that
25
month
period
before
you
start
maintenance
on
your
statistical
logs
differently
than
what
you
do
currently
so
that
you
have
that.
That's
that
same
range
building
up
to
refer
back
to
before
you
completely
switch
over.
A
That
would
probably
make
sense.
Yes,
I
would
probably
it'd
probably
be
best
to
have
that
much
backup
data,
the
thing
about
the
way
that
you
know,
one
of
the
reasons
I
feel
comfortable
with
only
keeping
that
much
data
is
because
you
know,
they're
statistics
is
the
data.
We
keep
the
longest
all
the
issues
and
old
issues.
We
keep
much
I.
A
A
Catalog
historical
data
was
saved,
so
we
lost
a
bunch
of
data,
but
we
have
data
now
going
back
to
2016.
That's
pretty
good.
I
do
have
I'm
putting
a
link
in
the
chat
box,
so
Christopher
can
find
it.
That's
a
report
that
I
wrote
that
will
let
you
what
it
does
is
it
it
looks
at
every
if
anybody
out
there
is
interested
in
it.
A
E
B
A
That
is
awesome
yeah.
This
is
a
lot
of
what
we
talked
about
here
is
stuff
that
I
did
in
a
presentation
at
the
McKinney
conference
remotely
from
my
house
here
in
Lawrence,
so
we've
this
is
a
lot
of
stuff
that
I've
been
interested
in
for
a
long
time
and
so
learning
a
little
bit
more
about
this
pseudonymization
is,
is
hopeful
here,
I.
B
Think
that's
I.
That's
really
useful
because
you
know
we're
going
through
some
organization
change
here
to
kind
of
tighten
up
our
databases
and
you
know
clean
up
things
and
you
know,
while
we
have
thought
of
certain
tables
that
certainly
could
be
cleaned
up
after
you
know
over
time
you
know
initially,
when
we
moved
over
to
Quahog,
our
deleted
patrons
table
was
just
growing
and
growing
and
growing.
We
didn't
do
anything
with
that
and
even
our
Patron,
you
know
just
our
Patron
database.
B
We
let
patrons
expire,
but
those
expired
patrons
stayed
in
there
forever
and
ever
and
ever
and
as
you
know,
one
that
was
looking
at
our
statistics
and
Gathering
that
information
for
our
director
each
month.
I
was,
you
know.
I
came
to
this
realization,
hey.
You
know
this
piece
of
information
about
how
many
patrons
we
have
isn't
serving
us,
because
we
don't
know,
you
know
what
you
know
it
really
doesn't.
You
know,
show
us,
you
know
how
many
patrons
we
truly
have.
B
You
know
because
we're
not
looking
at
you
know,
non-expired
patrons
we're
just
looking
at
how
many
people
are
in
our
tax
group
and
right.
That
number
just
grows
and
grows
and
grows,
and
so
I
I
had
to
make
the
hard
choice
of
telling
our
Consortium
hey.
We've
got
to
delete
this
information.
You
know
if
they've
been
expired,
why
are
we
holding
on
to
them?
They
are
not
pertinent
to
our
data
anymore,
and
so
we
looked
at
that.
B
We
decided
okay,
well,
we
expire
patrons
after
two
after
two
years,
and
so
it's
reasonable
to
say,
okay,
we'll
hold
on
to
that
expired
Patron
for
two
years.
In
case
they
come
back.
You
know,
because
we
are
a
vacation
in
town
they
may
come
back
after
a
year
or
so
and
re-up
their
account.
So
we
hold
on
to
that
expired
Patron
for
two
years
and
anything
beyond
that
we
purge,
and
so
it
was
a.
B
It
was
a
a
painful
thing
to
watch
for
our
directors
when
that
number
just
went
when
we
decided
to
do
that
initial,
Purge
and
and
month
by
month.
We
we
maintain
that
and
clean
up
that
that
database,
but
yeah
I
mean
you've
got
you
know,
that's
just
a
small
portion
of
the
tables
where
we're
holding
on
to
data,
and
it
would
be
great
to
see
all
the
tables
that
are
holding
on
to
stuff
from
the
beginning
and
get
that
cleaned
up
where
we
can
yeah.
A
Just
never
expired
or
they
did
expire,
but
they
were
still
in
the
system
and
they've
been
migrated
from
Once
from
one
system
into
koha
and
so
of
all.
The
total
number
of
cards
issued
in
Dairy
that
we're
still
in
the
cat
that
were
still
in
the
ILS
amounted
to
140
percent
of
the
people
that
lived
in
that
zip
code.
So
that.
D
A
B
If
you,
if
you
never,
if
you
don't
Purge
this
stuff,
I
mean
it's
like.
Okay,
you've
got
this
number
building
and
building
building.
It's
not
telling
you
anything,
and
now
that
we
purge
this
information,
this
old
information.
Now
we
can
actually
see
some
living
data
that
that
right-
and
we
can
say-
oh
look,
our
you
know
our
number
of
active
cards
or
our
number
of
cards
that
that
we
have
in
our
area
are
actually
going
down.
Why
is
that?
And
we
can
actually
analyze.
B
That
you
know
rather
than
oh
it's
just
this
number,
that's
screwing,
it's
like
well
yay.
Our
numbers
have
built
I
can
do
that
artificially
and
it's
like
right,
nothing.
You
know,
you
know
it's,
it's
like
our
our
door
counts.
You
know
our
door
counts
are
living
numbers.
You
know
we
we
see
how
often
people
are
you
know
ebbing
and
flowing
through
the
library,
and
now
we
can
see
how
often
you
know,
people
in
the
city
are
actually
participating
with
the
library
and
that's
much
more
useful.
D
E
E
E
A
D
E
Yeah
I
think
those
are
the
major
points.
I
think
something
that
would
be
useful
for
the
community
in
the
future
is
a
sort
of.
If
you
want
to
be
fancy,
you
can
call
it
a
white
paper.
If
you
want
to
be
more
practical
call
it
a
set
of
best
practices.
Yeah,
we
publish
on
the
wiki
for
how
to
set
these
things
up.
B
B
It
would
be
a
a
great
guideline
for
those
of
us
that
have
koha
or
those
of
us
thinking
to
use
koha,
especially
you
know,
people
that
are
shopping
around
for
an
ILS.
It
would
be
good
for
them
to
see
just
exactly
what
you
know
it's
capable
of
so
that
they
can
make
a
better
a
more
informed
decision
about
an
ILS
yeah.
E
Right
and
I
work
with
migrating
libraries
a
lot
for
those
who
don't
know
what
a
data
analyst
does
in
this
context,
I
migrate,
libraries
into
Coba
a
whole
bunch.
In
fact,
I'm
working
on
I
think
six
right
now
and
it's
a
big
process
for
them.
It'd
be
great
to
have
something
to
say:
you
don't
have
to
decide
this
day
one,
but
when
you
get
to
it
and
things
settle
down
a
little
bit
start
thinking
about
your
privacy
options.
Here's
something
to
start
with
great
cool.
B
So
yeah
thank
you,
Rogan
for
sharing
with
us
today.
Your
your
expertise
in
this
area.
I
I,
know
that
this
is.
These
are
some
things
that
we
want
to
look
more
into
and
and
explore.
You
know
we
value
our
patrons
privacy,
and
you
know
I
know
that
you
know
we
have
a
certain
level
of
privacy,
but
I
know
that
there
are
areas
that
we
could
certainly
tighten
up.
So
I
appreciate
you
sharing
what
what
you
know
and
and
if
anyone
watching
this
video
has
any
questions.
B
If
there's
something
that
we
didn't
talk
about
or
you
have
more
questions
on,
please
you
know
you
can
find
our
videos
on
our
website
at
the
kohan-us.org,
but
you
can
find
our
videos
also
on
our
YouTube
channel
at
youtube.com
forward.
Slash
koha
us
no
dash
and
you'll
find
all
of
our
playlists
there,
including
these
training
videos
and
please
like
And,
subscribe,
so
that
you
will
be
notified
when
we
have
new
videos
but
comment.