Skip to main content

How many different identities can one person sanely manage?

...asks John Udell, in Critical mass and social network fatigue.  I'd argue that the answer is about one and a half, in the long run.  (The Shockwave Rider pushed it a lot further, but then he was founding cyberpunk.  Also, he was fictional.)

When "identity" was just basically a system-local nickname used between you and a service, having multiple names for yourself was a minor inconvenience at worst, and sometimes mildly useful for privacy.  Now that the services are more and more intermediaries between people, nicknames are a problem.  Jon notes:
Years ago at BYTE Magazine my friend Ben Smith, who was a Unixgreybeard even then (now he’s a Unix whitebeard), made a memorablecomment that’s always stuck with me. We were in the midst of evaluatinga batch of LAN email products. “One of these days,” Ben said in, Ithink, 1991, “everyone’s going to look up from their little islands ofLAN email and see this giant mothership hovering overhead called theInternet.”
Yep.  Email is still the killer app of the Internet, and it wouldn't be if it were still stuck in LAN mail silos.  Though spam is now so bad that I literally can't send email to a few people who can't manage their spam filters.  That's a real issue and represents a real opportunity as well.

While OpenID isn't a total solution for these issues, it's a critical piece of infrastructure.  As an example of the kinds of things it enables, take a look at Jyte.

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

http://www.msnbc.com/rachel-maddow/watch/maddow-to-news-orgs-heads-up-for-hoaxes-985491523709

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.