search

DocNow / diffengine

track changes to the news, where news is anything with an RSS feed
MIT License
177 stars 30 forks source link

unable to tweet: Read-only application cannot POST #20

Closed larsschwarz closed 7 years ago

larsschwarz commented 7 years ago

Looking at the Twitter account's "Apps" settings this is actually correct: it reads "Permissions: read-only", however I just provided the tokens and secret as requested and opened the Twitter authorize URL that returned the pin.

I haven't played with Twitter OAuth for ages and I can't seem to find a way to change the permissions afterwards using the Twitter UI, so what would be the proper way to grant read and write to my app?

EDIT: I simply clicked "Regenerate My Access Token and Token Secret" and Twitter then magically makes it a Read and write token instead of a read-only

edsu commented 7 years ago

Ok, it sounds like you figured it out? It is tricky to get things set up on the Twitter side. It seems like there is some built in latency to cut down on the spambot problem on Twitter.

ghost commented 4 years ago

As for 2020 I had the same problem. Just go to twitter developer then to Apps and in you app you can edit the settings from read-only to read write and publish direct messages, then regenerate the tokens.

hannorein commented 3 years ago

In case this helps anyone else: The twitter dev page already showed read+write access for my app, but the authorization request still only requested read access. I had to click on "read+write" in the dev settings again (despite it already being selected), then click on save. This seems to be a bug on the twitter side of things, probably triggered by the recent API changes.

frankShih commented 2 years ago

In case this helps anyone else: The twitter dev page already showed read+write access for my app, but the authorization request still only requested read access. I had to click on "read+write" in the dev settings again (despite it already being selected), then click on save. This seems to be a bug on the twitter side of things, probably triggered by the recent API changes.

Hi, @hannorein

I try to retweet via API, it says I need WRITE permission. Then I try to enable that feature, however, I do not know how to setup these callbackURL … something like that

Any suggestions ?

edsu commented 2 years ago

Are you able to leave the callback url blank?

frankShih commented 2 years ago

Are you able to leave the callback url blank?

seems unlikely

image image image

I don't have much experiences in these "authentication&authorization" stuff. Could someone please give me some suggestions?

Thanks in prior

edsu commented 2 years ago

You can simply enter any URL there. diffengine doesn't uses PIN based authentication, so it doesn't need to use the URL. I recommend you try entering your personal URL there, or something like https://localhost:3000.