Re: [Mathmesh] Alternative approaches to Web passwords

[Michael Richardson <[e-mail]>]

Do you mean:
   Alternative approaches to Web passwords
or:
   Alternative use cases than Web passwords
   ??

Phillip Hallam-Baker <[e-mail]> wrote:
    > 1) The Mesh Password Manager is not intended to be limited to the Web
    > Browser application and that is probably not the early adopter area.

I think that it's worth recasting this slightly.
The problem is not about synchronizing passwords between browsers on
different devices, but between enabling access between devices with full user
interfaces, and those with limited user interfaces.

I write access rather than passwords, because I believe that more and more
the "login with X" is really important.

My TV's netflix would like to login with facebook, but I really don't want my
facebook password to be simple enough that I'd be willing to type it in with
the TV's <->^V remote control keypad.

While netflix could (and maybe they do) solve this by having me login to
facebook and connect my account up from my laptop or phone, and then store
the resulting OAUTH token in their cloud, (and there are dozens of reasons
why this model is less desireable), the problem is that it does not
generalize to arbitrary services and arbitrary devices.

There are extensions (plugins) to many browsers that will let you send a URL
to your phone.  This usually uses the infrastructure of the phone makers. I
don't know if it works cross-browser/phone. (So Chrome->Android works, and I
imagine Safari->iPhone works, but I don't know about the other combinatorics)

I am imaging a system where it could be common to be able to send
authorization to your TV/fridge,ec.  We need to this in a standard way
because we don't expect all our IoT devices to run the same browser as our
desktop, nor for every member of the household who wants to do this to have
to run the same browser.

As a simple and direct use case, if I had a fridge with an LCD
display (I think you have one Phill) then it would be nice if the detailed
(not just public) calendars for all the members of the household were visible
on the LCD.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-