<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A New Library: NSFW JS &#8212; Protect Your Visitors at Work</title>
	<atom:link href="http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/</link>
	<description>Stuff only Michi cares to read</description>
	<lastBuildDate>Sun, 22 Jan 2012 10:48:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TV Online</title>
		<link>http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/#comment-254</link>
		<dc:creator>TV Online</dc:creator>
		<pubDate>Fri, 29 Dec 2006 21:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://michikono.com/blog/2006/12/29/protect-your-visitors-from-nsfw-content/#comment-254</guid>
		<description>good example!</description>
		<content:encoded><![CDATA[<p>good example!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michi</title>
		<link>http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/#comment-252</link>
		<dc:creator>Michi</dc:creator>
		<pubDate>Fri, 29 Dec 2006 09:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://michikono.com/blog/2006/12/29/protect-your-visitors-from-nsfw-content/#comment-252</guid>
		<description>I thought about implementing it using CSS to cover it up. That is why easter egg #1 (automatic class assignment) is in place. However, hiding div blocks wasn&#039;t a solution I was pleased with since my goal was to never break any site. Large pieces of content dissapearing would present a problem. However, using visibility: hidden was exactly what I was going for with the coloring, so I will fix that.

I&#039;ll try to release another version over the weekend that will address the following:

1. individual initialization of objects rather than blanket initialization for speedier rendering of pages with lots of content but only very few NSFW tags.
2. Use visibility: hidden instead of re-coloring.
3. Add more support tags (span).
4. Create an auto-bind so that calling initialize is no longer required except when doing AJAX.</description>
		<content:encoded><![CDATA[<p>I thought about implementing it using CSS to cover it up. That is why easter egg #1 (automatic class assignment) is in place. However, hiding div blocks wasn&#8217;t a solution I was pleased with since my goal was to never break any site. Large pieces of content dissapearing would present a problem. However, using visibility: hidden was exactly what I was going for with the coloring, so I will fix that.</p>
<p>I&#8217;ll try to release another version over the weekend that will address the following:</p>
<p>1. individual initialization of objects rather than blanket initialization for speedier rendering of pages with lots of content but only very few NSFW tags.<br />
2. Use visibility: hidden instead of re-coloring.<br />
3. Add more support tags (span).<br />
4. Create an auto-bind so that calling initialize is no longer required except when doing AJAX.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJ Doland</title>
		<link>http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/#comment-251</link>
		<dc:creator>PJ Doland</dc:creator>
		<pubDate>Fri, 29 Dec 2006 09:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://michikono.com/blog/2006/12/29/protect-your-visitors-from-nsfw-content/#comment-251</guid>
		<description>Please look at the changes to the original spec that have been posted here:

http://pj.doland.org/archives/041574.php

A few small changes were necessary due to standards compliance issues.</description>
		<content:encoded><![CDATA[<p>Please look at the changes to the original spec that have been posted here:</p>
<p><a href="http://pj.doland.org/archives/041574.php" rel="nofollow">http://pj.doland.org/archives/041574.php</a></p>
<p>A few small changes were necessary due to standards compliance issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nanook</title>
		<link>http://www.michikono.com/2006/12/29/a-new-library-nsfw-js-protect-your-visitors-at-work/#comment-249</link>
		<dc:creator>Nanook</dc:creator>
		<pubDate>Fri, 29 Dec 2006 08:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://michikono.com/blog/2006/12/29/protect-your-visitors-from-nsfw-content/#comment-249</guid>
		<description>Nice (and quick!) but when you middle click for a new tab it doesn&#039;t work!</description>
		<content:encoded><![CDATA[<p>Nice (and quick!) but when you middle click for a new tab it doesn&#8217;t work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Object Caching 384/388 objects using disk: basic

Served from: www.michikono.com @ 2012-02-10 18:40:21 -->
