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

Notifications not delivered for user pings in comment threads #1475

Open
cellio opened this issue Dec 8, 2024 · 5 comments
Open

Notifications not delivered for user pings in comment threads #1475

cellio opened this issue Dec 8, 2024 · 5 comments
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working

Comments

@cellio
Copy link
Member

cellio commented Dec 8, 2024

meta:291852

A user made a post and is thus automatically subscribed to comment threads. The user received notifications for new comments except if those comments included @-mentions of the user -- exactly when we would want to prioritize a ping. We did some testing (see the comment thread on that meta question), and the user did not receive any ping for a new comment if it pinged that user. Ping-less comments continued to deliver notifications.

@cellio cellio added area: ruby Changes to server-side code type: bug Something isn't working priority: medium complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Dec 8, 2024
@trichoplax
Copy link
Contributor

Do we have a defined list of things that pings should be expected to do?

If you are following a thread (either automatically through being the author of the thread or post, or due to manually following) then you should be notified of every comment. If you unfollow a thread then you should not be notified of any comments. If you have never followed a thread you should not be notified of any comments.

Is there reason to expect mentioning a user to override any of those behaviours? If I am already being notified, presumably the mention should have no further effect, and is simply to inform anyone reading the thread that the comment is aimed at me? If I unfollow, should a mention be able to override that? I assume a mention cannot ping someone who has no relationship with the thread (has never followed), but is there the expectation that people who unfollow can still be reached with a mention?

It seems it might be useful (whether in this issue or another) to make 2 things explicit:

  • When a user unfollows, inform them that they will / will not be notified when someone mentions them.
  • When someone mentions a user who has unfollowed, inform the mentioner that the mentionee will / will not be notified by it. This might make a user's following status sometimes public - is this a concern?

@cellio
Copy link
Member Author

cellio commented Dec 8, 2024

I agree: if you're following, you should receive all notifications. It sounds like we have a bug where some are not delivered.

If you've never participated in a thread (and aren't the post owner), you're not supposed to be pingable. I don't know what happens if you would have been pingable but you unfollowed -- does your name show up in red if someone tries to ping you, like would be the case for an uninvolved user? Something to investigate. I agree this reveals your following status and that might not be desirable. Sounds like we need to work out what behavior we want for the unfollow case and then maybe make changes. Meanwhile, we seem to have a bug in the follow case.

@trichoplax
Copy link
Contributor

Yes I agree the specific bug raised here should be fixed without waiting for the discussion around people who have unfollowed. I just wanted to quickly mention it while I thought of it, but this might not be the right place.

@cellio
Copy link
Member Author

cellio commented Dec 8, 2024

It's a good catch, one I hadn't thought about before -- thanks for raising it! Now to make sure it doesn't get lost...

@trichoplax
Copy link
Contributor

Hopefully that should help keep track of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants