Magpie: expand scope to include outward social media management alongside inward data gathering #36

New issue

Open

opened 2026-04-21 09:07:58 -07:00 by pyr0ball · 1 comment

pyr0ball commented

2026-04-21 09:07:58 -07:00

Owner

Expanded Magpie brief

Inward (original): Job boards, eBay listings, pantry/barcode data, trust signals, community blocklist aggregation.

Outward (new): Reddit/Discord/social posting infrastructure, schedule management, engagement tracking, opportunity discovery.

What this replaces

claude-bridge/reddit-poster/ | the Playwright posting scripts and cron jobs move into Magpie as a managed subsystem
roadmap#35 (Reddit campaign dashboard) | absorbed into Magpie UI
Manual crontab management | replaced by Magpie schedule management

Sub/channel discovery: crawl a target topic, find communities, check rules automatically, score viability
Schedule management: per-campaign day/time/sub config, not raw crontab
Post + comment: current poster only supports new posts; Magpie needs to find existing threads (e.g. r/Flipping Sunday self-promo, r/cscareerquestions first-Sunday sticky) and post comments on them
Engagement tracking: pull post score, upvote ratio, comment count after posting; surface what is landing
Duplicate guard: per-sub post history so we never double-post
Content variants: per-sub framing (privacy angle for r/privacytoolsIO, Docker angle for r/linuxmasterrace, ND angle for r/AuDHD) generated or selected from a template bank
Dashboard UI: schedule view, per-post status (pending | posted | failed | removed), sub rules table, manual trigger

Architecture notes

Playwright posting layer already exists in claude-bridge/reddit-poster/ | migrate in, do not rewrite
Session management (xvfb-run, session.json) carries over as-is
FastAPI + Vue pattern (same as Peregrine/Kiwi/Snipe) for the dashboard
Internal only (MGPE tier) | no public-facing product, no license gating needed

Relation to other issues

Closes roadmap#35 (Reddit campaign dashboard) — that feature belongs here.

Magpie was originally scoped as an internal cross-product data gathering tool (job boards, eBay, pantry signals). That brief extends naturally to social media management, which is the same crawl-discover-act loop turned outward. ## Expanded Magpie brief **Inward (original):** Job boards, eBay listings, pantry/barcode data, trust signals, community blocklist aggregation. **Outward (new):** Reddit/Discord/social posting infrastructure, schedule management, engagement tracking, opportunity discovery. ## What this replaces - `claude-bridge/reddit-poster/` | the Playwright posting scripts and cron jobs move into Magpie as a managed subsystem - roadmap#35 (Reddit campaign dashboard) | absorbed into Magpie UI - Manual crontab management | replaced by Magpie schedule management ## Capabilities Magpie needs for social - **Sub/channel discovery:** crawl a target topic, find communities, check rules automatically, score viability - **Schedule management:** per-campaign day/time/sub config, not raw crontab - **Post + comment:** current poster only supports new posts; Magpie needs to find existing threads (e.g. r/Flipping Sunday self-promo, r/cscareerquestions first-Sunday sticky) and post comments on them - **Engagement tracking:** pull post score, upvote ratio, comment count after posting; surface what is landing - **Duplicate guard:** per-sub post history so we never double-post - **Content variants:** per-sub framing (privacy angle for r/privacytoolsIO, Docker angle for r/linuxmasterrace, ND angle for r/AuDHD) generated or selected from a template bank - **Dashboard UI:** schedule view, per-post status (pending | posted | failed | removed), sub rules table, manual trigger ## Architecture notes - Playwright posting layer already exists in `claude-bridge/reddit-poster/` | migrate in, do not rewrite - Session management (xvfb-run, session.json) carries over as-is - FastAPI + Vue pattern (same as Peregrine/Kiwi/Snipe) for the dashboard - Internal only (MGPE tier) | no public-facing product, no license gating needed ## Relation to other issues Closes roadmap#35 (Reddit campaign dashboard) — that feature belongs here.

pyr0ball commented

2026-04-21 10:30:19 -07:00

Author

Owner

Concrete example of the signal-extraction brief

https://www.reddit.com/r/selfhosted/comments/1srt89b/anyone_else_getting_tired_of_reexplaining_their/

This thread is a product post fishing for engagement (0.36 upvote ratio, community clocked it). Magpie should have flagged it anyway because the topic is live signal: r/selfhosted users are actively discussing persistent local AI context — exactly the cf-orch + product stack story.

What Magpie should do with a thread like this:

Flag: thread matches topic keywords (local AI, persistent context, self-hosted inference)
Classify: bait post vs genuine discussion (upvote ratio, account age, comment tone)
Extract: the underlying pain point from the comments, not the OP
Recommend: do not engage with this post; file the pain point framing for a future genuine post
Output: pain point summary + suggested framing angle for the content bank

Pain point extracted from this thread:
Self-hosters are re-explaining their system setup to AI every session. They want a persistent local assistant that knows their environment. Nobody in the comments mentioned a product that solves this cleanly. That is a gap cf-orch + Peregrine/Kiwi fills — local inference, persistent state, product-aware context. Worth a dedicated post framed around that pain point rather than as a product announcement.

## Concrete example of the signal-extraction brief https://www.reddit.com/r/selfhosted/comments/1srt89b/anyone_else_getting_tired_of_reexplaining_their/ This thread is a product post fishing for engagement (0.36 upvote ratio, community clocked it). Magpie should have flagged it anyway because the *topic* is live signal: r/selfhosted users are actively discussing persistent local AI context — exactly the cf-orch + product stack story. **What Magpie should do with a thread like this:** - Flag: thread matches topic keywords (local AI, persistent context, self-hosted inference) - Classify: bait post vs genuine discussion (upvote ratio, account age, comment tone) - Extract: the underlying pain point from the comments, not the OP - Recommend: do not engage with this post; file the pain point framing for a future genuine post - Output: pain point summary + suggested framing angle for the content bank **Pain point extracted from this thread:** Self-hosters are re-explaining their system setup to AI every session. They want a persistent local assistant that knows their environment. Nobody in the comments mentioned a product that solves this cleanly. That is a gap cf-orch + Peregrine/Kiwi fills — local inference, persistent state, product-aware context. Worth a dedicated post framed around that pain point rather than as a product announcement.