Yeah, it's totally not a new auth bug. I repeated the logout and log back in process using social-status-updater and I'm working fine again.