Don't forget that if you are running several accounts with #Fedilab, just long press buttons such boost, fav, bookmark, reply, etc. It will allow you to pickup another account to finish the action without changing.
So, you will never lose what you are currently doing. The app will do everything in background for you even if the message is not known by the instance of the selected account.
Time saver, isn't it?
@apps
Any chance of multiple (differently themed) timelines? I have a "me", a "work" & "professional organisation" persona to keep track of. Important that boosts/favorites/posts/replies go with the correct ID.
Human error issue, not technically a software capacity.
@Linecutter
Sounds close to that previous enhancement https://social.yesterweb.org/@nikkiana/109525445500398904
We replied, but if many people are concerned we will work faster on it.
@apps
Absolutely, although my "work me" & professional organisation are (maybe unsurprisingly) on the same instance. Which is a little different to the "theme by instance" you mentioned.
Thanks for even considering supporting this!
@Linecutter
We thought by account and not by instance :)
When using two accounts on the same instance, trouble arises when the 2nd account is being added and the web browser is opened to do the authentication.
If that browser hold credentials for that instance from the first account, those might be used instead of the second account's credentials.
The work-around is to clear the web browser of these credentials in between adding each account.
@idlestate
You should have a logout button with the Web browser.
@Linecutter
yes, but only if you go to the web interface using the same browser as was used to do the authentication.
this is not necessarily obvious to do, and how to do, especially if one doesn't usually use a mobile browser, or doesn't use it for that instance.
@idlestate
It should use the default browser. And if an account is already logged in, the logout button at the top right can be used.
Or I might no understand the issue?
@Linecutter
Making reference to the browser only helps if one uses the browser already. Otherwise there's no context for making sense of the reference, since when the app uses the browser it does so implicitly, without any obvious indication that it is using a browser. They just look like additional app screens and don't behave much like the browser does when being used for general purposes.
on the other hand, pointing out that button on the top right, and the text next to it saying what account is currently being used, does help, thanks. Either it wasn't there when I first encountered and tried to debug this problem for myself, or I missed seeing it.