Archive for the 'foxri' Category

FoXRI Updated for Firefox 3

Saturday, October 18th, 2008

Prompted by Emanuel in a comment to my post on i-names, I’ve finally tended to the long-overdue item in my TODO queue, i.e. update FoXRI to work with Firefox 3.

The request from Emanuel came almost serendipitously 2 days after =les nonchalantly asked me if I had plans to update it to FF3, to which I answered “one of these days.”

New in this version are 2 patches from Michael Krelin which adds detection of URIs for more OpenID versions, and the handling of append attribute values. Changelog for the patches are available at his git repository.
Thanks, Michael!

Due to what seems like a new security restriction that protocol handlers are not allowed to link to chrome URIs, I can’t seem to get it to load the CSS and icons from the chrome any more. Therefore, those files are now hosted remotely at xrid.net so if you see requests to that host, please don’t be alarmed.

FoXRI updated for Firefox 2.0

Saturday, November 4th, 2006

Just a quick mention that I’ve updated FoXRI to be compatible to Firefox 2.0. I haven’t had time to implement URI construction (which explains why some URI links don’t work in the FoXRI explorer).

Thanks to Gabe and Ken Walsh for the reminder.

New FoXRI Out Now

Monday, August 21st, 2006

I’ve just released version 1.1 of FoXRI – XRI extension for Firefox (and Flock!).

This version features an XRDS explorer that renders an XRI (I-name or I-number) in a nice user interface (see screenshot below).

Go install it at xri://=wil (oh you’re not XRI-enabled yet? No problem, go here instead).


Under the hood

The extension installs an XUL overlay that autocorrects an I-name / I-number in shorthand notation (e.g. =wil or @neustar) to the full version with “xri://” prefix. This is only for XRIs entered on the URL bar. Everything else is left untouched and functions as per normal.

At the same time, it installs an XRI protocol handler (XPCOM component implemented in Javascript) that takes care of resolving the XRI. For “bare” XRI – no path or query e.g. xri://=wil , it fetches the XRDS document from the xri.net proxy and renders it in HTML. Otherwise, the XRI is simply prefixed with http://xri.net/ and hands it off to the normal HTTP handler.

technorati tags:, , ,

Blogged with Flock