Closed jaredcat closed 1 year ago
this would be an edge cat that most users probably won't encounter, and depends on how twitter's auth works. auth credentials are taken from the request and stored with the user in the queue. so as long as twitter doesn't invalidate those credentials (which they would, if they were smart) when you log out, theoretically it would still work. but that's just a guess
edge cat
😄
But to clarify, I'm not talking about logging out. I'm referring to switching accounts via the user menu.
It seems like it keeps blocking users on whatever account is active
ah, I'm not too suuure. I would thiiink it would work the same way ? that would be the easiest thing to implement, just store multiple auth tokens in local storage. but I would need to check
thinking about this more, it probably still doesn't answer this question, annoyingly. would still require some investigation into how twitter's tokens work
I need to look into more too, but i think the token stays the same. Probably need to make an array of Queues and try to detect when switching accounts and switch Queues to match
I'd love to have different settings depending on the account.
closed in favor of #180
What happens, or how does this handle, when you switch between multiple accounts?