The Usability of Input Filtering. The original input is lost. There is no preview. I think this has to be a usability worse case scenario. +1. Filter with Forced Buffered Preview tempts me the most, but if you return unacceptable input unmodified, it’s hard to be sure your user will really look at the preview. […]
XML+Data: date-stamped 2005-04-01 or not, Joseph is an evil man. Eeeeevil. Handwaving away the problem of encoding “- -“? Bah!
Chuq on Susan Mernit on growing your blog audience. Mostly, I’m with Chuq, though sometimes being first does count; many of my widest-linked posts have been frist p0st!s, rarely when they were deep scoops, mostly when they were quick toss-offs because I knew I wouldn’t have time to write more later. It’s bad as your […]
A perfect way of looking at posting about the things everyone else already had more time to link to than you, but still you haven’t linked to it: Everybody knows that …
(What’s) next.yahoo.com: because you know you want to know. I’m quite fond of mysearch.yahoo.com, which among other things lets you block sites you don’t want in your results (whether because they are spam, crap, or just using a term you search on with a different meaning, RSS instead of RSS).
Why get your scripts to hijack Amazon links and your scripts to un-hijack Amazon links from two different places, when you can get them from a one-stop-shop?
According to the bottom of every Technorati page, … something is under a Creative Commons license. According to the Terms Of Service, you can’t even “download” or “use for any purpose” any of their materials without prior written permission from the owners. Who, it must be noted when considering their license, are almost never Technorati.
Yahoo!’s new Creative Commons search is cool, but given the horrible state of people’s explanation of what content is and isn’t licensed, I can’t believe they return anything which links to a license, without any disclaimer that some or all of any result may not actually be offered under a CC license.
Paul Festa: substantial security risks. Greaseblog: exact same security context as bookmarklets. Me: easier to audit, with line breaks and multiple-character names, though.
cursor:url() in Mozilla. Oh. Yay. It’s like a web standards version of Comet Cursor? Yay.