You are reading content from Scuttlebutt
@Christian Bundy %HhkEF4yj03+qpwa72pS8Cn9zhl6iC+hkAj4rPEIvmKM=.sha256

Frustrated that your link isn't clickable? Wrap the link in < and >, like this:

@dan %uEIm+KI3SSxiAcJvOMpWOEtLjaUHl9ygNRHPupZSHgs=.sha256

tim-and-eric-mind-blown.gif

@Christian Bundy %mMQyYUK5mCCS+vgRR/bKFE/ZgJC1L/5wUA5F+VGGnoI=.sha256

I don't know how I went so long using Markdown before realizing this.

cc: #markdown-tips #ssb-markdown

@kas %tg31BJ0+6yMyLJJPVqIkIv+XM0+NnTHTESdZ7SthYI4=.sha256

FYI: Only the DAT link looks clickable in patchfoo, the other addresses – angle-bracketed or not – look like plain text.

However:

[proto://host:port/path?query#fragment](proto://host:port/path?query#fragment)

proto://host:port/path?query#fragment

@Christian Bundy %fgNT83NP9gOEmWzgp3OUl9qDHUZTk9fsIjSf8d6qEpU=.sha256

@kas Bummer, I didn't realize that the current #ssb-markdown doesn't support that. Should be solved if/when my PR is merged! It seems to be working pretty well now.

@kas %R/GlHCMoudEsiIAOxssxNz9LnxrY4CC15d5HLy3HdWo=.sha256

@bundy, good to hear. Looking forward to seeing your PR merged.

@cel %Z2dr7bnU+6BGdSk0wu7vCGPTCFZknNkmuXmMC9LVkGU=.sha256

patchfoo doesn't use ssb-markdown, it uses ssb-marked. same for ssb-viewer and git-ssb-web. patchfoo and git-ssb-web edit the renderer objects to customize the rendering output, and git-ssb-web edits the lexer rules to linkify git object ids. so these won't be able to make use of updates to ssb-markdown as is. ssb-viewer might be the easiest to change to use ssb-markdown - i'm not sure. there is an update to ssb-marked %EnbxTha... that makes it linkify more protocols, but in a quick test I didn't it see it change how the post %HhkEF4y... was rendered. That said, I value compatibility of rendering, so if ssb-markdown is linkifying these then I will probably want to too.

@Christian Bundy %ijcZF1w9AuNh0/UsvdoLXVVtSMIbPo+vDpcKvCH9qGk=.sha256

@cel

That makes sense. For what it's worth, my branch of ssb-markdown is CommonMark plus:

  • Block: Full HTML output, accepts Markdown string and opts.
    • Any link starting with # has target="_blank" added as a property.
    • Emoji :name: renderer, defaults to UTF-8 emoji output but can use images with opts.emoji function.
    • Linkifier:
      • HTTP, HTTPS, FTP, data, and dat URI schemes by default.
      • Ability for plugins to add HTTP-like protocol handlers in opts.protocols array.
      • Sigil links, hashtags, and @mentions rendered with opts.toUrl() function.
    • Media:
      • Supports alt text starting with audio: or video: to render media players.
      • Wraps all imags in a link to that image with opts.toUrl() function (hmm).
  • Inline: Plaintext content preview, accepts Markdown string and opts.
    • Emoji :name: emojifier, defaults to UTF-8 emoji output but can use images with opts.emoji function.
    • Links are replaced with the plaintext text node inside the link (no href).
    • Images are replaced with their alt text.
    • Code blocks are replaced with their HTML-encoded contents.

If you think the git object id linkifier might be a good fit for ssb-markdown I'd be happy to look into adding it to my branch.

Join Scuttlebutt now