docs: scraping account replaced by erg05teur on 2026-10-14; warm-up rules apply

2026-10-14 21:34:14 -04:00
parent 5c3307685a
commit 99719d164b
2 changed files with 30 additions and 0 deletions
@@ -131,6 +131,16 @@ scraped profiles, plus 8 single-post live metadata fetches, paced):
  *outside* the Resilio-synced, viewer-scanned `archives/` tree; and the
  request budget (suggested: ≤40 posts/day, behind the preflight).
 **Account swapped (same day).** The scraping account is now `erg05teur`
 (also signed in on the owner's phone). It is a fresh account, so the
 "replacement account" rules in `docs/gallery-dl.md` apply — and were not fully
 followed on day one: the resolution check and an unplanned catch-up run (below)
 spent roughly 90 requests within hours of the login. The owner chose to leave the
 scheduled timers as they are rather than pause them; the preflight (exit 76) and
 the all-empty-stories streak (exit 77) are the safety net. Worth watching: the
 weekly profiles timer's first fire (~2026-10-23) is a much larger spend than the
 daily stories runs.
 **Host brought in line with the repo (same day).** Every tracked script and unit
 on `mattellite` is now byte-identical to `scripts/`, including the weekly
 profiles timer (it had been left monthly since 08-22). Installing it fired an
@@ -16,6 +16,23 @@ by hand.
 ## The account was suspended on 2026-08-17 — read this first
 > [!NOTE]
 > **The scraping account was replaced on 2026-10-14.** It is now **`erg05teur`**,
 > which is also signed in on the owner's phone (a separate session; the cookie
 > gdl uses lives only in the dedicated Chrome on `mattellite`). Everything below
 > about the suspension is the **previous** account's history and the reasons for
 > every rule; none of it has stopped applying, and the new account has no track
 > record, so treat it as a replacement account (see "For a replacement account"
 > below). The new session cookie was created 2026-10-14 ~10:07 EDT.
 >
 > What this account has been asked since then, honestly counted, because the
 > warm-up advice below was not followed to the letter: ~13 single-post / format
 > probes (resolution check, 2026-10-14), plus ~80 listing requests from an
 > **unplanned** reels catch-up run (installing the weekly profiles timer
 > triggered it via `Persistent=true`; stopped partway, `heejin / reels`
 > completed, `kimxxlip / reels` was abandoned ~7 min in). Scheduled runs were
 > deliberately left on their normal timers by the owner.
 The account used for all of the below was suspended the same day this tooling
 was built, for "activity that doesn't follow our Community Standards on spam".
 The fetching was not the expensive part. **Verification was.**
@@ -79,6 +96,9 @@ complaining, the rate-limited one has been unhappy for a while.
 ### For a replacement account
 (Applies to `erg05teur`, 2026-10-14 onward — see the note at the top of this
 section for what it has already been asked.)
 - Let it exist and be used normally for a while before pointing any tool at it.
 - Keep the cookie on one machine and one public IP, as before.
 - Start with a single small profile and stop for the day afterwards.