Going back to non-JSON sign-in responses; it seems to be the only reliable way to get the after-sign-in destination
Going back to non-JSON sign-in responses; it seems to be the only reliable way to get the after-sign-in destination

neinteractiveliterature/intercode,neinteractiveliterature/intercode,neinteractiveliterature/intercode,neinteractiveliterature/intercode,neinteractiveliterature/intercode