[bug] Subscription notifications are treated as mentions #656
Backend 3.10.4-1-gebfb617b, Frontend e7a558a
What were you trying to do?
The bell next to the Following! button, labelled as "Subscribe", enables receiving a notification for a user's posts. On Mastodon, these notifications are treated separately as "New Post" notifications, which can be filtered out in the frontend. I used this extensively to ensure I see posts I care about, but hide them occasionally to be sure I'm not missing any real notifications in the noise. It also is presented in a unique way to separate them visually, and reduce their importance compared to notifications directed towards you.
What did you expect to happen?
Notifications from subscribing should be treated uniquely, and be able to be filtered out like any other notification type.
What actually happened?
Notifications from subscribing are treated as mentions, even in frontends that make the distinction like Tusky. This makes it impossible to separate them from real mentions, increasing the odds of missing them in the noise. This is most obvious in the Interactions page, where new post notifications are placed in the mentions tab. It's also obvious if you disable mentions in the column filter.
I cannot use it as easily as I'd like
Have you searched for this issue?
- I have double-checked and have not found this issue mentioned anywhere.
wahay it happened again
sorry it just always amuses me when I implement something, masto gets inspired and implements it years later, and then my version gets a "bug" report because masto did it differently
happened like 4 times now, subscriptions were like one of my very first contributions to og pleroma like 5 years ago
I'll take a look though
Perhaps a bug report wasn't precisely correct, but in my defense, receiving them as mentions seems very confusing, considering... well, they aren't mentions. When I told nano, she actually insisted it was likely a bug, even though it seemed to me like deliberate implementation. It isn't just Mastodon, Twitter had the same feature and those notifications were also distinct. I wanted to check if Firefish does it too, but the only person I know that uses Firefish just... didn't respond to me? And I was very eepy and wanted to go sleeby deeby so I just posted the issue.
When I told nano
yo whats up ~w~
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?