5

Fuck Facebook!

Disabling apps without warnings or anything which means no customer login. This is a huge pain since the solution doesn't have any way to login to the same account with another credential.

"Oh did you use that? Now you can't. And the only way to do anything is to submit a form to 'appeal' the case which we'll just reject without any notifications or emails"

Normally I won't rant like this or use that much swearing.. but in this case:
Fuck you, Facebook. Fuck. You.

Comments
  • 4
    I get the anger.

    Still, this is the classic dependency problem.

    Using IdPs is very convenient... Until they pull the rug under your feet.
  • 2
    Blame yourself for trusting them for no reason
  • 4
    Yep, that is why single-signon is only a good idea when you are the single-signon provider...
  • 0
    @Oktokolo
    Yeah the implementation is horrible. Now we face the consequences of cutting corners I guess. Not funny when I'm the only dev in the company. Also wasn't me who made it in the first place. If it was, it would've been way different.
  • 1
    @electrineer
    I've never trusted that shit. But the company wants it to be as easy as possible to get customers. And moro.. sorry customers love Facebook.

    Stuff like Facebook integration, Google Ads makes me really want to look for another kind of job.
    I fucking hate these obese big tech data harvesting shitparties that's everywhere now.
  • 1
    Your fault for using google sign in/facebook sign in/microsoft sign in without rolling your own email/password login form. You are screwed when they suddenly change their API.
  • 0
    @daniel-wu

    It's usually... Not a good idea to roll your own authn/authz.

    Oauth2/OIDC can be tricky to get right, but you can host your own IDP with a battle hardened suite, or use external IdP but doing it right, by linking the iss/aud/sub with records of your own, so you don't lose user info.
Add Comment