DSPSTNMTRX01

Had Claude Opus 4.8 Max Thinking have a look for what that's worth.. Results below:

BEST-EFFORT AI ANALYSIS — AI Chat won't load + gallery saves failing

DISCLAIMER Written by an AI (Claude) reasoning from the reported symptoms plus publicly documented info on how Perchance is built. This is NOT confirmed — the AI cannot see Perchance's entire source code or server logs. Treat it as educated hypotheses to help narrow things down, not as fact. No public report confirming a current incident was found at the time of writing.

SYMPTOMS (reported, affecting everyone)

• Most chat channels won't load.
• Images only very rarely save to galleries.
• Sending a message to a channel that does load sometimes returns a 403 error.
• No visible error pages otherwise.
• Plain image generation still appears to work.

WHAT THIS PROBABLY ISN'T

• Not a "your browser / clear your cache / VPN" problem. It's hitting everyone, so it's server-side.
• Not the usual Error 521 outage. A 521 means Perchance's servers are unreachable and you'd see a full Cloudflare error page. Here the servers are clearly up (some channels load, some uploads succeed) — they're just refusing most requests. A 403 means "request understood but access refused," not "server down."

THE KEY POINT — why chat AND gallery break together Both are WRITES to Perchance's own backend services, and both sit behind the same access-gating:

• AI chat is built on the comments-plugin backend (comments-plugin.perchance.org).
• Saving to a gallery uploads the image to Perchance's file-storage server (same system as the upload plugin / perchance.org/upload), which has its own upload limits. Plain image GENERATION uses a different backend (the AI model service), which is why it can still work while chat + saving don't. So the common failure point is the authorization/security layer in front of those write endpoints — something there is rejecting most requests with a 403.

MOST LIKELY CAUSES (ranked, speculative)

1. Cloudflare WAF / bot-protection rule (edge-level block). Most likely. Chat loading and message-sending happen as background requests from embedded iframes — exactly the "looks automated" shape bot-protection flags. A tightened or newly-deployed rule would silently block most of these (no error page, channels just don't load) while a few slip through, and block gallery uploads the same way.
2. Broken or half-deployed auth on Perchance's side (origin-level block). Writes likely need a session/security token. A rotated key, a buggy update, or a degraded auth service would make the server refuse writes (and token-requiring reads, so channels don't load). The "a few still work" pattern fits some servers running old code, or cached tokens.
3. Anti-spam / quota filter turned up too high. Perchance leans heavily on abuse-prevention (banned-word/user systems on chat, upload limits on storage). If a filter was tightened — e.g. reacting to a spam or scraping wave — real users get caught as false positives. A 403 (blocked) rather than a 429 (rate-limited) points to a "blocked" decision. (These overlap — #3 is basically #1 or #2 set too aggressively.)

HOW TO TELL WHICH (optional, technical) Check the response headers of a failing request. A 403 with a "cf-ray" header and "server: cloudflare" → Cloudflare/edge (cause 1). A bare 403 from Perchance with no cf-ray → origin/auth (cause 2). On a phone this is fiddly (Kiwi Browser has dev tools, or remote-debug Chrome from a PC). Only worth it if you want to hand the devs a precise report.

WHAT WE CAN DO

• This is on Perchance's side; it can't be fixed from our end. It'll persist until a rule/auth/storage path is corrected, or it recovers on its own.
• Report it (forum + Lemmy). A good report: "platform-wide; no error page; 403 when sending chat messages and when saving to gallery; generation still works." If you can grab the response headers (cf-ray present or not), include that — it tells the devs edge vs. origin immediately.
• Interim workaround for saving images: since it's the save/upload path that's broken, generation likely still works — so save generated images directly to your device (long-press / right-click → Save) instead of relying on Save-to-gallery until it's fixed.

— Generated by Claude (Anthropic) as best-effort reasoning. Correct me if you have logs or header details that point elsewhere.

I'll add that the issue seems to be with all text to image generators galleries. All I've tried anyway.

And it still persists.

When is the last anyone heard from the Dev?