<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-253456272243673874</atom:id><lastBuildDate>Wed, 16 May 2012 16:11:53 +0000</lastBuildDate><category>best practices</category><category>site updates</category><category>reviews</category><category>web tools</category><category>test projects</category><category>how-tos</category><category>opinions</category><title>the soopergeek of svidgen</title><description>the official blog of svidgen.com</description><link>http://blog.svidgen.com/</link><managingEditor>noreply@blogger.com (Jon Wire)</managingEditor><generator>Blogger</generator><openSearch:totalResults>30</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6473298124037436827</guid><pubDate>Wed, 16 May 2012 16:10:00 +0000</pubDate><atom:updated>2012-05-16T09:11:53.032-07:00</atom:updated><title>building tables in IE7 with JavaScript</title><atom:summary type='text'>The documentation on this is a little old and hard to find, since IE7 is old and on rapid decline. But, for those still plagued with a significant percentage of IE7 users, please note that building tables in IE7 can require a step not required by other browsers.

We can normally build tables using HTML and omit the tbody tag without issue. Browsers are supposed to assume a single tbody when none </atom:summary><link>http://blog.svidgen.com/2012/05/building-tables-in-ie7-with-javascript.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-3165298203522813613</guid><pubDate>Fri, 16 Mar 2012 15:04:00 +0000</pubDate><atom:updated>2012-03-16T08:16:20.611-07:00</atom:updated><title>javascript namespaces</title><atom:summary type='text'>Well, I lied already: JavaScript doesn't really have namespaces — at least not exactly. But, we can fake it quite easily using objects, which readily serve the same purposes:

