Thank you, as always, for the important info. But this is a problem, as the new check system isn't as quick to judge as the old one (a complete review can take days), and I often realized very late that a site of mine had been excluded from the official listing, or had been totally blocked.

However, based on the info you provide, it should be possible to check if the site is on the listing, and if it's not (for whatever reason, including automatic check, manual ban list and ban word list) the switch should reflect that. If checking the official listing it too heavy on the server, maybe creating a JSON or XML snapshot updated every few hours would be better than nothing anyway.

Third's charm? Let's cross fingers. I love the Perchance universe, I truly do, but this way-too-strict check system, coupled with the lack of feedback, is starting to drain my energies and my passion...

EDIT - 3rd UPDATE (03 nov 2026)

Since the NSFW warning is still in place, on 03/11/2026 the entire site was subjected to a meticulous, almost obsessive review aimed at finding and eliminating every single element that could trip an automated "Mature content" check. The audit covered the whole shipped codebase (page chrome, mature gate, exit gate, SEO block, Hunk static notice including its IT/ES/FR/DE translations, badge, footer, owner dialog), the full corpus (both stories, word by word), all metadata ($meta, tags, manifests, blurbs), and every image — each cover and each in-story illustration was viewed individually. No nudity, no genitalia, no sexual acts depicted anywhere: the only bare skin shown is male chests, arms and faces, which is standard PG-13 imagery.

Changes applied on 03/11/2026

1. Full review of all stories, removing anything that could even vaguely fall outside PG-13 limits: the historical offence is now named with the period-appropriate legal term ("the offence of sodomy"); an anatomical reference became an abstraction ("trousers that highlighted their virility"); arousal vocabulary was neutralized ("barely able to restrain himself after such prolonged abstinence"); the bedroom scenes were softened ("take off his underwear", "make love on my first date").
2. A second gate on top of the entry gate. The entry gate already declares the site's PG-13 content; a further exit gate was added so that every link to an external NSFW site now requires explicit consent (a checkbox) plus an adult-age declaration before redirecting. Its wording was carefully drawn: parental guidance admits readers to this PG-13 site, but never to the adult-only external sites ("Continue only if you are an adult" — no exceptions).
3. Source hygiene. The developer documentation (README) and all other files shipped with the site were scrubbed of adult-vocabulary tokens, so that even a scanner reading the raw sources finds nothing — except the two intentional user-facing adult-content declarations (the "More stories at main site (18+)" card and the Butch's Tales blurb). They exist solely to warn the reader about what awaits on the external adult sites, and every one of those links sits behind the exit gate.

What PG-13 means on this site (again)

The PG-13 classification applied here follows one clear, defensible line: it forbids explicit descriptions of sexual acts and of intimate anatomical parts, but it allows descriptions of kisses and of non-intimate body parts — chest, muscles, facial and body hair. A young reader without prior knowledge of sexual acts perceives only passion in these pages, never mechanics: nowhere is it described how passion is turned into acts. Vague expressions that can only be understood by a reader who already knows the acts in question remain obscure to the inexperienced reader — who can ask a parent what they mean. That parental guidance is precisely what the "PG" in PG-13 assumes for this site — while the external adult sites remain strictly adults-only, as the exit gate now states without exception.

For the life of me, I can't really understand why someone should downvote such a useful post... 🙄 It seems like there are "serial downvoters" lurking around; whatever their reasons, they harm the entire community.

I've now edited my main post to include a thorough and detailed report exlaining why the site is PG-13 and what elements may trigger false NSFW alerts. Please someone review it.

It happens to me, too. I think it may be by design, to let the AI start answering sooner, at the risk of having to remove an incomplete answer and replace it with a more complete one.

Thanks, that's good advice, I'll try it!

EDIT to add: I've done as you suggested, and then I've renamed the URLs of the two copies so that the new fork got the URL of the older (flagged) one; so far, no NSFW content warning has been issued on the fork (the warning persists on the older site, despite the URL change). Let's cross fingers. Thank you again for the suggestion!

P.S.: if someone doesn't agree, for any reason, with what I just wrote, they might reply here and then downvote the post... 🙄

The easiest way is to go to edit mode and add a few comment lines ( = lines starting with // ) to the main list page; here is some of my own preferences (change it at will):

// === USER PREFERENCES (apply to every session) ===

// - The following preferences (including this one) should be placed in a dedicated User Preferences section in src/README.md; the source of truth of the User Preference is the main.pjs of this generator, that can be modified by the user only. The source of truth must be checked for changes whenever the User Preferences are read from the README.md file.

// - If the request is ambiguous, or two or more ways of doing it come to mind — especially if one departs from the last decision or touches something worth keeping — stop and ask before acting, sketching the alternatives in one or two lines and letting the user choose: never settle a doubt on his behalf.

// - Don't speculate on the user's intentions or unspoken desires: ask them to clarify.

// - If you're running in circles and something seem illogical, ask the user, as he has some basic knowledge about coding and how the Perchance infrastructure works.

// - Before making any code changes, explain the changes you intend to make and wait for the user's consent.

// - If you identify errors on code you did NOT change yourself, or pre-existing errors, ask the user to perform a hard refresh (F5) BEFORE investigating the error (a harness-side false positive may disappear after an F5).

// (add your own preferences)

When done, you issue --only for the first time-- an order like "Read the User Preferences from main.pjs". The AI agent will create a README.md file in src/ with your preferences. From now on, every time you think the AI agent is not following your Preferences, you just tell him: "Read README", and he will read again your preferences, checking if in the meantime you have added/modified the comment lines in the main list editor.

I gave similar instructions to my AI agent, to ask me if it got confused; I've written this info in the README.md file in src, and I ask the agent to read it now and then, when I feel he's forgotten, or when I start a fresh new chat.

When I've read that the problem was fixed, I tried again and still couldn't save; the error message was different, though: something like "The perchance server has timed out. Your generator was NOT saved". I checked what was wrong and realized that my browser was sending a whole lot of data (apparently, the entire generator) to cloudflareinsights.com.
This huge upload was using up my entire upload bandwidth, so the generator couldn't be sent to the Perchance server.

I blocked the scripts related to cloudflare (using NoScript), the bandwidth immediately freed up, and the save started working again.

Same here. Last save on Sep 28 at 20:39 UTC, then I began getting errors or endless "saving". It's comforting knowing that it's a general problem and not something bad into my code/src files, because I'm sure the devs will fix it sooner or later.

For anyone remotely interested: PROBLEM SOLVED.
To fool the stupid nsfw filter, I've applied a stupid trick: a simple diagonal texture superimposed to the image; it's barely visible and adds a touch of "artsy" to the image. And while I was there, I created a vector text to replace the "totally not genAI" 😂 previous one.
The Content Warning has gone (for the PG-13 site: the other two are definitely NSFW, and not for the $meta.image... 😅)
Final results for nsfw / pg13 / stories sites: