Full markdown support
I want full markdown support. This includes Headers, quotes, and possibly all the fancy charts and stuff. It would allow for better messages. Not to mention, bots could do a lot more with markdown.
I agree. I would love to use this for server announcements and my bot, voted!
I wish for table support.
I would love to see the markdown support/api get improved but apart from that maybe update the support page to show what features it does currently support a little more accurately -
Markdown Text 101 (Chat Formatting: Bold, Italic, Underline) [ https://goo.gl/JJXYDF ]
That document seems out of date and shows links & stuff that just don't work (anymore).
I'd define it as a subset of Markdown, not a fork of it or a language inspired by it.
i've seen some bots using beautiful links. i imagine like [link](http://url.com)
am i able to write links like this too? no?
it currently is more like a MarkDownDown. Please add more Markdown features to discord!!
Worded kinda rough, but I do agree. Full markdown support would be awesome.
As I asked here: https://support.discordapp.com/hc/en-us/requests/582310, I think complete Markdown is needed, or it shouldn't be called "Markdown".
I find myself very disappointed as well by the lack of true markdown support.
Agree with extended markdown support, disagree with the OP's personality.
I would have put it less arrogantly, but I agree that markdown support should be expanded to allow for more formatting options.
It would be particularly nice to have links. Tables, while useful, I feel would be less common in a setting such as Discord, but linking is quite common. For the normal user this isn't a huge deal, you are probably only posting one or two links at a time, but for my bot this is HUGE as far as beautification is concerned.
As you can see there is a massive difference, with reddit there are five nice, condensed links and then there is discord where we have five lines with links that are extremely long and not that pretty.
Yes I could improve this using bit.ly, but everyone I have talked with said that they would not feel comfortable clicking shortened links, even from a trusted source.
Johny aka. Kelrond commented
I would strongly suggest to use CommonMark instead, so it follows the same standard as sites like StackOverflow, reddit and GitHub, plus giving access to awesome libraries supported by their developers. :)
I think chat might get a bit messy if we started adding all that. Unless it was a specific permission for people to use "extended markdown" or some such.
I think that links would be a nice touch. If a user writes "Check out the [post](https://Google.com/groups)" Discord could render it as "post (Google.com)" to show the domain.
The main feature I try to use all the time but can't is quoting!
> Something someone else said.
It would be very nice. Right now I'm using `` to quote but the fixed-width font is less than ideal.
Luke Taylor commented
I totally agree with this. I want to see full markdown support.
I think markdown settings on a per-server basis would be beneficial, even if some features are off by default. For small servers, using headings and links might not be bad. And for all servers, there's *no* reason not to have quotes `>`.
Agreed it shouldn't be called something it isn't.
Albeit I'd present it more pacively than this, I'm very much fer having this wonder of a program falsely advertise itself.
Strange Penguin commented
Geezes... Dont act so entitled. While yes, I wouldn't mind expanded support for additional markdown, it should still be a very limited subset. This is for messaging. Not creating forums/posts. I already disagree with support for the code blocks/code fence, but I wouldn't mind seeing tables, lists, and quotes.
You dont need headers - This is not a forum. You would only be using them to format your text and make it larger...
You dont need markdown links (it will already parse URLs for you)
You dont need markdown images (it will already display a preview)
You dont need HRs (just send another message)
Lol chill dude
Do you really think being this aggressive will yield results? You haven't been wronged, don't play victim all of a sudden.
It looks like this is what came of the "standardize markdown" w3 group? http://commonmark.org/
> Why is my suggestion so rude?
I'd prefer the term "aggressive" - and It's because I feel I've been wronged by being informed "Discord supports markdown" when in fact it supports almost none of it. Certainly nothing even remotely close to what I've become accustomed.
> just to note ... markdown practically has no real specification right now
Interesting... because every time I've seen Markdown referenced, it's to this
Github does so. Reddit does so. The Python's implementation I'm aware of does so. Every flavor I've seen does so, so far. Even the link your link references does so (and does not apparently suggest anything like reducing its functionality to this degree).
> A standardization of the existing core Markdown conventions, as documented by John Gruber, in a formal language specification.
The top result for Markdown on The Google is that page, and on top of that the page itself is apparently reserving the name Markdown in some capacity.
Admittedly, it's not as standardized as I'd like - some things build on top of it and make tweaks (as in Github Flavored Markdown and a few other nice addons I've used). Nowhere have I seen "Markdown" used to refer to this obscenely limited feature set.