Release Notes

Release Notes

These describe the changes in each release. They run from newest to oldest. You may also want to look at the list of Known Current Major Bugs.

Release 0.3.2 -- 11/3/08

Fixed bug 232: if you wrote a multi-line post on the website, with no Subject line, you might get an IllegalArgumentException. This was a side-effect of the fact that we weren't trimming the newlines out of the generated Subject line, and Tomcat 6 choked on a cookie we were building. Minor problem, actually, but glaring enough to fix it promptly.

Fixed bug 233: IM notifications about postings to communities now tell you which community the conversation is in.

Story 760: Fixed the most glaring security hole in the system -- the fact that there was no validation of IM addresses, so it was possible to steal peoples' handles and spam them. I just wasn't comfortable releasing publically like that: while the risk was somewhat limited, the potential reputation damage was too great. So now, when you claim an IM handle, you are sent a validation link, and the change doesn't take effect until you click on that.

Release 0.3.1 -- 10/28/08

Another huge release, with lots of bugfixes and many tweaks to the look and feel.

Fixed bug 208: The browser title now includes "CommYou", so it's a little easier to find the right tabs. (Thanks to doubleplus for pointing this out.)

Story 690: The old keyboard shortcuts are now (mostly) working in the new UI. You can type "i" to ignore or unignore a conversation, or "n" to work your way through the new conversation contents. This is still apparently erratic, though, so I'll need to get it more solid.

Story 494: The CommYou logo now links to the website.

Story 698: The new "?!" command provides help for the extended commands.

Story 646: You now watch your own conversations automatically.

Story 652: The new "!threads" command shows you all of the conversation threads that are currently active in IM.

Story 699: First cut of presence sensitivity in CommYou. In this first version, we will only send you messages if you are Available on IM. This should cut down on pointless traffic, and generally be less annoying. When you go Away/Offline/DND, it will simply suppress messages to you; when you come back, it will send you a summary of which conversations have had traffic.

This is just a first step -- there are a lot more enhancements implied by this change. But it should be a major improvement in the long run, I think, allowing us to take your presence into account when deciding what to do. Requests and suggestions for changes and enhancements happily accepted.

IMPORTANT: CommYou will ask you for permission to see you in IM -- you need to grant this in order for IM to work. This lets CommYou see your presence, so it knows whether or not to send you messages.

Story 618: When you get a message in IM, CommYou will now mark it as "read", and won't push it at you when you do "Read New" in the Web UI. However, if there were previous unread messages in the conversation, it is still considered "new". (There is an outstanding story still to make this user-controllable.)

Look and feel polish: Gave the whole thing a touch-up. No one's going to mistake it for the work of a professional designer, but it's now a smidgeon better-looking (IMO) while still Googlishly spare. Also, changed the fonts to make it a bit easier to read.

Story 756: You can now log out of CommYou, via the "Log out" link at the bottom of the page.

Split the Catch Up function out into a new "Other Actions" page, since it really doesn't belong under "Settings".

Bug 225: If you put a link into a post's Subject line, it would crash the Jabber side of the server. (Long story, but suffice it to say it caused malformed XML.) Fixed this for the time being by simply scrubbing links from subject lines -- they were always problematic anyway, since the subject line is used as a link in the Summary View.

Bug 210: If you posted a message containing a link, and that link just happened to be at the point where we trim out over-long messages, it would cause Bad Things to happen.

Story 695: watchAll is now consistently set to "false" for new users. This is a bit of a risk -- it means that people won't get thrown into new conversations as much as they would be if it was true -- but I don't want folks to get overwhelmed, either. If you like a lot of active conversation, I recommend changing this to "true" in the Personal Settings.

Story 757*: when you get notified about a new conversation in Jabber, it includes the subject *and the beginning of the text. This usually gives you a better idea of whether you want to watch or respond to it.

Bug 201: we only boldface the Subject of a conversation in the Jabber notification, not the text.

