Re: [Uri-review] ssh URI

David Booth <david@dbooth.org> Tue, 13 October 2009 04:03 UTC

Return-Path: <david@dbooth.org>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C69B3A69FE for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 21:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level:
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OcX0Kqdo-61H for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 21:03:00 -0700 (PDT)
Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by core3.amsl.com (Postfix) with SMTP id 15D553A6783 for <uri-review@ietf.org>; Mon, 12 Oct 2009 21:02:59 -0700 (PDT)
Received: (qmail 30003 invoked from network); 13 Oct 2009 04:02:59 -0000
Received: from 209.6.102.232 (HELO ?192.168.7.2?) (209.6.102.232) by relay00.pair.com with SMTP; 13 Oct 2009 04:02:59 -0000
X-pair-Authenticated: 209.197.102.232
From: David Booth <david@dbooth.org>
To: bob@sporkmonger.com
In-Reply-To: <81c242240910121855q52319dbatafb6ee46c3364ed@mail.gmail.com>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC> <1255395156.5481.10083.camel@dbooth-laptop> <81c242240910121816y4becb1aevae5008b23537df2c@mail.gmail.com> <1255398140.5481.10279.camel@dbooth-laptop> <81c242240910121855q52319dbatafb6ee46c3364ed@mail.gmail.com>
Content-Type: text/plain
Date: Tue, 13 Oct 2009 00:02:58 -0400
Message-Id: <1255406578.5481.10704.camel@dbooth-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
Cc: uri-review@ietf.org, uri@w3.org
Subject: Re: [Uri-review] ssh URI
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2009 04:03:01 -0000

On Mon, 2009-10-12 at 21:55 -0400, Bob Aman wrote:
> >> I have a problem with this in the general case because I don't think
> >> there's currently a way for such a URI to be registered to a specific
> >> application in any major browser.
> >
> > Take a look at greasemonkey:
> > https://addons.mozilla.org/en-US/firefox/addon/748
> > Greasemonkey is based on recognizing URI patterns and performing special
> > functions when such patterns are recognized.
> 
> I'm familiar with greasemonkey.  Last I checked, greasemonkey didn't
> launch applications so much as rewrite pages in place, and even if it
> could, that's not even remotely user-friendly.  Beyond that, it's not
> something that really applies outside of the Firefox ecosystem.  The
> point isn't that it's not technically feasible, the point is that it's
> a path that has way more technical and psychological hurdles to
> overcome than getting a scheme registered with the IANA.

Getting a scheme registered is the *easy* part.  The hard part is
getting millions of installed clients to implement the special
recognition of that scheme.


-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.