ergosteur/instaarchive-viewer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: warn at the top of the README that this branch stays off GitHub

Browse Source 
This branch is the only place the fetching tooling still exists, and it names
the fetch host's public IP, the cookie's browser profile, the NAS path and the
accounts being archived. main's history was rewritten, the GitHub repo deleted
and recreated, and 22 ghcr images pruned to get that material out of public
view — one push of this branch undoes all of it.

Deliberately at the top of the README rather than in a separate file: gitea
renders README.md on the branch page, which is where someone actually looks
before pushing. That does diverge from main, but only by an addition, which a
merge cannot silently drop — unlike the CLAUDE.md/package.json case, where
main was DELETING lines this branch kept and every merge re-applied the
deletion. Worst case here is a trivial conflict if main edits the same region,
and the block says to keep both.

Also records that the pre-push hook is local and unversioned, since a fresh
clone is the realistic way this goes wrong.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UXfdJu7QhSJLr47K7koTDF
This commit is contained in:
ergosteur
2026-08-20 16:33:49 -04:00
co-authored by Claude Opus 5
parent 84c573b3ed
commit a54249e79d
1 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+32
View File
@@ -1,5 +1,37 @@
# InstaArchive Viewer
> [!CAUTION]
> ## This branch must not be published to GitHub
>
> You are on **`tooling`**. It is the only branch that still contains the
> archive-fetching scripts and their docs, and those name things `main` was
> rewritten to remove:
>
> - the fetch host's **public IP** (`docs/gallery-dl.md`)
> - the browser profile the session cookie is read from
> - the NAS archive path
> - the **list of Instagram accounts being archived**
>
> On 2026-08-20 `main`'s entire history was rewritten with `git filter-repo`,
> the GitHub repo was deleted and recreated, and 22 container images were
> pruned from ghcr — all to remove exactly this material from public view.
> **One push of this branch to GitHub undoes all of it**, and the second
> cleanup would be harder than the first: force-push residue stayed reachable
> by SHA until the repo itself was deleted.
>
> Guards in place, neither of them foolproof:
>
> - `.git/hooks/pre-push` rejects any ref but `main`/tags to the GitHub remote.
> It is **local and unversioned** — a fresh clone does not have it.
> - `git config remote.github.push refs/heads/main:refs/heads/main`.
>
> Recreate both after cloning. `origin` is gitea and is the right default for
> everything; GitHub only ever needs `main` and the current release tag.
>
> *This block exists only on `tooling`. If a merge from `main` ever conflicts
> here, keep both sides — the warning is not something `main` deleted.*
A high-performance React PWA for browsing archived Instagram data with a native-feeling interface. Supports both official Instagram exports and Instaloader archives.
## Features