guidelines

MNLN AI: links first, tags for routing, comments for discussion.

core rule

• Posts must be links. Text-only posts, open-ended forum threads, personal diary posts, and chat-style prompts do not belong here.
• Comments are for discussion of submitted links, tags, models, papers, evals, systems, and AI policy context.
• Tags are filters, not boards. Tag pages are filtered link lists, not separate forums.

links

• Model releases, technical reports, research papers, evals, benchmark methodology, safety reports, policy notices, and serious AI reporting.
• Inference cost, serving infra, training systems, agent frameworks, open-weight releases, incidents, and postmortems.
• Product launches only when the source has technical substance or a concrete policy, model, eval, pricing, or safety change.
• Do not submit prompt dumps, generic AI tool listicles, thin startup launches, unsupported AGI speculation, screenshots without a source, and affiliate SaaS reviews.
• Do not submit text-only forum posts. If there is no source link, it does not belong as a post.
• Do not submit hype threads, benchmark bait without methodology, slop news, and copied marketing copy.
• Submit the original source when possible. If a secondary article is useful, it should add real reporting or interpretation.
• Use the actual title or a clear neutral title. Do not use hype titles, price targets as bait, or claims the source does not support.

tags

• Every post should have one main routing tag such as General, Models, Papers, Evals, or another precise topic.
• Other Tags should describe model families, methods, evals, infra, safety issues, policy context, or tooling. Do not tag every company mentioned unless it is central to the link.
• This community does not use ticker lookup. Ticker-looking strings are treated as normal tags unless a future community setting changes that.
• Do not create duplicate tags for the same thing. Use one spelling and ask for cleanup if tags drift.

comments

• Comments are plain text discussion. External links must be submitted as posts.
• Post authors may mark one of their own comments as the author summary. Use it to explain why the link matters, not to turn the post into a text essay.
• Say what the source demonstrates, what benchmark or method is being used, and what remains uncertain.
• Add model details, eval caveats, system constraints, cost context, safety implications, policy nuance, or counterexamples.
• Avoid AGI prophecy, prompt spam, tool shilling, benchmark tribalism, personal attacks, and low-context hype.
• Disagree with the claim, not the person. Strong disagreement is fine; harassment is not.
• State uncertainty. MNLN discussion is not professional advice.

profiles

• Bios are optional, short, plain text context. They are not a place for links, contact handles, chat rooms, or promotion.

edits and deletes

• Authors may edit post titles and tags. Post URLs are locked after submission.
• Posts can be deleted by the author only before comments arrive.
• Comments can be edited or deleted by their author. Deleted comments with replies may remain as [deleted] placeholders so threads still make sense.
• Edits and deletes may be logged for abuse prevention and moderation integrity.

voting and karma

• Vote for signal, not agreement. Useful opposing views should not be buried just because they are inconvenient.
• Karma and trust limits exist to slow abuse, not to create status games.
• Downvotes affect other users and are intentionally harder to unlock.

moderation

• Spam, manipulation, ban evasion, undisclosed promotion, and off-platform solicitation may be removed or collapsed.
• Suspicious comments may be collapsed without a public warning label.
• Accounts that repeatedly promote chat rooms, signal groups, referral links, or pump language may be banned.
• Moderation keeps the feed source-backed and resistant to hype.

source warnings

Unlisted source warnings are advisory. They are there to catch promotion, referral, signal-room, and chat-room links, not to reject normal sources.