Bug 1898896 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I am opening this space as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

Make the setting not per-contact but per address book (AB):
Add a checkbox _**"prefer display name over message header"**_ to each AB.
(This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
By this means, users can move exceptional contacts with dynamically changing display name in a separate AB, which can be set no to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
I am opening this space as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

* Make the setting not per-contact but per address book (AB):
  Add a checkbox _**"prefer display name over message header"**_ to each AB.
  (This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
  By this means, users can move exceptional contacts with dynamically changing display name in a separate AB, which can be set no to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
I am opening this space as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

* Make the setting not per-contact but per address book (AB):
  Add a checkbox _**"prefer display name over message header"**_ to each AB.
  (This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
  By this means, users can move exceptional contacts with dynamically changing display name in a separate AB, which can be set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
I am opening this space as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

* Make the setting not per-contact but per address book (AB):
  Add a checkbox _**"prefer display name over message header"**_ to each AB.
  (This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
  By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
I am opening this space as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

* Make the setting not per-contact but per address book (AB):
  Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).
  (This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
  By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
I am opening this bug as a place to collect ideas for replacement of the per-contact setting _"prefer display name over message header"_ given its [planned](https://thunderbird.topicbox.com/groups/planning/Tec65c7b3d9001140) retirement discussed in bug 1894048.

Due to the planned switch to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

I don't have a brilliant idea, but one possible solution is:

* Make the setting not per-contact but per address book (AB):
  Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).
  (This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).
  By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

If you have other ideas, please add them in the comments below.
## problem
Due to the switch discussed in bug 1894048 from the per-contact setting _"prefer display name over message header"_ to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

## 💡 suggested solution / feature request

Make the setting not per-contact but per address book (AB):
Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).
(This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).

## benefit
By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.
## problem
Due to the switch discussed in bug 1894048 from the per-contact setting _"prefer display name over message header"_ to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

## 💡 suggested solution / feature request

Make the setting not per-contact but per address book (AB):
Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).
(This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).

## benefit
By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

## mockup
see comment #1
## problem
Due to the switch discussed in bug 1894048 from the per-contact setting _"prefer display name over message header"_ to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

## 💡 suggested solution / enhancement

Make the setting not per-contact but per address book (AB):
Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).
(This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`).

## benefit
By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

## mockup
see comment #1
## problem
Due to the switch discussed in bug 1894048 from the per-contact setting _"prefer display name over message header"_ to a single global setting, users who globally _"prefer display name over message header"_ will lose the current ability to make exceptions for senders with dynamically changing display name, such as
* friends who use it as a social media status update
* mailing lists
* multi-author tools (github, JIRA, Phabricator, etc.) which use the display name to specify the author
* other exceptional cases

## 💡 suggested solution / enhancement

Make the setting not per-contact but per address book (AB):
Add a checkbox _**"prefer display name over message header"**_ to each AB (*see design mockup below*).

This would come both instead of a checkbox on each contact and instead of a global preference in `tools > settings`.

## benefit
By this means, users can move exceptional contacts with dynamically changing display name in a separate AB set NOT to _"prefer display name over header"_, while activating this option on other ABs as they wish.

## mockup
see comment #1

Back to Bug 1898896 Comment 0