I think it's fine to use unique platform features like this, but if you're actually using this actively, be aware that not everyone will see your titles as you intended them. It's only Lemmy users that can see it actually render "properly", everyone else just sees the plaintext Markdown symbols.
Be careful of the character limit on each viewer, as they can "trim" your title in the middle of some markup tag and just display part of it as the title.
You can, but maybe you shouldn't. Given that this post is in the fediverse community, I don't feel too bad about mentioning that Lemmy is part of a federated network with PieFed and MBIN (I try not to bollock on too much about the platform I happen to be using).
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It's therefore not unreasonable for other platforms to render it as such.
Given this, and the poor support for mobile clients indicated in the comments, and the fact that it's only a subset of MarkDown tags, but include ones that aren't part of CommonMark standard, I'd argue that it's not necessarily a good idea.
Another commenter (who's contributed code to Lemmy) pointed to a link that provides the specification for that field: "A simple, human-readable, plain-text name for the object. HTML markup MUST NOT be included."
So in this case, it's more that the JSON looks a bit ambiguous: 'mediaType' is only referring to the format of the text in a post's body, but - unlike me - you'd also need to be aware of the spec to know that it doesn't apply to the title.
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It’s therefore not unreasonable for other platforms to render it as such.
Actually, the name property is explicitly plain text, it shouldn't contain any type of markup, whether that be markdown or HTML.
For clarity, I wasn't intending to say that PieFed treats that field as HTML (it treats it as text), I just meant that if you were looking at that JSON, and being a bit lazy like me and not looking at specs, then it wouldn't be unreasonable to assume that the 'mediaType' field also refers to 'name' (rather than a 'content' field which this post doesn't happen to have).
Anyway, this seems to be even more reason why MD shouldn't be put in titles, and front-ends shouldn't be encouraging the practise by rendering it.
Also, this gives me real text-on-image-in-Facebook-post-just-to-get-noticed vibes.
If everybody can use Markdown in their post titles, then everybody will use Markdown in their post titles, until it's a mess of colors, bold, and italics.
Markdown is plain text, so it's fine to go in the field. It's also fine for apps to allow OP's post to look like garbage because there's no requirement for support.
A comment here distinguishes between the 'plain text' that's allowed by the spec, and MarkDown as a markup language (it's confusingly named, I guess, but that's what Wikipedia categorises it as too)
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It’s therefore not unreasonable for other platforms to render it as such.
Actually, the name property is explicitly plain text, it shouldn't contain any type of markup, whether that be markdown or HTML.
I still have installed a dozen or so clients, so I opened Voyager to remind myself what it is in comparison to Jerboa, which is also my preferred client.
Suddenly my android device has an iOS user interface. To me, this is lazy development. I'm sure it's fine for someone accustomed to it, but even having a static header and footer seem out of date.
Onno (VK6FLAB)
in reply to Amon • • •steventhedev
in reply to Onno (VK6FLAB) • • •borth
in reply to steventhedev • • •Optional
in reply to borth • • •Ace! _SL/S
in reply to borth • • •Amon
in reply to Onno (VK6FLAB) • • •Ricky Rigatoni
in reply to Amon • • •catloaf
in reply to Onno (VK6FLAB) • • •lemmyng
in reply to Onno (VK6FLAB) • • •#is rendered as h1.IronKrill
in reply to Onno (VK6FLAB) • • •kat
in reply to Onno (VK6FLAB) • • •JohnnyEnzyme
in reply to Amon • • •(unlike Reddit, for example)
I use bold and italic a lot in post titles. Some of the other stuff wouldn't make much sense I don't think, but every little bit helps.
Amon
in reply to JohnnyEnzyme • • •codecould work and maybe ^superscript^ or ~subscript~ and that's about it I thinkinfeeeee
in reply to Amon • • •Can you create headings in headings?
smeg
in reply to infeeeee • • •infeeeee
in reply to smeg • • •OK, I will never use it again.
like this
TimeSquirrel likes this.
smeg
in reply to infeeeee • • •A_Union_of_Kobolds
in reply to infeeeee • • •smeg
in reply to Amon • • •infeeeee
in reply to smeg • • •Lemmy-ui uses
markdown-it: github.com/LemmyNet/lemmy-ui/b…Markdown-it follows the CommonMark spec with extensions: spec.commonmark.org/current/ As I see superscript is not part of the spec, but listed in the markdown-it readme as a plugin, so I guess it's coming from there: github.com/markdown-it/markdow…
They are also listed in package.json:
github.com/LemmyNet/lemmy-ui/b…
Lemmy docs about markdown support: join-lemmy.org/docs/users/02-m…
lemmy-ui/package.json at main · LemmyNet/lemmy-ui
GitHubPamasich
in reply to JohnnyEnzyme • • •JohnnyEnzyme
in reply to Pamasich • • •Hmm, sounds like a good point. Here's my sub:
lemm.ee/c/eurographicnovels
Can you tell me how our formatting might be messing search engines and stuff..?
bdonvr
in reply to Amon • • •perviouslyiner
in reply to Amon • • •Fitik
in reply to Amon • • •like this
hitstun, BentiGorlich and korendian like this.
Andrew
in reply to Amon • • •You can, but maybe you shouldn't. Given that this post is in the fediverse community, I don't feel too bad about mentioning that Lemmy is part of a federated network with PieFed and MBIN (I try not to bollock on too much about the platform I happen to be using).
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It's therefore not unreasonable for other platforms to render it as such.
Given this, and the poor support for mobile clients indicated in the comments, and the fact that it's only a subset of MarkDown tags, but include ones that aren't part of CommonMark standard, I'd argue that it's not necessarily a good idea.
like this
BentiGorlich, MHLoppy, ignirtoq and AlexanderESmith like this.
schnurrito
in reply to Andrew • • •Andrew
in reply to schnurrito • • •Yes - it's easy to do from a command line. For this post, it would be:
curl --header 'accept: application/activity+json' --location https://lemmy.world/post/24241974 | jq .::: spoiler it looks like
:::
Yes - it's easy to do from a command line. For this post, it would be:
curl --header 'accept: application/activity+json' --location https://lemmy.world/post/24241974 | jq .::: spoiler it looks like
:::
Amon
2025-01-13 20:48:50
like this
ignirtoq likes this.
schnurrito
in reply to Andrew • • •BentiGorlich
in reply to schnurrito • • •BrowserPub · A browser for exploring ActivityPub and the fediverse
browser.publike this
AlexanderESmith and Fitik like this.
AA5B
in reply to Andrew • • •This seems like a bug. Regardless of what clients may support, the json ought to accurately describe fields
Andrew
in reply to AA5B • • •Another commenter (who's contributed code to Lemmy) pointed to a link that provides the specification for that field: "A simple, human-readable, plain-text name for the object. HTML markup MUST NOT be included."
So in this case, it's more that the JSON looks a bit ambiguous: 'mediaType' is only referring to the format of the text in a post's body, but - unlike me - you'd also need to be aware of the spec to know that it doesn't apply to the title.
Activity Vocabulary
www.w3.orglike this
Fitik likes this.
flamingos-cant (hopepunk arc)
in reply to Andrew • • •Actually, the name property is explicitly plain text, it shouldn't contain any type of markup, whether that be markdown or HTML.
Activity Vocabulary
www.w3.orglike this
MHLoppy likes this.
Andrew
in reply to flamingos-cant (hopepunk arc) • • •Oh, wow. Thanks.
For clarity, I wasn't intending to say that PieFed treats that field as HTML (it treats it as text), I just meant that if you were looking at that JSON, and being a bit lazy like me and not looking at specs, then it wouldn't be unreasonable to assume that the 'mediaType' field also refers to 'name' (rather than a 'content' field which this post doesn't happen to have).
Anyway, this seems to be even more reason why MD shouldn't be put in titles, and front-ends shouldn't be encouraging the practise by rendering it.
kat
in reply to Andrew • • •P03 Locke
in reply to Andrew • • •Also, this gives me real text-on-image-in-Facebook-post-just-to-get-noticed vibes.
If everybody can use Markdown in their post titles, then everybody will use Markdown in their post titles, until it's a mess of colors, bold, and italics.
fmstrat
in reply to Andrew • • •Andrew
in reply to fmstrat • • •A comment here distinguishes between the 'plain text' that's allowed by the spec, and MarkDown as a markup language (it's confusingly named, I guess, but that's what Wikipedia categorises it as too)
plain-text formatting syntax, which is popularly used to format readme files
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)flamingos-cant (hopepunk arc)
2025-01-14 00:00:54
fmstrat
in reply to Andrew • • •misk
in reply to Amon • • •motor_spirit
in reply to misk • • •like this
TimeSquirrel likes this.
Ricky Rigatoni
in reply to motor_spirit • • •driving_crooner
in reply to Amon • • •like this
AlexanderESmith likes this.
f4f4f4f4f4f4f4f4
in reply to driving_crooner • • •driving_crooner
in reply to f4f4f4f4f4f4f4f4 • • •kat
in reply to driving_crooner • • •AmidFuror
in reply to Amon • • •jagged_circle
in reply to Amon • • •targetx
in reply to jagged_circle • • •GamingChairModel
in reply to targetx • • •Amon
in reply to jagged_circle • • •jagged_circle
in reply to Amon • • •Jtee
in reply to jagged_circle • • •JoshuaFalken
in reply to Jtee • • •I still have installed a dozen or so clients, so I opened Voyager to remind myself what it is in comparison to Jerboa, which is also my preferred client.
Suddenly my android device has an iOS user interface. To me, this is lazy development. I'm sure it's fine for someone accustomed to it, but even having a static header and footer seem out of date.
I'll stick with Jerboa for the time being.
jagged_circle
in reply to JoshuaFalken • • •Jtee
in reply to JoshuaFalken • • •Blaze (he/him)
in reply to jagged_circle • • •Thunder, Eternity, Connect, Summit?
lemmyapps.com/
Discover Fediverse apps with LemmyApps
www.lemmyapps.comjagged_circle
in reply to Blaze (he/him) • • •J4g2F
in reply to jagged_circle • • •jagged_circle
in reply to J4g2F • • •Feathercrown
in reply to Amon • • •Amon
in reply to Feathercrown • • •Clot
in reply to Amon • • •