3 ms·
I just checked LastPass; 324 out of 770 of my accounts use an email address as the username.
by pavel_lishin 10y ago
I just checked LastPass; 324 out of 770 of my accounts use an email address as the username.
- dredmorbius 10y ago770 accounts?!!! I think this whole "set up a service for everything" concept ain't workin'. I'm trying to think how much storage just the TOS and Privacy Policies for those would run.
- pavel_lishin 10y agoMany of them are old, and there are services for which I have multiple sign-ons. (e.g., four sign-ins for Hipchat, five for Slack, two for Amazon.) There are also a lot of one-off things that require registration to try out whatever they're offering. Some appear to just be security notes or stored keys from previous employers; others are imported from 1Password and haven't been used in the entire time I've used LastPass (5 years.) Some are just fucking baffling, to be honest. What the hell is vodka-hoop.com, and why do I have an entry for it? Anyway; what's the alternative to "set up a service for everything" that's not a single point of failure? (Although, I guess LastPass is that already.)
- dredmorbius 10y agoThe alternative I've been leaning toward increasingly is to have user-controls-data as the model. Rather than pop up to a particular vendor, supply auth tokens, and have them pull up their information on you, you show up, they provide their tokens, and you provide your information (in their formats). Combine this with a strong regime prohibiting inter-enterprise transfers of personal data. So that if Firm A want to talk to Firm B about User X, Firm A submits User X the request, Firm B confirms, and User X either complies or doesn't. This would ... change certain dynamics of use of personal data. Avoiding data loss: mumble, mumble something PKI key escrow trusted parties distributed encrypted data. Some form of personal data server as data origin, with re-shares distributed around social infrastructure. It may be a pipe dream, but at the very least it's a different model for considering pervasive data. If the user's Personal Data Stick or Home Server Box is destroyed in fire (or stolen or the cat eats it, or ...), then they and a trusted set of key escrow holders if necessary can reconstruct the data from shards spread amongs some n other systems, no one of which could individually reconstruct the whole. "Services" in this model would be applications distributed out to operate on the user's own data directly. Among other implications, the concept of coming up with a common base universal data format seems like a possible outcome. That could still be modified for individual service use, but the transforms would still have to map back to the core.
- pavel_lishin 10y agoSo basically OAuth, with more additional metadata, but with the flow going in the opposite direction? Sounds interesting, but they'd still need to cache it on their end for it to be remotely useful, right?
- dredmorbius 10y agoNot if you: 1. Move processing to data. 2. Use minimum viable data. E.g., Google (Roberto Bayardo) state that the two critical elements for ad placement are a) current location and b) current search term. Everything else is quite minimally beneficial. I'm not sure this is viable. I think it's worth tossing into the discussion.