Fazal

#22 should fix the issue.

According to the spec ( as far as I understand ) this is not possible, as only a single ID is returned in the response. So if returned message ID...

@McSwitch That is correct. What I am asking may not be possible from what I have gathered.

Any update on this?

Hey @Benehiko Thank you for checking into this. It's a bit confusing what you can do with Twitter OAuth 1.0a and OAuth 2.0. As of now there's no way to...

That would break user expectations given how Login with Twitter is implemented and used in the wild. Which as I understand (as limited as it may be) is a big...

@Benehiko how about we send a new PR for v2. You could close this one if you feel that's the best way forward.

Unfortunately I don't think it's possible because of this issue https://github.com/golang/oauth2/issues/534

@arekkas [coreos/go-oidc](https://github.com/coreos/go-oidc) isn't this for OIDC providers. Twitter v2 is not an OIDC provider, just OAuth 2.

Use case I have is to allow cache lookup with two different unique identifiers. A common example is to lookup cached user information by both ID and username/email.