You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on the GlitchSoc mastodon instance I am on (v4.3.0-beta.2+glitch), there is no option to disable grouped notifications. I looked under the gear in the notifications tab, as well as in the "app settings" menu and "preferences" page, and saw nothing regardless of if i used "advanced" view or not. And when multiple people star something they still get clumped together.
Is this fixed already in the current codebase? Or maybe intentional? Or some sort of caching that will resolve itself?
Sorry if this is the wrong place to report this or i didn't provide information you needed.
The text was updated successfully, but these errors were encountered:
It was possible to opt in or out of grouped notifications when they were in early testing, but grouped notifications are the only maintained interface going forward.
It was possible to opt in or out of grouped notifications when they were in early testing, but grouped notifications are the only maintained interface going forward.
that's a shame. about half the people i follow were because i noticed their existence when they liked something i said, and now their names are hidden behind additional clicks if multiple people have reacted. It also makes it hard to tell if you've read someone's reply when a post keeps getting bumped above replies by someone else random reacting to it if your post is popular.
also it looks like upstream there may still be an option to ungroup some things? mastodon#32610
on the GlitchSoc mastodon instance I am on (v4.3.0-beta.2+glitch), there is no option to disable grouped notifications. I looked under the gear in the notifications tab, as well as in the "app settings" menu and "preferences" page, and saw nothing regardless of if i used "advanced" view or not. And when multiple people star something they still get clumped together.
Is this fixed already in the current codebase? Or maybe intentional? Or some sort of caching that will resolve itself?
Sorry if this is the wrong place to report this or i didn't provide information you needed.
The text was updated successfully, but these errors were encountered: