[WIP] Custom keys for app #46
Open
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
YoruNoHikage
force-pushed
the
custom-keys
branch
from
2f77e00
to
49609f9
Compare
YoruNoHikage
force-pushed
the
custom-keys
branch
from
49609f9
to
a31070f
Compare
YoruNoHikage
force-pushed
the
custom-keys
branch
from
a31070f
to
c10b896
Compare
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.
With all those recent breaks, I had to backport fixes and stuff into my own version of Echofon. But tired of doing this, here are changes that could be integrated into the main repo so people can change their prefs to add their own Twitter app keys (no form for the moment).
What do you think ? (maybe we can move the sign algorithm, that used to be in the binary, into a new file).
It also breaks previous authorized accounts, you have to re-auth by deleting and re-adding them.
I'll squash everything later, so please, do not merge. ;)