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
This is one big behaviour difference between Sengi and Tweetdeck that trips me up.
In tweetdeck, if I add columns from multiple accounts, then my interactions in that column will be from the "owning" account. So I can like a tweet on the home feed of AccountA, as AccountA, and then like a tweet in the notifications of AccountB, as AccountB.
If Sengi could support this behaviour of defaulting the user context from the column, instead of the account switcher, that would be awesome.
The text was updated successfully, but these errors were encountered:
Yeah, I've been running into this a lot too. With two accounts (for two different languages) I have two columns, one for the local timeline on each server, and regularly have the "wrong" account selected on the far left :|
I agree! I also find myself quite frequently using the wrong account to interact because of this.
But I'd like to add that I do really appreciate the ability to browse a column from one account, but interact using another - I tend to use some accounts for discovery, but then boost/reply using which-ever of my accounts is most on-topic.
So changing the default, but keeping the ability to switch, would be ideal, in my opinion. Also - thanks so much for Sengi, it's great tool, a game-changer for my Fedi use so far.
This is one big behaviour difference between Sengi and Tweetdeck that trips me up.
In tweetdeck, if I add columns from multiple accounts, then my interactions in that column will be from the "owning" account. So I can like a tweet on the home feed of AccountA, as AccountA, and then like a tweet in the notifications of AccountB, as AccountB.
If Sengi could support this behaviour of defaulting the user context from the column, instead of the account switcher, that would be awesome.
The text was updated successfully, but these errors were encountered: