pink and repink

February 23rd, 2007

Quoting from Sucking less, on a budget, for reasons that will be obvious to some:


A friend asked me today if Camino 1.1 was even in alpha. Heck, we’re on alpha two, but I guess we haven’t really done the best job of promoting it. To some extent, that’s reasonable, alphas generally aren’t the kind of thing you want your grandmother using. However, our standards are usually a little higher than most, and I’ve been running 1.1a2 daily on both home and work machines for a while.

In fact, we’re really close to beta. We wanted to have something for Presidents Day (Abe Lincoln is a *huge* Camino fan) but we extended our deadline to pick up some last minute crash fixes. I promise to blog about it when we do reach beta, and we’re going to have an increased presence, both on the Camino website and among download sites. It’s important that we get a lot of people to try it out and send us feedback before we go final.

Ben disputes my claim that Camino never crashes. Personally, I think he’s on crack. I have 1.1a2 running for over a month and a half of intense usage on both my laptops and my work desktop without a single crash. Maybe it’s because I turn Java off. What’s Java, you ask? Beats me. I think I used it in 1995. Really, would you allow a 12-year old to run wild in your browser? I think the blink tag is more relevant these days….props to Lou Montulli.

If Pacman Jones can make it rain for $81,000, then I want to be a stripper. Seriously. What’s the visual of a man walking into a club with $81,000 in his pocket?

Oh, I’m sorry, did I digress from Mozilla-related content? Oops. I did it again.

(In fact, they did go beta, but that was just today, so you can’t expect pink to know yet.)

Tell me you were lyin’

August 23rd, 2006

I really, really hope that SPI Labs, whose widely trumpeted report on JavaScript vulnerabilities in feed readers left me cold, were spoofing their user-agent string when they filed their bug on (an old version of) Firefox (that didn’t actually do anything in the component where they filed it).

“Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)” doesn’t give me a secure feeling, even without the “(ax)” for ActiveX.

Some Mac and <p>s

May 22nd, 2006

Back in February, not long after the Intel iMacs came out, I decided I needed one. I’d been using a limping Windows desktop as a stereo, and a not so limping Windows laptop as an everything-else, but I’d idly wanted another Mac ever since my 512K “Fat Mac” died in 1991 or so.

Getting one hasn’t turned out to be the best idea I ever had.

It’s a delightful computer, quick and smooth and elegant, that part’s not a problem. But, now I’ve got a Windows laptop to my left, the Mac directly ahead, and my old Windows desktop turned to Linux to my right. I’m building Firefox trunk on Windows to see if I broke anything with a patch, typing this post and being less funny than I think on IRC and reading email and trying to figure out how to patch the appearance of readonly XUL textboxes on the Mac, and building Firefox branch on Linux, though I’ve already forgotten why and what I’m supposed to test once the build finishes. Most of the time, I think that three computers has made me one third as productive, but sometimes, when I can’t remember what I was doing on any of them, I think it’s worse than just arithmetic.


February 21st, 2006

Because I’m both stupid, and a glutton for punishment, my reaction to the news that Six Apart wants to make Trackback a standard was to sign up for the mailing list.

Their reaction?

The email address you supplied is banned from this mailing list. If you think this restriction is erroneous, please contact the list owners at…

You know what? I think I’ll blog it, instead.

<Boy, this nest sure is roomy>

February 8th, 2006

I wonder, does anyone have anything they’d like to say about some new work they’re doing, maybe with an open source project?

Where’s Mama Bear’s update notification?

February 4th, 2006

Paul Bausch is absolutely right that Firefox’s current update notification, a popup dialog that gives you the choice between “stop what you are doing and restart your browser right now” and “be nagged at some random later time until you stop what you are doing and restart your browser” is the sort of annoyance we use Firefox to avoid, not to seek out.

But the previous version, a red Christmas tree that I think was supposed to be an arrow displayed up by the throbber, flat out didn’t work. For every single non-geek on whose computer I installed Firefox, that was something for me to see when I was doing something else for them, my little Christmas present of also getting to update their browser, and not anything for them to even notice, much less do anything about.

A couple of hours of thinking about less extreme methods of reminding people about an update without being invisible has only left me reinventing Clippy. So, what sort of notification can’t be missed, but can be ignored until you’re ready for it?

