Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

"Generating your API key" needs to be updated #150

Open
nancym opened this issue Jun 14, 2020 · 2 comments
Open

"Generating your API key" needs to be updated #150

nancym opened this issue Jun 14, 2020 · 2 comments
Assignees
Labels

Comments

@nancym
Copy link

nancym commented Jun 14, 2020

Twitter disabled their old user interface on 2020-June-1 so I'm in search of a new way to use Twitter and I'm optimistic about Oysttyer so thank you for this! I'm going through http://oysttyer.github.io/docs/userGuide.html#apikey and have some feedback and questions.

Thank you!

@funnelfiasco
Copy link
Contributor

It should. I'll fix that.

It's only required if you use the sign in with Twitter option, which you don't need. Uncheck that boc and it should work.

Full disclosure, though: I'm still using Oysttyer, but I haven't done any development in...a few years at this point. 😔

@funnelfiasco funnelfiasco self-assigned this Jun 14, 2020
@mikeride
Copy link

This documentation seriously needs to be thrown out and rewritten. It doesn't reflect ANY of the new "apply to be a developer" stuff. Nothing in your docs is where you say it is on the website, nothing is called the same thing.

WELCOME TO oysttyer: Authorize oysttyer by signing into Twitter with OAuth

When I try that, I get:
Request from https://api.twitter.com/oauth/request_token ...... FAILED!: "{"errors":[{"code":32,"message":"Could not authenticate you."}]}"
unable to fetch token. here are some possible reasons:

  • root certificates are not updated (see documentation)
  • you entered your authentication information wrong
  • your computer's clock is not set correctly
  • Twitter farted
    fix these possible problems, or try again later.

You can't tell me to "see documentation" in an error message for root certificates when the user guide doesn't contain the word "root" or the word "cert".

I tried using the API key and API key secret, and I tried using the Access Token and Access Token Secret. Neither of those worked, both giving the above error. I have regenerated the Access token/secret and the API keys multiple times. Is the Bearer Token supposed to be given somewhere? Basically I have 5 separate codes, and your docs only tell me to give 2 of them (oauthkey and oauthsecret).

My system is using ntp, and has the correct time and timezone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants