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
When it comes to notifs on bluesky, I find one thing particularly aggravating, which is that notifications in your feed seem to interrupt each other on posts. Say you were to get 2 likes on one post, a like on a different post, and then another 3 likes on the first post. This creates 3 separate notifs instead of stacking the likes from the first post in a persistent notification. This creates a -LOT- of notification clutter if you have many posts.
I'd suggest just a general update to the way notifications are updated in the feed, just by simply updating a single persistent notification of likes/reposts on a post, rather than creating multiple new notifications in the feed when a new post's notifications interrupt a previous ones.
There exists the "filter low quality notifications" feature, but I feel it doesn't quite fit the bill for what I'm searching for to curate the notification feed a little better. I'd rather not get rid of notifications, much more so condense them in a better, more consistent way.
To add a small visual, without creating an image, I'm suggesting that a feed that looks like this:
5 users liked Post 1
2 users reposted Post 2
User commented "Great Art!" on Post 1
4 users liked Post 1
3 users reposted Post 1
6 users liked Post 1
... where the likes notification splits into a new notif when interrupted, to instead persist and update each post's notifications and just sort by which notifs are latest in this persistent list, turning the previous example into:
15 users liked Post 1
2 users reposted Post 2
User commented "Great Art!" on Post 1
3 users reposted Post 1
I think in general, this solution would work better as a default notification feed method, since it still displays all notifs, but condenses the most common notifs in a solid way that still prioritizes being able to see peoples replies to a post, instead of burying them in like/repost clutter.
The text was updated successfully, but these errors were encountered:
When it comes to notifs on bluesky, I find one thing particularly aggravating, which is that notifications in your feed seem to interrupt each other on posts. Say you were to get 2 likes on one post, a like on a different post, and then another 3 likes on the first post. This creates 3 separate notifs instead of stacking the likes from the first post in a persistent notification. This creates a -LOT- of notification clutter if you have many posts.
I'd suggest just a general update to the way notifications are updated in the feed, just by simply updating a single persistent notification of likes/reposts on a post, rather than creating multiple new notifications in the feed when a new post's notifications interrupt a previous ones.
There exists the "filter low quality notifications" feature, but I feel it doesn't quite fit the bill for what I'm searching for to curate the notification feed a little better. I'd rather not get rid of notifications, much more so condense them in a better, more consistent way.
To add a small visual, without creating an image, I'm suggesting that a feed that looks like this:
5 users liked Post 1
2 users reposted Post 2
User commented "Great Art!" on Post 1
4 users liked Post 1
3 users reposted Post 1
6 users liked Post 1
... where the likes notification splits into a new notif when interrupted, to instead persist and update each post's notifications and just sort by which notifs are latest in this persistent list, turning the previous example into:
15 users liked Post 1
2 users reposted Post 2
User commented "Great Art!" on Post 1
3 users reposted Post 1
I think in general, this solution would work better as a default notification feed method, since it still displays all notifs, but condenses the most common notifs in a solid way that still prioritizes being able to see peoples replies to a post, instead of burying them in like/repost clutter.
The text was updated successfully, but these errors were encountered: