Context: Voyager shows these options which results in a large amount of reports just being "Breaks community rules" with no info or reason whatsoever.
this post was submitted on 31 May 2026
426 points (98.0% liked)
memes
21662 readers
1618 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know, I opened an issue on Voyager's GitHub last year to suggest changes
What's the significance of this syntax with regard to it not rendering?
I've long wanted a somewhat standardized way to define community rules so I could do exactly what you were describing in your issue, but I'm not clear on how/why that syntax doesn't render.
I tried it in Tesseract, which admittedly use a different markdown renderer than other apps, and the first line shows but the second and third don't.
If other apps can get on board with that, then I may need to understand what's happening in that syntax to make sure it doesn't render.
It's been a while, but I think it's based on a trick to add comments to Markdown. I tried it with Tesseract, and none of the lines rendered, but only if I add an empty line in front.
It's a bit of a hack, but it can use existing endpoints and only needs some minor changes on the client side. The alternative would be implementing support for it in Lemmy, Mbin, PieFed, etc. but that probably takes a while and can also be done later when it has proven its usefulness.
Edit: I think I found the explanation behind the syntax https://stackoverflow.com/questions/4823468/comments-in-markdown
Cool, thanks. I'll give that a read and see if I can make it work cleanly. At this point, it's just an experiment, but I've wanted to have some mechanism for a standardized machine-readable community rules for a long time, specifically to put into the report and moderation workflows. If I can make it work cleanly, and if it's not something already planned for Lemmy 1.0, I'm absolutely willing to make that a Tesseract feature.