fb-replylisted

# /fb-reply — reply to the comments under the owner's posts (safely) **Why.** Comments pile up under the posts (often valuable — like the counter-thesis one engineer left about tailscale). Replying on your OWN posts is a low-risk task, but Facebook still bans for PACE. So: read safely, write personally in the owner's voice, post one at a time with pauses, under a counter. **Main rules (from Deep Research #32):** - **Pace decides, not "bot vs human".** Every reply passes `fb_guard check reply`: ≤40/day, ≥5 min between replies, no back-to-back series. The guard physically will not let you overshoot. - **Every reply is personal and different** (top-tier model, the owner's voice). The same text sent to many people = a spam flag → a ban. - **Draft-first:** show the owner a batch of drafts, post only after a `+`. - **Account safety:** do NOT click "View more comments" on reshares — it navigates away. Read what already loaded under the original. --- ## 0. The fuse — status at the start ```bash python "$USERPROFILE/.claude/scripts/fb_guard.py" status ``` Shows how many replies went out today and whether we are paused. If `reply` is already at the daily limit — tell the owner and defer. ## 1. Browser + reading the commenters (no risky clicks) > Strictly LOCAL, a live tab, we never touch the login. Is the Chrome MCP connected? (`list_connected_browsers`). > ⛔ IP gate (owner, 07-16): Facebook commenting happens ONLY from the hub (a stable IP). On another machine do NOT reply — send