Bug Twitter API v2 Client ID vs Consumer key

There is a bug in this version
I

i_n_k

Guest
It looks like Twitter made a change affecting the API, which seems to be pushing people to v2 which seems to use a Client ID vs a Consumer Key. Are there any upcoming plans to add that as an option in the "Connected Accounts" area in a coming update? It looks like a recent change on their end broke the integration, which now seems to require this other option.

Continue reading...