Consumer key/secret for official Twitter clients
gist.github.com
Consumer key/secret for official Twitter clients
1–10 of 104 posts
Re: Consumer key/secret for official Twitter clients
#2uh, this is not good. Why would someone post that under their own github account?
Re: Consumer key/secret for official Twitter clients
#3uh, this is not good. Why would someone post that under their own github account?
It's more or less public knowledge. You can find it yourself by running "strings" on the Twitter app binary. Any attempts on Twitter's part to limit the disclosure of these tokens would almost certainly invoke the Streisand Effect.
Re: Consumer key/secret for official Twitter clients
#4uh, this is not good. Why would someone post that under their own github account?
It's more or less public knowledge. You can find it yourself by running "strings" on the Twitter app binary. Any attempts on Twitter's part to limit the disclosure of these tokens would almost certainly invoke the Streisand Effect.
Couldn't another app use these tokens and take advantage of lax api limits ?
Re: Consumer key/secret for official Twitter clients
#5uh, this is not good. Why would someone post that under their own github account?
Isn't this actually a great thing since it enables developers to develop Twitter clients that aren't dependent on tokens and approval from Twitter?
Re: Consumer key/secret for official Twitter clients
#6Earlier quoted context omitted.
It's more or less public knowledge. You can find it yourself by running "strings" on the Twitter app binary. Any attempts on Twitter's part to limit the disclosure of these tokens would almost certainly invoke the Streisand Effect.
Couldn't another app use these tokens and take advantage of lax api limits ?
Yes. And that's the point of the disclosure.
Re: Consumer key/secret for official Twitter clients
#7Earlier quoted context omitted.
It's more or less public knowledge. You can find it yourself by running "strings" on the Twitter app binary. Any attempts on Twitter's part to limit the disclosure of these tokens would almost certainly invoke the Streisand Effect.
Couldn't another app use these tokens and take advantage of lax api limits ?
NekoTsui supports to change consumer key/secret.
https://itunes.apple.com/app/nekotsui/id476924886
Re: Consumer key/secret for official Twitter clients
#8uh, this is not good. Why would someone post that under their own github account?
Isn't this actually a great thing since it enables developers to develop Twitter clients that aren't dependent on tokens and approval from Twitter?
You could only make an app that would explode if/when they decide to change keys
Re: Consumer key/secret for official Twitter clients
#9Earlier quoted context omitted.
Isn't this actually a great thing since it enables developers to develop Twitter clients that aren't dependent on tokens and approval from Twitter?
You could only make an app that would explode if/when they decide to change keys
But they can't change those keys without isolating every installation until it's updated, right?
Re: Consumer key/secret for official Twitter clients
#10Earlier quoted context omitted.
Isn't this actually a great thing since it enables developers to develop Twitter clients that aren't dependent on tokens and approval from Twitter?
You could only make an app that would explode if/when they decide to change keys
Along with any official client that is slightly out of date. Twitter might be hesitant to alienate their users.