Bug 164: experimentally, we've turned down the "? for help" IM comments that have been annoying people. Instead, we're just occasionally including that (or one of a couple of other contextually-relevant messages) once in a while. Let's see what we think of that.

Story 759: when you reply to a conversation, you now automatically start watching that conversation. The consensus was, if you join in, you probably want to see what other people are saying.

Bug 231: CommYou log in from LiveJournal stopped working on October 23rd, apparently because LJ changed their OpenID stack. I believe that LJ is slightly broken in what they're now doing, but I hacked the OpenID library to work around it.

Release 0.3.0 -- 9/29/08

There have been massive changes throughout: this is the biggest release since the first, but it all comes down to two principal areas.

First, CommYou has a new UI, made up of plain old web pages instead of the original heavyweight Javascript UI. The new system should work fine on pretty much any Web browser, even with zero Javascript. The general look and feel is similar to the old one, at least for the moment, but making improvements should now be significantly easier, and ordinary web functions like "Back" and "Open in New Tab" should now do what you expect. Note that some of the fancy details of the old UI haven't made it into the new one yet, although most will come with time. The new UI is currently extremely spartan -- a modest spit-and-polish pass will come soon, but I wanted to get functional first.

The new UI is coupled with CommYou now supporting LiveJournal. For the time being, it only supports LJ, although that will gradually change. Facebook users will still get the old UI for the moment, but will be migrated over to a version of the new one sometime in the next month or two, once Facebook Connect is fully deployed and I can merge the two sides.

For the time being, I'd appreciate it if the current CommYou users could play with the new UI, kick the tires a bit, and see that things are still functioning. After I've gussied it up a bit and made a few enhancements and bugfixes, I'll be talking it up more on LJ.

For the moment, to log in using your LJ handle, go to http://app.commyou.com/CommYouFB/login.jsp. If you find bugs (which will not surprise me: there's a vast amount of new and rewritten code), please post them to CommYou Discuss or email them to me. Thanks, and have fun!

Release 0.2.5 -- 8/21/08

• Fixed (finally) bug 173: IM was periodically ceasing to work. This seemed to mostly happen right after I did a release, and has been driving me nuts. The problem turns out to be that XMPP can't cope with poorly-formed HTML, and the wikitext system was generating poor HTML for lists. And of course, the first thing I do after each release is post the release notes -- as a list.
• Story 647: added the !off and !on commands, which allow you to turn IM messages off and on, so you can tell CommYou to shut up while you're at work. See the wiki for details on how to use these commands.
• Fixed bug 194: "m"ore now tells you who said it, not just what they said.
• Fixed bug 196 with a fairly major change: rather than sending arbitrary HTML down through IM, we are now rendering the key bits down into plaintext and scrapping the rest. Users were finding the HTML to be a mixed blessing at best, and the slightest malformation in it was causing the system to choke. Currently we are leaving links live, and generally translating HTML back into wikitext where appropriate, but it's just a first cut.
• Fixed bug 195 by request: more tweaks to "m"ore. If you say "m 3", that now shows you the conversation topic rather than the latest message in the thread -- that is, it behaves the same as "m 3.1". Also, when showing the conversation topic, it also shows you the subject line for the conversation iff that is separate from the body text. Saying simply "m" still shows you the most recent message sent to you, though.
• Fixed bug 197: as suggested by a few folks, simply giving a conversation or message number is now synonymous with the "m" command. So you can either say "m 2.4" or "#2.4" -- they mean the same thing.
• Special note: if your IM client is plaintext-only (such as the GTalk web client), you can get the conversation URL by looking at the root message of the conversation. Saying something like "m 2" or "#2" will give you the URL, as well as the actual conversation text.

Release 0.2.4 -- 8/18/08

