Notification doesn't hide when user posts in a topic and the topic gets moved to a private category

סיכום מבוסס בינה מלאכותית

A user reported confusion after receiving notifications for a topic that was moved to a private category they couldn’t access. Chaboi_3000 confirmed the issue occurs when a notification is generated before the topic is recategorized — the user still sees the notification despite lacking access, leading to frustration. simon reproduced this behavior, noting the notification remains visible until the user logs in, at which point clicking it leads to an access-denied page. Chaboi_3000 shared the user’s detailed timeline, showing repeated notifications for inaccessible content. They proposed hiding such notifications when topics are moved to private categories Chaboi_3000, but codinghorror argued the notification was valid when sent and shouldn’t be hidden. codinghorror attributed the confusion to staff actions — specifically, a TL3 member moving a topic to a restricted #lounge category without warning. Chaboi_3000 clarified it wasn’t a moderator but a TL3 user acting independently, and noted they’ve since added an apology note to explain the category changes. jtbayly reported a similar issue on their site. codinghorror acknowledged the TL3 context but noted such category usage is rare. Chaboi_3000 joked TL3 members are overly fond of their lounge. codinghorror concluded this is primarily a culture issue, not a software bug, and shouldn’t be fixed in code.

Full quote of user:

After seeing a topic and reading and checking it, it was marked as “watching” for me,
after that it has been moved to a category i don’t have access to, but still recieved notifications of edits/posts inside, which was confusing as i had no access to that topic anymore.
So one thing to improve could be (so confusion like that wouldn’t occur)
to have notifications check if that user still has access to it and if not, ignore possible notifications.
(believe me, it’s really confusing, especially if the user experiencing it has no idea what’s going on)

I have only been able to reproduce this if the notification is generated before the topic is recategorized. For example, a user is watching a topic that receives a new post. After the new post is created, the topic is then recategorized to a category the user doesn’t have access to. The next time the user logs in, they will receive a notification about the post that was created before the topic was recategorized. If they click on the notification, they will receive the “Sorry, you don’t have access to that topic!” page.

Is it possible that this is what was happening with the user on your site?

Yes. That’s probably it. Since I was a moderator, I couldn’t check it.

Another update from the user about what exactly happened:

Ok, I’m going to rename this topic so it makes more sense. A fix to this is to hide the notification when the topic is moved to a different private category.

Why would the notification hide? It was valid at the time it was sent.

Wouldn’t hiding it be better than confusing users with the “inaccessible” topic notification?

I think your moderators are doing confusing things, and the software is manifesting the results of those confusing decisions.

If you force a topic into a hidden category you will need to let the users involved know what to do, rather than just yanking the rug out from under them with no explanation. That’s the job of staff.

It wasn’t the moderators, it was one of those “careless” TL3 members who tried to handle the “bad-post” themselves by moving it to the #lounge category and pinging the moderators. I’ve reminded that user to use flags instead to avoid confusion.

After that “incident”, I’ve made a little apology note (Even though that TL3 user should’ve done it :disapproval:) about why the category was being moved around.

I’ve got a user reporting a notification he can’t get rid of on our site. I wonder if this is why.

Aha this makes more sense as a TL3 event. Thanks for explaining. Still, it is rare to have a category only visible to TL3 that is actively in use, even rarer to have TL3 people actively moving topics into that category.

I think the TL3 people are waaaay too proud of their lounge category, they put anything in there.

This is a culture thing first and foremost, not really something to be addressed in software.