پرش به مطلب اصلی

Comments

StatusCurrent
OwnerAparat Product Team
Last verified2026-08-02 — Figma "AWD - Video Single", the single-video API mapping, the live product, and five support-centre articles on commenting

Part of the Video Single page. UI labels are given as an English gloss followed by the Persian string in quotes; the quoted Persian is authoritative — except for the word video, which this documentation always spells «ویدئو» even where the screen shows «ویدیو» (see the language note).

Introduction & Purpose

The comments section («دیدگاه‌ها») is where viewers discuss a video and where the channel owner engages with and moderates that discussion. This page covers posting and replying, the reactions and threading, ordering, the limits that govern how often a viewer can comment, the owner's inline moderation tools, the signed-out experience, and the special state where commenting is temporarily disabled.

Business goal: foster healthy engagement under each video while giving creators the tools to keep their comment section on-topic and safe.

Scope

Viewing, posting, replying to, liking, pinning, and moderating comments on this page; the signed-out state; and the “commenting disabled” state. Reporting the video (not a comment) is covered in Video actions.

Out of scope: the creator's comment-management screens. Bulk comment management and the spam queue («دیدگاه هرز») are dashboard surfaces, not watch-page ones — the owner controls documented here are only the inline ones that appear next to a comment. Reporting a comment as inappropriate or spam is likewise a dashboard action.

Audiences & Roles

Reading comments is open to everyone. Posting, replying and liking a comment require sign-in. Moderation controls appear only for the channel owner viewing their own video. See the hub roles.

Business Rules

  • BR-1 — Comment count and ordering. The section header shows the number of comments as «N دیدگاه» (e.g. «۵ دیدگاه»). Comments are ordered by popularity — the most-liked comment first, not chronologically, so the comment most people agreed with is the one most people see. The list is paged; further comments load on demand.
  • BR-2 — Posting requires sign-in. The compose box placeholder is «دیدگاه خود را بنویسید...»; for a signed-out visitor, attempting to post opens the sign-in modal.
  • BR-3 — Comment length limit. A comment is limited to 300 characters, shown by the counter «۰ از ۳۰۰»; compose actions are Send comment («ارسال دیدگاه») and Cancel («انصراف»). The limit is set by the server and delivered with the comment list, so it is one number for the whole product rather than a client constant.
  • BR-4 — Replies. A comment can be replied to («پاسخ»); the reply is placed directly under the comment it answers so the conversation stays readable. A thread's replies can be expanded and collapsed with Show N replies / Hide N replies («نمایش N پاسخ» / «بستن N پاسخ»).
  • BR-5 — Likes on comments. Each comment shows a like control with a count (e.g. «۱۱۲»). The control is the heart to the right of the reply action; liking turns it red. Liking a comment requires sign-in.
  • BR-6 — Pinned comment. A comment can be pinned from its three-dot menu, and is then shown with a «پین شده» marker above the rest.
  • BR-7 — Owner moderation. For the channel owner, each comment exposes a moderation menu: Pin / Unpin («پین کردن» / «خروج از پین»), Edit comment («ویرایش دیدگاه»), Delete comment («حذف دیدگاه», confirmed with «آیا می‌خواهید این دیدگاه را حذف کنید؟»), Reject comment («عدم تأیید دیدگاه»), Report violation («گزارش تخلف»), and Spammer user («کاربر هرزنویس»).
  • BR-8 — A username is required before a first comment. A viewer with an account but no username set cannot comment: a dialog titled «تعریف نام کاربری» (“set a username”) explains «کاربر عزیز آپارات، برای نوشتن دیدگاه روی ویدئوها، ابتدا باید نام کاربری مخصوص خود را در صفحه تنظیمات > اطلاعات کانال تنظیم کنید.» with Set username («تنظیم نام کاربری») and Cancel commenting («انصراف از نوشتن دیدگاه»).
  • BR-9 — Commenting can be switched off per video and page-wide. Whether commenting is available is carried as a property of the video and, separately, as a page-level setting; both must allow it.
  • BR-10 — Rate limits and abuse blocks. Posting several comments back to back with no pause blocks further commenting for 1 minute. Repeating near-identical comments (the classic “follow me back” pattern) blocks the channel from commenting for a set period. Filing incorrect video reports or using unrelated tags also costs the viewer the ability to comment for a period — commenting privileges are tied to the account's overall conduct, not only to what it writes here.
  • BR-11 — Commenting disabled (temporary). During certain periods the whole section can be switched to a disabled state: the comment input is fully disabled (no interaction, and its inner actions too) and a notice explains that showing and posting comments is turned off. The design records this as a temporary, administrative state that is reverted afterwards.

