返回资讯中心
外部精选
软件工程
#开发者实时流

Afterfeed: A tool to view all your social media backups

✨ Your social history, back in your hands.

Hacker News 最新RebeccaTheDev2026/10/24 · 13 天前21 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

✨ Your social history, back in your hands.

A private, local-first home for browsing, searching, and rediscovering

your personal social media archives—without depending on the platforms that created them.

Features · Platforms · Quick start · Import guide · Product tour · API & MCP

Afterfeed turns disconnected export files into one calm, searchable timeline. Your archive and media stay in the installation you control, original metadata is retained, and private annotations never modify the source records. Authentication and per-user ownership keep libraries isolated when an installation has more than one user.

🗂️ Browse everything together — normalize posts, replies, messages, and media from multiple services into a single timeline.

🔎 Find old moments — use full-text search, reconstructed threads, yearly heatmaps, statistics, maps, and a cross-service On This Day view.

🏷️ Curate privately — favorite, tag, annotate, collect, or hide posts without changing the imported archive.

🧭 Understand your history — explore activity patterns and a local relationship index built from conversations, follows, friends, mentions, and reactions.

🎁 Share selectively — turn one memory into a social-ready image, or export a collection as HTML, PDF, JSON, or a media bundle with granular privacy controls and metadata stripping.

🔌 Connect your tools — query your own archive through a user-scoped, read-only JSON API or the bundled Model Context Protocol server.

📦 Supported archives

Service Preserved content

Twitter / X Posts and deleted posts, media, likes, profiles and profile history, follows, lists, saved searches, timezone, and verification status

Mastodon Posts, replies, boosts, content warnings, visibility, engagement, favorites, bookmarks, profile fields, aliases, and media

Facebook Posts, check-ins, photos, videos, comments, reactions, friends, saved items, profile history, and media

Reddit Submissions, comments and reply relationships, votes, saved and hidden items, communities, moderation, multireddits, and messages

Instagram Posts, videos, comments, media, profile details, likes, saved posts, follows, and direct messages

Google+ Posts, reshares, authored and embedded comments, +1s, external link previews, visibility, check-in locations, profile identity, and post media from Google Takeout

Nextdoor Posts, comments, reactions, private messages, For Sale & Free listings, seasonal activity, and privacy-filtered profile details

LiveJournal Journal subjects, HTML and readable text, tags, userpics, item IDs, dates, and original entry links

Jekyll Published Markdown posts, YAML front matter, tags, categories, original permalinks, author identity, profile image, and referenced local media

Sensitive security and account data—such as IP history, device tokens, phone numbers, cryptographic keys, payment records, birth dates, and advertising preferences—is intentionally excluded where present.

Requirements

PHP 8.4.1 or later

Composer

Node.js and npm

SQLite (default), MySQL/MariaDB, or PostgreSQL

Install

git clone https://github.com/rebeccathedev/afterfeed.git cd afterfeed composer run setup composer run dev

Then open the local URL shown in your terminal and create the first account. SQLite works out of the box; see database backend setup to use MySQL/MariaDB or PostgreSQL with native full-text search. The first account adopts data from an older single-user database during an upgrade.

Requirements: Docker Engine with the Compose plugin and access to the repository's GitHub Container Registry package. The application image contains PHP-FPM only; the included production Compose file adds Nginx and persistent volumes for SQLite, archived media, and compiled public assets.

git clone https://github.com/rebeccathedev/afterfeed.git cd afterfeed

export AFTERFEED_IMAGE=ghcr.io/rebeccathedev/afterfeed:latest docker pull "$AFTERFEED_IMAGE" docker run --rm --entrypoint php "$AFTERFEED_IMAGE" artisan key:generate --show

Copy the generated key into a new .env.container file. Replace the image and URL values for your deployment:

AFTERFEED_IMAGE=ghcr.io/rebeccathedev/afterfeed:latest APP_KEY=base64:paste-the-generated-key-here APP_URL=http://localhost:8080 AFTERFEED_PORT=8080 AFTERFEED_MCP_ALLOWED_ORIGINS=http://localhost:8080

Start Afterfeed:

docker compose --env-file .env.container -f compose.production.yml up -d docker compose --env-file .env.container -f compose.production.yml ps

Open http://localhost:8080 and create the first account. Keep .env.container private and backed up: changing APP_KEY invalidates sessions and encrypted application data. The entrypoint creates SQLite, applies migrations, refreshes public assets, and warms Laravel caches before FPM starts.

docker compose --env-file .env.container -f compose.production.yml pull docker compose --env-file .env.container -f compose.production.yml up -d

For HTTPS, external databases, backups, a custom FastCGI proxy, and troubleshooting, see container deployment.

Afterfeed automatically recognizes supported Twitter/X, Mastodon, Facebook, Reddit, Instagram, Google+, Nextdoor, LiveJournal, and Jekyll archive formats. Browser uploads are attached to the signed-in user. For a command-line import:

php artisan archive:import /path/to/twitter-export.zip me@rebeccapeck.org

Imports are safe to repeat. A content fingerprint prevents accidental duplicate imports, while re-importing an existing archive refreshes its normalized records through the latest importer so newly supported metadata can be backfilled.

The import guide documents format recognition, ownership, privacy, and the Google+ Takeout layout and coverage in detail.

Archive imports refresh the People index automatically. To rebuild it manually:

php artisan archive:people me@rebeccapeck.org

🎁 Export with control

Collections can become a self-contained HTML album, a PDF memory book, a JSON subset, or a ZIP containing HTML, JSON, and selected media. Choose whether to include text, media, identities, dates, private annotations, original links, and precise locations.

Privacy-friendly defaults remove image EXIF, remux video losslessly with FFmpeg to strip metadata, and omit raw platform metadata. Self-contained HTML and PDF media is capped at 60 MB, and PDF books at 250 posts; use ZIP for larger collections.

Individual posts can also become square, portrait, or landscape PNG cards. Identity, platform, date, footer, and archived photo controls make it easy to share an old memory without exposing or linking to Afterfeed.

Afterfeed includes a read-only JSON API under /api/v1:

GET /api/v1/status GET /api/v1/accounts GET /api/v1/posts?q=&account_id=&platform=&year=&month=&has_media=&page=&per_page= GET /api/v1/posts/{id} GET /api/v1/statistics

Results use bounded pagination of at most 100 records per page and omit hidden posts. Every request requires a per-user bearer token created in Settings → API & MCP access, and the API exposes only that user's archive.

To connect a local MCP client such as Claude Desktop or Codex, configure it to launch:

php /absolute/path/to/afterfeed/artisan afterfeed:mcp me@rebeccapeck.org

The stdio server provides search_posts, get_post, list_accounts, and archive_statistics. Remote clients can use the authenticated Streamable HTTP endpoint at /api/mcp; see remote MCP setup and security. Each token is revocable and can access only its owner's archive.

Every platform importer translates its export into four shared records:

SocialAccount ──< Archive ──< Post ──< Attachment identity import item local media

SocialAccount represents one identity on a platform.

Archive represents one export and its source account.

Post represents a normalized post, reply, message, or timeline item.

Attachment represents local media associated with a post.

Original export metadata remains in JSON columns, keeping normalization lossless. Large Facebook exports use chunked database upserts and streamed ZIP media reads, avoiding full extraction and unbounded memory use.

Start the application, queue worker, logs, and Vite

composer run dev

Run the test suite

composer test

Build production assets

npm run build

🌱 Built for the version of your internet history that belongs to you.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →