Archive for October, 2006

We have destroyed evolution

This is all the evidence I need that the human race has destroyed evolution. [googlevideo]-143292750174818734[/googlevideo]

Biff Tannen Sings!

Tom Wilson - aka "Biff" from the Back To The Future - sings a song about the questions he constantly gets asked by fans, as part of his standup act. I think if I met him I WOULD ask him to call my friend a butthead on his answering machine... [youtube]0MNHBON01Uk[/youtube]

Heroes is(are?) Cool!

In case you've been living under a rock or are one of those annoying people who say they don't watch TV because its a waste of time (by the way pop culture just called and said fuck you), you've heard about the new TV show on NBC Heroes. So far it is only 3 episodes into its season and already it is the highest rated new show on network TV. This goes to show that interesting shows with creative plots and characters can be successful in today mass media society wheren people are constantly bombarded by different types of entertainment. This also goes to show that NBC's new policy to only have reality shows and game shows in the 8 pm time slot is stupid. True Heroes is in the 9pm time slot but will people really be tuning in earlier to watch some shitty game show where people pick yes or no. Maybe NBC should focus on making for good TV shows then putting out cheap crap to get people to watch their network. Unless the game show is a real life Running Man, I don't think that the world needs another game show brought over from Europe. So be sure and watch Heroes, unless your one of those lame people who would rather do something outside in which case go fuck a tree.

RICO Is Not So Suave

While researching the RICO statutes, I was astonished to find two disturbing applications of these laws. First, when RICO intersects with mail and wire fraud statutes, it allows the federal government to turn underlying offenses outside the scope of RICO into actual RICO offenses. Second, the federal government can prosecute an offender both under RICO and on the underlying crimes that constitute a RICO violation, creating a scenario equivalent to double jeopardy. After the cut, I will explain what the RICO statute is, how these two applications work, and why this is injust.

RICO stands for the Racketeer Influenced and Corrupt Organizations Act codified in 18 U.S.C. 1961-68. RICO was created to deal with organized crime but Congress judiciously wrote it broadly enough to deal with a range of criminal and civil cases, enabling federal prosecutors to utilize RICO to go after everything from accounting firms to abortion clinic protestors to Don King. In the simplest terms, a RICO violation consists of two elements: (1) a person commits repeated "predicate acts" constituting a "pattern of racketeering activity" and (2) those acts involve an entity known as a RICO "enterprise" used in a manner specified by the statute. There are all sorts of rococo curlicues when it comes to the specific language and Supreme Court cases have delved into ornate statutory construction to determine what exactly "enterprise" or "pattern" means when dealing with edge cases, but good common sense is all that is needed to envision the normal application of RICO.

But common sense flies out the window when you combine RICO with federal wire and mail fraud statutes. The requisite violative acts of the enterprise consist of a slew of federal crimes and also a good number of state crimes that are substantive, if not literal, analogues of the laundry list of offenses listed in the statute. Although this greatly expands the scope of federal control over the traditional domain of the State police power by federalizing any state crimes that meet the RICO standard, this clearly stemmed from Congressional intent. While I lament the continued federalization of all crime, it is fully within the Constitution for Congress to enact such a statute. What I find particularly egregious is the use of mail and wire fraud statutes to expand the scope of RICO beyond its already extremely broad ambit.

Mail and wire fraud is easy to prove. It is the interstate use of the mail or wires to engage in a scheme to defraud. Almost every fraudulent activity can be shown to have an interstate mail component. If your credit card statement that records a fraud is sent from Visa's headquarters to your state, the interstate element is met. If you mail a fraudulent document to a government authority which in turn mails it somewhere else, the interstate element is met. The trouble arises when mail fraud is used as the criminal underpinning of a RICO prosecution. It doesn't matter whether the underlying fraud or crime is within the jurisdiction of RICO because mail and wire fraud explicitly is. For example, if repeated perjury resulted from fraudulent depositions mailed to a court from another state, then not only is there perjury, there is also mail fraud. Further, if this mail fraud activity meets the requirements for RICO, then in effect a RICO prosecution can be brought for the underlying crime of perjury cloaked in the guise of mail fraud. This happened in United States v. Eisen, 974 F.2d 246 (2d Cir. 1992). Tax fraud is another substantive area that can be abused in the same way. Tax fraud is not a predicate crime for RICO but it involves mail fraud in almost every case since the fraudulent tax return has to be sent to the IRS. Again, this is not a theoretical example and was the theory under which United States v. Regan, 937 F.2d 823 (2d Cir. 1991) was brought.

This is a concern for two reasons. First, it gives the government more latitude than it should have under the RICO statute. It is always a concern when the federal government's power is not expressly constrained in a criminal statute because it gives prosecutors the ability to over-apply a law. In this case, they have been able to get away with it because there has been no direct challenge of RICO under the void for vagueness doctrine. It is not fair to expect people to understand that RICO will be applied far beyond its expressly stated limitations. Consequently, it is not fair to punish people for committing "crimes" that only become crimes after judicial acrobatics. Second, this broad application of RICO raises federalism issues already alluded to above. The RICO statutes are so far-reaching that ordinary state criminal and civil cases get federalized for no good reason. From the inception of the Constitution, the police power has always been within the realm of the State. There were only three federal crimes in 1800. Now there is a veritable thicket of federal crimes, often needlessly duplicating state statutes or, as in this case, asserting power over the States for no discernable reason.

