Twitter doesn't respond to to non-https traffic anymore #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It works for me as it is now. |
|
The package didn't work for me, because the request to authorise presents a blank screen. I presume that it worked for you because you already had a token issued prior to Jan 14, 2014? |
|
Ahh, I thought token should be re-generated every time I press 'authorize' in the browser. I tried deleting the package (including the settings file) and re-installing/re-authorizing it again: it still worked. |
rozboris
added a commit
that referenced
this pull request
Feb 13, 2014
Twitter doesn't respond to to non-https traffic anymore: fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since January 14th, 2014 - Twitter has started restricting all api.twitter.com traffic to HTTPs only (https://dev.twitter.com/discussions/24239)