We've had to change our registration confirmation mails too recently to not confirm on GET only, but with another form - in hindsight it was stupid before but many services do that.
This has been a thing since forever lol
If merely GET on the link was sufficient to trigger the behaviors, the adversary generating the link would just GET it themselves.
I was replying more generally about the "don't click links" advice and cases of server generated confirmation-token links (not saying this was the case at OpenAI)
[0]: https://che01.safelinks.protection.outlook.com/?url=https%3A...
- "sign in via one-time code."
- "Click here to see our latest update".
250k refresher fee