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.

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

Make default notification setting for conversations 'mentions only'. #2649

Open
wants to merge 1 commit into
base: unstable
Choose a base branch
from

Conversation

ianmacd
Copy link

@ianmacd ianmacd commented Jan 14, 2023

The current default of 'all' is very noisy, especially when restoring an account or linking a new device, which causes all instantiated conversations to start sending notifications.

Contributor checklist:

The current default of 'all' is very noisy, especially when restoring an
account or linking a new device, which causes all instantiated
conversations to start sending notifications.
@KeeJef
Copy link
Collaborator

KeeJef commented Jan 18, 2023

As you mentioned in your explanation, the main annoyance here is when restoring/linking a device from seed, i agree with this annoyance. But i think we can probably tackle this issue by writing some custom logic which suppresses notifications while we are restoring an account. Changing the default here i think is a little heavy handed.

@ianmacd
Copy link
Author

ianmacd commented Jan 18, 2023

As you mentioned in your explanation, the main annoyance here is when restoring/linking a device from seed, i agree with this annoyance. But i think we can probably tackle this issue by writing some custom logic which suppresses notifications while we are restoring an account. Changing the default here i think is a little heavy handed.

Personally, I think it's the default behaviour that is heavy-handed.

It's not just account restoration and device linking that poses a problem. Why would anyone want to receive a notification for every single message posted to a (busy) open group, for example? Regular readers of a given open group will catch up on its postings as a matter of course. They don't need to be alerted to every new posting.

Perhaps there needs to be a different default notification setting for open groups than for 1-to-1 conversations and closed groups.

In private conversations, a more aggressive notification policy makes more sense. In an open group, it's superfluous and quickly becomes an irritant, and this is only exacerbated by the absence of any synchronisation of conversation notification status across clients. The first thing I have to do when linking any new client is individually configure all of the conversations to stop blasting me with notifications. And I don't mean the initial burst, either. I mean the ongoing notifications from each new posting throughout the day.

@KeeJef KeeJef added the Jira This ticket is being tracked in Jira label Mar 28, 2024
@KeeJef
Copy link
Collaborator

KeeJef commented Mar 28, 2024

Tracking the resolution of the link a device / restore a device spam issue internally here https://optf.atlassian.net/browse/SES-1664

@Bilb Bilb changed the base branch from clearnet to unstable September 30, 2024 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Jira This ticket is being tracked in Jira
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants