131 karma · joined May 16, 2013
Edit: typo
I managed to find a decent looking study that somewhat supports my position [1]. Here's an interesting quote from the abstract:
"many (40%) were hesitant to consent to the release of their personal profile information; and (6) many (36%) ex- pressed concern with the use of SSO on websites that contain valuable personal information or, conversely, are not trust- worthy. We also found that with an improved affordance and privacy control, more than 60% of study participants would use Web SSO solutions on the websites they trust."
[1] https://cups.cs.cmu.edu/soups/2011/proceedings/a4_Sun.pdf
This is a very important discussion -- I'd love to see some papers that study the benefits of a single login / profile, rather then the negatives.
The frustration comes from removing the option of customizing my profile for each service.
Just to clarify, I am making a distinction between being able to sign into a Youtube profile with a Google account and forcing the same profile across all Google properties.
Judging from my preferences, and based on my (limited) anecdotes, it seems that users appreciate the convenience of single-signin solutions, as long as each property they are signing into has a profile that can be managed separately.
It is the unification of user profiles that is causing all the uproar.
How were they incentivized to repay early? Having a below-market interest rate seems like it would do the opposite.
The question is, what should happen to that group of people?
Not only that, but I have been finding that most problems where I would originally turn to using objects and classes are better solved by using static functions that operate on large data structures. This strategy also helps sidestep the object-relational mismatch in a lot of cases.
[1] https://news.ycombinator.com/item?id=5743500
Edit: typos
Back to the OP -- this technology looks like a legitimate advance compared to all the valve technologies I have used previusly for camping. Inflating a mattress is a pretty small part of setting up a campsite, however, and I am not sure inflating a mattress is annoying enough to warrant a new purchase, for me at least.
I am really curious to see where they apply this technology in the future.
I'm not a big fan of Akamai's control panel -- setting up new distributions is way to complicated (albeit more flexible), and configuration changes were taking almost a day to propogate.
I think I'm going to have to rewatch the promo video in depth to see if they have any unrealistic demos with glasses-wearing users.
I still believe this technology would be really useful for doing Real Work. You could get around the shadow problem by working in a black surface. I am imagining an interface with a black drafting desk, small bluetooth keyboard, and a 3d tracked pen with this AR display could be absolutely revolutionary for certain engineering disciplines.
[1] http://money.howstuffworks.com/personal-finance/debt-managem...
Theoretically, it should be possible to overpower the background light and have an object appear to be totally opaque, which is similar to the principle behind one-way mirrors. That amount of light might be blinding in certain circumstances, though.
In practice, this almost seems like "sugar" that automatically binds an input to a value if it's value contains ONLY the property.
To test out the binding sugar, I tried using this input: <input value=" {{name}}"></input> (note the space before {{name}}), which did not bind {{name}} to the input.
I'm still of the opinion that the binding should be more explicit.
Edit: typo fix
Does this mean that it is the value="{{age}}" attribute that is causing the binding?
What happens if I want to do something like: <input value="{{firstName}} {{lastName}}"></input>?
For example, in their Getting Started page [0], they have an example of binding component data to elements. It appears that the Age slider is bound to the {{age}} value because its ID is "ageInput". I would prefer to declare the binding with a data-bind="age" attribute on the input, or something else equally explicit.