How this board works: review before publishing, no images, nofollow links, daily limits

Site FeedbackLiangke Li4 replies

Liangke LiMember#1

A few decisions behind this community that are worth stating up front, because they differ from most forums.

Every post is reviewed before it appears. A model reads it first; if it is not sure, a person does. Most posts are public within a minute. Nobody skips this, including the people who run the site. The review is not about opinions. Criticising software is fine. Promotion, referral links and recruiting are not.

No image uploads. Hot-linked images are tracking pixels with extra steps and they double the moderation work. Markdown is supported: code blocks, lists, links, quotes. Paste the error text instead of a screenshot of it; it is searchable and the next person can copy it.

Links carry rel="nofollow ugc". Posting here passes no search ranking to anything you link. That removes the main reason spam gets posted on forums.

Daily limits grow as you take part. A new member can start 2 topics and write 15 replies a day. After 3 published posts and a day on the site that becomes 5 and 50. After 20 posts, 10 likes received and two weeks, 10 and 120. The levels are computed from what you did, never granted by hand.

Published posts earn 3 points, at most one reward every five minutes and five a day, shared with project comments. Points are spent on the paid tools under /tools. The cap is there so the forum is not a points farm.

Topics can be tied to a project. Fill the "Related project" field with the last part of a project page address (for example ollama-ollama) and the topic is listed on that project's page under "Community discussions".

Editing a post is not possible yet, only deleting it; an edited post would have to go through review again and we have not built that. Say so here if that gets in your way.

4 replies

IvanMember#2

One question on the no-edit rule: a typo in a code block is the most common thing I would want to fix, and deleting the whole post to fix a flag name feels heavy. Would a short edit window right after posting (say 10 minutes, before anyone has replied) be reasonable, with the edited version going back through the same review?

Liangke LiAuthorMember#3

In reply to Ivan (#2)

That is the version we would build if we build it: a short window, no replies yet, and the edit is re-reviewed exactly like a new post. The reason it is not there today is only that re-review after edit touches the moderation queue, the cached pages and the notification that already went out to people who replied. For now, post a correction as a reply; it stays attached to the thread and is honest about what changed.

HermanMember#4

For anyone wondering whether fenced code blocks keep their language: they do. A block opened with three backticks and yaml, bash, python and so on comes out with the class on the <code> element, so the highlighting on the page follows it. Inline code works too. HTML in the post is stripped, which is the point.

ValerieRegular#5

Feature request, since this is the board for it: search within the community. The site search in the header only covers projects. Until there are enough topics it is fine to browse, but the Help board will outgrow that quickly if the accepted-answer mechanic works as intended.