On 7/22/10 2:10 PM, Roan Kattouw wrote:
Note that, as Aryeh's proposal mentions, it'll have to rely on JavaScript in order to not totally kill our caching infrastructure. This means censoring will not work for users who have JavaScript disabled or use JavaScript-incapable browsers.
Half of Aryeh's proposal is about generating CSS rules on the fly. But imagine if you could load content-blocking CSS like we have for skins today.
I imagine a system that lets you pick which categories to block, and then either creates or reuses a simple CSS file that can be cached forever.
So the CSS could set visibility:hidden for the offending content first. Then *if* the JS manages to run you get the click-through-to-view interface.