this post was submitted on 19 Mar 2024
8 points (100.0% liked)

Perchance - Create a Random Text Generator

441 readers
4 users here now

⚄︎ Perchance

This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.

Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)

This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.

See this post for the Complete Guide to Posting Here on the Community!

Rules

1. Please follow the Lemmy.World instance rules.

2. Be kind and friendly.

  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

6. Search through the Community Before Posting.

  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
8
Text to Image Plugin Gallery Moderation Example (perchance.org)
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

Unfortunately for now it's just phrase banning (with regex pattern-matching supported) and user ID banning - i.e. no ability to "login" and delete stuff, like you can do with the comments plugin. Hopefully this will suffice until I get around to making it easier (I want to make moderation easier on comments plugin at some point too - e.g. 1-click bans alongside existing 1-click delete).

There may be bugs! Please let me know if you find one in the comments below. I haven't thoroughly tested it, so I'm relying on y'all :)

Edit: Also, a reminder that when I'm short on time (like lately) I'm most likely to fix things that people complain about often. Thanks to Allo and others for posting and complaining about this. Feel free to complain repeatedly and tag me often. It helps me prioritize.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 7 months ago* (last edited 7 months ago) (1 children)

🎉🎉🎉
Just a suggestion, can we have a hide button to only hide images for ourselves? i.e. to self moderate the images for ourselves?
We might not want to block the user generating them, but only hide some images that we don't want to see.

Also, possibly the RegEx formatting here can be applied to the RegEx for the comments-plugin, since we still can't use commas (,) on the RegEx for the banned words.

Edit: I think RegEx with Perchance Syntax ( square brackets, curly brackets, caret, etc) still doesn't work or at least it currently throws errors.

Thanks again for the amazing update!!! 💜💜💜

[–] [email protected] 3 points 7 months ago (1 children)

Thanks! Just fixed the perchance-syntax-in-regex problem, and I added the ability to specify a list of ban patterns for comments-plugin. Let me know if you notice any more issues, of course.

RE a hide button for gallery - the downvote does hide it, but I'm guessing you want to hide without downvoting?

[–] [email protected] 2 points 7 months ago (1 children)

yeah, I assume that it would be only hidden unless it passes the certain threshold specified in the hideIfScoreBelow or was that changed, which is why a hide button is suggested.

[–] [email protected] 2 points 7 months ago (1 children)

I'm not 100% sure what you mean by "a hide button to only hide images for ourselves". Are you talking about a moderator tool, or a feature for individual users to hide images. If it's the latter, then the downvote button should suffice since it does hide the image for the individual user who clicked said button. If you downvote an image, and then refresh the page, it should still be hidden. If not, then that's a bug.

[–] [email protected] 2 points 7 months ago (1 children)

I do see the 'blacked out' image when it is downvoted. By 'hide' I think would be 'remove' the element/image from the gallery directly, which will shift the images, reclaiming the lost space. But I think it is alright for now.

Some update on the comments-plugin, the RegEx works, but not on RegExes with ^ or $ for matching start and end strings, not really a problem I don't think.

Also, the RegEx doens't work in the following configuration (in comments-plugin only, in text-to-image-plugin it works fine):

commentOptions
  bannedWords = [banned]

banned
  /badregex/ig
  /badregex2/ig
  ...
[–] [email protected] 2 points 7 months ago

Thanks!! bannedWords = [banned] should work now, and I fixed the ^ issue too. Just make sure to put a backslash before ^ due to perchance odds notation (Not ideal - maybe odds notation errors should happen at runtime rather than compile time - that would fix this, but would make odds bugs harder to find. Could maybe use warnings at compile time instead of error, and add a way to disable warnings for a list/sublist/item. Needs some thought...)