The devs working on Wordpress Multi-User, or MU, have similar thoughts on the no-www domain preference, but do they kindly make their case with suggestions and education? No, they ram the no-www mantra down your throat, hardcoding multiple and irreversible blocks of code in the setup and load scripts that expressly forbid a user from ever using a www. subdomain! Their reasoning for this seamingly arbitrary dictation? I can’t seem to find one that isn’t based on their own personal preferences.

For the most part, the MU community seems to agree with this decision as a sound one! Wow, does anyone else see a major lapse in judgement here? Here’s an abbreviated forum thread on the subject, names removed to protect the innocent:

Smart Person: Wordpress MU forcess no-www. This is a huge mistake!

Person 1: Set up your server to forward www to non-www, everything will be ok

Smart Person: No, it won’t. Why should I change my entire site structure to accomodate this arbitrary decision?

Person: Do redirects and xml sitemaps so that google re-indexes your site with no www.

Smart Person: You’re missing the point! I want a subdomain!

Person: So install MU on a subdomain like ‘blogs.example.com’

Smart Person: *sigh* ok, how about this subdomain - ‘www.example.com’!?

It just seems so silly to me that they have an unfounded, non-technical bias against ‘www’ as a subdomain. They support any other subdomain except for ‘www’!

A hack to fix this on install

Warning: This is definitely just a ‘hack’ and will most likely break on upgrade! And unfortunately, I was unable to revers the no-www effects after a complete installation, this has to be done before a fresh install.

This is for version 2.6.

In index-install.php make the following changes:

In wpmu-settings.php make the following changes:

So how do I attack my feeds? Well, I’ve set google reader to default to the ‘All Feeds’ page, so I open up the reader and just start ‘hitting the j’ (’j’ is the hotkey for next item) - get it, eh? I barely get done reading the headline of the feed before I hit ‘j’ again keeping a rapid clip through usually 500-800 articles in the morning.  Then I’ll attack it again a few times throughout the day.

I only stop and read if the title pops out at me - or, and I can’t help it, but it’s true - I see a picture that pops out. I wasn’t one of those kids that just skimmed through books only looking at the pictures, but hey I guess that’s a lesson if you want people to read your feed.  Either come up with a damn good title or include an eye catching picture of some sort.

So who’s with me waking and baking with google reader in the morning?

The delay is most likely caused by the host trying to reverse DNS the client’s ip address.  You can make sure this is the reason by connecting to the remote host with the -vv parameter (this is all assuming debian/ubuntu type distros):

ssh -vv user@example.com

If the debug output pauses before a message like:

debug1: Authentications that can continue: publickey,password

Then most likely reverse lookup is the problem. Fortunately, the solution is simple - on your remote host, edit the ssh config file:

sudo nano /etc/ssh/ssh_config

Add the following line if it doesn’t already exist:

UseDNS no

Then restart ssh:

sudo /etc/init.d/ssh restart

Voila! You should not experience a delay anymore when connecting via SSH or SFTP, etc.

Turns out, there’s a simple solution - run an SSH tunnel to the ec2 server:

When you access your local port 5984, i.e. http://localhost:5984/_utils, you’re actually tunneling to your EC2 instance. Now, you can run the couchdb server safely and still enjoy the Futon admin!

Many of you have asked us to let you know ahead of time about features and services that are currently under development so that you can better plan for how that functionality might integrate with your applications. To that end, we are excited to share some early details with you about a new offering we have under development here at AWS — a content delivery service.

This new service will provide you a high performance method of distributing content to end users, giving your customers low latency and high data transfer rates when they access your objects. The initial release will help developers and businesses who need to deliver popular, publicly readable content over HTTP connections. Our goal is to create a content delivery service that:

 

• Lets developers and businesses get started easily - there are no minimum fees and no commitments. You will only pay for what you actually use.
• Is simple and easy to use - a single, simple API call is all that is needed to get started delivering your content.
• Works seamlessly with Amazon S3 - this gives you durable storage for the original, definitive versions of your files while making the content delivery service easier to use.
• Has a global presence - we use a global network of edge locations on three continents to deliver your content from the most appropriate location.

 

You’ll start by storing the original version of your objects in Amazon S3, making sure they are publicly readable. Then, you’ll make a simple API call to register your bucket with the new content delivery service. This API call will return a new domain name for you to include in your web pages or application. When clients request an object using this domain name, they will be automatically routed to the nearest edge location for high performance delivery of your content. It’s that simple.

