4
Mature-flag reviews should say what triggered — what got your flag lifted? (lemmy.world)
submitted 6 days 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?

all 3 comments

sorted by: hot top controversial new old
[–] 3 points 6 days ago* (last edited 6 days ago) (1 child)

I agree a 'this is why' would be nice when your generator is tagged as mature, but on the same note - if the generator is or could create mature content, why put effort into having the flag removed if the cost is stripping out features? If you would prefer to make the changes and your intended audience is in fact only PG-13 or whatever the threshold is, then working to resolve the issues may be worthwhile - but if it is or could be used with mature content, then that is what it is, no reason to change it, but then it is also prudent to have the mature content gate and not a punishment.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 3 points 6 days 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
    • [–] 2 points 4 days ago* (last edited 4 days ago)

    true, always getting punished with no way knowing why, ngl tho i just asked the helper to analyze and the previous one used some sus words lol

  • permalink
  • fedilink
  • source
    •