Earlier quoted context omitted.
Many 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 LastP…
The 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 t…
Why We Should All Dump Yahoo
101–102 of 102 posts
Re: Why We Should All Dump Yahoo
#102Earlier quoted context omitted.
The 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 t…
So 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?
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.