A pedant that hangs out in the dark corner-cases of the web.
Wednesday, July 27, 2005
Tuesday, July 26, 2005
Thursday, July 21, 2005
Wednesday, July 20, 2005
Tuesday, July 19, 2005
JD starts his article by explaining that he can't figure out Creative Commons (apparently he missed the Learn More link). This doesn't stop him from writing two pages about it, making broad pronouncements, though. In fact, he's decided that since he cannot figure it out, it must just be "trendy"--"There is no other answer" he proclaims.
For some reason, he seems to think registration and paperwork are necessary (they aren't). He complains about excesses in the current copyright system, which is what CC was written to address, but completely misses the point. Paradoxically, he whines about CC weakening the copyright system as he bemoans copyright being too extreme. He spouts some piffle about restrictions for commercial use (which is only one option of the license, if the creator decides to include it).
It must be great to be a columnist: you get to write endlessly about things you don't even have to pretend to understand! Plus, you get to use the word "dumb" a lot.
Here's Creative Commons in a nutshell, as condensed in a slashdot post: "Creative Commons is a way of *giving up* some rights. But without giving up *all* rights."
Wednesday, July 06, 2005
To the embarassingly uninformed third party vendors of web-based applications, I present a quick look at HTML entities. This is Chapter One stuff in even the most basic HTML book, but I still get puzzled, dismissive, and even indignant replies when I request fixes for simple HTML bugs.
Three important characters:
These characters are special to HTML for processing. In the text or attribute values of a page, you must use entities that stand for them:
&(respectively). In attributes,
" should also be replaced with
" (actually, you can use
" anywhere, but it isn't required outside attribute values).
The Web Is A Big Place
If you forget to entify your special characters, some browsers will sometimes let you get away with it. If you intend to produce code for the widest possible audience (which is the whole point of the Internet, after all), it is best not to assume your indiscretions will always go unnoticed; better to do it right to start with, and you won't have to double check every support call ($$$) to see if unentified HTML is part of the problem.
Unentified HTML Is Insecure HTML
All Cross-Site Scripting (XSS) attacks are caused by unentified HTML, and can be prevented using entities. The liability of such an attack, though potentially considerable, is nothing compared to the loss of client trust.
Every web development language has a single function you can call to entify the contents of string or text variables (numeric and date/time variables do not typically require escaping), e.g.
Server.HTMLEncode() in Active Server Pages or
htmlentities() in PHP. In cases where the language does not provide such a function, writing one is trivial: four search-and-replace calls (do the ampersand first).