• Fixed bug 190: if you hadn't already added CommYou in the old Facebook UI, there was no way to do so in the new one. Adjusted the system to cope with the new way of doing things in Facebook -- you no longer have to "add" the application, you can simply go into it. The first time you do so, it'll ask for permission to access your data; after that, it will just work. The documentation still needs to be updated to match.
• Fixed bug 192: previously, if someone responded to an older conversation, you'd get that in IM -- but when you said "m" for more, it would interpret as being for the most recent conversation to start, which was kind of useless. It now always works for the most recent message to come through.
• Story 651a: when you get a response via IM, it now has a response number as well as the thread number. So response 12 of conversation 4 will be identified as "#4.12".
• Story 651b: rewrote the "m"ore command pretty much completely. You can now specify a message number, and it will give you the full text of that message. If you specify just a conversation number, it will give you the full text of the most recent message in that conversation. If you just say "m", it will give you the full text of the most recent message sent. This should be far more useful, and means that you can dig out messages that came flying past. (Note that this will not work for messages written prior to 0.2.4, which didn't yet have response numbers assigned. I'm not going to the hassle of going back and cleaning up all those old messages.)

Release 0.2.3 -- 8/14/08

• We have an ongoing problem that the IM connections are occasionally getting "wedged": you give commands and nothing happens, and you don't get anything from CommYou. In fact, everything looks fine inside CommYou proper, but the messages aren't going from there to the IM server. While I figure out what's going on, I've added the "!kickJabber" command, which kicks Jabber in the head and hopefully will reboot the connection. This really ought to be just for admins, but for the moment I'll let anyone do it -- it's fairly harmless. So if IM has been working for you, and seems to have mysteriously stopped, feel free to "!kickJabber" and see if that fixes it.
• Fixed "bug" 176: replaced the "i"gnore shortcut command with "!ignore". Since the difference between Ignore and Watch is pretty subtle, and Ignore mostly isn't relevant to IM, I'm focusing on the more-useful "w"atch command inside the IM interface.
• Workaround for bug 189: If your IM client does auto-reply when you are away/idle, it is very easy to get into a scary loop, where something comes from CommYou, your IM client auto-responds, CommYou takes that as a response, you auto-respond again, and so on infinitely. The workaround is that, if you send the exact same response three times in a row, CU decides that this may be an auto-response, and drops your responses until you say something at least slightly different. Crude, but should fix the problem without causing too many headaches. We can gradually make it more sophisticated if we find the need to do so.
• Story 638: The "active conversation" concept has been pretty broken. The theory is that it's trying to reduce cross-talk between conversations when things are flying fast and furious, but in practice it has proven to cause a lot of cross-talk when things are slow. So I've taken most of the teeth out of it: the "active conversation" is only active for two minutes after your last message to it. The theory is that if you're in the middle of an active conversation when new stuff comes in, it doesn't immediately interrupt you, but most of the time you will wind up responding to the most recent message you received. Let's see how that does. (Also, please keep in mind that you can always explicitly say which conversation you want a message to go to -- this is all about trying to DWIM when you don't.)

Release 0.2.2 -- 8/11/08

