That stance has already cost Mac users much further development of at least one popular Twitter client. …Developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. In kicking off that uproar, Sarver wrote: If it’s your first time logging in with that app, you’re then asked to approve the specific Facebook permissions that app is requesting.īack in March, Twitter famously (and controversially) clamped down third-party apps.
When you log in to Facebook via a third party app, that app must briefly display an inline Web view of the Facebook login screen. If you use third-party desktop or iOS apps that leverage Facebook’s login credentialing system, you already have a sense of what this will look like. But in order for those apps to embrace Twitter’s new permission model, they’ll need to embrace oAuth. Thus, it’s rather likely that we’ll see a slew of third-party Twitter app updates in the next couple weeks. That would obviously leave such third-party apps rather crippled any user who relies on direct messages will instead be greeted by some unspecified error and/or blank direct messages list. So what does this all mean? It means that unless Twitterrific and the rest issue updates to their apps by Twitter’s deadline of “the end of this month,” those apps will soon be unable to display or send your direct messages. Most non-Web third-party apps-iOS apps and Mac apps, for example-prefer to go the xAuth route, which allows for a more seamless experience. Most Web apps historically rely on oAuth you’re already using the Web, so sending you off to Twitter’s site for a moment during the login process flows naturally.
0 kommentar(er)
