I think that it would be helpful for the image backgrounds on the embeddable images to be transparent.

We should present a hidden, text-only message at the top of the page for users of alternative user agents, especially screen readers. This message should be marked as a WAI-ARIA live region with the appropriate attributes.

Reported bug when using member code on Blogger:

blogger complains about semicolons and undefined values (campaign and variant)

Any particular reason the embed code has this;

idl.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'members.internetdefenseleague.org/include/?url=' + (_idl.url || '') + '&campaign=' + (_idl.campaign || '') + '&variant=' + (_idl.variant || 'banner');

when this works the same:

idl.src = '//members.internetdefenseleague.org/include/?url=' + (_idl.url || '') + '&campaign=' + (_idl.campaign || '') + '&variant=' + (_idl.variant || 'banner');

As Paul Irish explains here, http://www.paulirish.com/2010/the-protocol-relative-url/, it's only really an issue for IE6. I'll admit, it's not a huge change, but why evaluate a conditional if you don't have to?

An oversight: no character set was defined in the HTML files served by the idl_launch campaign. These should be added.

When we have a new campaign, we should publish a static version of the script for organizations that don't want to run outside code (for various reasons, including security).

Functionally this will be the same code - it might also be nice to provide it in a way so they can see a clean well documented version as well as a minified no-nonsense version. Assets could also be included - maybe zipped up with the minified version of the code.

More details here.

This is what the IDL was invented for. Now lets activate it. Four Three days until possible doom.

Republicans control congress. Republicans have mostly been talked into by team cable to vote "nay" to net neutrality. Unless we harness the public, the net will become an active battleground of censorship, hate, and monopolies.

Use +1 for support

To ensure that ISP proxies only serve compressed responses to users whose browsers support compression, the Vary: Accept-Encoding header should be sent with all static assets.

Campaign HTML should be minified, to reduce the number of bytes pushed through the pipe.

I installed the Wordpress plug-in for my Wordpress page on Dream Host, and all worked fine. However on two pages (www.mcgurrin.com and www.mcgurrin.com/ics/) I've tried installing code just below , just before and just before and don't see anything appearing on either page. This is on the 4th of July, so there should be a display. Any clues what might be wrong or something I need to change on my site?

Grooveshark is defunct, due to being seized through a RIAA lawsuit, and now being used to spam a ticket site called scorebig.
internetdefenseleague.org is still listing them as a member.

I had some issues with a banner-based campaigns in the past that they destroyed the layout of the website. I have just been updating the theme on my blog, but I am unable to test if the banner campaign will block it again. Is there a way to force rendering of some past campaign just to see how it would look like? Do you know which one had a banner which pushed the whole content of the website down?

We should develop an evergreen campaign that allows users to always display IDL messages, even when there are no active campaigns. Effectively, this creates a third frequency option:

1. Only a specific campaign
2. Any active campaigns
3. Any active campaigns, and an evergreen message when there are no active campaigns

Messaging of the evergreen campaign should be similar to the launch campaign: it should convey that the site is a member of the IDL and present a signup form for others to join.

We have a user report that gzip is not working properly. We should investigate this with both static files served on S3 and those generated and cached by Django.

I've been using the Wordpress plugin version of the Fight For the Future code and the author suggested I post here. I'd like to know how many times the campaign message should be shown to one visitor, because it seems inconsistent. Testing my site on Google Chrome, I got the popup appearing every time I browsed to a new page. This is unacceptable to me and will just likely annoy visitors. On IE and Firefox however I only get the message once per site visit, which is absolutely fine.

I don't understand this inconsistency as apparently no cookies are set per-visitor. I'd suggest that showing the message every time a new page is loaded is simply going to frustrate visitors and be unacceptable to webmasters. Although the code can be added to just the homepage, many visitors will enter the site through a search engine link to read an article that interests them and therefore may never touch the homepage.

I suggest adding code so that the message is only displayed once per visit.