feat: grow new accounts by commenting on active threads
A new Reddit account cannot start chats until Reddit considers it established, and nothing in the app previously did anything about that. Account growth posts a small number of AI-written comments per day on active threads in an operator-chosen list of communities, per account, so the history that lifts the hold actually accumulates. Growth is account-scoped rather than part of the shared outreach funnel: karma, comment history and pacing all belong to one identity. It runs as the lowest-priority work in the account runtime, after inbound replies, and deliberately keeps running while an account is held out of outbound messaging. Comments publish without operator review, so the guards are the feature: - Both screening stages fail closed. A deterministic gate rejects links, contact solicitation, user tags, filler and any text that reveals the generator; the classifier must actively approve with confidence, and an outage stalls growth rather than publishing unreviewed text. - Thread text reaches the model only as fenced untrusted data, since Reddit posts do contain instructions aimed at automated readers. - The daily allowance is adaptive, not configured: it starts at two per day and rises only while comments survive and earn upvotes. - Posted comments are swept at ~15m/2h/24h with one batched info.json request, plus a single signed-out probe that detects a comment the public cannot see. Two consecutive removals, an invisible comment, or a captcha challenge pauses the account until an operator clears it. A failed probe never pauses anything. - One comment per thread across every owned account, enforced by a unique index, because two of our accounts on one post is the easiest pattern to correlate. - A comment interrupted mid-post is abandoned, never retried: we cannot know whether the write landed and a duplicate cannot be withdrawn. - Reddit's refusals are authoritative — a ban disables that community for that account, a throttle backs off at the scope Reddit named, and a signed-out response invalidates the session. Comments are submitted through the account's own browser session against the old.reddit form endpoint, which returns machine-readable error codes and needs no credentials beyond the cookies already imported. API-first: /api/growth exposes state, settings, the community list and pause/resume, all verified against a local instance. Route responses are parsed with the shared contracts in tests so the server-side mirror cannot drift from what the dashboard expects. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
14d92e14ee
commit
1ac6ad22ad
46 files changed
+7500
-5
No files matched your search
@@ -66,6 +66,7 @@ SIGINT/SIGTERM abort shared loops, stop account runtimes, stop the web server, c
|
||||
- verified Reddit and Matrix identity;
|
||||
- persistent Playwright browser profile;
|
||||
- posts, messages, outcomes, activity, outbox, and conversation state repositories;
|
||||
- growth settings, community list, comment history, and adaptive comment allowance;
|
||||
- Matrix chat cache and sync cursor;
|
||||
- media index and files;
|
||||
- rate limiter and invitation cooldown;
|
||||
@@ -135,6 +136,7 @@ docs/ Maintainer and agent documentation
|
||||
- New persisted state: add an append-only migration, expose it through a small repository, and test fresh plus upgraded databases.
|
||||
- Shared operator media: keep it under `MediaLibraryService`/`MediaLibraryRepository`; never merge it with account-owned received media.
|
||||
- New account behavior: place it in the account runtime or a service injected into it; do not add mutable cross-account identity to a singleton.
|
||||
- New account-growth behavior: keep it account-scoped and lowest-priority, fail closed before anything is published, and make every outcome visible in the growth audit trail.
|
||||
- New candidate stage: make transitions durable and idempotent, expose counts/reasons, and define lease/retry behavior.
|
||||
- New dashboard feature: add a feature slice and route, use shared schemas and query keys, and treat HTTP as authoritative.
|
||||
|
||||
|
||||
Reference in new issue
Block a user