<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Exploited Web &#187; Web Development</title>
	<atom:link href="http://blog.exploitedweb.com/category/web-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.exploitedweb.com</link>
	<description>Arbiter between Virtuality and Reality</description>
	<lastBuildDate>Tue, 20 Apr 2010 03:07:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Web Technology List</title>
		<link>http://blog.exploitedweb.com/web-development/web-technology-list/</link>
		<comments>http://blog.exploitedweb.com/web-development/web-technology-list/#comments</comments>
		<pubDate>Mon, 12 Apr 2010 19:45:41 +0000</pubDate>
		<dc:creator>Jonathan Discipulo</dc:creator>
				<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://blog.exploitedweb.com/?p=98</guid>
		<description><![CDATA[I am constantly eyeing for existing as well as emerging web technologies. Below is the list of them along with their current version plus reference site if available. I will be updating this page whenever possible. Web XHTML 2.0 [ http://en.wikipedia.org/wiki/XHTML#XHTML_2.0 ] CSS 3 [ http://www.css3.info/ ] HTML 5 [ http://www.w3schools.com/html5/html5_reference.asp ] JavaScript [ http://www.w3schools.com/js/default.asp [...]]]></description>
			<content:encoded><![CDATA[<p>I am constantly eyeing for existing as well as emerging web technologies. Below is the list of them along with their current version plus reference site if available. I will be updating this page whenever possible.</p>
<p><strong>Web</strong></p>
<ul>
<li>XHTML 2.0 [ <a href="http://en.wikipedia.org/wiki/XHTML#XHTML_2.0">http://en.wikipedia.org/wiki/XHTML#XHTML_2.0</a> ]</li>
<li>CSS 3 [ <a href="http://www.css3.info/">http://www.css3.info/</a> ]</li>
<li>HTML 5 [ <a href="http://www.w3schools.com/html5/html5_reference.asp">http://www.w3schools.com/html5/html5_reference.asp</a> ]</li>
<li>JavaScript [ <a href="http://www.w3schools.com/js/default.asp">http://www.w3schools.com/js/default.asp</a> ]</li>
<li>Adobe Flash CS4 [ <a href="http://labs.adobe.com/technologies/flashcs5/">http://labs.adobe.com/technologies/flashcs5/</a> ]</li>
<li>ActionScript 3 [ <a href="http://www.adobe.com/devnet/actionscript/articles/actionscript3_overview.html">http://www.adobe.com/devnet/actionscript/articles/actionscript3_overview.html</a> ]</li>
<li>AJAX [ <a href="http://www.w3schools.com/Ajax/Default.Asp">http://www.w3schools.com/Ajax/Default.Asp</a> ]</li>
<li>PHP 5 [ <a href="http://www.php.net/">http://www.php.net/</a> ]</li>
<li>MySQL 5 [ <a href="http://www.mysql.com/">http://www.mysql.com/</a> ]</li>
<li>Apache [ <a href="http://www.apache.org/">http://www.apache.org/</a> ]</li>
<li>Linux [ <a href="http://www.linux.org/">http://www.linux.org/</a> ]</li>
</ul>
<p><strong>Syndication</strong></p>
<ul>
<li>XML [ <a href="http://en.wikipedia.org/wiki/XML">http://en.wikipedia.org/wiki/XML</a> ]</li>
<li>RSS [ <a href="http://en.wikipedia.org/wiki/RSS">http://en.wikipedia.org/wiki/RSS</a> ]</li>
<li>RDF [ <a href="http://en.wikipedia.org/wiki/Resource_Description_Framework">http://en.wikipedia.org/wiki/Resource_Description_Framework</a> ]</li>
<li>JSON [ <a href="http://www.json.org/">http://www.json.org/</a> ]</li>
</ul>
<p><strong>API<br />
</strong></p>
<ul>
<li>Twitter API [ <a href="http://apiwiki.twitter.com/">http://apiwiki.twitter.com/</a> ]</li>
<li>Facebook API [ <a href="http://wiki.developers.facebook.com/index.php/API">http://wiki.developers.facebook.com/index.php/API</a> ]</li>
<li>Google Gadgets [ <a href="http://code.google.com/apis/gadgets/">http://code.google.com/apis/gadgets/</a> ]</li>
<li>Google Maps [ <a href="http://code.google.com/apis/maps/">http://code.google.com/apis/maps/</a> ]</li>
<li>Google Chart [ <a href="http://code.google.com/apis/chart/image_charts.html">http://code.google.com/apis/chart/image_charts.html</a> ]</li>
<li>Google Analytics [ <a href="http://code.google.com/apis/analytics/docs/">http://code.google.com/apis/analytics/docs/</a> ]</li>
</ul>
<p><strong>Facebook Apps</strong></p>
<ul>
<li>RESTful [ <a href="http://wiki.developers.facebook.com/index.php/API">http://wiki.developers.facebook.com/index.php/API</a> ]</li>
<li>FBJS [ <a href="http://wiki.developers.facebook.com/index.php/FBJS">http://wiki.developers.facebook.com/index.php/FBJS</a> ]</li>
<li>FQL [ <a href="http://wiki.developers.facebook.com/index.php/FQL">http://wiki.developers.facebook.com/index.php/FQL</a> ]</li>
<li>FBML [ <a href="http://wiki.developers.facebook.com/index.php/FBML">http://wiki.developers.facebook.com/index.php/FBML</a> ]</li>
<li>XFBML [ <a href="http://wiki.developers.facebook.com/index.php/XFBML">http://wiki.developers.facebook.com/index.php/XFBML</a> ]</li>
<li>Connect [ <a href="http://developers.facebook.com/docs/?u=facebook.jslib.FB.Connect">http://developers.facebook.com/docs/?u=facebook.jslib.FB.Connect</a> ]</li>
</ul>
<p><strong>Ad Tracking</strong></p>
<ul>
<li>Motif [ <a href="http://www.doubleclick.com/products/richmedia/index.aspx">http://www.doubleclick.com/products/richmedia/index.aspx</a> ]</li>
<li>Atlas [ <a href="http://www.atlasrichmedia.com/">http://www.atlasrichmedia.com/</a> ]</li>
<li>PointRoll [ <a href="http://www.pointroll.com/">http://www.pointroll.com/</a> ]</li>
<li>EyeBlaster [ <a href="http://www.eyeblaster.com/">http://www.eyeblaster.com/</a> ]</li>
</ul>
<p><strong>Mobile</strong></p>
<ul>
<li>Android [ <a href="http://www.android.com/">http://www.android.com/</a> ]</li>
<li>iPhone [ <a href="http://developer.apple.com/iphone/index.action">http://developer.apple.com/iphone/index.action</a> ]</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.exploitedweb.com/web-development/web-technology-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Code Search</title>
		<link>http://blog.exploitedweb.com/web-development/google-code-search/</link>
		<comments>http://blog.exploitedweb.com/web-development/google-code-search/#comments</comments>
		<pubDate>Tue, 10 Apr 2007 20:19:26 +0000</pubDate>
		<dc:creator>Jonathan Discipulo</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://blog.exploitedweb.com/?p=5</guid>
		<description><![CDATA[There are lots of  experiments on-going that you can find in Google Labs. One I find interesting and useful at the same time is the Google Code Search. This Google feature is still in its experimentation stage but is available for public usage. I am very much impressed they have thought of this developer-friendly search. [...]]]></description>
			<content:encoded><![CDATA[<p>There are lots of  experiments on-going that you can find in Google Labs. One I find interesting and useful at the same time is the <a href="http://www.google.com/codesearch">Google Code Search</a>. This Google feature is still in its experimentation stage but is available for public usage. I am very much impressed they have thought of this developer-friendly search.</p>
<p>The feature, unlike the usual web search, returns pages that includes individual files, mostly source codes of different programming languages. This doesn&#8217;t only search for the page that contains codes but  do search the source codes itself. You have to try it to see it for yourself.</p>
<p>By searching again and again, I have observed that Google Code bot is crawling codes available for public viewing, mostly open source programs, zipped applications, compressed libraries of files and public SVN/CVS repositories.</p>
<p>I like this since it will help developers like me to search for specific classes or functions in a particular application. I can even search using the author&#8217;s name or email as the keyword and get the results I wanted. You can also use the version numbers as keywords to filter the versions of the source codes you are searching for.</p>
<p>Here are some screen shots querying Google Code Search for the keyword <em>papervision</em>. Screen 1 is the first page of Google Code Search. Screen 2 is the result page after submission. Screen 3 is the actual source code you did choose from the result page.</p>

<a href='http://blog.exploitedweb.com/web-development/google-code-search/attachment/code1/' title='Screen 1'><img width="150" height="150" src="http://blog.exploitedweb.com/wp-content/uploads/2007/04/code1-150x150.jpg" class="attachment-thumbnail" alt="Screen 1" title="Screen 1" /></a>
<a href='http://blog.exploitedweb.com/web-development/google-code-search/attachment/code2/' title='Screen 2'><img width="150" height="150" src="http://blog.exploitedweb.com/wp-content/uploads/2007/04/code2-150x150.jpg" class="attachment-thumbnail" alt="Screen 2" title="Screen 2" /></a>
<a href='http://blog.exploitedweb.com/web-development/google-code-search/attachment/code3/' title='Screen 3'><img width="150" height="150" src="http://blog.exploitedweb.com/wp-content/uploads/2007/04/code3-150x150.jpg" class="attachment-thumbnail" alt="Screen 3" title="Screen 3" /></a>

<p>If you are a developer or  programmer that constantly checks for open source codes, you will definitely love and find this tool useful.</p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<p><!--Session data--></p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.exploitedweb.com/web-development/google-code-search/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cloaking can be ethical</title>
		<link>http://blog.exploitedweb.com/search-engine-marketing/cloaking-can-be-ethical/</link>
		<comments>http://blog.exploitedweb.com/search-engine-marketing/cloaking-can-be-ethical/#comments</comments>
		<pubDate>Wed, 28 Feb 2007 20:43:27 +0000</pubDate>
		<dc:creator>Jonathan Discipulo</dc:creator>
				<category><![CDATA[Search Engine Marketing]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[cloaking]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[sem]]></category>
		<category><![CDATA[seo]]></category>

		<guid isPermaLink="false">http://blog.exploitedweb.com/?p=15</guid>
		<description><![CDATA[Another term other than cloaking should be made in reference to this kind of SEO practice; maybe alternate content or backup content perhaps.  Showing content with different presentation or in different format is not a bad SEO habit. This is just to optimize your content for whatever device that reads your content. Examples of readers [...]]]></description>
			<content:encoded><![CDATA[<p>Another term other than <em>cloaking</em> should be made in reference to this kind of SEO practice; maybe <em>alternate content</em> or <em>backup content</em> perhaps.  Showing content with different presentation or in different format is not a bad SEO habit. This is just to optimize your content for whatever device that reads your content. Examples  of readers are standard web browsers, text browsers, SmartPhone/WAP browsers, hand-held devices with built-in browsers, screen readers and search engine bots.</p>
<p>Cloaking is practically a black hat SEO method that presents a totally different content rather than the  content it should present. So how can cloaking be an ethical SEO method?</p>
<p>Consider a full Flash site with all the content embedded on it. How can search engines crawl the content on your Flash-based site? The solution is simple&#8211;cloaking. By utilizing the CSS method of making a block invisible, you can display your Flash site as well as the content you intended to get indexed on search engines.</p>
<p>Consider this Flash site with cloaked content: <a href="http://www.wideout.com/">Wideout Technology Services, Inc.</a></p>
<p>The content you see is embedded on Flash itself but I did include the same original text within the HTML and did use CSS to hide the text to the actual audience. Now, try viewing the source code <em>(View then Page Source or CTRL+U on Firefox)</em>. You will notice the original content on the HTML itself and if you look more closely, you will see the context enclosed in this block:</p>
<pre id="line31">&lt;<span>div</span><span> class</span>=<span>"noflash"</span>&gt;
 &lt;<span>h1</span>&gt;A True Global Workplace&lt;/<span>h1</span>&gt;
 &lt;<span>p</span>&gt;We believe that a business should not submit to geography.
  ...
&lt;/div&gt;</pre>
<p>And in my style sheet goes the trick to hide the text content to browsers but not to search engines and text/screen readers:</p>
<pre id="line1">.noflash {
	display: none !important;
}</pre>
<p>For the conclusion, you can ethically use cloaking to your site&#8217;s pages provided you are still showing the same original content to both search engines and your actual viewers/users.</p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.exploitedweb.com/search-engine-marketing/cloaking-can-be-ethical/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comply often with web standards</title>
		<link>http://blog.exploitedweb.com/search-engine-marketing/comply-often-with-web-standards/</link>
		<comments>http://blog.exploitedweb.com/search-engine-marketing/comply-often-with-web-standards/#comments</comments>
		<pubDate>Wed, 28 Feb 2007 20:22:58 +0000</pubDate>
		<dc:creator>Jonathan Discipulo</dc:creator>
				<category><![CDATA[Search Engine Marketing]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[sem]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://blog.exploitedweb.com/?p=9</guid>
		<description><![CDATA[Why often? Sometimes you should break a rule and surpass the standards if you want your web pages to be effective. These standards are set of rules recommended and sometimes enforced when developing websites. Examples of these standards are: HTML compliance &#8211; Make every page comply with the HTML version you are using with consistency. [...]]]></description>
			<content:encoded><![CDATA[<p>Why often? Sometimes you should break a rule and surpass the standards if you want your web pages to be effective. These standards are  set of rules recommended and sometimes enforced when developing websites. Examples of these standards are:</p>
<p><strong>HTML compliance</strong> &#8211; Make every page  comply with the HTML version you are using with consistency. We currently have HTML 4.01 and XHTML 1.1. You must understand that both versions are different and should not be used together&#8211;just choose one. After making your page with proper HTML syntax, you may use this link to verify that your HTML is properly coded:</p>
<pre>http://validator.w3.org/check/referer</pre>
<p><strong>Meta Tag compliance</strong> &#8211; Most search engines, crawlers and spiders ignore meta tags that aren&#8217;t written correctly. This can make your site out of their indexes. There are search engines today that don&#8217;t rely on and totally ignore meta tags; But still, it is a good practice to include those in every page of your site.</p>
<p><strong>Image Optimization</strong> &#8211; Images should be optimized accordingly to make it load faster even in browsers running with slow internet connections. This includes dial-up and wireless connections. Also, including correct dimensions in &lt;img&gt; tags, stuffing title and alt properties will make search engines crawl your site seamless and faster.</p>
<p><strong>CSS compliance</strong> &#8211; If you are using cascading style sheets, you should validate every line and comply with the CSS rules. This link will verify that your CSS is properly constructed:</p>
<pre>http://jigsaw.w3.org/css-validator/check/referer</pre>
<p>There are lots of standards to follow like banner sizes, ways on displaying links, hierarchy of categories/sections, content management, etc. After you have complied with all those in mind, you can be confident not only of your site&#8217;s visibility in search engines but also about your site being developed in a professional way. You can even tell your clients about those standards you did apply on their sites. This will make them trust your web professionalism and spread the word about your business.</p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.exploitedweb.com/search-engine-marketing/comply-often-with-web-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
