sengi
sengi copied to clipboard
NicolasConstant
Feature Request: Better Multiaccount distinction
As it is now it's very easy to accidentally favorite/boost/post from one account thinking you're in another. A way to more readily see which account you're posting with other than the dimmed inactive account icons on the left would be appreciated.
Account theming is my first though. Ability to set a color per account and have columns associated with that account shown in that color, and the main window color to follow what account is currently active would be nice.
Other mobile applications at least show the user account in the comment bar to show what account is currently being used to comment.
I have the same avatar on my two accounts, it makes it hard to rely on the avatars to understand what account it is. Supporting colors for differencing accounts would be a good possibility.
This has been a problem for me also. Several times in the past few days I replied to a post as the wrong account. Maybe adding the instance icon or name somewhere in the reply box.
As I see it, there are really two different features in this request: One is better distinction of which account a given column belongs to, the other is a stronger visual clue to which account you are posting or interacting as. I would love both, and I suppose color hints would be a possible way to do both in a consistent way: For example, to have (subtle) color differences in column background or column header, and colorize either the sidebar or the entire surrounding UI according to which account is currently active. Just an idea.
An alternative implementation could be to (optionally) hide columns not belonging to the currently active account, a bit like in e.g. Slack. Or the two could possibly be combined.
Please. I added a second account. I figured out how to get the timelines from that account to display (which seemed not entirely obvious). Now I want to post in the new account and I have absolutely no idea how to do that. I hit the post button and I get a box to type into and it will go ... where?
How about a little bit of UX in the bit shown that lets me select which of the servers I am posting to, and shows it to me through the entire posting process?
The way to add timelines is the same as at the first app startup: it's why there was a little "tutorial" explaining what to do.
For the account selection part, that's surely something that could be explained better indeed: all actions (posting, boosting, favs, etc.) you're doing in Sengi is made with the current active account (the non-semi-transparent one). Maybe I'll add this in the on-boarding tutorial to make it more obvious.
I didn't think this would bother me, but now that I have a few accounts, I routinely boost, favourite, and even reply from the wrong one.
For replies (and other posts) the solution seems obvious: put an account selector above the post text, just like TweetDeck does on Twitter.
For boosting and favouriting, I'm not sure what the solution is. Always ask which account you're boosting/favouriting from? Always boost from the account whose column the post is in?
In fact, maybe that's the most elegent: if I click Boost on a status in the column for [email protected], it stands to reason I want to boost from [email protected], and NOT [email protected], even if [email protected] happens to the the account I last posted from. Although that might not always be the case, so maybe some combination -- always ask which account you're boosting or favouring from (provided you have more than one account, of course), but default to the one related to the column?
And then it would be the same for replying -- put an account selector above the text, but default it to the account relating to the column I'm replying from.
@GrahamDo I'm relying on the fact that not all instances are federated the same way to be able to reach other content from multiple accounts, so using the column account for actions would not fit for me. But it can totally be a setting.
We could implement multiple options that are listed it and get feedbacks for what is used and what should be supported.