Nice <gorilla>; what’s he weigh?

February 1st, 2006

Several things are interesting me about IE7β2, but most of all is a relatively minor decision in the feed handling code.

If you start from the RSS 2.0.1-rv6 spec, and follow along carefully, you should notice that the <description> which is a child of <item> is described as allowing escaped HTML, while no other element is so described, and you then should conclude that no other element allows escaped HTML, that the content model for all other elements is plain text, and if someone has a <title> like <title>&amp;eacute;</title> it is because they want their readers to see &eacute;, not because they want their readers to see an e with an acute accent.

If, however, you start with most weblog software or most existing aggregators, you’ll find that you can put links in your weblog’s subhead by editing its description, and that if you want to italicize Odyssey in a title to make it clear you mean the book, not your car or your own road trip, it not only works in your weblog, but probably makes it into your feed, and works in your aggregator, because someone else tried it long ago, and people complained about how bad it looked when the aggregator displayed <I>Odyssey</I>, so the aggregator author thought “why not?” and started treating item and channel titles and channel descriptions as escaped HTML.

Despite the enormous amount of time people have spent arguing over which one of those is “right,” it really doesn’t matter (except perhaps for a couple dozen people like Norm Walsh who will absolutely refuse to have anything to do with escaped markup). What matters is that there only be one way. If you have to create workable feeds for searches of 300,000 browser bug reports, many of which want to display examples of HTML tags in the titles, then it doesn’t matter too much whether you use <title>&lt;foo&gt; support broken</title> or <title>&amp;lt;foo&amp;gt; support broken</title>. However, if using one is clearly correct and to spec, but using the other one is required to avoid breaking some aggregators and opening XSS holes in others, but that then breaks some which were not broken by doing The Right Thing, then you’re likely to wind up saying “screw you guys, I’m going home” and using Atom, which mostly exists for precisely this reason.

While I have as much hope for the spec rewrite that the new version of the RSS Advisory Board is starting on as all the other people who’ve been banging their heads against the syndication brick wall for so long they’re at risk of naming all their children George, that much hope is about… George! you stop teasing George this instant, or you’ll be grounded like George and George!

So I was quite interested to see that IE7, and thus presumably the Windows Feed Platform, have decided to do the right, and hard, thing, and treat all RSS elements other than item/description as the plain text they are supposed to be. Which leaves me wondering: are they really enough of an 800lb. gorilla to convince everyone else to follow along, and make it once again possible to include a less-than character in an RSS title?

A Google just for <me>

January 11th, 2006

Now that’s my kind of Google: via their results weblog, Last Google (Beta), providing you with the last thing Google wants you to see. For lots of things we both talk about, Randy‘s got me beat for the bottom, since he’s been going out of his way to post duplicate content, but there’s still an enormous number of things for which I’m the very last thing you should look at.

In related news, so far I’m very happy with my switch to searching Yahoo!: their results are quite good, and I’m much happier having to sift through five different sites with the same Wikipedia article than I am wondering what’s being mistakenly hidden from me every time I search. Google may be mostly okay if there’s one and only one possible result for your searches (something that I remember being fairly true a few years ago, when “I’m feeling lucky” was moderately useful, but these days I’m only rarely looking for one exact page), but if you want to look around and decide for yourself, Yahoo! feels like a better bet.

Another <Google> loser heard from

January 9th, 2006

Because it lacked the all-important feature of being about me, me, me, I’d forgotten that I wasn’t the only one getting unpersoned by Google: Matt Mower doesn’t exist either.

The situation isn’t quite as bad as he thinks: in fact, he shows up in [“Matt Mower”], it’s just that when your weblog is result 151 for your own name as a phrase it feels like you’ve been disappeared.

Hmm. Moved from one URL to another (and worse yet, the old one doesn’t redirect to the new), content republished by at least one aggregator which doesn’t decline to be indexed by search engines. Sounds pretty familiar to me.

I’d say the one difference is that Matt cares and I don’t, but if (MS employee) Duncan Mackenzie is going to have trouble finding me again because I’m not indexed in MSN Search unless you already know my URL… well, now you’re starting to get into “actually does matter to me” territory.

<Searching where I’m not hated>

January 8th, 2006