var com = {};
com.google = {};
com.google.www = {};
com.google.www.search = function(s) {

  // since we're actually working in the context of an object,
  // we can refer to "this" to set static-ish variables, like a </atom:summary><link>http://blog.svidgen.com/2012/03/javascript-namespaces.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-1854988523175778256</guid><pubDate>Sun, 22 May 2011 02:00:00 +0000</pubDate><atom:updated>2011-05-21T19:00:42.741-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>small updates</title><atom:summary type='text'>We've made a few small changes in the past few days. Some of them are invisible to most users, backend changes. A few of them are stylistic changes that we feel are steps in the transition to a prettier bookmarking tool.

First, we cleaned up our bookmarks lists a little bit:


As you can see, we added some space between bookmarks, floated the info and edit/save links to the right, and replaced </atom:summary><link>http://blog.svidgen.com/2011/05/small-updates.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-r7reL9adeow/TdhpezTac0I/AAAAAAAAALY/KakZmGkjEM4/s72-c/Screen+shot+2011-05-21+at+8.39.21+PM.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-120532588956783488</guid><pubDate>Wed, 15 Dec 2010 17:57:00 +0000</pubDate><atom:updated>2010-12-15T09:57:47.035-08:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>opinions</category><category domain='http://www.blogger.com/atom/ns#'>best practices</category><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>thepointless.com: beginning facebook integration</title><atom:summary type='text'>I've been taking time recently to work on thepointless.com. Frankly, it generates significantly more traffic than Svidgen currently does, and I'd like both reward and harvest those visitors, rather than let the flow of people slowly die off as I have in the past.

On a content level, I've removed a lot of fluff and pushed article-type content out to the angry stickman blog. The site has been </atom:summary><link>http://blog.svidgen.com/2010/12/thepointlesscom-beginning-facebook.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6184523210074110943</guid><pubDate>Mon, 22 Nov 2010 21:28:00 +0000</pubDate><atom:updated>2010-11-22T13:29:06.909-08:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>efficiency concerns</title><atom:summary type='text'>I just wanted to let folks know that I'm aware of some efficiency concerns on Svidgen. Namely, your Heros' Bookmarks list and tag autocompletion for &lt;user x's=""&gt; Bookmarks have the potential to operate very inefficiently. The latter issue deals with the order in which tags are being filtered. And there's actually a two-stage optimization that I'm considering there. I have some ideas for the </atom:summary><link>http://blog.svidgen.com/2010/11/efficiency-concerns.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-4885222649957597322</guid><pubDate>Mon, 11 Oct 2010 20:13:00 +0000</pubDate><atom:updated>2010-10-11T13:18:42.588-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>best practices</category><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>A brief authentication issue has been resolved</title><atom:summary type='text'>An issue with authentication, which was reported this afternoon, was preventing users from signing in. We can see how preventing users from signing in might be bad for business. So, we promptly corrected it.

The issue involved a few misplaced lines of code that break the user out of SSL after successful authentication. The code should have been moved to it's new home with a larger segment of </atom:summary><link>http://blog.svidgen.com/2010/10/brief-authentication-issue-has-been.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-7049568149217620639</guid><pubDate>Fri, 01 Oct 2010 21:45:00 +0000</pubDate><atom:updated>2010-10-06T08:54:29.665-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>New Feature: search tailoring!</title><atom:summary type='text'>Since its inception, Svidgen has provided bookmark-improved search results a Google Custom Search Engine (CSE). Well, we've finally enabled a Search Just These Sites feature. You can now slice and dice the public bookmarks on Svidgen in any way choose and search within just those sites.

I'm talking about some pretty vast flexibility here. You can search across some really particular slices of </atom:summary><link>http://blog.svidgen.com/2010/10/new-feature-search-tailoring.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_33Bk6YuuZ48/THa1Ub_IajI/AAAAAAAAAJc/j8RBNYAxgUY/s72-c/200px-Pizza.png' height='72' width='72'/><thr:total>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-1869471956179352731</guid><pubDate>Fri, 09 Apr 2010 14:10:00 +0000</pubDate><atom:updated>2010-04-09T10:36:25.419-07:00</atom:updated><title>for your PHP library: send_cache_control_headers()</title><atom:summary type='text'>Good caching is a really important part of getting the most out of your server(s) while providing visitors with the best experience. While I am not going to discuss best practices for caching now, I will share a very simple, but helpful PHP function that I use on svidgen.com.

And here it is:

function send_cache_control_headers($t = '+1 year') {
    // set cache-control header
    $cc_header = </atom:summary><link>http://blog.svidgen.com/2010/04/for-your-php-library.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-9073276577211497426</guid><pubDate>Sat, 13 Mar 2010 03:14:00 +0000</pubDate><atom:updated>2010-03-12T19:16:49.349-08:00</atom:updated><title>forcing the www subdomain</title><atom:summary type='text'>I've finally decided to force the www sub-domain on Svidgen. This offers a few advantages:
I can separate cookies from the "root" site and its sub-domains  if the need arises.
Search engines / Crawlers will not see "duplicate" sites.
People are accustomed to seeing the www sub-domain.
In the event that I add additional services using different protocols  to the site, the www sub-domain will serve</atom:summary><link>http://blog.svidgen.com/2010/03/forcing-www-subdomain.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-8576920449551484078</guid><pubDate>Mon, 22 Feb 2010 21:31:00 +0000</pubDate><atom:updated>2010-03-29T12:46:59.451-07:00</atom:updated><title>Eschew Obfuscation</title><atom:summary type='text'>All types programming and software development, including web development and design, have some things in common. A litany of these commonalities is not the scope of this post. However, I would like to stress an oft-forgotten rule, common to nearly every form of development: Eschew Obfuscation!

This rule is something that all Computer Science majors learn in the classroom—or were at least taught</atom:summary><link>http://blog.svidgen.com/2010/02/eschew-obfuscation.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_33Bk6YuuZ48/S4L3bcpiyRI/AAAAAAAAAII/ScoufEgUACc/s72-c/200px-Javascript_icon.svg.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-1432649408610238422</guid><pubDate>Fri, 11 Dec 2009 04:32:00 +0000</pubDate><atom:updated>2010-10-01T14:47:39.470-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>Oops! We had a tiny security issue ...</title><atom:summary type='text'>Alright, it's not like there are enough users or conversations taking place on Svidgen that a little security hole here and there is a big deal--it's in BETA, and I'm pretty sure I know the entire user base on a personal level.  I am still slightly embarrassed to admit, though, that I just noticed a big security issue with internal messaging.  Until a few minutes ago, psuedo-knowledgeable users </atom:summary><link>http://blog.svidgen.com/2009/12/oops-we-had-tiny-security-issue.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_33Bk6YuuZ48/SyHLQgUZmMI/AAAAAAAAAH8/csjOqvpMOow/s72-c/Crystal_Clear_action_lock.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-7679561907847822426</guid><pubDate>Mon, 07 Dec 2009 15:24:00 +0000</pubDate><atom:updated>2010-10-01T14:47:51.341-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>(IE8) Cookies have been reassembled!</title><atom:summary type='text'>Well, I said I would post back when I determined in what way IE8 was breaking my cookies, and I think I have.  The issue seemed to be a combination of a difference in behavior in which IE8 handles session cookies (cookies that are deleted when the browser closes) for linked resources (such as my opensearch xml specification) and an authentication policy I previously had on Svidgen.  That is, </atom:summary><link>http://blog.svidgen.com/2009/12/ie8-cookies-have-been-reassembled.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_33Bk6YuuZ48/Sx0d_N8fQII/AAAAAAAAAH0/Ur8mWoZDg14/s72-c/800px-Choco_chip_cookie.jpg' height='72' width='72'/><thr:total>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-1765945987046593617</guid><pubDate>Wed, 25 Nov 2009 16:30:00 +0000</pubDate><atom:updated>2010-10-01T14:48:05.161-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>Internet Explorer 8 broke my cookies!</title><atom:summary type='text'>Fairly recently, I discovered that svidgen.com does not properly manage sessions with IE8.  Is seems as though the general session cookie (svession) is being set and maintained correctly in all browsers, including IE8.  However, my "subsession" authentication token (atoken) headers are not being respected by IE8 in all cases, causing signin to last for only a single page view.

After spending </atom:summary><link>http://blog.svidgen.com/2009/11/internet-explorer-8-broke-my-cookies.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_33Bk6YuuZ48/Sw1bRwbcnxI/AAAAAAAAAHs/Jriv_97RB94/s72-c/cookies.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-3606931406128873319</guid><pubDate>Thu, 22 Oct 2009 17:07:00 +0000</pubDate><atom:updated>2010-10-01T14:50:02.214-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>opinions</category><title>Search Engine Optimization (SEO) woes</title><atom:summary type='text'>Search Engine Optimization (SEO) is a curious thing.  Search engines are designed and continually optimized to provide better results, based on what searchers want to see.  These engines take advantage of Artificial intelligence (AI) algorithms to index pages in a meaningful way, with respect to quality content.

Why then, should anyone even be seeking SEO services?  Is a page with quality </atom:summary><link>http://blog.svidgen.com/2009/10/search-engine-optimization-seo.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>3</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-2973506898395307878</guid><pubDate>Fri, 09 Oct 2009 21:53:00 +0000</pubDate><atom:updated>2010-10-01T14:50:52.365-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>how-tos</category><title>JavaScript: Script-ably Rewriting a Function</title><atom:summary type='text'>I've seen numerous posts in forums in regards to the ability to access, and sometimes modify, the contents of a JavaScript function dynamically (using JavaScript itself of course).  To respond "globally" to these questions, I've created a quick little demo, hosted on Svidgen: JavaScript: Script-ably Rewriting a Function.

I considered posting the code for a brief moment; but, the demo provides a </atom:summary><link>http://blog.svidgen.com/2009/10/javascript-script-ably-rewriting.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_33Bk6YuuZ48/Ss-1Xq9QvII/AAAAAAAAAHE/GE1-HETxGdY/s72-c/temp.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6311430285159901030</guid><pubDate>Fri, 09 Oct 2009 16:59:00 +0000</pubDate><atom:updated>2010-10-01T14:51:03.202-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>Messaging on Svidgen has arrived!</title><atom:summary type='text'>Hooray!  You can send messages to other users on Svidgen now!

Now all it needs is some users ...</atom:summary><link>http://blog.svidgen.com/2009/10/messaging-on-svidgen-has-arrived.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-2804252967723749045</guid><pubDate>Fri, 25 Sep 2009 15:40:00 +0000</pubDate><atom:updated>2010-10-01T14:51:47.895-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>Adding Messaging to Svidgen</title><atom:summary type='text'>Svidgen development has been delayed for awhile now. However, in the past few days I have gotten a good amount of work done on an upcoming messaging feature. A pretty standard feature on most social sites, it will allow users to send messages amongst themselves.

Svidgen's implementation of messaging will come in the form of conversations—at least initially. Conversation messages never get </atom:summary><link>http://blog.svidgen.com/2009/09/adding-messaging-to-svidgen.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6400777688664496950</guid><pubDate>Thu, 02 Jul 2009 16:17:00 +0000</pubDate><atom:updated>2010-10-01T14:53:25.351-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>site updates</category><title>Added Bookmarklets and the Webmaster's add2svidgen link</title><atom:summary type='text'>
When I started Svidgen, I wanted to make sure to provide some greak bookmarklets--links that do magical things from your browser's bookmarks menu or links bar.  I started with the most essential, the add2svidgen link.  It pops open a little window, prefilled with the URL and Title for the page you wish to bookmark.  Just add tags and a description (both optional) and click Save Bookmark.  Of </atom:summary><link>http://blog.svidgen.com/2009/07/added-bookmarklets-and-webmasters.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_33Bk6YuuZ48/SkzfvFslTbI/AAAAAAAAAGk/_1xYNPI2TUI/s72-c/crystal_potatohead.png' height='72' width='72'/><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-3993031185299753997</guid><pubDate>Sun, 14 Dec 2008 15:51:00 +0000</pubDate><atom:updated>2010-10-01T14:54:25.216-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>opinions</category><category domain='http://www.blogger.com/atom/ns#'>best practices</category><title>to javascript, or not to javascript?</title><atom:summary type='text'>I often read forum posts in response to JavaScript questions that end in things like, "but you really shouldn't use JavaScript, because like a billion percent of users don't have it enabled.  So, just don't use it-mmmmmk???1/1/1?lol!z/."

... Alright, I admit, I put my a bit of a spin on that. But, the message is the same: accessibility nuts want us all to stop using JavaScript to tailor to the 1</atom:summary><link>http://blog.svidgen.com/2008/12/to-javascript-or-not-to-javascript.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6686762598769942899</guid><pubDate>Wed, 17 Sep 2008 06:37:00 +0000</pubDate><atom:updated>2010-10-01T14:54:44.143-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>web tools</category><title>HTML/CSS Rounded Corner Generator</title><atom:summary type='text'>To follow my last post, I've created an HTML/CSS image and code generator.  You can use it to quickly create rounded corners for your pages and see how they look immediately.  The page is located here: http://svidgen.com/rcg.php

Enjoy.</atom:summary><link>http://blog.svidgen.com/2008/09/htmlcss-rounded-corner-generator.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-4529972109529231005</guid><pubDate>Sun, 14 Sep 2008 19:14:00 +0000</pubDate><atom:updated>2010-10-01T14:55:08.495-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>how-tos</category><title>html and css: elegant rounded corners</title><atom:summary type='text'>Creating rounded corners for your DIVs and other HTML block elements isn't too tricky to figure out.  However, some solutions are more elegant than others.  And since I basically stole the following idea from Google, I'm going to claim it is a very elegant solution.

The concept is relatively simple.  Any block element that needs rounded corners needs an image of each corner in each corner.  One </atom:summary><link>http://blog.svidgen.com/2008/09/html-and-css-elegant-rounded-corners.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-2586992074415033737</guid><pubDate>Wed, 10 Sep 2008 14:40:00 +0000</pubDate><atom:updated>2010-10-01T14:59:36.637-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>opinions</category><category domain='http://www.blogger.com/atom/ns#'>reviews</category><title>hulu.com - "IPTV"</title><atom:summary type='text'>If you've been looking for a good source of internet television, you ought to be checking out hulu.com.  Before I continue, let me first announce that I am not getting paid to write this post.  I really think Hulu just rocks.

When it's time to burn some brain cells away by mindlessly zoning out to a good TV show, my usual first source is hulu.com.  I can catch my Monk, Psych, House, Pretender, </atom:summary><link>http://blog.svidgen.com/2008/09/hulucom-iptv.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-6487984983683653923</guid><pubDate>Thu, 28 Aug 2008 15:27:00 +0000</pubDate><atom:updated>2010-10-01T14:57:12.390-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>best practices</category><category domain='http://www.blogger.com/atom/ns#'>how-tos</category><title>effective use of the expires header and client-side caching</title><atom:summary type='text'>There are two problems for web developers when it comes to client-side caching:
The browser aggresively caches everything on your site, so the user doesn't see your new images, scripts, or stylesheets for days or weeks.
The browser carefully checks for new images, scripts, and stylesheets on every page load.

So, there's one group of people who are seeing old content and another group of people </atom:summary><link>http://blog.svidgen.com/2008/08/effective-use-of-expires-header-and.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-7052114367297521187</guid><pubDate>Tue, 11 Dec 2007 04:05:00 +0000</pubDate><atom:updated>2010-10-01T14:58:36.798-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>web tools</category><title>the generic you widget</title><atom:summary type='text'>Just a little harmless self promotion here: The Generic You is now available in "widget" form:



If you are seeing this message, your browser is not running JavaScripts! You may still view this content here.

You like?</atom:summary><link>http://blog.svidgen.com/2007/12/generic-you-widget.html</link><author>noreply@blogger.com (Jon Wire)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-253456272243673874.post-5433976075307119677</guid><pubDate>Thu, 22 Nov 2007 04:54:00 +0000</pubDate><atom:updated>2010-10-01T14:59:04.905-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>best practices</category><title>a unity08.com oops!</title><atom:summary type='text'>At about 10:50pm, central time, I visited unity08.com after its mention on the Colbert Report. The site loaded just fine initially. However, another click brought me to the following page:


Now, it's probably not so bad to know that they're running Drupal. A lot of people proudly run Drupal. However, zooming in, we can see that Drupal was kind enough to reveal the MySQL username and server name </atom:summary><link>http://blog.svidgen.com/2007/11/unity08com-oops.html</link><author>noreply@blogger.com (Jon Wire)</author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_33Bk6YuuZ48/R0UQEoGpAzI/AAAAAAAAADg/05EeVwtGeic/s72-c/unity08.png' height='72' width='72'/><thr:total>3</thr:total></item></channel></rss>
