Summary:
Please add a feature to Summit for Lemmy where, if a user is logged in with multiple accounts, they receive a visual indicator (e.g., a symbol, badge, or number) on the inactive accounts when a new notification or inbox message arrives on them. This would help users quickly identify that they have notifications on other accounts without needing to manually check each one.
Problem:
For users managing multiple Lemmy accounts (e.g., for different communities or purposes), it’s easy to miss notifications or messages on inactive accounts when they’re logged into just one. Currently, users need to switch between accounts periodically to check for activity, which is both inconvenient and easy to overlook.
Proposed Solution:
Introduce a cross-account notification system where:
- When logged into Account A, and a new notification or inbox message arrives on Account B, a small indicator (like a numbered badge or icon) appears next to Account B in the account-switching menu.
- The badge could display the number of unread notifications or simply alert users that attention is needed on the other account.
Benefits:
- Improved User Experience: Users don’t have to “guess” if there’s activity on their other accounts.
- Increased Engagement: Notifications will ensure users are prompt in responding, especially if the other account is for managing a community.
- Time-Saving: Users can focus on one account without manually checking others unless they know there’s something pending.
Optional Features:
- Customizable Notifications: Users can toggle cross-account notifications on/off for specific accounts.
- Sound/Push Alerts: Optionally allow a subtle sound, vibration, or push notification when activity is detected on inactive accounts.
Conclusion:
This small enhancement would GREATLY improve the usability of Summit for Lemmy for individuals managing multiple accounts. It ensures no notifications go unnoticed and streamlines workflow across accounts, aligning with Summit’s goal of making Lemmy more user-friendly and efficient.
Thank you for the suggestion. This is likely going to require some pretty granular controls simply because this could result in a very large number of API requests especially at a time where a lot of instances appear to be getting DDOSed and are enforcing strict API limits. I’ll add it to the roadmap but this is going to be a pretty involved feature.
You are very Welcome.
That’s fine, at least it’s on the roadmap.