Scenarios

Scenario 1: Post a comment

Purpose — a viewer adds a comment under the video.

Roles Involved — signed-in viewers (a signed-out visitor is prompted to sign in).

Preconditions — the viewer is on the watch page and commenting is enabled.

Main Flow

  1. The viewer clicks comments («دیدگاه‌ها») in the action bar. → The page scrolls to the comments section, headed «N دیدگاه», with the most-liked comment first (BR-1).
  2. The viewer types in the compose box (placeholder «دیدگاه خود را بنویسید...»). → A character counter shows «۰ از ۳۰۰» counting up (BR-3).
  3. The viewer clicks Send comment («ارسال دیدگاه»). → The comment is posted and appears in the list; Cancel («انصراف») discards the draft.

Extensions — Alternative & Exception Flows

  • 2a. The viewer is signed out:
    • 2a1. Submitting opens the sign-in modal (BR-2). On the live product a signed-out visitor sees only the compose box — no comment list, count, or sort control is shown until signed in.
  • 2b. The viewer has an account but no username:
    • 2b1. The «تعریف نام کاربری» dialog opens and commenting is blocked until a username is set (BR-8).
  • 2c. The viewer wants the comment attached to a specific second of the video:
    • 2c1. The viewer pauses at that moment, opens the comments, presses the clock icon, writes the comment and sends it — the comment is then tied to that timestamp.
  • 3a. The comment exceeds 300 characters:
    • 3a1. The counter caps at the limit and the comment cannot exceed it (BR-3).
  • 3b. The comment is empty:
    • 3b1. Send is unavailable until text is entered.
  • 3c. The viewer has just posted several comments in a row:
    • 3c1. Commenting is blocked for 1 minute; the viewer must wait before posting again (BR-10).
  • 3d. The viewer repeatedly posts the same or near-identical text:
    • 3d1. The channel is blocked from commenting for a set period (BR-10).

Postconditions — the comment is added to the discussion (subject to any moderation).

Scenario 2: Reply to and react to comments

Purpose — a viewer engages with an existing comment.

Roles Involved — signed-in viewers (reading is open to all).

Preconditions — the video has at least one comment and the owner has left commenting enabled.

Main Flow

  1. The viewer clicks Reply («پاسخ») on a comment. → A reply box opens under it; Send reply («ارسال پاسخ») posts it, and the reply is placed under the comment it answers (BR-4).
  2. The viewer expands a thread with Show N replies («نمایش N پاسخ»). → The replies appear; Hide N replies («بستن N پاسخ») collapses them.
  3. The viewer likes a comment by pressing the heart to the right of the reply action. → The heart turns red and the comment's like count updates (BR-5).

Extensions — Alternative & Exception Flows

  • 1a. The viewer is signed out:
    • 1a1. Replying or liking a comment opens the sign-in modal.
  • 1b. The comment already has a long reply thread:
    • 1b1. Replies are collapsed by default and loaded on demand rather than shipped with the first page of comments.
  • 3a. The viewer likes their own comment or an already-liked one:
    • 3a1. The control is a toggle — pressing it again removes the like.

Postconditions — the reply/like is recorded on the comment.

Scenario 3: Moderate comments (channel owner)

Purpose — the channel owner manages the discussion on their own video.

Roles Involvedchannel owner only.

Preconditions — the signed-in viewer owns the video's channel and opens a comment's menu.

