-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request]: In the notifications list view, do not show hyperlink URLs preview cards (and consider truncating text contents) for my own posts, to reduce visual overload #814
Comments
Should this be the default? What if someone replies to you with a link? Maybe only hide it on own-posts by default?
Should clicking show the full post in place or open the thread? |
Yes this makes sense :)
I think opening the thread directly would be fine and more efficient, but if you want to make it a two-steps/two-clicks operation (first click expands, 2nd click opens the thread), I could understand that too. |
I also just found #176 again now (which, for some reason, I was unable to find earlier today), but it could be argued that the specific case I'm presenting here, and its possible stopgap solutions (hiding URL previews, and maybe text truncation) might be simpler to implement than the "smarter" layout that issue 176 advocates for... |
Yep, actually let me reply on that issue |
Describe the request
Tuba seems to have some notion of grouping notifications (according to the presence of such a setting in the prefs), but it still feels overwhelming not-space-efficient to me. Today I realized one of the reasons why, or at least, one way that the problem could be partially alleviated: every one of your own posts gets retranscribed in full for every notification, including the URL preview cards.
Here is an example, with the thing just below each URL:
Here are my suggestions:
I can always click/tap the individual notification's row item to view its detailed view, in any case.
Implementation Details
The text was updated successfully, but these errors were encountered: