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!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
Just noticed that some generators in the /generators page have a blank white thumbnail while it should display the captured content from the generator page. Could there be something wrong with the getGeneratorScreenshot API, or any other reasons?
I also tried to open one of the blank white thumbnails in a new tab to trigger a getGeneratorScreenshot response, but it had the same issue.
Yeah quite a few of them have. My generators are all blank, I believe. But $meta.image does work though.
Same with some of my generators/plugins too, even my generator hub page has a blank thumbnail. (Here's a link for testing)
I've found some even show with a big question mark--when there's not even a blank image for it. 😅
My latest couple of public pages do have thumbnails now!
Maybe it's related to the page being private or public during development, something like that?
Probably not, I've never set any of my plugins private before or after saving. Either way this may happen at any chance.
This most likely happened on very newly created generators, when the automatic thumbnail for those haven't been captured yet.
Also @[email protected], at least only on the hub page, one sub-list async function assignment is somehow mistakenly recognized as a parsing error (I've only encountered this on desktop and not mobile).
