I intentionally lowered the steps of editing on bleedwrite to one, two if it's a new post, though now that I've got it up and running, I notice that I'm using it in a way I didn't really anticipate.

After I'm done writing anything, I always log out. Every time.

I'm doing it to:

1. see the site from the public face, which is practically the exact same, and kind of a dumb thing to be doing. Good to check I guess.
   
2. lock myself out from doing something on accident.

I think that it might be to my benefit to add a lockout checkbox or something, just to add a single step to the editing flow. It'd just be a safety, essentially, if its on, none of the editing functionality would be live.

Its a super simple change, but its against the original design philosophy laid out in the opening post. Does that make it a bad idea? No, but I'm worried about feature creep if I were to lose focus on the design goals I'd setup. I can always add it and see if affects my usage at all.

There's three things left I'd like to add:

1. One is a silly easy one I just keep forgetting when I have Coda open, code formatting, kind of essential. I think I'm just gonna add a BB style tag for it, ie [tag]codez[/tag], though I could see if theres a browser intent like I'm using for the links and stuff.
   
2. Stripping out the Webkit ghost formatting, it wasn't in Chrome but at some point was folded back in, useless spans with Apple class names, its weird, I don't know why they're there, but they're annoying to have in my database.
   
3. This is more of a conceptual feature than actually useful. I've done some stuff with websocket, and the thought I had at the outset with bleedwrite is that it'd be cool to build it to stream out what I'm writing in real time, if you were on the page while I was typing you see my revisions Google Wave style, it wouldn't be cached, just streamed as it happened.
   

So, now that most of the functionality I need is here, moving on to the look.