AFAIK the Reddit-style markup is John Gruber's markdown. In any case there will have to be some differences. I'd rather use # as a tag than a header for instance. TBH, I think a non-janky markup is the markup you use most. The url markup does freak out if you put other markup in it. Perhaps one easy step in that direction is to swap + for two asterisks for bold. It would be nice to get the plus sign back out of potential conflicts. Also an escape character is badly needed. I'll do some work.
It's Gruber's markdown with some changes. Which is also dumb. Messing with syntax is beneath you. I know you like things to be a certain way, but the way you do stuff doesn't work. - your quotes methodology borks with a space in it - your italics/bold borks when mixed with other markdown - you can't do tables - you can't do superscript - you can't do hover text - inline images are great, but they read poorly and are immune to gifs Don't "do some work" adopt something you don't have to rethink every time I gripe. ;-)
Yeah, given the robust communities other markup syntaxes benefit from (the most readable being Markdown), I'm surprised to see a roll-your-own here. Why maintain your own reinvented wheel when there are so many really good ones out there (and that also come with good user penetration). As far as hashtags, I don't think it will be interpreted as a header unless it's at the beginning of a line so wouldn't that rule out most cases?
It basically started with news.arc, the HN source, which apes some of the functionality of markdown in Arc. What we have was the result of me adding to that incrementally. forwardslash and I'll will get together and discuss the best way forward to a happier place. 'most cases' is what bites you in the ass with designing a markup. ;)As far as hashtags, I don't think it will be interpreted as a header unless it's at the beginning of a line so wouldn't that rule out most cases?
I don't think any of these light weight markup language are capable of eliminating the known edge cases without compromising their usability. You just have to find the right balance that fits your use case. The reason I lean towards (Multi)Markdown is because of the aforementioned wide adoption (lots of users know it; lots of solid libraries support it). Beyond those things it mostly just comes down to personal preference when selecting a markup language.'most cases' is what bites you in the ass with designing a markup. ;)