Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow grouping of messages based on email and name #1194

Open
struan opened this issue Sep 23, 2016 · 0 comments
Open

Allow grouping of messages based on email and name #1194

struan opened this issue Sep 23, 2016 · 0 comments
Assignees
@mhl
Labels
in progress

Comments

@struan
Copy link
Collaborator

struan commented Sep 23, 2016

At the moment the /from/ page only uses email on to group messages from the same person on one page.

In some circumstances it may be useful to group based on name rather than email to avoid it being obvious that a set of messages were all sent by the same person.

We should provide an option to group by name and email for such circumstances. (We need both to stop people with the same name but different emails being grouped together)

This option should be off by default, and possibly not exposed in the admin interface as in most cases grouping by email is the correct thing to do.
mhl added a commit that referenced this issue Nov 15, 2016
@mhl
Add an instance config option for stricter anonymity
ff808d6 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
@mhl mhl mentioned this issue Nov 15, 2016
Merged
@mhl mhl self-assigned this Nov 15, 2016
mhl added a commit that referenced this issue Nov 15, 2016
@mhl
Add an instance config option for stricter anonymity
96f3d91 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
mhl added a commit that referenced this issue Dec 2, 2016
@mhl
Add an instance config option for stricter anonymity
92a583b 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
mhl added a commit that referenced this issue Feb 9, 2017
@mhl
Add an instance config option for stricter anonymity
3167509 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
mhl added a commit that referenced this issue Feb 9, 2017
@mhl
Add an instance config option for stricter anonymity
a426206 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
mhl added a commit that referenced this issue Feb 9, 2017
@mhl
Add an instance config option for stricter anonymity
8c71f40 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes #1194
mhl added a commit to mysociety/writeinpublic that referenced this issue Sep 28, 2017
@mhl
Add an instance config option for stricter anonymity
83f9c46 
There is a view ('all-messages-from-the-same-author-as') which, given a
message slug, allows you to list any other messages with the same author
email address as the message with that slug. In situations where anonymity
is important, this is undesirable - someone might send a sensitive message
with a false name and an uncontroversial one with their real name, in
which case this view would reveal that they're sent by the same person.

This commit introduces a new instance config option
('email_and_name_must_match') which means that the
'all-messages-from-the-same-author-as' view will only show messages that
have the same author_email *and* author_name, to avoid this information
leak.

Fixes mysociety/alpaca#35
Fixes ciudadanointeligente#1194
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhl mhl

Labels
in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@struan @mhl