As it looks like we will most likely be using CentralNotice for the blackout (for a variety of reasons - easy scheduling, geotargeting, caching, doesn't interfere with site indexing by Google, etc.), you will likely be able to bypass the blackout simply by turning off Javascript. There has been discussion of taking more extreme measures, but I'm not sure how likely any of them are to be implemented. It's also likely that the mobile site will not be blacked-out since they are launching a new interface right around that time, but you'd have to ask Tomasz about that.
On the issue of cookies, that is actually a tricky detail to implement. Right now, if you have the cookie set to hide CentralNotice banners, it will not show you the blackout (or any other banners). I was thinking we could work around this by adding some JS to Common.js on the 18th that resets that cookie for everyone. The cache on Common.js is only 5 minutes client-side, but how long is the cache on the server-side? Does that sound like a good solution? Ryan Kaldari On 1/15/12 7:23 PM, Tim Starling wrote: > On 16/01/12 13:30, Krinkle wrote: >> The default behavior taken with central notices is a close button >> which will set a cookie. Once the cookie is set, the banner >> is no longer shown. > The "soft blackout" option on WP:SOPA has only 74 support votes (30 > oppose), compared to 519 support votes (77 oppose) for a "full > blackout", i.e. without a close button. > > -- Tim Starling > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
