-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Improve Errors #45
Comments
P.S. I opened an issue for once, @dgw, so clearly you've died and gone to heaven. You're welcome. 🤪 |
There isn't. The plugin would already handle it separately if there was. |
In that case, I simply propose we modify our current error to explain a third case: that it may be an 18+/NSFW tweet. |
Seems this is resolved by #46 |
ghost
closed this as completed
May 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I haven't looked at the upstream tool used, but if there's a separate error message provided for 18+ (NSFW) tweets, it would be good for Sopel to reply with that, rather than saying (very incorrectly) that the tweet is not found/deleted.
The text was updated successfully, but these errors were encountered: