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
In the latest update, a line of text has been added to some statuses explaining their context in a thread ("in reply to..."; "continued thread").
I suggest this is either rolled back to the previous icon-based version, or that the two options are made toggleable in the preferences.
Motivation
The change was made per a request in #3771 , but the implementation takes up space and diverts focus from the feed content. IMO the previous solution of marking such statuses with only an icon was subtler but also more UX friendly.
The previously raised issue shows that some users prefer the more verbose version, but it detracts from the elegant simplicity of Tusky's interface design. Not everything from the Mastodon web UI or other apps needs to be implemented in Tusky 🙂
As a compromise, I suggest this becomes optional as a toggle in the app preferences.
The text was updated successfully, but these errors were encountered:
Pitch
In the latest update, a line of text has been added to some statuses explaining their context in a thread ("in reply to..."; "continued thread").
I suggest this is either rolled back to the previous icon-based version, or that the two options are made toggleable in the preferences.
Motivation
The change was made per a request in #3771 , but the implementation takes up space and diverts focus from the feed content. IMO the previous solution of marking such statuses with only an icon was subtler but also more UX friendly.
The previously raised issue shows that some users prefer the more verbose version, but it detracts from the elegant simplicity of Tusky's interface design. Not everything from the Mastodon web UI or other apps needs to be implemented in Tusky 🙂
As a compromise, I suggest this becomes optional as a toggle in the app preferences.
The text was updated successfully, but these errors were encountered: