Lack support for Twitter OAuth

According to Eldad's comment in the issue: https://github.com/appwrite/appwrite/issues/410#issuecomment-1030484754

"Twitter OAuth 2.0 still supports app-only scope and not the user one, which is the one we need @ Appwrite."

It's hard for developers to use appwrite as BAAS who may want to integrate twitter OAuth in their app as it adds unnecessary user flow of email signup.

Will it make sense if we integrate OAuth1.0 until twitter make changes to their OAuth 2.0 as a workaround??

I think other opensource alternatives like supabase are doing this.

TL;DR

A user is requesting support for Twitter OAuth with Appwrite, but it is currently not supported. The issue has been brought up on GitHub, but the current status is unknown. The user suggests integrating OAuth1.0 as a workaround until Twitter makes changes to OAuth 2.0. Another user mentions that other open-source alternatives like Supabase are already supporting this feature. Solution: Currently, Appwrite does not support Twitter OAuth. A workaround could be integrating OAuth1.0 until Twitter updates OAuth 2.0.

Not really because we only support oauth2

That said, they might support oauth2 now: https://developer.twitter.com/en/docs/authentication/oauth-2-0/user-access-token

You're welcome to submit a PR to add the provider

Cool thanks @Steven , I would surely love to work on this. Shall I create an issue first and then start working???

It seems a major roadblock for me to build my latest project TwitterGPT using appwrite.

I'm really looking forward to it! Looks like this issue has already brought up, but I don't know what's the current status yet https://github.com/appwrite/console/issues/389