Skip to main content

Webfinger now available for Google public profiles

If you've seen ReadWriteWeb's "Email as Identity", you know that Brad just turned on Webfinger for anyone with a public Google profile.  What this means is that, if (and only if) you've enabled your public Google profile at http://www.google.com/profiles/{username}, you can now use Webfinger to look up information you've added to your profile.  Here's the one for john.panzer for example.  By default this exposes only generic service endpoints, not actual information about the user.  But you can link it to private or public feeds, services, or basically anything you want to associate with your online identity.

A next step for Salmon is to let users add a link to their public key from their Webfinger discovered info.  Then given an email address it will be trivial to look up their preferred public key.  It'd look something like this via the discovery tool:




links {
  rel: "magic-public-key"
  type: "application/magic-public-key"
  href: "data:application/magic-public-key;,RSA.mV...ww.AQAB"
}

Comments

  1. What we're going to need is a way to share UserIDs without revealing email addresses (which Webfinger requires). For example, you can share your twitter userid in the form of @TwitterUserID without actually exposing your actual email address (which may change by the way over a period of time). I think with some changes in Google Buzz and Google Profiles we will start seeing things like ~UserID starting to denote a Google Profile ID which can be followed (and cannot be construed as UserID@gmail.com is the email Id of the user behind the profile). I wrote about this yesterday in my blog - http://MohanArun.com/feb-11-2010/

    ReplyDelete
  2. @marun -- already now you can have a Google account without having Gmail activated there. That is the simplest way to accomplish what you're asking for.

    ReplyDelete
  3. In general, Webfinger only requires an email like identifier like x@y.com, not an actual email account. Having an account but not an email inbox is a simple way to accomplish this. Also, the Webfinger spec itself is actually a wrapper around lower level protocols like LRDD and XRD that work with arbitrary kinds of identifiers. I certainly plan to accept all kinds of standards-based identifiers in things like Salmon, so you could for example use http://twitter.com/ev as your ID and have it work.

    My current term for all of these kinds of identifiers, email like or not, are "discoverable identifiers". In the market for a better term.

    ReplyDelete
  4. In taking a wick read at these parts of the Salmon protocol, it seems like there is some overlap with the PGP web-of-trust infrastructure. Do these two forms of PKI intersect at all?

    ReplyDelete
  5. Noticed that the webfinger rel redirects to a blog with a 404:
    http://webfinger.net/rel/profile-page

    ReplyDelete

Post a Comment

Popular posts from this blog

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…

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.

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.