It appears Twitter has started using Cloudflare, which often prevents tweety-ns from logging in. Unfortunately tweety-ns seems to treat this as InvalidCredentials, which causes sopel-twitter to reply with "Can't authenticate with Twitter. Please ask my owner to check my credentials."
Errors should probably be logged by the plugin, rather than leaving the problem invisible until a user figures out the bot admin and reports it - Especially errors that definitely require owner intervention to fix, like a real login failure.
Until tweety-ns figures something out, my workaround is to manually update the bot's [...].sopel-twitter.tw_session file with the relevant cookies from a logged-in browser session.
It appears Twitter has started using Cloudflare, which often prevents tweety-ns from logging in. Unfortunately tweety-ns seems to treat this as
InvalidCredentials, which causes sopel-twitter to reply with "Can't authenticate with Twitter. Please ask my owner to check my credentials."Errors should probably be logged by the plugin, rather than leaving the problem invisible until a user figures out the bot admin and reports it - Especially errors that definitely require owner intervention to fix, like a real login failure.
Until tweety-ns figures something out, my workaround is to manually update the bot's [...].sopel-twitter.tw_session file with the relevant cookies from a logged-in browser session.