EDIT: on web, it renders like this
Oh no
this post was submitted on 13 Jan 2025
147 points (96.8% liked)
Fediverse
28954 readers
1091 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
Oh no indeed
Wow, amazing
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.
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.
Oh yea, I just mean that all markdown characters are ASCII, and thus allowed in a plain text field. 😉
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.
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.
Eh, I'll probably use italics tho, just like I did * in reddit.
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.
The Lemmy backend doesnt treat this field as markdown, if you look at the Activitypub data (curl -H "Accept: application/activity+json" https://lemmy.world/post/24241974 | jq) the title is federated as plaintext. Only lemmy-ui decides to render it as markdown for some reason.
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. …. it says it contains HTML
This seems like a bug. Regardless of what clients may support, the json ought to accurately describe fields
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.
load more comments
(4 replies)
If you have markdown on your title, then is not being rendered by Jerboa.
load more comments
(3 replies)
Word of caution, it doesn't render on Connect for Lemmy.
Nor Boost. It does in Raccoon, though.
Hmm, but the best part about markdown is that it is human readable regardless so it should still be fine
i am not human
Or Thunder
load more comments
(2 replies)
I'd settle for good spelling and grammar. Once most posters have mastered that, let them play with the formatting.
Lol apparently you can't
Guess it depends on your client because it works for me.
Works for me on Sync.
What client do you use?
Jerboa. Its awful but there's nothing better
Voyager
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.
I'm pretty sure there's a preference to not be iPhone UI
It wasn't just the UI. There was something else broken about it since I last tried it.
Thunder, Eternity, Connect, Summit?
I'll try eternity, thanks. None of the others are on fdroid
Thunder is in the IzzyOnDroid repo you can add it in fdroid
Thanks but I dont trust third party repos
You can also edit them after the fact unlike other platforms
What good is it for if I can’t change post title font to Comic Sans.
ABSOLUTELY NOTHIN
Good god, ya'll.
(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.
I mean, code could work and maybe ^superscript^ or ~subscript~ and that's about it I think
Can you create headings in headings?
You can, and it'll probably get annoying if everyone catches on!
load more comments
(1 replies)
load more comments
(2 replies)
load more comments
(2 replies)
@amon@lemmy.world Doesn't render it on Mbin
view more: next ›