Hello,
I was wondering about the best approach to deal with the Twitter Sign-in API when there are about 15 domains ( each in a different language ).
So far, we have a working sign-in flow for some of them : each app has different callback URLs ( we use 3 callback URLs for each domain : dev, preproduction and production ), and each app has a translated description of what it does as well as language specific links to the TOS and privacy policy. In our case the only thing it does is retrieve the user name end email.
By looking for similar cases online, I have two main concerns :
- Is there a better way of dealing with multiple domains?
- I’m not certain our use of the API follows the Twitter’s developer policies since the use of each app is almost identical
It sounds like it’s against policy for the “no multiple apps for the same purpose” rule. The way to do it would be to make an “api gateway” for Twitter logins, using a single app, and show the language and domain specific TOS / privacy policy on your end somehow.
This 1 “Twitter Login Service” app will serve all domains (you will be limited to 100,000 users for this - if you hit the limit you’ll need to fill out a form and apply for more). This service would be completely separate from the “domains” and will only handle Twitter authentication.
I don’t know if there’s a good opensource example of such an implementation out there, but if you find one or make one it’s a good thing to share.
Allowing developers to provide multiple language versions of the descriptions / links to TOS for a single app is not possible but it’s a good idea to post here if you want: https://twitterdevfeedback.uservoice.com/forums/921790-twitter-developer-labs?category_id=362647
1 Like
system
closed
#3
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.