As (Google employee) Nelson Minar notes, sometimes changing URLs by returning a 301 Moved Permanently with the new URL works out fine with search engines: if you search Google for [for fear they’ll lose visibility in search engines], his post at his new URL is the first result.

And as (Google employee) Matt Cutts notes, sometimes it doesn’t work out quite so well. Back at the end of October, when I switched to WordPress, I moved my weblog to the subdomain “weblog.” and changed to WordPress’s default URL scheme, with the words from the post title separated by hyphens (because Underscores are bad (for search engines)) and without the “.php” extension (because, among other things, it makes search results for [foo php] horribly cluttered with things only published using PHP, not about PHP), and redirected all my old URLs to the new ones. Now when you search for a set of words I’ve used in a post, like [when Gmail first added Atom feeds], you will not find my post.

If you want to find me in your Google search results, you need to do one of two things: remember that the parameter to include “duplicate results” is &filter=0 and add that to your query URL, or work your way to the end of the results (in this case, that would be around result 747, despite their claim to have 412,000 results) and click the link to include omitted results. Then, once again work your way out to the end of the results (now at result 976, despite the complete and utter lie of “412,000 results”), and you’ll find me: the last damn thing they think anyone would ever want, with my useless front page, my worthless permalink, my crap-filled paged archive (now blocked off in robots.txt, because there’s really no value a search engine can extract from that view), and my spammy HTMLized version of the Atom autodiscovery RFC (which at least serves the purpose of increasing my spam load).

The other, and faster, way to find me in Google results, searching for the words as a phrase, might hold a partial clue to why I’ve become persona non grata in Google’s view: [“when Gmail first added Atom feeds”] returns one result, from Sameer D’Costa’s aggregator. Include duplicates on that search, and you’ll also see a couple more Gregarius installs, along with my own worthless results. You won’t see my Gregarius install, though, because I know search engines hate duplicate content, so in Gregarius’s Admin/Config I set rss.config.robotsmeta to “noindex, follow” so that every page gets a <meta name="robots" content="noindex,follow" /> to tell search engines not to index my aggregator as duplicate content, though they are welcome to discover any URLs they don’t already know about. I don’t have any way of knowing whether Google first decided I was garbage, and then decided that made me a duplicate of other people aggregating me, or decided I was garbage because I was a duplicate of people duplicating me, but I know it isn’t helping: the only time you should let search engines index the output of an aggregator is when that’s the only place the feeds appear as HTML. Otherwise, it’s duplicate content, and that’s going to wind up hurting someone, whether it’s you or the source.

Now, maybe it’s just me, but I really don’t like getting fucked by someone who spends the whole time punching me and swearing at me and insulting me. If that’s the way Google feels about me, I’d rather just end our relationship. That takes two things. First, I went to about:config and changed keyword.URL to so typing search terms in the addressbar will take me to Yahoo! rather than doing a Google “I’m feeling lucky” search, changed to Yahoo so that selecting text and choosing Search Web for from the context menu would search at Yahoo, and changed to Yahoo so Google wouldn’t be on top. I should probably delete the google.src plugin file, too, but for now I’m not quite willing to burn every last bridge. (And I didn’t switch to MSN Search because they make Google look like the kindest and gentlest of lovers: the only way you’ll find me in any results there is to include in your search terms. Otherwise, I simply don’t exist.)

Then there’s the other half of breaking up: taking away Googlebot’s and msnbot’s keys to my house. Despite the fact that Google just flat out hates me, they’ve requested 6226 pages from me already this month (msnbot has only requested 1836, but they’ve requested robots.txt 104 times, to Googlebot’s 31 — maybe they know what’s coming).

That ain’t free: to keep my host from pushing me into a dedicated server, I had to install a caching plugin, and then reconfigure it to an even longer cache time to prevent misses when they came back for more, just for search engines, which are the only things that ever look at most old weblog posts (well, along with confused and misled searchers, if you happen to be returned as something other than the very last result after duplicate results are included). But, block Googlebot? That seems pretty serious, somehow, even though most of the “visitors” they deliver are just comment spammers (one of the clues that I’d become invisible in search engines was just how little comment spam I’m getting).

So, just like every abused woman on a crappy talk show that you want to shake some sense into, I’ll give Googlebot and his buddy msnbot another month, hoping he’ll change his abusive ways. After all, maybe one of his friends is reading this, and can talk some sense into him.