Google Voice back as Approved Service Provider!?

<< < (5/15) > >>

Marc:
Steve,
Thank you for the great update and all the details and information that you have been able to share.  I read the conspiracy type comments and laugh at how absurd people can be.  In business there are reasons for everything and most of the time lay people couldn't and shouldn't be expected to know all the regulations, trade practices, etc that go into making decisions.

I have an acquaintance who, when he heard the two doctors in Atlanta that were being treated for Ebola were released from the hospital, went off on how this is how Obama is going to maintain power and get around the constitutional amendment limiting him to 2 terms.  I'm sure he heard it on Fox or some similar network.  But my point is that people have the need to see a conspiracy, despite the cold hard facts, because it gives them excitement and something to bitch & moan & complain about.

You're professional style prose should allay those that fear the great OBi/Google VOIP take over of 2014/2015. 

Crow550:
With Hangouts, Google added real 3rd party support to Google Voice / Hangouts.

I detailed it in this thread: http://www.obitalk.com/forum/index.php?topic=8092.msg54177

So Obi still uses XMPP just a more secure version?

SteveInWA:
Quote from: Crow550 on August 30, 2014, 02:59:11 pm

With Hangouts, Google added real 3rd party support to Google Voice / Hangouts.

I detailed it in this thread: http://www.obitalk.com/forum/index.php?topic=8092.msg54177

So Obi still uses XMPP just a more secure version?


No.  This has nothing to do with the Hangouts API, and the Hangouts API has nothing to do with "real 3rd party support to Google Voice."

No.  There is no "more secure version of XMPP."  Obihai changed the authentication method.  They are no longer using your Google (Gmail/Google Chat) user ID and password to directly sign into your Google account as a Chat client (a security exposure).  They are now using an entirely different method, which involves OAUTH 2.0 authentication and exchange of access tokens.  Obihai now has no knowledge of your Google user name and password.  This has nothing to do with XMPP signaling protocol, and it has no relevance as to whether XMPP (which was the Google Chat signaling protocol) will continue to be supported, and it is completely irrelevant to the WebRTC APIs.

This is just uninformed speculation, and it's incorrect.  I've explained it in extensive detail in my previous post:

http://www.obitalk.com/forum/index.php?topic=8443.msg55493#msg55493

MikePA:
Quote from: Marc on August 21, 2014, 04:10:07 pm

Steve,
Thank you for the great update and all the details and information that you have been able to share.  

Agreed. Steve's post was great.

Quote from: Marc on August 21, 2014, 04:10:07 pm

I have an acquaintance who, when he heard the two doctors in Atlanta that were being treated for Ebola were released from the hospital, went off on how this is how Obama is going to maintain power and get around the constitutional amendment limiting him to 2 terms.  I'm sure he heard it on Fox or some similar network.  But my point is that people have the need to see a conspiracy, despite the cold hard facts, because it gives them excitement and something to bitch & moan & complain about.

Then there are moronic portions of posts as quoted above.

Brightershade:
Is the new authentication method the reason outbound calls display a caller ID of 760-705-8888 and don't show up in my call history at https://www.google.com/voice#history ? ???

UPDATE: I found the answer here -- http://www.obitalk.com/forum/index.php?topic=8512.0

Navigation

[0] Message Index

[#] Next page

[*] Previous page