fb-reply

/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

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 the task to the hub as text. Canon: ip-sensitive-actions-hub-only.

1. Open the owner's post (he gives the link, or go to facebook.com/<profile> → his latest posts). ⛔ PITFALL 2026-07-28: the profile wall does NOT hand out permalinks. Scrolling the profile yields zero pfbid links (Facebook populates href only on hover), and the feed is virtualized — a JS scroll outruns lazy loading and the posts stay skeletons. The working entrance = the notifications feed facebook.com/notifications: every row "X commented on your post" already carries a ready /posts/pfbid… and tells you WHO wrote and WHEN. One pass over it replaces the whole wall scroll. The Graph-API path (fb_posts_poll.py) is dead for now — there is no FB_USER_TOKEN. ⚠️ An open Messenger window pollutes the results: its div[role="article"] elements are DM messages, not comments. Close the chat window before collecting.
2. Extract the commenters INSIDE THE PAGE ITSELF (Facebook hides names/links across the MCP boundary → match and filter inside the page, and hand out only safe text). Through mcp__Claude_in_Chrome__javascript_tool:

   const out = [];
   const seen = new Set();
   document.querySelectorAll('div[role="article"][aria-label]').forEach(a => {
     const al = a.getAttribute('aria-label') || '';
     if (!/^Comment by|^Reply by/i.test(al)) return;                     // comments only
     const blocks = [...a.querySelectorAll('div[dir="auto"]')]
       .map(d => (d.innerText || '').trim()).filter(Boolean);
     const text = (blocks.sort((x, y) => y.length - x.length)[0] || '').slice(0, 500);
     if (!text || seen.has(text)) return;
     seen.add(text);
     const link = a.querySelector('a[role="link"][href]');               // the author's profile
     const handle = link ? (new URL(link.href).pathname.replace(/\//g,'')) : '';
     const hasImg = !!a.querySelector('img[src*="scontent"],img[src*="fbcdn"]');
     out.push({ handle, text, hasImg });                                  // handle = username, not a display name
   });
   out;
   

   You get back a list of {handle, text, hasImg} — no hidden strings, safe to display. (If Facebook runs in another language, add that locale's aria-label prefixes to the regex.)
3. Virtualization: if there are few comments, gently scroll the comments area (computer scroll down the page, WITHOUT clicking expander buttons) and repeat §1.2. On a RESHARED post do NOT press "View more".
4. ⚠️ MANDATORY: expand collapsed threads BEFORE choosing "who to reply to" (lesson 2026-07-05): Facebook hides existing replies under "View N replies" — the owner has often ALREADY replied himself, and from the outside you cannot see it (a duplicate = embarrassment + a spam signal). On YOUR OWN post the inline thread expanders are safe (not to be confused with "View more comments" on reshares). Through JS: click every toggle matching /View (\d+ )?repl/i, wait ~3s, then collect aria-label^="Reply by <owner's name> to <Name>" → the list of ALREADY answered people; reply only to those not on it. In the 2026-07-05 run this filtered out 7 of 8 "candidates".