My Own URL Shortener
Nobody likes link rot. Link rot breaks the Web. But in the age of Twitter, short URLs are a necessity. I think the best way to keep my short URLs from rotting is to take charge of the process myself. This post shows how I built a simple, reliable URL shortening service that runs under my control.
Continue reading {My Own URL Shortener }
Detecting URLs with Regexps
Jeff Atwood talks about the problem of detecting URLs in text. The problem, as Jeff points out, is that lots of interesting characters are legal in URLs, including parens. So, writing a regular expression to distinguish between these two URLs is hard (but not impossible): My website (http://www.example.com) http://en.wikipedia.org/wiki/PC_Tools_(Central_Point_Software) Jeff's solution is pretty comprehensive and cuts the Gordian Knot of enclosing the URL in parens by removing them programatically--a good solution since we're not worried about nesting.
Continue reading {Detecting URLs with Regexps}
URLs as Identity
Johannes Ernst thinks that's URLs should be used to identify people. That's the basis of his LID identity system. Open ID is based on the same concept. Johannes notes that OPML has joined the party and talks about an emerging consensus on how it should work.
Continue reading {URLs as Identity}
IIW 2005: Brad Fitzpatrick on OpenID
OpenID is similar to LID in that URLs are used for identifiers. Identity URLs can be static web pages so there's a low barrier to entry. Also, no SSL is required, nor is a browser plugin. OpenID is simply a way to prove you own a URL. OpenID can be stateful or stateless. Stateful access is faster, but requires more infrastructure to support. When you grab a URL, the URL has a way of saying who the identity server is (in the <link/> tag). The identity server provides a way for the person claiming the URL to prove (i.e.
Continue reading {IIW 2005: Brad Fitzpatrick on OpenID}





