Oh boy was I wrong.

At the very core of Wave is the “Wave Federation Protocol”, designed for server to server communication, which is actually very simple: a (lower-case) wave has multiple wavelets which are individual XML documents that are constantly mutated in real time. If somebody adds a character or deletes a line, it does so inside the construct of this XML document. When a mutation happens, such as a simple key press, the server must send a skip command to place the “virtual cursor”, and then the key(s) pressed to modify the document to the receiving server.

(upper-case) Wave is Google’s implementation of the wave protocol for real-time collaborative messages. It creates a new wavelet (XML Document) and apparently controls the mutations over Javascript. My plans for a Wave-like forum experience was crushed by the large complexity of Wave over Javascript.

My gung-ho/cowboy style got me pretty far, check out the video: http://twitvid.io/aba4

It’s possibly a story of bad design decisions, but I decided to use something similar to the server to server protocol. I even wrote an XMPP over BOSH server, which was fairly trivial to do. It was nice and simple until I got to the actual typing part: It’s impossible for a simple “textbox” Wave over Javascript. To get my demo working, I had to manually parse over “onKeyPress” or “onKeyUp” events. In addition, I couldn’t find a way to store the document in a Wave friendly format. The “skip” command is just a letter skip with an XML element counting as one character. Wave supports no DOM searching and I had to just do a depth-first search on the XML DOM to both find and place a cursor based on it’s skip value.

I persevered for two weeks until I finally got to a point where I could test the live stuff by opening up Firefox, which itself had issues with my hacked up Javascript just trying to get it to work in Safari. I could barely get the enter key working. And it’s at this point that I decided to give up. The wave protocol might seem easy and makes sense on the outside, but to get the live collaborative editing on Javascript is a whole other issue. It took me 915 lines of Ruby and 725 lines of Javascript just to get to that video demo.

Google has hinted that they’ll provide libraries for Wave, but I don’t think I will use them. Wave is far too complex for me to spend two weeks, full-time, on a simple private message system. For those that want simple blog comments, the embed API looks nice enough to use. If you want to own your data and drop-in on an existing system, look elsewhere because Wave is far too complex for a one man team.

Anyway, a lot of people have problems with the newlines and how they work. I’ve tried all kinds of things, but none of them work well really. Since I used RedCloth 3, the Ruby parser for Textile, there wasn’t a nice answer. Going without it is impossible, since there’s a legitimate reason to have single breaks. Enabling the official hard breaks on RedCloth 3 caused havoc on quotes and spoiler matocode tags. I eventually settled on an ugly hack.

In comes RedCloth 4. It fixes the line break issue, it’s a C-based extension for extra speed. And it doesn’t have disablers, it’s all or nothing. I have to disable images on the forum because it’s possible to display tasteless images. Not to mention the occasional Goatse hotlink protection. Stuff I really don’t want to be shown on a forum that has members of 12 or less.

However, We offer regular users the ability to post images in certain forums, like the Fan Forum, to show off their artwork. Administrators and moderators like images for various real needs, as well as special permissions allow certain users to post images for various needs. (ie. the runner of the currently running Mafia game.) So the feature disabler had to be easily disabled/enabled.

After a brief email in their mailing list, I manned up and added it myself. Unfortunately, I didn’t know Ragel, or Ruby C Extensions for that matter. It was a long and tough battle, but I defeated the final boss!

RedCloth.new("!image.jpg!",[:disable_inline=>:image]).to_html
#=>"!image.jpg!"

Hopefully — With the feature disabler that I needed — this fixes a lot of problems that have been plaguing the Textile implementation on the forum.

The next step is to port the crappy MatoCode (my implementation of BBCode) to the fancy Ragel system. Things like the [quote] and [spoiler] tags need to have their insides parsed separately from the outside.

• Needed a DVD, so I looked forever to find one.
• Remembered that blank DVDs where in my car, went and got one.
• Burned the iPartition boot DVD.
• It didn’t work.
• Burned it again.
• Didn’t work.
• I realized it might not have drivers for my new iMac, so I tried copying my /System/Library/Extentions over to the DVD, burned another one.
• It didn’t work either.
• I realized I could use my iBook instead while my iMac was in target disc mode.
• Except my iBook would let me put in the DVD I burned. There appeared to be something jamming it. (WTF?)
• So I tried a credit card to unblock it, no dice.
• I had to open up my iBook, but I needed a smallish Allen wrench to open it. I looked everywhere.
• I realized that it too, was in my car, so I went to go get it.
• I took my iBook apart.
• I took the Combo Drive apart. The disc let me put it in, no clue why. I guess it wanted some fresh air inside?
• Put the iBook half-way back together, except I forgot to connect the Combo Drive up again.
• Took it apart, hooked up the Combo Drive, and then put the iBook back together again.
• Booted the iBook with the iPartition boot disc. (It worked fine.)