@tekphloyd M↓ is good, but #orgdown might be even better choice.

@tekphloyd @elk supports a limited subset of markdown, and it's wonderful. I’d love to see it in @ivory.

@tekphloyd let us add more geek only features to scare away ordinary users.

@tekphloyd I think this should be something you explicitly flag per post to avoid misrendering. (With a setting to always flag your posts.) Does Mastodon support custom metadata like a post format flag?

@tekphloyd all i really need is italic and maybe bold...

and strikethrough would be nice

@tekphloyd No, because markdown should be supported on the server.

@tekphloyd Bad idea. We don't want to go back to MySpace. However, it's free for grabs for any client to implement MD interpretation, but shouldn't be forced through the API upon users who want a clean timeline

@tekphloyd @devinprater Custom fonts and different emphasis are an Accessibility nightmare on Twitter so, no, they should not. There's nothing stopping you from using *Markdown* syntax to add the _emphasis_ you want to your content, without having it change the way things look for everyone else.

Definitely the display of Markdown customisation should be optional if ever supported.

@tekphloyd This is something that is already supported on most servers. I think it's only base Mastodon that doesn't expose it, and even goes through the effort of stripping much of the markup when displaying posts.

This is the reason some clients have poor markup support, it's only been tested with basic Mastodon. Posts themselves are HTML, and are rendered fine in most places.

This post has bold and italics as well as a link with description.

@tekphloyd Option 3: Fine to use it for authoring, but convert it to HTML on save/distribution.

@tekphloyd YES

@tekphloyd Not without some kind of opt-in for "process this message as markdown"

#NotH1Tag

@tekphloyd @MichalBryxi Please don’t mess my feed up with crazy ass formatting.

@tekphloyd in my opinion it should not be supported. People will just use it to attract attention and my Timeline will look scattered. Let's keep it simple :)

@tekphloyd it doesn't even have to implement everything in Markdown. Even just a subset of bold, italics, strikethrough, inline code and code blocks, and tables maybe are enough.

@tekphloyd only if mastodon does (and it does not as far as i know)

it would make the timeline a mess

mastodon/twitter works because the messages are easy to read. don't ruin it

@tekphloyd what's a markdown?

@tekphloyd @clonezone I would like to answer with a qualified yes: *only* if they can round-trip saving, editing, and re-saving #Markdown successfully to and from #Mastodon without losing data or mangling a post. I have had problems with this in @icecubesapp

@tekphloyd classic Mastodon post where a deep-in-the-code geek assumes everyone else knows what geeky thing they're talking about.

@tekphloyd I think @Mastodon's role in the #Fediverse should be to *avoid* adding certain (most?) features. It should be the lowest common denominator option to help introduce new users to the wide world of the Fediverse, and then let the unique qualities of ActivityPub and WebFinger (etc) do the rest.

Want markdown support? Try X!

@tekphloyd Need a "Heck Yes" option.

No point writing 500 characters and *not* have the ability to emphasize and be fairly certain that others see the emphases.

@tekphloyd which markdown flavour though?

@tekphloyd torn on that one

@tekphloyd Everything is better with markdown 

@tekphloyd They should offer some sort of native formatting option, because otherwise people will use the mathematics characters to fake bold & italic, and those are a accessibility nightmare

@tekphloyd Support for #Markdown would be really great. And instead of just “favorite” it would be useful to support multiple reactions to a post. Both LinkedIn and Facebook have a good selection.

@tekphloyd@social.lol COUGH COUGH https://github.com/mastodon/mastodon/issues/18958

@tekphloyd doesn't it already?

There's a #source propert in #activitypub with a #mediatype that could be text/markdown, while the actual content of a note is text/html resulting from this.

https://www.w3.org/TR/activitypub/#source-property

I believe there are some mastodon forks already doing this

@tekphloyd yes

@tekphloyd Markdown should not be supported on Mastodon. It’ll force a support burden on all future mastodon apps to be backwards compatible. Once it’s available, people will expect you to use it , like they do on Discord. it won’t be opt-in. Also, writing markdown on mobile really sucks .

@tekphloyd this should be a server-side feature, and unless you're using vanilla Mastodon, that's what the rich-text-enabled part of the Fediverse already does. the spec says HTML on the wire, not Markdown, and definitely not HTML, strip it into plain text, and then pretend it's Markdown.

@tekphloyd do posts not have something comparable to a content-type header?