Platform blocks — Instagram image posts and Substack phantom listings (June 2026)

Cross-platform friction on author-owned publishing after a public 9/11 / controlled-opposition thread — opaque errors, no contestable notice

TL;DR: June 2026 — Instagram refuses new image posts on every account tested (PC and phone); error modal: Something went wrong. Please try again. Substack returns Page not found when the author opens own post URLs (including the edit flow) on paradigmthreat2, while Latest still lists titles (The Hidden History of Words, Royal Rife). Editing is a minor inconvenience; the stronger read is phantom listing — feed chrome that looks published while the article may not resolve for anyone. No written policy notice or appeal path. Author read (L3): timing rhymes with a 9/11 CO thread — not proved coordination. Mitigation: paradigmthreat.net as canonical; verify Substack URLs from a logged-out / third-party browser.

What broke (documented)

Instagram — image upload / post fails with a generic error modal on every account tested (PC browser and mobile device). Message: Something went wrong. Please try again. No written policy notice or appeal path.

Substack — Page not found when the author opens own post URLs on paradigmthreat2 (including paths used for edit); the public Latest feed still lists the same titles (The Hidden History of Words, Royal Rife, etc.). Documented: 404-style failure on post resolution from the owner account. Author read (L3): the list may be UI residue — titles visible in Latest while the article body does not load for anybody, a shadow-delist that preserves the appearance of a live publication without delivering readers. Not yet externally verified in this file (no third-party load test logged); treat as working hypothesis until a logged-out or subscriber confirmation pass is recorded.

Why edit is not the point: losing the editor barely matters when the repo and paradigmthreat.net hold canonical text. What matters is whether Substack URLs still serve content to subscribers and strangers — or only show ghost rows in the author’s feed.

Not claimed: proof that Meta or Substack received a government order, that a specific report was filed, or the identity of the thread opponent. Claimed: reproducible owner-side failures without explanation during the same window as high-signal 9/11 CO public debate.

Screenshots (June 2026)

Instagram — image post blocked

Instagram — Something went wrong when posting images (June 2026)

Modal text (visible): Something went wrong — Something went wrong. Please try again. with Try again button. Occurred when attempting to post new images; tested across multiple accounts and both PC and device.

Substack — Page not found on own posts; Latest feed still lists titles

Substack — Page not found on post/edit while Latest feed still lists Paradigm Threat titles (June 2026)

Page not found when the author tries to open own articles (edit flow and post URLs). Latest still shows PARADIGM THREAT rows (The Hidden History of Words, Royal Rife, etc.). Author inference: the feed is not proof the posts are live — same 404 grammar on the author’s click path suggests phantom listing: subscribers and the public may also get nothing, while the publication looks active in the dashboard list.

Context — 9/11 controlled-opposition thread (author thesis, L3)

The same window included a public thread arguing AE911Truth / Richard Gage and adjacent lanes as controlled opposition — thermite-vs-DEW fracture, no-planes bypass as intentional movement strategy, Epstein–Commission proximity in 2026 releases. See Richard Gage / AE911Truth investigation and Not Like This for the project’s two-camp / CO frame.

Author inference: an interlocutor behaving as a 9/11 controlled-opposition agent (defend the safe demolition lane, poison no-planes and DEW hangout, keep debate inside thermite theater) may have triggered platform-side friction — report spam, shadow restrictions, or vendor trust-and-safety automation. Tier: interpretive only until either platform states a cause or the block lifts with documentation.

Cross-read: IC911A CO investigation; 09-11 investigation; GitHub ban — silence permits inference.

Practical response (this project)

Canonical site first — ship and revise on paradigmthreat.net (GitLab / relay remotes); assume Substack may be non-delivering until proven otherwise.
Screenshot archive — this file + images under influence/censorship/ for future blog / legal / audience record.
Retry discipline — Instagram Try again loop documented; do not assume user error when all accounts and both form factors fail the same way.
Substack verification — from a logged-out browser or a third party, try opening public Substack URLs for recent posts; record whether 404 reproduces outside the author session. Until then, do not treat Latest list presence as delivery.
Audience note — if phantom listing is confirmed, point readers to on-site mirrors linked from each article’s **Substack:** footer line.

What this file does not claim

Not proof Instagram or Substack acted on behalf of a specific intelligence agency or CO network.
Not that text-only posts on Instagram were tested the same week (this record is image-post failure).
Not that third-party Substack URL tests were logged in this file yet — phantom listing for all readers is author L3 until an external load test is recorded.
Not a substitute for formal appeal — log kept because opaque enforcement prevents contest without a stated rule.

Keywords: #Censorship #Instagram #Substack #PlatformBlock #ControlledOpposition #911 #AE911Truth #ParadigmThreat #June2026

Last updated: 2026-06-27T19:30:00-04:00