-
Notifications
You must be signed in to change notification settings - Fork 62
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
Twitter Posting #115
Comments
No, unless someone wants to pay Twitter $100 per month for pywws to be able to post messages. |
I did wonder after it stopped working in July 23 and it hadn't been fixed yet. Shame really, oh well I'll post the stats on mastodon instead. Thanks for the feedback Jim, been using pywws for longer than I can remember 😊 |
I've looked into this and I believe the free account is allowed to post up to 1500 posts a month, so in theory if the user only tweeted hourly weather conditions, it'd equate to approx 740+ tweets a month.
|
pywws has more than one user. If you create your own developer account and generate your own key/secret then you can post to Twitter. But if you share that key/secret (as pywws does) then all the users soon add up to more than 1500 posts per month. |
Apologies, I'd always used pywws with my own twitter account in isolation. |
There are two sets of key/secret pairs. The one corresponding to your user account, which is stored in weather.ini, and the |
Is there any fix to the following error since twitter changed the api access?
:pywws.service.twitter:TwitterError([{u'message': u'You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product', u'code': 453}],)
The text was updated successfully, but these errors were encountered: