4
Mature-flag reviews should say what triggered — what got your flag lifted? (lemmy.world)
submitted 1 week ago by to c/perchance@lemmy.world
3 comments fedilink hide all child comments
 

Builder question + suggestion. My generator got flagged as mature. I then deleted the entire adult block — all porn domains, adult queries, uncensored link cards — and verified with a full-text search that zero matches remain in the shipped code (main.pjs, index.html, src/). Saved, re-requested review, still failed, with no detail on what the trigger is.

The generator in question, so anyone can check: https://perchance.org/zunzum?c=kkk-perchance — anonymous Orkut-nostalgia social network, no email. If you spot anything in it that could still be tripping the filter, I'd genuinely like to know.

Suggestion: the flag notice should work like a linter report and cite the trigger (file + matched pattern, e.g. "found 'pornhub.com' in src/search.js"). Right now creators fix what they guess, save, fail again, and learn nothing.

And a question for fellow builders: has anyone gotten a mature flag lifted? What was the trigger in your case and what fixed it?

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 3 points 1 week ago

Makes sense, and a "this is why" on the flag would genuinely help.

Just to be clear on my side: the focus here is socializing — it's a community/chat hangout — and the mature flag gives the wrong impression about what the site is. I'm not trying to gut the site to chase the flag off; that would defeat the purpose. But I do think it's important to understand what triggers flags, because right now it's a black box.

Honestly, on the 29th I got hit with a privacy policy strike, and then out of nowhere it was removed again by the bot/person — and I hadn't changed anything. So I have no idea what I did wrong or right. That's the frustrating part: without knowing the trigger, I can't fix anything even if I wanted to.

  • permalink
  • fedilink
  • source
  • parent