We’re currently working with a small group of private beta customers, and expect to have this service widely available before the end of the year. If you’d like to be notified when we launch, please let us know by clicking here.

Sincerely,

The Amazon Web Services Team

Here’s how it works according to the representative:  You have about 1 million free pageviews per month, but it’s not a simple you-have-exceeded-your-monthly-limit quota.  The app engine team has developed a way to evenly spread out your quota over the full month, so it is possible that you receive a generic “this account has exceeded its limit” page at the beginning middle or end of the cycle.  See anything wrong with that?

From what I’ve seen, most of the web properties that are looking for traffic do it in a very specific pattern that invovles two phases iterated many times.

Phase 1 - get a huge spike in traffic somehow.  Get on Digg’s homepage,  get a mention on Techcrunch, etc etc. You now have an unusually large number of visitors over a short period of time.

Phase 2 - a small percentage of those visitors will stick around and become loyal or engaged visitors.  This is the traffic you care about!

Here’s a snapshot of this site’s traffic after getting linked to by a popular internet pundit last month.  You can see the two phases very clearly.

One of the primary benefits of hosting in the cloud is that they are built to handle this type traffic profile - large random spikes!  Google’s App Engine is so promising as a platform because you can leverage their infrastructure to handle a lot of traffic.   But, very few sites have high, steady traffic - it’s mostly spikes like this.

But, with google’s “smart” quota - you have all the limitations of a single physical server!  When their quota system detects you’ve gone over your micro quota for the day, or the hour, or however they track it, then your site is officially taken down and a generic quota screen is shown.  Ouch!  Now that bump in steady traffic doesn’t quite stay as high as you’d like because many of those visitors that would stick around never get to see your content.

This very well may change when Google announces it’s pricing and other features, but for now this is a non-starter for sites that are looking to take advantage of google’s infrastructure to handle a lot of traffic.

There is a lesson here for all media companies. Whether they are producing videogames, movies, or music, adding DRM won’t stop piracy. The best way to stop piracy is to hobble the pirated version, not the official one.

Easier said than done, right?  No, not really - this concept was pioneered and perfected over a decade ago by none other than Blizzard Entertainment with the release of Diablo 1 and battle.net (bnet).  If you’re not familiar with bnet, it was a network integrated into Diablo that managed all of it’s multiplayer interactions (minus LAN).  It opened up a whole new, exponentially more valuable gaming experience because it was the first mainstream game that made the social interactions that we all take for granted in gaming today easily accessible!  The game was ‘complete’ without battle net, but the entire experience wasn’t.

How did they combat piracy?  A valid CD key was required to get on - that’s it - no crazy DRM scheme, no limiting installs, none of the stuff Spore is getting a lot of flak for.  And people bought the game like crazy because no self-respecting gamer played Diablo alone!  (I mean alone in the macro sense, i.e. in the context of bnet).

So, am I saying that every game developed today should have a valuable online component?  That solo gaming is a thing of the past and developers should be expected to provide multiplayer experiences with everything they develop?  Yes!  If the game industry wants to prevent piracy, then yes, the internet is the answer.  Ironically, the internet is also the reason piracy has become so prominent.

This is a pretty specific setup, but works really well for playing around:

• Running Ubuntu Hardy 8.04 on EC2 (alestic makes the defacto instance - ami-c0fa1ea9)
• The latest and greatest Jaxer release candidate (http://aptana.com/jaxer/download)
• Using the built-in apache in jaxer
• port 80, publicly accessible

Step 1 - get your instance up and running.  I recommend ElasticFox.  Instance ID I use most often is ami-c0fa1ea9.  (As a quick aside - why don’t I just repackage the instance? Because I want to use the latest and greatest Jaxer and it changes fairly frequently. When Jaxer 1.0 comes out, I’ll repackage the instance if Aptana doesn’t do it themselves.)  Instructions on how to get an AMI up and running are a dime a dozen so I won’t go into them here.

Step 2 - grab a few necessary libs that don’t come with the alestic hardy.

Step 3 - grab the latest jaxer zip from http://aptana.com/jaxer/download

Then follow the instructions Aptana provides for making jaxer publicly accessble.  If you want to run apache safely, I recommend creating its own user:

Make sure to set your User and Group to apache in /opt/AptanaJaxer/Apache22/conf/httpd.conf.

Voila! That should do it. Start jaxer with:

Access your site through http://[public DNS instance name]/aptana and run the diagnostics.