This new 2nd factor authentication method when going to the API developer platform site was foisted on me.
As if I would
- allow the ChatGPT app to EVER run in the background
- allow the ChatGPT app to EVER emit notifications
That, besides, the prior demand for an emailed code upon ANY new login and any short expiration of Oauth2, despite a fully cookied-up browser that is hitting the platform site to manage an organization.
I installed and updated the mobile application to verify for another user that the light/dark theming is broken there, to where the text of “pulse” can’t even be seen.
NOT to have my device information transmitted back to OpenAI to be replayed in that screen, with whatever other information they are trying to scarf up out of personal devices.
The platform site and an organization is NOT ChatGPT, and this factor/login/auth method conflating consumer applications and a developer product should have never even have been considered. Secondly, it is a completely dumb pattern, because the app uses the EXACT SAME authentication challenge when logging in, so protects against nothing and even lowers the quality of account protection.
It is sufficient to say that the phone app is GONE, the desktop app is GONE, no software from OpenAI will be installed and no helping of ChatGPT users is in the future.
Then, that authentication challenge test better now respect that existence of any such mechanism is toast in the future, with no more communication or authentication demands against NOTHING. This is a violation of trust besides being an untrustworthy method, besides spewing my personal information to multiple vendors to mishandle - now even emails from ‘hubspotlink’ spamming me about the other forum.