Main Flow

  1. The owner opens a comment's three-dot menu. → It offers Pin / Unpin («پین کردن» / «خروج از پین»), Edit comment («ویرایش دیدگاه»), Delete comment («حذف دیدگاه»), Reject comment («عدم تأیید دیدگاه»), Report violation («گزارش تخلف»), and Spammer user («کاربر هرزنویس») (BR-7).
  2. The owner pins a comment. → It is marked «پین شده» and surfaces above the rest (BR-6).
  3. The owner rejects or deletes a comment. → Deleting asks «آیا می‌خواهید این دیدگاه را حذف کنید؟» before removing it; the comment leaves the public list.

Extensions — Alternative & Exception Flows

  • 1a. The viewer is not the channel owner:
    • 1a1. The moderation menu is not shown; only the standard reply/like controls appear.
  • 2a. A comment is already pinned:
    • 2a1. The menu shows Unpin («خروج از پین») instead of Pin.
  • 3a. The owner wants to work through many comments at once, or handle the spam queue:
    • 3a1. That is the dashboard's comment-management surface, not this page — the inline menu handles one comment at a time.

Postconditions — the discussion reflects the owner's moderation.

Scenario 4: Commenting is temporarily disabled

Purpose — a viewer opens a video whose comments are turned off during a special period.

Roles Involved — all viewers.

Preconditions — the commenting-disabled state is active for the page (BR-11).

Main Flow

  1. The viewer reaches the comments area. → The compose input is fully disabled — neither it nor the actions inside it respond — its placeholder changes to the disabled message, and — where the component allows it — its avatar is replaced by an info icon (the design records the icon as preferred but falls back to the avatar).
  2. A notice explains that comments are off. → On desktop: «نمایش و ارسال دیدگاه، در این روزها غیرفعال شده است.» On mobile: «نمایش و ارسال دیدگاه برای مدتی غیرفعال است.»
  3. The viewer clicks the comments action in the action bar. → The page scrolls down so the disabled notice comes into view; no compose is possible.

Extensions — Alternative & Exception Flows

  • 2a. Existing comments while disabled:
    • 2a1. Both message strings say that showing as well as posting is off, which reads as the list being hidden too. [CLARIFICATION NEEDED: confirm whether existing comments remain visible in this state.]
  • 2b. The owner opens their own video while the state is active:
    • 2b1. [CLARIFICATION NEEDED: whether the owner's moderation menu remains reachable while commenting is disabled.]

Postconditions — the viewer cannot post; the state reverts to normal when the disabled period ends.

Mobile & Tablet View

Only the differences from desktop (see the hub Mobile & Tablet View):

  • The comments section is reached from the action row / details sheet and stacks in the single column.
  • The commenting-disabled notice uses the shorter mobile string «نمایش و ارسال دیدگاه برای مدتی غیرفعال است.» (Scenario 4).

Open Questions

  • 2026-07-21 — Whether existing comments stay visible while commenting is disabled, and whether the owner's moderation menu is still reachable (Scenario 4). — waiting on Product.
  • 2026-08-02 — Ordering vs pinning. Comments are ordered most-liked first and a pinned comment sits above them. Confirm what happens when the owner pins a comment that would already rank first, and whether more than one comment can be pinned (BR-1, BR-6). — waiting on Product.
  • 2026-08-02 — Timestamped comments in the list. The support centre documents attaching a comment to a moment, but the design does not show how such a comment is rendered or whether clicking it seeks the player (Scenario 1, 2c). — waiting on Product/Design.

Changelog

DateChangeSource
2026-08-02Rewritten. Added comment ordering (most-liked first — this closes a previous open question), the 1-minute rate limit and the abuse blocks, the username prerequisite, timestamped comments, the like-control placement, the delete confirmation, and the boundary with the dashboard's comment-management screens. Added a machine-readable endpoint-context block to the page's front matter, for developers who read this repository rather than the site.Design contracts + Figma + live product + support centre
2026-07-21Initial version.Figma "AWD - Video Single" + live product