It's Just this Little Chromium Switch Here

Weblogging and commentary by Chip Rosenthal

MeFi Meetup

A meetup for Austin-area MetaFilter users has been scheduled for June 3rd. I think I may go. Anybody else?

More info here.

Public Wireless Netiquette

I'm currently sitting in the Green Mesquite sipping on an ice tea. I've got three hours until my next appointment. Rather than go back home to work, I'm going to stay downtown. I can do that thanks to ubiquitous free public wireless.

I've been thinking there should be some code of etiquette for using free wireless. A lot of businesses are taking a risk by making it available. If wireless access is abused or starts becoming a burden, they will quickly pull the plug.

Here are the guidelines I tend to follow, to try to be a good wireless citizen.

  • Avoid peak hours. The venue is making money on the drink I'm sipping, but they'd make even more money if they could serve somebody lunch at the table I'm occupying. Last Friday morning I was at Quack's 43rd Street Bakery, eating a coffee roll and doing some work. As lunchtime neared it started filling up. That was my cue to hit the road.
  • Tip a little more. If I stay somewhere for a while I'll tip a couple of extra bucks. I feel like I ought to compensate them a bit more, particularly if there is table service. I'm concerned that free wireless users might be perceived as freeloaders. Extra tipping may dispel that.
  • Limit my time. I won't stay at one place all afternoon. I'm not sure an extra cup of coffee and couple bucks tip is sufficient compenstation for monopolizing a table. Plus, since wireless is so readily available, it's easy enough to pick up stakes and move elsewhere. After about two hours, I'll move along.

I suspect many wireless users take care to use the resource courteously. Like all Internet facilities, a form of netiquette will evolve. We probably ought to make some effort to document and publicize it.

Spam with your Salsa

Recently, I ordered a gift box of salsa from Jardine's Foods (of Buda) for my mom. Jardine gave me an extra little present that is causing me indigestion: they started spamming me with junk email advertisements.

Technically speaking, even though the unsolicited email is annoying and abusive, it's not really spam. That's because I bought something from them, so I have a business relationship with them. It's generally considered acceptable for businesses you work with to email you, but most reputable companies will at least verify you want to opt-into their advertising materials before they start spamming you.

So, I today I severed that relationship. I directed them to stop spamming me, and I vowed to never purchase another Jardine's product. Before you purchase any Jardine's products, you might consider whether you want to open yourself to the risk of junk email, and whether you want to support businesses that use spamming practices.

Silence of the A-List

I've been reading a lot about the Movable Type license change. I already noted that I'm unhappy about this. I think this was handled extraordinarily poorly. I've been reading a lot on the issue, not just to see people's responses, but also to pick up hints for possible replacement tools.

While reading the responses, I'm stricken by the complete lack of comment on the matter among the A-List bloggers—at least the ones I follow. I suspect many of them have been placed in an awkward position. They may see the move as ill-advised, but don't want to talk trash about their friends Anil and the Trotts. So rather than comment on this important development, we're hearing a lot of silence.

It's almost like we've got our own little form of media consolidation in the blogosphere.

Movable Type License Harmful to Group Blogs

You know that article I blogged about sticking with Movable Type? Is it too late to take it back?

Today, Six Apart announced a new licensing and pricing structure for the Movable Type weblog platform. Although a no-cost version will continue to be available, it will be severely limited. If you are doing anything more complicated than a single person blog, then you'll probably need to start paying. Depending on what you are doing, you may end up paying some big bucks.

Sticking with Movable Type

I've been messing around with various online publishing and collaboration tools recently. I found several appealing options for blogging. There are, however, a number of reasons I keep coming back to Movable Type.

Apologies to RSS Readers

People viewing this blog via RSS may be seeing recent articles reposted. I'm converting the site from HTML 4.01 to XHTML 1.0. I've made markup corrections to a lot of articles, and the updates may be appearing in your RSS stream. Sorry for any inconvenience.

Spam Assassin versus Movable Type

Spam Assassin and Movable Type got into a little tussle today. I have comment notification enabled, so I can see whenever somebody posts a comment to my blog and I can respond to comment spam quickly. My favorite part of the MT-Blacklist module is that it adds a de-spam link at the bottom of these notifications. It allows me to remove comment spam with a single click. My blog ends up being pretty spam free, but this depends upon receiving prompt notification.

I was perturbed to find that a bunch of spam had accumulated on my blog today. I never saw any notifications of the postings, so they've just been sitting there all day.

On a hunch I checked my email spam folder and—sure enough—the notifications had been classified as spam and refiled. I never saw the notifications because they never made it to my mailbox.

So, if you are running Spam Assassin (or similar spam filtering tools) you may want to take care to ensure comment notifies aren't classified as spam. I added a whitelist_from entry to my system /etc/spamassassin/local.cf file, and set it to accept all email generated by the web server.

Movable Type "better_spam_protect" Plug-In

Link: Software Archive: better_spam_protect

In the Movable Type weblog system, the names of entry and comment authors often are linked to their email address. Movable Type has a spam_protect feature to protect these addresses against harvesting by spam spiders. This feature, unfortunately, is not effective.

A new plug-in called better_spam_protect provides improved spam protection. Javascript is used to produce email addresses, thus making it less prone to harvesting. Users without Javascript (and—hopefully—spam harvesters) will see the name, but not the email address.

Comment Author Email Addresses Enabled

A week ago I disabled links to email addresses for comment authors. Tonight, I enabled them again.

When somebody leaves a comment, I don't spam spiders harvesting their email address. Movable Type has protections against this, but they don't work. So, I stopped publishing those addresses while I worked on finding a technique that is effective.

I think I've got that technique now. I'll leave a comment on this posting. You can view the source to see what you think.

I'll publish the code here once I have a chance to finish testing and documenting it.

Apr 29 update: It's published.