Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Naughty" prompts #93

Open
waynemareci opened this issue Jun 6, 2023 · 5 comments
Open

"Naughty" prompts #93

waynemareci opened this issue Jun 6, 2023 · 5 comments

Comments

@waynemareci
Copy link

Wonder if you've given any thought to processing rejected prompts

image

I've seen this using words like "flesh" or "overdose". Right now Imagine() eventually times out and returns a null message. Can anything be done to catch this response?

@zcpua
Copy link
Member

zcpua commented Jun 6, 2023

@waynemareci
Copy link
Author

I have Ws set to true

@waynemareci
Copy link
Author

I failed to run client.init(); this seems to resolve my issue. Can you explain the purpose of client,init()? It's not used in Usage in the readme.md on the midjourney-api home page.

@zcpua
Copy link
Member

zcpua commented Jun 7, 2023

Wait for Discord websocket to connect successfully

@LukeFerris
Copy link

Some interesting further behaviour on this. If you appeal successfully, it looks like that key word (blood in my example below) is then allowed going forwards - but with a slight difference in behaviour. Once the image is created, it seems to delete the original message and displays the result in a new message (see "original message was deleted" at the top of the image).

Screenshot 2023-06-11 at 09 04 25

This thwarts the midjourney api code in ever linking up with the successful image (I suspect) which causes it to eventually return null / timeout.

I wonder whether this bit is solveable..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants