Posts and comments are the primary content on Artemis. A post (internally called a “link”) can be either a link to an external URL or a self-post containing Markdown text. Beneath each post, users can reply in a nested comment thread. This page covers the full lifecycle of a post — from submission through comment discussion — including listing sorts, gilding, saving, reporting, and the share close workflow.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/artemis-development-group/artemis/llms.txt
Use this file to discover all available pages before exploring further.
Submitting a post
All posts are submitted through the/submit route. You can also submit into a specific branch by navigating to /r/:branchname/submit.
Open the submit form
Navigate to
/submit or click the Submit button in any branch sidebar. You must be logged in.Choose a post type
Select either Link (paste an external URL) or Text (write a self-post in Markdown). The available types depend on the branch’s
link_type setting: link, self, or any.Select a branch
Pick the branch you want to post to. If you arrived via
/r/:branchname/submit, the branch is pre-selected.Add optional details
- For link posts: paste the URL in the URL field.
- For text posts: write the body using Markdown in the text area.
- Optionally choose a link flair if the branch has flair templates configured.
If the branch has a custom submission text set (
config/submit_text), it is displayed above the form as a reminder of rules or guidelines.Post listing sorts
Each branch and the front page support five listing sorts, accessible as URL paths.| Sort | URL | Description |
|---|---|---|
| Hot | /r/:branch/hot or /hot | Default. Ranks posts by score and recency using the hot algorithm. |
| New | /r/:branch/new or /new | Chronological, newest first. |
| Rising | /r/:branch/rising or /rising | Posts gaining votes quickly relative to their age. |
| Top | /r/:branch/top | Highest scoring posts. Supports time filters: hour, day, week, month, year, all. |
| Controversial | /r/:branch/controversial | Posts with roughly equal upvotes and downvotes. Also supports time filters. |
t query parameter:
Comment threads
Comments live at/r/:branchname/comments/:article/:title/. Threads are nested — each reply creates a child node under its parent comment. Deep threads are collapsed automatically and can be expanded by clicking load more comments.
Individual comments have permanent URLs:
Suggested comment sort
Branch moderators can set a defaultsuggested_comment_sort on the branch. Individual users can override this with the sort dropdown on the comments page. Available sorts are: confidence, top, new, controversial, old, random, qa.
Saving posts and comments
Logged-in users can save any post or comment for later retrieval. Saved items are accessible at:/api/save with the item’s fullname.
Gilding
Any logged-in user can award gold to a post or comment they find valuable. Gilding requires gold credits.- Gild a post or comment via the gold icon below the item, or via the API:
POST /api/v1/gold/gild/:fullname - Give gold directly to a user:
POST /api/v1/gold/give/:username
/r/:branchname/gilded and the site-wide feed at /gilded.
Reporting
Users can flag a post or comment as violating branch rules or site-wide policies using the Report button. Reports are sent to the branch’s moderation queue at/r/:branchname/about/reports.
Send a report via the API:
Share close
The/share/close route handles cleanup after a post is shared externally. It is used internally by the sharing flow and does not require direct user interaction.
Related comment actions
| Action | API endpoint |
|---|---|
| Submit a comment | POST /api/comment |
| Edit a comment | POST /api/editusertext |
| Delete a post or comment | POST /api/del |
| Distinguish a comment (mod) | POST /api/distinguish/:how |
| Mark as NSFW | POST /api/marknsfw |
| Lock comments | POST /api/lock |