All things considered, a pretty large update! I've got more to talk about, but check back past the break for that.
As I've stressed before, time and again, this site exists for the community, so if you've got some ideas, post them below, and let us hear about it!
On the business side of things, I'm working on drafting a "longer-term" plan, hopefully ready to present something this week, or early next week, which lays down a specific "here's what we are going to do" plan, and then let you guys think it over, poke it with a stick, then call me an idiot, and have me do it again; as far as running a site, its been a pretty successful model thus far :-)
Expect one or two more "meta" posts in the next few days, and until then, let me know your thoughts below
Interesting idea but I personally think it couldn't help but lead to rampant stupidity.
You think marking italics like *this* instead of <i>this</i> of <em>this</em> leads to stupidity?
Or quoting text
> like this
Maybe you think the problem of Usenet was that exactly this style was standard on Usenet?
Wait ... you've got an bidirectional NNTP gateway in the list ... there people will inevitably use ">" formatting for quotes because that's how newsreaders do it automatically. If you don't support this, posts sent through NNTP will probably look awkward on the web site (and vice versa).
I'd really like to know how a slightly easier to type (and to read!) formatting will lead to rampant stupidity.
What it would cause is less formatting errors in posts due to incorrectly closed tags.
Ease up there guy. It's just an opinion not a personal insult.
If we allowed full markdown it would be opening up formatting that we currently do not allow for very good reasons. That was the rampant stupidity I was talking about.
If we limited markdown to mirror the tags we allow, you'd only be getting bold, italic, lists, and quote. Hardly seems worth the bother it would take to code properly* to me but if you want to convince paulej72 or NCommander to code it or to submit a pull request of your own for consideration, welcome to it. The issues tracker is here [github.com] if you want to submit it as a feature request.
* You should see all the checks and transformations incoming text goes through before it ever makes it to even the preview much less the db. They would all have to be extended, tested, and debugged. And that's not even considering rendering the markdown correctly.