What security problems do you foresee? As I outlined in my post, I created a dedicated Dropbox account for the blog and it only synchronizes files meant for the blog. If those became public it wouldn't be a problem.
I'm referring to the known (and still not fixed?) issues with dropbox, including logging out having no real effect on disabling access to the dropbox files. Or someone being able to steal the dropbox keys from one computer and reuse them on a different computer.
In addition, as I'm sure you recognize, this reduces breaking into your hardened box and filling it with unicorn pr0n to swiping your friend's laptop while she is in the loo at the Starbucks.
So someone can steal the key to your server with a few minutes access to your home computers or laptops and you will not know until you have unicorn pron all over your blog.
This may be fine, and I mean that, for a personal blog (that also has regular backups.) I wouldn't set this up for clients (as suggested by others) to make it easier for them to blog, I think I would find a different solution for them.
Don't get me wrong. For my own personal needs, I think your solution is better than say, posterous which seems to be going downhill fast.
I like the idea of easily, quickly, blogging within emacs.
When I install Dropbox on a new machine, I can use selective sync to decide which folders are kept in sync on that machine. You can configure selective sync in CLI mode using 'dropbox exclude <path>'. (Unfortunately, I don't think there's a whitelist option.)
Is there a reason this wouldn't work for your use case?
I don't want my personal account on the server in case it was compromised. Besides, even if you use that "dropbox exclude" command, the client will start downloading all of your files when you first link it and there's no way to tell it not to do that before you have the chance to do all of your excludes.
In addition, as I'm sure you recognize, this reduces breaking into your hardened box and filling it with unicorn pr0n to swiping your friend's laptop while she is in the loo at the Starbucks.
So someone can steal the key to your server with a few minutes access to your home computers or laptops and you will not know until you have unicorn pron all over your blog.
This may be fine, and I mean that, for a personal blog (that also has regular backups.) I wouldn't set this up for clients (as suggested by others) to make it easier for them to blog, I think I would find a different solution for them.
Don't get me wrong. For my own personal needs, I think your solution is better than say, posterous which seems to be going downhill fast.
I like the idea of easily, quickly, blogging within emacs.