The second issue I have with RICO is quite simple: it enables prosecutors to violate the spirit of the double jeopardy rule. The Fifth Amendment states that no person "shall [be] subject for the same offense to be twice put into jeopardy of life and limb." In layman's terms, this says that you cannot be tried for the same crime twice. This is a cornerstone of the American criminal justice system and its jurisprudence. Yet, in the case of RICO, its animating spirit can be circumvented through an overweening technical reading. The government may prosecute a defendant under RICO based on the specified predicate acts necessary for a RICO conviction, such as arson or kidnapping, AND the government can later prosecute the same defendant for the predicate criminal act itself. The Supreme Court itself has upheld this interpretation in the depressing case of Garrett v. United States. To be fair, the Court in that case made certain to indicate that this was possible under the specific facts of this case, but while this leaves wriggle room for future cases, it still functions as persuasive precedent beyond obiter dicta. It is dishonest for the government to create a crime and then create a new crime based on the repetition of that crime in certain situations and then be able to prosecute an individual for both. While I appreciate the Kafkaesque/Borgesian quality to such an interpretation, I prefer my fabulist literature to stay fabulist and not creep into dreary social realism.

RICO is mostly a good and worthwhile statute, as it makes it easier to prosecute criminal organizations which do substantial economic and moral harm to the country. But the application of RICO needs to be constrained in a few very specific circumstances to ensure that it is used primarily to positive and fair ends and is not abused in ways that constrain or injure our liberty.

EDIT: I struck out the last paragraph because RICO is much worse than I thought. A former federal prosecutor mentioned that he didn't like the statute because it was so easily abused. I neglected to mention that RICO is used often in the civil context where treble damages and attorneys' fees are awards if a claim is successful. This gives impetus to plaintiff firms to try to turn every run of the mill state fraud case into a RICO charge, glutting our courts with vexatious litigation. RICO is poorly written, overapplied, and frequently misused: a complete legislative failure.

WordPress Tutorial: Using WP-Cache on Windows / IIS

Is your blog starting to bog down? Getting nasty emails from your ISP about overloading the database server? Since most blogs are read far more often than they are updated, caching your pages can result in a real performance improvement.

Wordpress has some very basic object caching, but you really need to be able to cache whole pages to see a big benefit. Luckily there is a very good page-caching plugin, WP-Cache.

If you are on a Linux or Unix host, installation is pretty straightforward.

Now, what if you are on a Windows/ IIS host and using 'date and name based', almost-pretty permalinks? No sweat. Okay, a little bit of sweat.

The code for WP-Cache makes a few assumptions about the environment it's running in which don't work out so well in Windows. My first major step in getting it to work was a great blog post on CPUIdle. Since that blog seems to be down, I'll quote their steps here:

"1. Download WP-Cache zip file (current version as of writing is 2.0.17) and unzip into wp-content/plugins folder.

2. Copy wp-content/plugins/wp-cache/wp-cache-phase1.php to wp-content/advanced-cache.php (not really sure why this isn’t simplified by the author).

3. Open the standard wp-config.php file and add define('WP_CACHE', true);

4. Now comes the tricky part:

open wp-content/plugins/wp-cache/wp-cache.php in your favourite text editor. Search for the wp_cache_add_pages function and change the function code like this:

add_options_page('WP-Cache Manager', 'WP-Cache', 5, 'wp_cache/wp_cache.php', 'wp_cache_manager');

Reason the original code doesn’ work is that the original __FILE__ resolves to wp_cache\wp_cache.php which some browser eat and convert to wp_cachewp_cache.php- which doesn’t exist.

5. Second problem is that WP-Cache checks for installation step 2) in a windows-incompatible manner. Search for the wp_cache_check_link function. Change the first three lines after the variable declaration in this way:

# if ( basename(@readlink($wp_cache_link)) != basename($wp_cache_file)) {

# @unlink($wp_cache_link);

# if (!@symlink ($wp_cache_file, $wp_cache_link)) {

if (!file_exists($wp_cache_link)) { {

6. Finally, open wp-content/plugins/wp-cache/wp-cache-phase2.php and search for ob_end_clean(); and replace with ob_end_flush();. Without this change the cached page contents are not written back when the page is initially cached. It’s unclear to me if that works under *nix, I assume it couldn’t.

7. That’s it- you’re done. No goto Options/WP-Cache and turn caching on."

Unfortunately, if you are set up like we are, using the “index.php� style permalinks, there's one last step you're going to have to do. In Windows / IIS, $_SERVER['REQUEST_URI'] is blank. You need to use $_SERVER['SCRIPT_NAME'].$_SERVER['PATH_INFO'] instead. If you don't, WP-Cache will happily cache your index.php file, but it will also think your /index.php/category/cheese/ page and your /index.php/2006/01/01/I-am-very-interesting/ page are the same as index.php.

In wp-cache-phase1.php (and also advance-cache.php) look for this line:

$key = md5(preg_replace('/#.*$/', '', $_SERVER['REQUEST_URI']) . wp_cache_get_cookies_values());

and change it to this:

$key = md5(preg_replace('/#.*$/', '', $_SERVER['SCRIPT_NAME'].$_SERVER['PATH_INFO']) . wp_cache_get_cookies_values());

By the way, one nice thing about step 6 above is that it also fixes a blank-page bug that some people have run into.

Finally, what if you want to use both WP-Cache and gzip? Here's how.