[Code] OpenId on no HTML user-agents

[valentino miazzo]

Thank you for the question.

On a BD player you have to enter all the information via a remote control.
It is very similar to TV remote controller: digits from 0 to 9, and few
more keys.
99% of them use IR and rubber keys.
For this reasons, to type more than few digits is cumbersome.

We want to link our BD applications to some our web services and
therefore we face the problem of having the user registered and logged in.
Too much typing and the user will skip our web services.
Typing is a barrier to enter our services.

OpenId seems a great way for the user to reuse an account he already have.

Plus,

we want to integrate with other social applications munging and feeding
social data.
Here OAuth seems useful.

So, our reasons to use OpenId and OAuth are not very different from the
reason of anyone developing a new social webapp.
Our problems are the remote controller and the absence of an HTML browser.
These problems are shared with other connected consumer electronics
devices like STB, HDTV.

Valentino


Yang Zhao said the following on 05/02/2010 7.35:
> On 3 February 2010 03:58, valentino miazzo
> <valentino.miazzo at blu-labs.com> wrote:
>   
>> I'm developing applications for Bluray players and I would like to add
>> OpenId compatibility of our applications.
>>     
> Here's a question that's yet to be asked: *why* do you want to add
> OpenID support in your BluRay app?  Specially, what use cases require
> a decentralized authentication system like OpenID.
>
> I think this would better allow us to answer the question in terms of
> what alternative options are appropriate, or if it's something that's
> even feasible.
>
>