@gurupanguji

Social Automation: Meta & Pixelfed Integration Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Complete the social media automation suite by adding Threads, Instagram, and Pixelfed integration to the existing publish_social.py engine.

Architecture: Extend the current modular Python script. For Meta platforms (Threads/Instagram), utilize the official Graph API which requires two-step container publishing and publicly accessible media URLs. For Pixelfed, leverage the ActivityPub/Mastodon-compatible API. Maintain existing image optimization and error-handling patterns.

Tech Stack: Python 3.x, requests, Pillow, Mastodon.py, GitHub Actions, GitHub Secrets.

---

File Map

Modify

• scripts/publish_social.py Responsibility: Add publish_threads, publish_instagram, and publish_pixelfed functions. Update the main execution loop.
• .github/workflows/publish_social.yml Responsibility: Map new secrets for Threads, Instagram, and Pixelfed to environment variables.
• AGENTS.md Responsibility: Update supported platforms documentation.
• README.md Responsibility: Update key features list.

Implementation Tasks

Task 1: Threads Integration (Phase 4)

Files:

• Modify: scripts/publish_social.py, .github/workflows/publish_social.yml

• Test: manual dry-run and workflow_dispatch

• Step 1: Implement publish_threads in scripts/publish_social.py
  • Use graph.threads.net/v1.0.
  • Step 1: Create media/text container (POST /{id}/threads).
  • Step 2: Handle media URL by prepending https://gurupanguji.com to local paths.
  • Step 3: Publish container (POST /{id}/threads_publish) after a 10s safety delay for media processing.
• Step 2: Update .github/workflows/publish_social.yml for Threads
  • Add THREADS_ACCESS_TOKEN and THREADS_USER_ID to env.
• Step 3: Verification
  • Run python3 scripts/publish_social.py --date 2026-03-15 --dry-run to verify parsing.
  • Push to a feature branch and trigger workflow_dispatch to verify production posting.

Task 2: Instagram Integration (Phase 6)

Files:

• Modify: scripts/publish_social.py, .github/workflows/publish_social.yml

• Test: manual dry-run and workflow_dispatch

• Step 1: Implement publish_instagram in scripts/publish_social.py
  • Use graph.facebook.com/v19.0 (or latest).
  • Instagram requires media. Use the resolved hero_image (local or fallback).
  • Step 1: Create media container (POST /{id}/media) with image_url and caption.
  • Step 2: Publish media (POST /{id}/media_publish).
• Step 2: Update .github/workflows/publish_social.yml for Instagram
  • Add INSTAGRAM_ACCESS_TOKEN and INSTAGRAM_ACCOUNT_ID to env.
• Step 3: Verification
  • Dry-run and manual workflow trigger.

Task 3: Pixelfed Integration (Phase 7) - PARKED

Files:

• Modify: scripts/publish_social.py, .github/workflows/publish_social.yml

• Test: manual dry-run and workflow_dispatch

• Step 1: Implement publish_pixelfed in scripts/publish_social.py
  • Reuse Mastodon.py logic but pointed at the Pixelfed base URL.
  • Use the “Pixelfed” specific snippet from the markdown.
  • Note: Commented out in main() loop due to instance setup issues.
• Step 2: Update .github/workflows/publish_social.yml for Pixelfed
  • Add PIXELFED_ACCESS_TOKEN and PIXELFED_API_BASE_URL to env.
• Step 3: Verification
  • Dry-run and manual workflow trigger.

Task 4: Documentation & Cleanup

Files:

• Modify: README.md, AGENTS.md

• Delete: scripts/find_linkedin_urn.js

• Step 1: Update README.md and AGENTS.md
  • List all 7 platforms as fully supported.
• Step 2: Remove temporary scripts
  • Delete scripts/find_linkedin_urn.js.
• Step 3: Final PR & Merge
  • Create final PR for the Meta/Pixelfed branch.
  • Merge into main after verification.

---

Plan Review

Local review outcome

Status: Approved

Notes:

• Follows the established incremental implementation pattern.
• Reuses existing image optimization logic.
• Addresses the Meta public URL requirement by assuming deployment state.