ListeningKitListening to local Facebook groups
The same accounts can join the local groups in their town and hear when someone asks for what the business sells ("anyone know someone who can take away an old sofa?"). This page shows the parts.
How it runs
An account asks to join a neighbourhood group in its town. Once in, each poll brings back the group's newest posts as a step in the account's open browser, nothing clicked and no comments opened. A read by hand (read group) can add their comments; without --live, on a numeric group id, it runs on the direct-API engine (fbk) first when the account has a saved session, and falls back to the open browser. What each part must do is in the spec, Facebook groups.
The commands
| Step | Command | MCP tool | What decides it |
|---|---|---|---|
| Join | log facebook join group --account <a> --group <url or id> [--live] | join, joinLive | the group's own join state |
| Read | log facebook read group --account <a> --group <id> | readGroup | the feed's answer; the direct API first, the browser behind it |
| Poll | log facebook poll <group> <account> <how long> | poll | each read's answer; OpenMagpie's watch picks the matches |
| Members | log facebook read members --account <a> --group <g> --count 40 --owners | readMembers | the members list's answers, about 10 more per scroll |
read members --owners keeps people whose bio says owner, founder, CEO or self-employed, or who run a page, saved under ~/.logCli/members/.
Next
- #40 acts on a match: a comment or a message from the same account.
Sources: docs/groupListening.md, docs/groupMembers.md, docs/commandNaming.md.