• Fixed bug 161: by popular demand, conversation numbers on IM now start with 1 (the way normal people count), rather than 0 (the way computer programmers do).
• Fixed bug 166: web-based Google Talk and some other IM clients weren't working. The problem turned out to be that they don't cope with HTML IM messages, and that was all that I was sending. We're now sending plaintext as well. The transform from HTML to plaintext is a little rough around the edges, but it should work fine in most cases. Note that it isn't including the link to the conversation in every message (the way the HTML version does), because that would take up too much screen space, but if you get, eg, the information on conversation 3 by typing "#3", it'll include the link to the conversation's web page.
• Fixed bug 181: Wikitext in responses was producing bogus behaviour in IM. (The response wasn't showing wiki-texted, and "m"ore was somewhat screwed up.)
• Fixed bug 182: Wikitext links were generating excess spaces in the generated page. (Very minor, but it was getting in the way of my automated tests.)

Release 0.2.1 -- 7/28/08

• Fixed (?) bug 167: We seem to have developed crashes at login. Things run okay for a while, then start failing. I'm not sure exactly what's happening, but it seems to be related to nested transactions. So I've made the DB manager smarter, to avoid nesting transactions; hopefully this will make the problem go away.
• Story 624: IM notifications now show the first 300 characters of a message, not just the first 80. This feels more reasonable, but it's an arbitrary number: opinions on this length are welcomed.
• Story 666: By popular demand, you can now name a conversation! If you say "!name n name", it will assign that name to the conversation. The name can be any simple word, made up of letters, numbers and underscore. The name will be displayed on all messages in the conversation, and you can refer to the conversation using that name instead of the number in all commands. For the time being, this name is only seen by you, although it is possible that, down the road, the owner will be able to name it more broadly.
• You can also name the conversation as an optional parameter to the "w"atch command. So if you say "w 4 tuesDinner", it means "watch conversation 4 and name it tuesDinner". I figure that this is often going to be when you want to name it anyway.
• Fixed bug 155: if you say an unknown conversation number via IM, it no longer posts that as a response.

Release 0.2.0.1 -- 7/23/08

• Fixed bug 156: Due to a fairly dumb bug, nearly all IM notifications were going to me personally. They should now be getting routed properly.
• Despite showing all indications of working, the "watchAll" command was broken. Now fixed. This will matter mainly when volume comes up, and you stop wanting to listen to conversations by default.
• CommYou was failing to load in IE. Far as I can tell, this was a subtle bug introduced by the new libraries. Now loading properly, at least in IE7.
• CommYou's icon in Jabber was showing up as my personal one; it got set entirely by accident during early manual setup, and I hadn't noticed. It's now the icon from Facebook -- annoyingly low-res, but at least a recognizable placeholder.

Release 0.2 -- Initial IM functions -- 7/22/08

• Story 149: There is now a very simplistic Settings -> Personal Settings screen. So far, all that you can set here is your Jabber IM handle, but I expect this to expand fairly rapidly. If there is anything about the system behaviour that you really want to be able to do some other way, please request it and I'll put it onto the story list.
• Story 598: You can now enter your Jabber handle in the Personal Settings screen. Note that we are not doing any validation of this yet, so Alex should not feel the need to push at the many edge cases here. (Story 599 is validating the handle, but first I want to get the basic concepts working.)
• Lots of little tweaks to the look and feel, especially of the Summary View. Changed a bunch of labels that have been confusing people; we'll see if the new choices are any better. I still consider this all in flux.
• Fixed bug 138: When you start a new conversation, it doesn't appear on older pages of the Summary View.
• Story 429: The big one. Jabber integration is now live. Set your Jabber handle as described above, and see what you think of it. Play with it, and tell me what you find. There are a lot of open issues here, since we're wrestling with a lot of hard problems, squishing a bunch of conversations into a simple IM stream. More sophisticated threaded Jabber support may well come in a bit, but I want to see if we can get the lowest common denominator working adequately first.
• CommYou now has a bit of command-line functionality. This is mainly intended for power users and testing, but if you are interested in more details, see the Command Line help page .
• Fixed bug 144: when you Ignored a conversation, the Details View for that conversation would come up blank until you reloaded CommYou.
• Fixed bug 145: when you respond to a conversation, it now clears the text box after it is successfully posted. (The send buttons also now provide a little feedback that it's sending.)
• Fixed bug 139: since the new MooTools libraries came in, when you "n"ext from a long conversation (that was scrolled), the new conversation comes in with weird whitespace on top. I suspect it's a bug in the new libraries; worked around it by scrolling up before we begin the slide-in. We'll see whether that's acceptable.
• Fixed bug 142: after you responded to a conversation, the OverText message that should appear to be in the reply box was winding up in the wrong place, often obscuring some of the text of the conversation. This turned out to be a bug in the Clientside library I'm using; updating to a newer version fixed it.
• Fixed bug 146: when you respond to a conversation, that normally shouldn't mark the conversation as having new content. (That is, it shouldn't be pushing your own messages back at you.) If you want it to do that, you can do so with the new "leaveOwnDirty" flag, available from the command line.

Release 0.1.8.2 -- IE7 patch -- 6/24/08

• Previous release seems to have killed IE7. I'm not exactly sure why these changes caused it to go non-functional, but it should now be working again. IE6 is still questionable at best, but I'd like to keep IE7 working decently. Please tell me if you see major functional problems. (I'm aware that the details of the styling are still a bit off, but it should work right.)

Release 0.1.8 -- CatchUp -- 6/23/08

• Upgraded to the released version of MooTools and release candidate of Clientside (the client AJAX packages). This should be good in the long run, but for now has introduced many bugs. Tooltips are disabled for the moment (because they were too broken to fix right now); please tell me if you see other visual bugs. The changes are all at the visual layer, where automated test coverage is weakest, so it wouldn't surprise me if there are bugs I've missed.
• Story 586: when you sign up, you no longer get *everything added to your "to be read" pile.* It now only adds conversations that have been active in the past five days.
  This currently has a slightly unfortunate side-effect -- older conversations don't show up in your Summary View. This does make sense when you understand that the Summary is not a "friends list" as on LJ: instead, it's conversations that you have a relationship with. I believe this side-effect will cease to be a real issue once we get proper views of specific friends and communities, which should allow you to go arbitrarily far back for them.
  If there proves to be demand, we can add a feature that lets you fetch older conversations into your Summary View. But it's expensive enough that I don't want to do it automatically for every conversation that ever happened.
• Story 574: there is a new "Catch Up" feature available off the View menu. This allows you to mark all conversations older than a given time as "caught up", so they don't show up in your new-reading list. This should be helpful to people who only check in occasionally, or who come back from vacation.
• Hacked the way static files are fetched, which will hopefully work around any style/script discrepancies folks may have seen between versions in the past.
• Fixed bug 128: Extra newlines around quotes now get sensibly compressed away. (Minor, but it was annoying me.)

Release 0.1.7 -- "the textual self-expression release" -- 6/12/08

• Story 116: a bunch of HTML tags are now allowed in messages. By and large, the list is most of the simpler ones allowed in LiveJournal, but not yet div and span (since I'm not allowing attributes yet, and they're kind of useless without them), nor forms (because I haven't thought through how they should work yet). And the syntax of <a> and <img> is pretty strict at the moment, due to limitations in the regular expressions I'm using -- most attributes aren't allowed. This will need lots of enhancement yet, but that'll need much more work on the HTML sanitizer. For now, it should suffice for many simpler cases.
  

Only a few basic tags are legal in subject lines -- any other legal tags simply gets dropped silently.
Please fiddle around with this code, and tell me anything you find -- there are undoubtedly bugs. In particular, if you manage to figure out any Javascript injection attacks, please bring them to my attention immediately! Feel free to request enhancements to permit HTML syntax that isn't there yet, but keep in mind that it may take a while to get things really robust.
For the full list of supported tags, see the CommYou Legal HTML page.

• Story 517: you can now use some simple WikiText in messages. The syntax is adapted from several sources, but it's intended to be as intuitive as possible. There are only a few tags at this point, and we might stick with that. Since you can give raw HTML for the fancy stuff, I don't see the need to provide wikitext for everything. Instead, this is intended as a simple DWIM mechanism to make some of the most common idioms easier to express. So there are easy ways to do things like bold, underline, quotes, links and lists, but I'm not worrying about less-used features like tables.
  

The old feature that automatically turned URLs into links has been removed: it had too many ambiguous edge cases causing problems. Please instead use the wikitext version ([http://www.thing.com/path Link Text]), which is both more powerful and safer, while still being pretty simple.
For a full description of the current markup, see the Comm You Wikitext page.

Release 0.1.6 (pre-alpha) -- 6/3/08

NOTE: Again, clearing your cache and reloading may help pick up some style tweaks.

• Story 153: The Summary View is (finally) paged, so you can step backwards and forwards through it, and can get to older conversations. The pages are arranged by creation date. The Older and Newer buttons do pretty much what you expect them to, I think. The page size is currently hard-coded to five days; that will eventually be under user control.
• The Refresh function from the Summary View is now even more insanely efficient. This will eventually allow us to have auto-refresh on a regular basis.
• Fixed Bug 56: The Detail View's "Refresh" button now shows when you are refreshing, the same way the Summary View's button does. You'll notice that there are actually a lot of little refreshes going on -- those reflect the times we go to the server and ask for the current full details of this conversation.
• Fixed Bug 112: The Detail View's "Refresh" button was just plain broken.
• Progress on Bug 78: The CSS layout is gradually improving. Still decidedly imperfect, but we're gradually ironing out the kinks.

Release 0.1.5 (pre-alpha) -- 5/22/08

GENERAL NOTE: If the layout looks weird (in particular, if the button bar shows up at the very top), clear your browser cache and reload. Firefox doesn't seem to be picking up the CSS changes properly -- not quite sure why yet. (Likely an Apache/Tomcat configuration issue.)

• Story 108: If you include a valid URL in a conversation topic or response, it will be turned into a live link. There are probably edge cases that fail here -- some legal URLs that don't turn into links, and some illegal ones that do. If you catch any cases that seem to be significant, please bring them to my attention.
• Story 485: The button bar is now fixed-position. This means that, at least in well-behaved modern browsers, the Next and Ignore buttons shouldn't scroll away when you scroll the Conversation Details View.
• General refactor of the button bar and keyboard handlers. In and of itself, this shouldn't change anything user-visible, but makes things more consistent.
• Story 492: There is now a "Read New" button at the top of the Summary View, which does the same thing as View > Read All New. More importantly, it is sensitive to the "n" and right-arrow keys, so you can navigate entirely through your conversations using those. (I kept wanting to press "n" to start reading, and got at least one other report of the same, so I figured I might as well make that work.)
• Story 484: The "buttons" (such as Ignore and Next) now use underlining to hint at their keyboard shortcuts.
• Fixed Bug 105: Shift-right-arrow was going to next conversation, which got in the way of browser functionality. Changed things so that the keyboard controls don't do anything if shift is held down. (This was already true of the other control keys.)
• Fixed Bug 95: The section headers in the Conversation Summary View were tooltip-sensitive all the way to the right-hand border, which was causing confusion about why the tooltips were appearing. The tooltip-sensitive area is now just the text itself.
• Fixed Bug 107: The popup message you got if you weren't logged in to Facebook and went directly to CommYou was misleading. It now tells you to log in.

Release 0.1.4 (pre-alpha) -- 5/14/08

NOTE: All conversations are currently public. That's intentional: we haven't gotten to friend-locking and community-locking yet. They'll be coming in a while. For the time being, though, the public-ness affects several of the items below.

• Story 102: You can now go directly to a specific conversation in CommYou, with a simple RESTful URL. (Comm You base?/conversation/conv Id?) This isn't so directly useful on its own, but is the base of many future stories to allow you to link to particular conversations. The loading in this case is optimized to show you the conversation as quickly as possible, preloading the rest of CommYou in the background while you read. I think you should be okay switching to the other views while it's finishing preload, but tell me if you manage to find problems in this: I could easily believe I've missed things.
• Story 320: If you haven't installed CommYou, you can still read publicly visible conversations (that you find from, eg, your News Feed). You still can't respond, I'm afraid -- for the moment, we're not allowing anonymous responses (due to spam/abuse concerns), and Facebook won't tell us your identity until you've installed the app.
• Fixed Bug 100: When you can't log in for some reason (for instance, if you haven't added the application), you now get helpful and decently clear error messages, instead of cryptic Java stack tracebacks.
• Story 152: When you post new conversations, they will now show up in your Facebook Mini-Feed. (And potentially in your friends' News Feeds, if the gods of Facebook smile upon us.) This should start making the system more practical and easy to use. You can click directly from these feed stories to the conversation. At least for the moment, this also includes conversations started in communities; that may become optional down the line, if people want.
• Tweaked the tooltips a bit. They now fade in and out, and don't appear quite so fast. Tell me what you think of them!
• Story 268: There is now an explicit limit on the length of a post or response (currently 32k). If you go over this limit, you now get a friendly error message, instead of a horrible stack traceback. Hopefully this is the end of the Hamlet saga.
• Fixed Bug 97: OverText no longer implies that there is no limit to the length of a post.
• The internal tables are now running on InnoDB instead of MyISAM. This mostly means that the system is more stable.

Release 0.1.3 (pre-alpha) -- 5/7/08

• Fixed Bug 89: If someone managed to create a Conversation with no content, it caused things to choke at load time. It now tolerates the bad data, although shows it up in a Big Ugly Way so that we remember to prevent this situation from arising in the first place.
• Fixed Bug 70: The menus were sensitive to both mouseover and click, and that was producing weird and confusing interactions. Removed the mouseover bit, so menus just click in and out, pretty much as you usually expect. Note that you may need to clear your browser cache to pick this up: it's in a subscript, and Firefox is sometimes bad about detecting changes in those.
• Fixed "Bug" 62: The Summary View now auto-refreshes whenever you switch to it. This is usually what you want, so it picks up anything new as soon as you look there.
• Fixed Bugs 41 and 87: When you either made several responses in a conversation or opened the old compressed responses, the OverText (the grey text over the input area that tells you to type here) was getting misplaced. It now gets repositioned properly in both those cases.
• Fixed Bug 82: ctrl-n was opening a new window and going to Next Conversation. Tweaked so that "n" only goes to Next if alt, meta and control aren't pressed.
• Story 441: Unignore is now properly implemented. If you have ignored a conversation, you can unignore it from either the Summary or Details Views, and it will start to show up when you Read New again.
• Workaround for Bug 77: conversation slide-in looks bad in IE7 -- it causes the scrollbars to go all wonky. So disabled that for now. It might come back after the CSS refit happens.
• Story 487: Added support for Google Analytics. This shouldn't have any user-visible effect, but please tell me if you see anything weird happening.
• Added the CommYou Discuss community. Everyone has access to this, and it is turned on by default. Whereas CommYou News is intended as a low-volume group for me to publish relevant news, CommYou Discuss is a place for anyone to suggest features, report bugs, and generally talk about the system. If you don't want to follow that, feel free to turn it off from Settings > Who You're Reading.
• Fixed Bug 53: when you hide or show a friend or community via Who You're Reading, the relevant conversations appear and disappear appropriately. (Note that, if you hide something, your reading state for their conversations will be lost. If we decide that this is a serious problem, we can fix that later.)

Release 0.1.2 (pre-alpha) -- 5/1/08

• Fixed (I think) Bug 68: the timeout problems that were causing things to crash in the morning. I found out the hard way that MySQL times out inactive connections after 8 hours, and with just a few people here we do go inactive overnight. After that happens, it became basically impossible to log in until Tomcat got kicked. So I've put in a short-term hack (strobing the DB every 10 minutes) for the time being, and we'll fix it more properly soon.
• Fixed Bug 64: When you create a conversation, it no longer immediately shows up as "new" for you.
• Fixed Bug 42: The old Responses no longer re-compress when you Refresh or respond to a thread.
• Fixed Bugs 45 and 57: some inconsistencies in the number of new Responses showing up in the Summary View (it hadn't been taking new responses made while you were participating in a specific conversation into account correctly).

Release 0.1.1 (pre-alpha) -- 4/29/08

The initial release! Lots of bugs still known, so we're not going to enumerate them all.