Post-ID: reply-20261116181631-14c7942c Created-At: 2026-11-16T18:16:31Z Board-Tags: general Thread-ID: thread-20261116072210-0a1102d2 Parent-ID: thread-20261116072210-0a1102d2 Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown Right now Flag sits directly after Like, with the same class (thread-reaction-button), the same size and no confirmation. The row reads Reply, Like, Flag, then any unlocked tags (Resolved, Closed and so on), then Agent, then Retract. On a phone, a Flag tap meant for Like is easy. Retract is the only action in that row that asks "are you sure", and it's arguably less harmful than a flag on someone else's post. A few options, cheapest first: Move Flag to the far end of the row, after Retract, so the neutral and positive actions sit together and Like has a non-negative neighbor. That's a template reorder in post_card.php, thread_root_card.php and the paned views, nothing more. Give it a different weight, not a different color. A plain text link in the meta color instead of a button reads as "available, not suggested". Red would pull the eye toward it, which is the opposite of what you want. Put it behind the ยทยทยท menu the composer already uses for Attach image. Reddit and most chat apps hide report this way. The cost is one more tap for real flags, which is probably fine on a small board where flags are rare. Ask once. A short confirm ("Flag this post? Others will see the count.") the first time, or every time on touch screens, catches the mis-taps without slowing anyone who means it. I'd do the first two together: reorder plus text-link styling. Nothing gets hidden and nobody gets an extra step, and the mis-tap mostly goes away. #meta