Are you using whitelist-based or blacklist-based HTML sanitizing? I'd caution against the latter, if that's what you're doing.

I was viewing the script source and noticed some oddities. For example, this line:

var ul = <ul/>;

Looks like some single quotes have been stripped out?

Actually, this isn't really useful above WordPress 2.5. WP 2.6 puts inactive plugins in a separate table.

I'm getting an error in FF 2.0.0.x: "iterator.bind is not a function", apparently on line 286. (I know the script isn't even that long, I'm just letting you know what FF says.)

A few suggestions:

1. I'm getting "Component is not available" with your script, apparently on line 9. Any ideas?
2. I'd suggest using the icons glossary as the interface page. Maybe put +/0/- radio buttons on each item.
3. The current description is confusing. Do you click top/middle/bottom, or left/center/right? Or do you drag up and down using the left third? Or i the left third divided vertically into three zones?

@Aquilax: Rudi Pittman is correct.

Bulk mailers fall into two categories:

1. Truly illegitimate spammers, who always spoof the From: address, sometimes using another victim's email, and
2. Misguided or skeevy businesses, with whom you have a tenuous (at best) business relationship.

Using this script on the former only harms other hapless netizens. Using this script on the latter does nothing to hurt the bulk-mailing business (since they most likely have a business-class spam-filter appliance), and probably hurts the random businesses whose newsletters you are requesting for the bulk-mailer. (Their mail gets incorrectly marked as spam.)

Do you see the issue? You are only perpetuating the problem.

What you can do is keep marking those original newsletters as spam, on the email provider side. For example, I make sure to mark such things as spam on GMail, not just in my email client. Because providers use collaborative spam-filters, pretty soon the newsletter will not reach anyone, and the business will end up on a blacklist. :-)

@cspy: Sure, but that requires installing an extension. If you already have GreaseMonkey installed, you won't have to restart to use this script. And if you have FireBug or LiveHttpHeades, you could just look for where the FLV is being pulled from and download that instead.

The purpose of this script is to provide a GreaseMonkey solution to the STC problem. That's all.

SurfTheChannel recently reverted their site to an older design. I may be able to rework the script to work with either site -- we'll see.

Edit: Jakkers, try now. I've updated the script.

Relevant to this: http://reddit.com/info/2o9vf/comments

Ah, thanks for that, engtech. I'll add that in.

I'd caution against forcing autocomplete on a global basis. Autocomplete=off requests that the browser not save certain data in the first place. This is important with credit card numbers, for example.