authorization for remote follows and switching from pleroma-fe to masto-fe prompts user to login again
expected behavior: pleroma uses existing token of logged in user
what happens in remote follow: cookie is gone after being redirected back to your instance, forced to log in again to authorize
what happens in switching to masto-fe: forced to log in again to authorize
The session isn't killed, it still persists on other tabs.
Edited by Mike Travis