Re: [webfinger] Vision for Webfinger - what are we doing?
Bob Wyman <bob@wyman.us> Fri, 01 November 2013 15:13 UTC
Return-Path: <bobwyman@gmail.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 408C511E8162 for <webfinger@ietfa.amsl.com>; Fri, 1 Nov 2013 08:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16bW2BPYty4Y for <webfinger@ietfa.amsl.com>; Fri, 1 Nov 2013 08:13:45 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id C37BB11E817D for <webfinger@ietf.org>; Fri, 1 Nov 2013 08:13:41 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id ez12so1219175wid.3 for <webfinger@ietf.org>; Fri, 01 Nov 2013 08:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=FSOG1PhQUQ1jwBzAgQr/+2oY+eOdmSzOmTzXCC6MbQo=; b=sssWhEB3dFj7HZ9BVq4b2kFt7LieVJ/gnZhDD9Ag6Pm8eOFHC1q53JaCiuOeJ3SgV2 rtlbhVupxHw8GMtFNBHOhALXE2/9cI+80W7z+tyPlA2sFl1Z17I1eBSM016b158mVs5y +J40Mm/VawOy4C4Qh7iCVRjzVWl+/jerhu/pbRBmZWey3p6v73mtujrZ6oNr9upfUQSO NOxkXFqoWNQNtDL/htpAUYkvibzPz8UJPpakHRIdcdU/0g4gf7uJOlYyi/HuXLSqBdlx KhIexmly5hwIdcp05PlRhCasppupJAApaAX3TTl+UNSN4CTNk5oEADTfQAA/bFL94wcI jdOw==
MIME-Version: 1.0
X-Received: by 10.194.8.137 with SMTP id r9mr23377wja.78.1383318820852; Fri, 01 Nov 2013 08:13:40 -0700 (PDT)
Sender: bobwyman@gmail.com
Received: by 10.194.190.166 with HTTP; Fri, 1 Nov 2013 08:13:40 -0700 (PDT)
In-Reply-To: <CANBOYLXVtj1ppNGZmATkgJv2aqsG-q4ZedkOPNesUhwwCTd-XA@mail.gmail.com>
References: <CANBOYLVNwmneMiNaM+7DGm+UyDbZBhhcX15b=CeNoZgxf+oEDw@mail.gmail.com> <525D9646.7010306@packetizer.com> <CANBOYLXNktGGHSaC4BEi4nN19OY=tLU16SocqO6akdybC40p0A@mail.gmail.com> <CANBOYLXVtj1ppNGZmATkgJv2aqsG-q4ZedkOPNesUhwwCTd-XA@mail.gmail.com>
Date: Fri, 01 Nov 2013 11:13:40 -0400
X-Google-Sender-Auth: ZVkRifnKo5WUXNgkoBj-nwK6O-8
Message-ID: <CAA1s49UkDhKhpimMLR0J3Gj1=-QYEi3FouEEwvh7ei4u=eBJ+w@mail.gmail.com>
From: Bob Wyman <bob@wyman.us>
To: Eric Mill <eric@konklone.com>
Content-Type: multipart/alternative; boundary="047d7b5d2532ed9da104ea1f02af"
Cc: "Paul E. Jones" <paulej@packetizer.com>, WebFinger List <webfinger@googlegroups.com>, "webfinger@ietf.org" <webfinger@ietf.org>
Subject: Re: [webfinger] Vision for Webfinger - what are we doing?
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Nov 2013 15:13:46 -0000
Eric, you wrote: "Webfinger is a standard way to attach information to an email address. " This isn't really accurate. It would be much better written as: "Webfinger provides a standard mechanism that can be used to associate data with an email address." it is essential to understand that Webfinger is useful for much more than the single use-case you discuss. bob wyman On Fri, Nov 1, 2013 at 10:58 AM, Eric Mill <eric@konklone.com> wrote: > I channeled this into a blog post, if anyone's interested: > > https://konklone.com/post/webfinger-gets-a-final-chance > > I imagine it's going to rankle some people who disagree with my prognosis > that some things are dead, but it's how it feels from here. Webfinger needs > rapid experimentation, high profile adoption, and the energy of the rest of > the open web community. > > > On Wed, Oct 16, 2013 at 11:38 AM, Eric Mill <eric@konklone.com> wrote: > >> This is all helpful to hear, and I hope these all come to fruition, >> especially OpenID Connect. I'll take a stab at setting up my own OpenID >> Connect service on my domain and see how it feels. >> >> I guess it's inevitable that we have to hope the big companies make a >> meaningful gesture, too. Giving Google's outdated Webfinger endpoint<https://gmail.com/.well-known/host-meta> for >> Gmail a big update would be a great start. >> >> On Tue, Oct 15, 2013 at 3:23 PM, Paul E. Jones <paulej@packetizer.com>wrote: >> >>> Eric, >>> >>> OpenID is not entirely dead, yet. I still run my own OpenID OP server >>> and use it to log into some sites. I still allow OpenID logins on >>> forums.packetizer.com, too. It's still in use, but the large sites >>> just didn't have enough users using it, so they axed it. On its heels, >>> though, is now OpenID Connect and it will use WebFinger for discovery. so, >>> sure... push it :-) >>> >>> Personally, I can think of a lot of good uses for WebFinger: >>> * When I log onto a web site, I want the site to grab my name an picture >>> automatically. >>> * If I want somebody to send me bitcoins, I'd much rather give them my >>> email address (and I do have that in my WF account) >>> * My contact info is published via WebFinger, so I don't have to give >>> people a lot of info on a business card >>> * WebFinger will hopefully be used as the starting point for >>> auto-provisioning of email clients or other devices and applications where >>> one has to enter server and port information >>> >>> Paul >>> >>> >>> On 10/14/2013 11:21 PM, Eric Mill wrote: >>> >>> Hey all, >>> >>> I was at a hackathon<http://fedscoop.com/code-dc-calls-furloughed-feds/> today, >>> and spent the day working on Webfinger libraries for Sinatra<https://github.com/konklone/sinatra-webfinger>and >>> Jekyll <https://github.com/konklone/jekyll-webfinger>. It was really >>> productive, but -- at the end of the day, a reporter was there asking >>> everybody questions about their projects. >>> >>> When he asked what Webfinger was for, I realized that the original >>> easy-to-communicate killer app for Webfinger, easing universal login >>> through OpenID, was<http://productblogarchive.37signals.com/products/2011/01/well-be-retiring-our-support-of-openid-on-may-1.html> >>> dead <https://www.myopenid.com/>. The only thing I could think to say >>> was "Remember OpenID? Before it died? Well, this is a piece of the puzzle >>> to putting something like that back together again." >>> >>> That didn't feel like a very impressive answer. So, now that OpenID is >>> dead, what's the one line explanation for why Webfinger is important? >>> What's the path forward to making Webfinger something people are >>> incentivized to support? >>> >>> Should we be pushing really hard to resuscitate OpenID via OpenID >>> Connect? Do we just need to wait for internal lobbying inside of >>> Google/Microsoft/Twitter/etc to pay off in some announcement? I know >>> Webfinger supports more than email lookup -- is there some particular >>> killer app people were envisioning when they lobbied for that feature? >>> >>> I'm so happy there's finally an RFC, after so many years. I recognize >>> how much work was put in to make that happen, and this shouldn't be taken >>> as a criticism of anyone. I just want to know what others see for the >>> future of Webfinger, and what I should do next. >>> >>> -- Eric >>> >>> -- >>> konklone.com | @konklone <https://twitter.com/konklone> >>> >>> >>> _______________________________________________ >>> webfinger mailing listwebfinger@ietf.orghttps://www.ietf.org/mailman/listinfo/webfinger >>> >>> >>> >>> _______________________________________________ >>> webfinger mailing list >>> webfinger@ietf.org >>> https://www.ietf.org/mailman/listinfo/webfinger >>> >>> >> >> >> -- >> konklone.com | @konklone <https://twitter.com/konklone> >> > > > > -- > konklone.com | @konklone <https://twitter.com/konklone> > > _______________________________________________ > webfinger mailing list > webfinger@ietf.org > https://www.ietf.org/mailman/listinfo/webfinger > >
- [webfinger] Vision for Webfinger - what are we do… Eric Mill
- Re: [webfinger] Vision for Webfinger - what are w… Brad Fitzpatrick
- Re: [webfinger] Vision for Webfinger - what are w… Paul E. Jones
- Re: [webfinger] Vision for Webfinger - what are w… Kingsley Idehen
- Re: [webfinger] Vision for Webfinger - what are w… Melvin Carvalho
- Re: [webfinger] Vision for Webfinger - what are w… Eric Mill
- Re: [webfinger] Vision for Webfinger - what are w… Eric Mill
- Re: [webfinger] Vision for Webfinger - what are w… Bob Wyman
- Re: [webfinger] Vision for Webfinger - what are w… Melvin Carvalho
- Re: [webfinger] Vision for Webfinger - what are w… Eric Mill
- Re: [webfinger] Vision for Webfinger - what are w… Bob Wyman
- Re: [webfinger] Vision for Webfinger - what are w… Eric Mill
- Re: [webfinger] Vision for Webfinger - what are w… Kingsley Idehen