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).
- https://perchance.org/text-to-image-gallery-moderation-example
- https://perchance.org/text-to-image-plugin
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.
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, intext-to-image-plugin
it works fine):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…)