Gosh, it really would be a fuckup if their badge security system itself depends on Facebook
It's really easy to fall into the trap of having a circular dependency without intending to, or realising you've done so.
All you need are two things X and Y (could be tools, services, etc.) and you decide that it's "best practice" to use both of them. So X adds a dependency on Y, Y on X, and of course everyone else is depending on both
The insidious part is that it works fine - until it doesn't. As long as both are at least partially working you can usually recover. But as soon as one goes down it becomes very difficult to bring either back
And even if you think X has no dependency on Y, maybe it does have a dependency on Z, and you don't know *it* depends on Y.
The usual solution is to bootstrap from simpler tools and self-contained systems without dependencies but that of course has its own issues.
Like maybe you take the time to set up your emergency fallback and think you're covered, but then a year later you find it's bitrotted and doesn't work any more
re: Facebook outage
This kinda reminds me of an article I’ve read a few years ago.
An insurance company (I’m not sure if from the UK or the US) which faked a fire alert and for all people who were laid off the access cards didn’t work anymore.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!