Missing Code Challenge
Online identity management and single sign-on still doesn't work. Not well enough, anyway. OpenID is a good step forward. So are a bunch of other less familiar approaches. But we still haven't arrived.
For example, I've been a member of Blogger for the duration. That is, since long before Google bought the company. In the old days, making a comment on a Blogger blog was fairly easy. Now it's a lot more complicated. I'm sure that's mostly because comment spam is a gigantic problem, especially for a gigantic company like Google.
But still, from the human visitor's perspective, it's a mess. Here's a screen shot I took after failing for the Nth time to successfully post a comment on a Blogger blog:
For what it's (not) worth, I have a Blogger ID, a Google ID, several OpenIDs, some number of i-names, maybe some information cards (I'm not sure I actually have any yet, but I do think they're good to have), plus cookies from countless sites in my browser's jar, none of which seems to help with this.
I shouldn't complain, because I've been involved in the user-centric identity development community for many years, and have played an active role in helping various efforts (both competing and complementary) to move forward and get along with each other in the process.
But still, we ain't there. And I don't believe we'll get there until each of is known and/or trusted automatically by those with which (or whom) we have relationships. You know, like in the Real World.
For that to happen, we need to hack a way for the individual to drive the interaction. It isn't enough for identity to be "user-centric". In fact, it isn't enough to focus just on identity. After all, I don't need to identify myself when I walk into a grocery store and pay cash to buy stuff. In fact, the stores' "loyalty cards" are terrible systems that not only fail as identity cards, but require dual pricing for every item they "discount", while also slowing down the checkout line. It's as if some kind of digital identity disease has infected ordinary brick & mortar stores as well.
Real engagement needs to be user-driven. That means the individual should be fully empowered to engage with any person or service in the digital world on his or her own terms, in easy, consistent and well-understood ways that may or may not require identifying one's self.
We each need to be independent variables, not dependent ones. What makes me trustworthy to a service like Blogger shouldn't be code that lives entirely on Blogger's side, while all I've got is one among a zillion ID/password combinations, most of which I don't remember. I need to be trusted when I show up. Automatically.
Maybe the means for making this happen will live out in the cloud somewhere. Or in many places. (I can see a lot of potential business here, actually.) But none of it will work unless it starts with the individual. Each of us operating in the digital world needs tools for engagement that belong to us, are operated by us, and give us autonomy, capability and control.
If we get that, we can say goodbye to ugly stuff like the interface above — plus the massive market friction that comes from every vendor having its own silo'd ways of dealing with customers, including CRM (customer relationship management) systems that are controlling and inhuman beyond endurance.
Can we do that? Can we build tools that make individuals both independent of vendor control yet better able to engage with vendors? Can we fix the silo'd authentication problems that have plagued online markets from the beginning? I think we can. That's one reason why I started ProjectVRM at Harvard's Berkman Center.
But I don't know the answer yet, because we don't have the code. Some of us are working on it. You might see evidence by peeking through windows here, here, here, here, here and here — as well as in various corners of the identity community and via links in the blogroll here.
But it's still early. The challenge is still out there.
Is this an itch any of you programming folks feel like scratching — for your own good as well as the rest of the world's? If so, say so below. Or follow what we're doing at the VRM Workshop on Monday and Tuesday.
Doc Searls is Senior Editor of Linux Journal
|illusive networks' Deceptions Everywhere||Aug 29, 2016|
|Happy Birthday Linux||Aug 25, 2016|
|ContainerCon Vendors Offer Flexible Solutions for Managing All Your New Micro-VMs||Aug 24, 2016|
|Updates from LinuxCon and ContainerCon, Toronto, August 2016||Aug 23, 2016|
|NVMe over Fabrics Support Coming to the Linux 4.8 Kernel||Aug 22, 2016|
|What I Wish I’d Known When I Was an Embedded Linux Newbie||Aug 18, 2016|
- illusive networks' Deceptions Everywhere
- Happy Birthday Linux
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- New Version of GParted
- What I Wish I’d Known When I Was an Embedded Linux Newbie
- All about printf
- Updates from LinuxCon and ContainerCon, Toronto, August 2016
- ContainerCon Vendors Offer Flexible Solutions for Managing All Your New Micro-VMs
- Blender for Visual Effects
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide