Honestly, this has been a relatively low priority bug. We have a very small dev team in general, so web resources are already limited. Web app dev and other web dev (and assessing the data gap issue) are taking priority away from this, as those issues affect far more users than a Community login issue, which does have a pretty solid workaround (desktop browser and Discourse app, which is no more third-party than the forum itself or the browser it’s accessed from). Again, this is not an issue that’s just affecting our Discourse community. Others are dealing with similar problems. Like the vast majority of online forums, we’re utilizing a third-party service. Issues occasionally arise that we are unable to prevent.
Trust me, this issue is frustrating for me too as it limits access to a core component of my work here at Sense. It’s being looked into and work is scheduled.
Also, this really has no bearing on the Support team. The bug is logged already, so it’s out of Support’s hands.