My Posterous posting procedure
After a few hours of tedious programming, I'm now able to compose a message in Gmail using haml markup language and have it delivered to Posterous by a Ruby on RAILS application hosted at Heroku. Please take a look at the attached image showing the actual workflow.
All tools are free, a paramount condition if one takes into account that this blog won't ever pay for itself. The problem is that the whole process is COMPLEX. Will it become simpler when Garry Tan implements markup language posting via email at Posterous? Yes indeed, but he'll have a hard time implementing it because:
- Implementing haml is pretty easy, but dangerous because you can insert arbitrary ruby code inside the text.
- implementing textile is hard because email servers tend to cut lines that are too long, and there is no easy way to revert that by the parsing engine.
- markdown markup language doesn't suffer that much from line reformatting policies, but it's not as expressive as textile or haml.
You see? Whatever I do, wherever I go, I always end up messing with complex stuff. Who is the complex guy: me or the world?
Attachment: Posterous posting procedures.pdf
Comments [2]