Skip to main content

Stamping out brush fires, one by one

An update to Joe's update of  todayThe Patch:Problem identified; it was of course a typo; re-release should go outsoon.  Again, what you'll get is exactly what's onbeta.journals.aol.com/(screen name)/(journal name) right now, so thereshould be no more surprises.  Knock on wood.  Character Set: Problem identified (see below) and we think we have a full fix, whichwill need a bit of testing, so that should go out a bit after thepatch.  Archive Counts: Still working on it.  Ad Banners:We're listening to suggestions and doing some brainstorming; note thatwhatever we come up with has to pass muster with executives. I'm  hopeful, though.  Jason Calacanis has a great post about the situation on his blog.  I couldn't agree more, and I know that people at AOL are listening.

OK, so now for the geek update.  The character set encodingissue?  Well, basically, the major technical update  in thisrelease involved moving to a new web server and servlet engine(Tomcat).  Unfortunately, we discovered too late that Tomcat bydefault decides that HTML form data is encoded in ISO-8859-1. Also unfortunately, Journals uses UTF-8 throughout. For most commonEnglish characters, the two encodings give the same bytes; it's whenyou start speaking French (or talking about your re'sume') that you runinto differences.  So the problem here is we didn't test thisenough after the switchover and got caught by surprise.  Thesolution involves setting the encoding to UTF-8, but doing it in theright place is a bit of a problem -- if you set it AFTER the servletengine starts reading stuff, it ignores you.  Personally I thinkit should throw an exception if this happens since encodings are, well,kind of important, as we've demonstrated over the past couple ofweeks.  In any case, the solution we're looking involves a servlet filter similar to this one.More generally, we need to figure out how to add this as a general,automatic test so that it's just not possible to skip it -- and so thatwe'll be alerted within hours if some other configuration change breaksthings, hopefully weeks before we make that change to the liveproduction site.

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

XAuth is a Lot Like Democracy

XAuth is a lot like democracy:  The worst form of user identity prefs, except for all those others that have been tried (apologies to Churchill).  I've just read Eran's rather overblown "XAuth - a Terrible, Horrible, No Good, Very Bad Idea", and I see that the same objections are being tossed around; I'm going to rebut them here to save time in the future.

Let's take this from the top.  XAuth is a proposal to let browsers remember that sites have registered themselves as a user's identity provider and let other sites know if the user has a session at that site.  In other words, it has the same information as proprietary solutions that already exist, except that it works across multiple identity providers.  It means that when you go to a new website, it doesn't have to ask you what your preferred services are, it can just look them up.  Note that this only tells the site that you have an account with Google or Yahoo or Facebook or Twitter, not what the…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.