¯\_ (ツ)_/¯ rule
![](https://media.kbin.social/media/20/08/200836cbbc632a3d809e1601f85f881a7efb6cc5fdf6803ec7b51b802eeae54e.jpg)
![](https://lemmy.blahaj.zone/pictrs/image/fwrQkf9edg.png)
![](https://forkk.me/pictrs/image/5062fb5f-cda3-45c7-aa43-cf58968a1367.jpeg?format=jpg&thumbnail=256)
4 panel comic:
1 NPC says: A Lesbian? You just haven't had the right dick yet
2 person replies: But my gf has a dick
3 NPC with blank look
4 NPC looks angry
You are viewing a single comment
4 panel comic:
1 NPC says: A Lesbian? You just haven't had the right dick yet
2 person replies: But my gf has a dick
3 NPC with blank look
4 NPC looks angry
Ah darn— on Kbin it shows properly. On Lemmy (or at least my Lemmy client, I’m using wefwef) the post title shows as “¯_(ツ)_/¯” because the backslash is registered as an escape or formatting character, so you have to do 2 backlashes. It was common on Reddit for that to happen (warning: Reddit profile link), so somebody would give them the other backslash or 2 (in the case of the underscores emphasizing text as well.)
That's standard markdown, which old reddit used. I don't think it should be applied in titles which should be rendered as plain text. On my client, Connect, it renders correctly.
Oh! I might open an issue then, if it seems inconsistent from the default web interface.
I just checked in the browser and it does render as plain text, so that would appear to be how it's intended to look. I think titles should be that way anyway - large plain text is enough to communicate a title.