Google yanks sketchy iMessage clone for Android from app store

Re:Google yanks sketchy iMessage clone for Android from app ... by lnanek2 on Sunday September 29, 2013 @08:35AM (#6465005)

There isn't any API for iMessage as far as I know, collecting username and password was the only way to do it. It's a lot like many Twitter apps nowadays just ask for username and password since the Twitter API, which is needed for oauth/xauth, is pretty locked down and useless nowadays.

[ Parent | on HN ]

Re:Google yanks sketchy iMessage clone for Android from app ... by joshstrange on Sunday September 29, 2013 @08:52AM (#6465036)

Correct me if I'm wrong but I was under the impression Twitter only supported oauth nowadays with password auth being phased out a few years ago.

[ Parent | on HN ]

Re:Google yanks sketchy iMessage clone for Android from app ... by abraham on Sunday September 29, 2013 @07:21PM (#6466979)

The Twitter API only supports OAuth now. There is an API method developers can use to jumpstart the OAuth flow with a password but this is restricted to apps that Twitter allows to use it.

[ Parent | on HN ]

Re:Google yanks sketchy iMessage clone for Android from app ... by joshstrange on Friday October 04, 2013 @03:59PM (#6497568)

I was not aware of this, thank you for informing me. Do you know if this is like Facebook+Spotify (and only a couple other FB apps that can use password) or is it much wider-spread in the Twitter ecosystem?

[ Parent | on HN ]

Re:Google yanks sketchy iMessage clone for Android from app ... by Adirael on Sunday September 29, 2013 @09:28AM (#6465118)

I guess that you can always make your own wrapper and act like you were a browser.

[ Parent | on HN ]

Re:Google yanks sketchy iMessage clone for Android from app ... by eknkc on Sunday September 29, 2013 @11:00AM (#6465333)

Twitter REST Api and oauth login facilities seems to be feature complete and many 3rd party client apps use that. (Tweetbot, at the top of my head)

[ Parent | on HN ]