Markdown support #140

Closed
neave opened this Issue Aug 28, 2012 · 6 comments

Projects

None yet

4 participants

@neave
neave commented Aug 28, 2012

Currently App.net uses the Twitter tradition of using full URLs as the only way to link to content, and offering no way to stress or emphasise text other than SHOUTING.

We need some sort of mark up, like HTML or Markdown (just as GitHub uses). It would be much more expressive, concise, and useful. I and a few others would love to see a subset of Markdown support added to App.net. Then the end clients can render the bold, italic text and hyperlinks how they see fit.

@JoshBlake

Someone mentioned this in a post or elsewhere, and I suggested that with the Annotation API, client could be free to indicate which sections of a post are bold, italic, etc., and other clients could render appropriately if they support the convention.

@dquick-freelance

As post content is currently 256 plaintext characters, I don't see where this requires API support - it would be trivial to implement client-side, with the added benefit that forcing Markdown annotations to use some of those characters might make people think more about what actually needs to be bold, italicized, etc.

On Aug 28, 2012, at 9:01 AM, Paul Neave notifications@github.com wrote:

Currently App.net uses the Twitter tradition of using full URLs as the only way to link to content, and offering no way to stress or emphasise text other than SHOUTING.

We need some sort of mark up, like HTML or Markdown (just as GitHub uses). It would be much more expressive, concise, and useful. I and a few others would love to see a subset of Markdown support added to App.net. Then the end clients can render the bold, italic text and hyperlinks how they see fit.


Reply to this email directly or view it on GitHub.

@neave
neave commented Aug 28, 2012

@dquick-freelance You are correct, this probably isn't a spec issue but more of alpha.app.net client feature request. However, if each app.net post includes meta data, it would be preferable to have hyperlinks included in that meta data. That way long URLs and Markdown hyperlinks wouldn't take up valuable text space, and we won't have to resort to URL shorteners.

For example, this:

Here is a link

is better than this:

Here is a link: https://www.google.co.uk/#hl=en&output=search&sclient=psy-ab&q=test&oq=test&gs_l=hp.3..0l4.809.1057.0.1278.4.4.0.0.0.0.109.332.2j2.4.0...0.0...1c.rBkE7OIrzGE&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=6dd2acfce60f574c&biw=1680&bih=929

@dquick-freelance

The URL linking behavior you describe is already in the API spec under post.entities.links but is not yet complete.

On Aug 28, 2012, at 9:20 AM, Paul Neave notifications@github.com wrote:

@dquick-freelance You are correct, this probably isn't a spec issue but more of alpha.app.net client feature request. However, if each update includes meta data, it would be preferable to have hyperlinks included in that meta data. That way long URLs and Markdown hyperlinks wouldn't take up valuable text space, and we won't have to report to URL shorteners.

For example, this:

Here is a link

is better than this:

Here is a link: https://www.google.co.uk/#hl=en&output=search&sclient=psy-ab&q=test&oq=test&gs_l=hp.3..0l4.809.1057.0.1278.4.4.0.0.0.0.109.332.2j2.4.0...0.0...1c.rBkE7OIrzGE&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=6dd2acfce60f574c&biw=1680&bih=929


Reply to this email directly or view it on GitHub.

@neave
neave commented Aug 28, 2012

@dquick-freelance OK, great. I guess I'll champion Markdown support over at alpha.app.net, rather than as a spec addition.

@mthurman
Member

Sounds like this can be closed.

@mthurman mthurman closed this Aug 29, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment