<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Analog Point Solutions [Weblog]</title>
	<atom:link href="http://blog.analogpoint.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.analogpoint.com</link>
	<description>Rants on Php, MySQL, JS, Ajax, Web Standards and anything else I find interesting</description>
	<pubDate>Fri, 21 Dec 2007 02:40:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>Ebay is a couple of years late</title>
		<link>http://blog.analogpoint.com/ebay-is-a-couple-of-years-late/</link>
		<comments>http://blog.analogpoint.com/ebay-is-a-couple-of-years-late/#comments</comments>
		<pubDate>Fri, 21 Dec 2007 02:40:19 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Weird]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/ebay-is-a-couple-of-years-late/</guid>
		<description><![CDATA[I&#8217;ll let the screen cap speak for itself.

]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ll let the screen cap speak for itself.</p>
<p><img src='http://blog.analogpoint.com/wp-content/uploads/2007/12/ebay.gif' alt='ebay.gif' /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/ebay-is-a-couple-of-years-late/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Forward your site to Coral Cache</title>
		<link>http://blog.analogpoint.com/forward-your-site-to-coral-cache/</link>
		<comments>http://blog.analogpoint.com/forward-your-site-to-coral-cache/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 02:54:54 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Webserver]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/forward-your-site-to-coral-cache/</guid>
		<description><![CDATA[If you&#8217;re getting hit with digg/slashdot/reddit traffic, you can easily forward you site to Coral Cache to relieve the strain.

RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192.168.1.2$
RewriteCond %{HTTP_USER_AGENT} !^CoralWebPrx
RewriteCond %{QUERY_STRING} !(^&#124;&#038;)coral-no-serve$
RewriteCond %{HTTP_REFERER} ^http://(www.)?digg.com [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?slashdot.org [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?slashdot.com [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?fark.com [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?somethingawful.com [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?engadget.com [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?boingboing.net [OR]
RewriteCond %{HTTP_REFERER} ^http://(www.)?del.icio.us
RewriteRule ^(.*)$ http://blog.analogpoint.com.nyud.net/$1 [R,L]
]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re getting hit with digg/slashdot/reddit traffic, you can easily forward you site to <a href="http://www.coralcdn.org/">Coral Cache</a> to relieve the strain.<br />
<code><br />
RewriteEngine on<br />
RewriteCond %{REMOTE_ADDR} !^192.168.1.2$<br />
RewriteCond %{HTTP_USER_AGENT} !^CoralWebPrx<br />
RewriteCond %{QUERY_STRING} !(^|&#038;)coral-no-serve$<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?digg.com [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?slashdot.org [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?slashdot.com [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?fark.com [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?somethingawful.com [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?engadget.com [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?boingboing.net [OR]<br />
RewriteCond %{HTTP_REFERER} ^http://(www.)?del.icio.us<br />
RewriteRule ^(.*)$ http://blog.analogpoint.com.nyud.net/$1 [R,L]</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/forward-your-site-to-coral-cache/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Character that Broke Reddit</title>
		<link>http://blog.analogpoint.com/the-character-that-broke-reddit/</link>
		<comments>http://blog.analogpoint.com/the-character-that-broke-reddit/#comments</comments>
		<pubDate>Mon, 27 Aug 2007 03:32:37 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Weird]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/the-character-that-broke-reddit/</guid>
		<description><![CDATA[
There&#8217;s an interesting story on reddit today that talks about the rotund ninja star character that does cool stuff like reverse text direction.  The reddit story links to this post, where an enlightened commenter points us to Wikipedia.  I still feel all but enlightened.  Can anyone comment on this?  
I&#8217;d also [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://blog.analogpoint.com/wp-content/uploads/2007/08/reddit-broke.png' alt='reddit-broke.png' /></p>
<p>There&#8217;s an interesting <a href="http://reddit.com/info/2iy4c/comments">story on reddit</a> today that talks about the rotund ninja star character that does cool stuff like reverse text direction.  The reddit story links to <a href="http://www.tipotheday.com/2007/08/26/wtf-is-this-character/">this post</a>, where an enlightened commenter points us to <a href="http://en.wikipedia.org/wiki/Unicode_control_characters#Bidirectional_text_control">Wikipedia</a>.  I still feel all but enlightened.  Can anyone comment on this?  </p>
<p>I&#8217;d also like to know who that character shows up in reddit <em>after</em> the URL.  Reddit is busted. <img src='http://blog.analogpoint.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Here&#8217;s the test ‫‬‭‮‪‫‬‭‮ Here&#8217;s the test. ҉</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/the-character-that-broke-reddit/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Stop NoScript from opening the update/welcome page every time it&#8217;s updated</title>
		<link>http://blog.analogpoint.com/stop-noscript-from-opening-the-updatewelcome-page-every-time-its-updated/</link>
		<comments>http://blog.analogpoint.com/stop-noscript-from-opening-the-updatewelcome-page-every-time-its-updated/#comments</comments>
		<pubDate>Wed, 22 Aug 2007 15:42:12 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Firefox]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/stop-noscript-from-opening-the-updatewelcome-page-every-time-its-updated/</guid>
		<description><![CDATA[I appreciate the security enhancements that NoScript offers for Firefox, but with the tight update schedule (an update is pushed through often several times a week), the &#8220;update&#8221; page that is shown every time gets kind of tiresome.  I did some quick googling, and couldn&#8217;t find a solution.  I finally did find the [...]]]></description>
			<content:encoded><![CDATA[<p>I appreciate the security enhancements that NoScript offers for <a href="http://mozilla.com">Firefox</a>, but with the tight update schedule (an update is pushed through often several times a week), the &#8220;update&#8221; page that is shown every time gets kind of tiresome.  I did some quick googling, and couldn&#8217;t find a solution.  I finally did find the answer buried in the <a href="http://noscript.net/faq">NoScript FAQ</a>.  Just type <strong>about:config</strong> in the location bar, then type <strong>noscript.first</strong> in the filter to bring up the <strong>noscript.firstRunRedirection</strong> preference.  Double-click it to change it to false.  I hope it helps someone.</p>
<blockquote><p>Q:   I don&#8217;t like NoScript redirecting the browser on its welcome page every time I upgrade it. Is there any way to prevent this?<br />
A:   First time you install NoScript and every time you upgrade it to a newer major version, Firefox opens an additional tab containing the NoScript welcome page, where you can read the release notes, announcements and an explanation of the most important NoScript features. If you&#8217;re a power user and you feel you don&#8217;t need such heads up, you can disable this feature by opening about:config (just like it was a normal web address) and toggling off the noscript.firstRunRedirection preference. </p></blockquote>
<p><img src='http://blog.analogpoint.com/wp-content/uploads/2007/08/noscript.PNG' alt='noscript.PNG' /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/stop-noscript-from-opening-the-updatewelcome-page-every-time-its-updated/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The easiest way to check your site at different screen resolutions</title>
		<link>http://blog.analogpoint.com/the-easiest-way-to-check-your-site-at-different-screen-resolutions/</link>
		<comments>http://blog.analogpoint.com/the-easiest-way-to-check-your-site-at-different-screen-resolutions/#comments</comments>
		<pubDate>Thu, 28 Jun 2007 19:04:34 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/the-easiest-way-to-check-your-site-at-different-screen-resolutions/</guid>
		<description><![CDATA[There are still a few folks out there with old 800 x 600 pixel monitors, and if you want to take that into account when designing your website, you can use this handy trick to quickly see what any site looks like at different resolutions.  Simply copy and paste the following Javascript into the [...]]]></description>
			<content:encoded><![CDATA[<p>There are still a few folks out there with old 800 x 600 pixel monitors, and if you want to take that into account when designing your website, you can use this handy trick to quickly see what any site looks like at different resolutions.  Simply copy and paste the following Javascript into the Location bar of your browser and hit enter while viewing the site in question. The following bit will resize your browser to 800 pixels wide and 600 pixels high. You can change the width and height to any other resolution you&#8217;d like to test as well.<br />
<code><br />
javascript: self.resizeTo(800, 600);<br />
</code></p>
<p>I&#8217;ve also created a quick bookmarklet. Take this link: <a href="javascript:self.resizeTo(800,600);">800&#215;600</a>, and  drag it to your bookmarks/links toolbar and then click it to resize your window to 800 x 600 pixels.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/the-easiest-way-to-check-your-site-at-different-screen-resolutions/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Microsoft Makes Fun of Itself</title>
		<link>http://blog.analogpoint.com/microsoft-makes-fun-of-itself/</link>
		<comments>http://blog.analogpoint.com/microsoft-makes-fun-of-itself/#comments</comments>
		<pubDate>Mon, 28 May 2007 02:12:59 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/microsoft-makes-fun-of-itself/</guid>
		<description><![CDATA[Microsoft must really have some nerve to run this ad.  Or it was a disgruntled employee trying to get back at his employer. I especially like the &#8220;Bulletproof reliability&#8221;.

]]></description>
			<content:encoded><![CDATA[<p>Microsoft must really have some nerve to run this ad.  Or it was a disgruntled employee trying to get back at his employer. I especially like the &#8220;Bulletproof reliability&#8221;.</p>
<p><img src='http://blog.analogpoint.com/wp-content/uploads/2007/05/microsoft-joke.jpg' alt='Microsoft Ad' /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/microsoft-makes-fun-of-itself/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Redirect to the HTTPS version of a page</title>
		<link>http://blog.analogpoint.com/redirect-to-the-https-version-of-a-page/</link>
		<comments>http://blog.analogpoint.com/redirect-to-the-https-version-of-a-page/#comments</comments>
		<pubDate>Mon, 14 May 2007 14:43:44 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Webserver]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/redirect-to-the-https-version-of-a-page/</guid>
		<description><![CDATA[I often have the problem that a client wants their customers to login on a secure site.  The following .htaccess files are a simple way of accomplishing this by redirecting the the sercure version.
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
If that doesn&#8217;t work, try this:
RewriteEngine On
RewriteCond %{SERVER_PORT} !443
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R]
]]></description>
			<content:encoded><![CDATA[<p>I often have the problem that a client wants their customers to login on a secure site.  The following .htaccess files are a simple way of accomplishing this by redirecting the the sercure version.</p>
<p><code>RewriteEngine On<br />
RewriteCond %{HTTPS} off<br />
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}</code></p>
<p>If that doesn&#8217;t work, try this:</p>
<p><code>RewriteEngine On<br />
RewriteCond %{SERVER_PORT} !443<br />
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R]</code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/redirect-to-the-https-version-of-a-page/feed/</wfw:commentRss>
		</item>
		<item>
		<title>C++ Quote</title>
		<link>http://blog.analogpoint.com/c-quote/</link>
		<comments>http://blog.analogpoint.com/c-quote/#comments</comments>
		<pubDate>Sun, 13 May 2007 00:57:21 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[C++]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/c-quote/</guid>
		<description><![CDATA[c++; /* this makes c bigger but returns the old value */ -- Unknown
]]></description>
			<content:encoded><![CDATA[<blockquote><code>c++; /* this makes c bigger but returns the old value */ -- Unknown</code></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/c-quote/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Dollar-Sign Function</title>
		<link>http://blog.analogpoint.com/the-dollar-sign-function/</link>
		<comments>http://blog.analogpoint.com/the-dollar-sign-function/#comments</comments>
		<pubDate>Wed, 02 May 2007 17:37:09 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/the-dollar-sign-function/</guid>
		<description><![CDATA[There are many dollar sign functions out there, especially in the Javascript packages such as Prototype or MooFX. Peter-Paul Koch over at Quirksmode offers a cross-browser version of document.getElementById.   Let&#8217;s combine all the goodness from each of these to make a souped-up $() dollar sign function that works in most browsers, and is [...]]]></description>
			<content:encoded><![CDATA[<p>There are many <a href="http://www.dustindiaz.com/top-ten-javascript/">dollar sign functions</a> out there, especially in the Javascript packages such as <a href="http://www.prototypejs.org/">Prototype</a> or<a href="http://mootools.net/"> MooFX</a>. <a href="http://www.quirksmode.org/about/intro.html">Peter-Paul Koch</a> over at Quirksmode offers a <a href="http://www.quirksmode.org/js/dhtmloptions.html">cross-browser version of document.getElementById</a>.   Let&#8217;s combine all the goodness from each of these to make a souped-up $() dollar sign function that works in most browsers, and is not dependant on the DOM implementation of just one.  It&#8217;s actually 2 functions, the $() and then a helper function.</p>
<p><code>
<pre>
function $() {
	var elements = new Array();
	for (var i = 0; i < arguments.length; i++) {
		var element = arguments[i];
		if (typeof element == 'string')
			element = getElementByIdCompat(element);
		if (arguments.length == 1)
			return element;
		elements.push(element);
	}
	return elements;
}
function getElementByIdCompat(name) {
	if (document.getElementById) {
		return document.getElementById(name);
	} else if (document.all) {
		return document.all[name];
	} else if (document.layers) {
		var theobj = {};
		theobj = document.layers[name];
		theobj.style = document.layers[name];
		return theobj;
	}
}</pre>
<p></code></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/the-dollar-sign-function/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Random Post Wordpress plugin</title>
		<link>http://blog.analogpoint.com/random-post-wordpress-plugin/</link>
		<comments>http://blog.analogpoint.com/random-post-wordpress-plugin/#comments</comments>
		<pubDate>Mon, 30 Apr 2007 18:34:08 +0000</pubDate>
		<dc:creator>Analogpoint</dc:creator>
		
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://blog.analogpoint.com/random-post-wordpress-plugin/</guid>
		<description><![CDATA[I&#8217;ve just written and released a Random Post plugin for Wordpress.  Read more about it (and download it) on the download page.  If you have any issues, suggestions, compaints or feature requests, post in the comments here.   Test it out by clicking &#8220;random post&#8221; to the left.
]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve just written and released a <a href="http://www.analogpoint.com/wp-plugins/random-post/">Random Post plugin</a> for Wordpress.  Read more about it (and download it) on the <a href="http://www.analogpoint.com/wp-plugins/random-post/">download page</a>.  If you have any issues, suggestions, compaints or feature requests, post in the comments here.   Test it out by clicking &#8220;random post&#8221; to the left.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.analogpoint.com/random-post-wordpress-plugin/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.792 seconds -->
