Hi, sorry about this, the moderation flags currently don't give any specific info to explain what caused it, so I understand the confusion. For your specific case, it may be a coding mistake by your AI if you used one to create it - try pasting the message below to the AI Helper:

The Privacy warning isn't about nicknames, scores, or public chat. Those are fine. It's about private messages. The DM panel says "Private", but two kinds of people can read anyone's DMs.

First, you: your admin/creator password passes the ownership check in nickCallerOwns, which dmPoll and dmSend use. If you want admin/creator access to DMs for moderation, just make that clear to users in the DM panel (for example "Admins can read private messages for moderation.").

Second, other players on the same IP address (same home, school or mobile network): for normal nicknames, nickCallerOwns also accepts a matching IP, so they can take a nickname and read its DMs. To fix it, make dmPoll and dmSend accept only the nickname's real owner (the uuid), not your admin/creator password or the IP. Then request a review again.

(the above message was written by an AI, I haven't personally checked so it could be wrong - let me know if you disagree)

Generators that import ai-text-plugin or text-to-image-plugin have an ad displayed at the bottom of the page which funds the GPUs required to support those plugins. If you don't import either of those plugins on your generator, then no ads are ever shown.

Note that if you're logged in, then no ads are ever shown, even on pages that import ai-text-plugin or text-to-image-plugin. The idea is that you're contributing to the perchance ecosystem/community via creating stuff (that's the whole point of having an account on perchance), instead of via seeing ads.

Sorry about that! Fixed.

From an AI, paste this to AI Helper to check/fix:

The privacy warning is correct. When you are signed in, AI Hub saves your chats, characters and projects to an "editable" file named after your username (aihubbk-yourname). Editable files are public: anyone who knows the name can open the file. Usernames are shown in Community, so anyone can read other users' chats. The second warning is likely because of the message you added that tells visitors the Perchance warning is a mistake and safe to ignore. To fix both, give each account's file a long random name (keep that name on your server, not based on the username), or encrypt the data before saving it. Then remove the "false flag" message, and request a new review from the warning's "More info" box.

Thanks! Should be fixed now.

Thank you for the report! Should be fixed now. The issue was hideIfScoreIsBelow defaulted to zero (if param was omitted) when you bypass the plugin and fetch the server endpoint directly using the super-fetch-plugin. So @ccufcc@lemmy.world was correct that it was related to your custom code, but I've just fixed it on the server side so the default is now "don't hide regardless of score" if the parameter is omitted from the request URL. Thanks again for the bug report.

Thanks! Fixed.

Please check this (it may be wrong - from ai helper):

The "Save as proven" button in Proof Lab still sends the user's phrase, with no opt-in, to a server vault that any visitor can read. Meanwhile the page tells users it was "Saved as proven on this device".

Also check for anything that could be reasonably interpreted as a feature designed for creating celebrity/real-people nudes/deepfakes, since I think it's flagged for that too. If there's nothing like that, let me know - it could be a false positive.

@Mack2@lemmy.world sorry about this! I'm rolling out a new moderation system - can you check if your generator has anything that might trigger the "may publicly show user inputs that most users would expect to be private by default" message? And also features that might be interpretted as specifically designed to create nsfw deepfake images of real people. You can ask the AI Helper to do a search for anything that might be triggering it. If you've checked and made any relevant changes and waited an hour or so and it's still not fixed, please let me know. If you can't find anything and think it might be a false positive, please also let me know and I'll dig deeper. It's very possible this new system needs some tuning.

@Bestaigen@lemmy.world I believe the message "may log or publicly show user inputs that one might expect to be private by default" is gone now. The reason it didn't go away immediately after you fixed the issue is because the moderation system was overloaded. Sorry about that, and thank you for letting me know. I'm working on making it faster so this doesn't happen again, though it'll likely always take at least 20 minutes, so I should make that clear in the UI somewhere.

Hi, thanks, you can DM me here on lemmy by clicking my username and then clicking the "Send message" button on my profile page.

Sorry for the delay here, I think I've fixed this - please let me know if you still see issues (pls refresh the page to get new updates).

Thanks again for all your bug reports. I'm still in the process of fixing a bunch of issues. Hopefully things will be back to a more stable state soon.

Sorry about all these bugs, and thank you for all your bug reports! I've been migrating everything to new, bigger servers (to hopefully fix comments plugin lag and a bunch of other issues), and so I've likely introduced a bug in collab stuff during that process. That said, I have tried about 5 times now and haven't been able to reproduce the issue. Have you noticed any specific sequence of actions which I might be able to try to reproduce it?