-
-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a more modern Twitter Android version that works #1482
base: master
Are you sure you want to change the base?
Conversation
How does one do this please? Is there an .APK? The Android consumer codes I find only give errors. I am inexperienced with GitHub though |
This PR needs to be merged by the owner of this project, which I'm not sure is going to happen 😞 |
Ahhh; I was worried I was missing something. Thanks!
…On Monday, 13 March 2023, Torvin ***@***.***> wrote:
How does one do this please? Is there an .APK?
This PR needs to be merged by the owner of this project, which I'm not
sure is going to happen 😞
—
Reply to this email directly, view it on GitHub
<#1482 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2LSPV3XE5JADQCGPRITPTW37EGRANCNFSM6AAAAAAURQB5C4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Where did you find the key? https://gist.github.com/pvieito/ee6d2c8934a8f84b9aeb467585277b8a。 That's Invalid. |
It's not invalid. But it's not going to work unless this PR is merged |
Are you sure? I see that you have only changed one file and only the version number. Would that have worked? |
You have changed the version number of the Twitter client. I noticed that twidere determines if it is Twitter Android by the consumer key, that key is defined, so what is the SECRET key? |
Yes, changing the version number is enough to make it work. I'm using the key you linked ("Twitter for Android") |
I'll try it, so what is the mechanism? In addition to checking the key, does twitter check the request header? This version number is not the latest twitter version, only a specific version number can be normal? |
That's right, twitter banned its own old client - version 6 that is hardcoded into Twidere doesn't work anymore. It doesn't have to be version 8 to make it work, but I tested this version and it works |
|
Could it be that it was normal when you tested it, but it is now invalid |
I use Twidere every day and it works perfectly. You need to log in with that official key though (via XAuth), otherwise it doesn't use the official key |
Awesome, it does. How did you do it, did you use the official twitter client to capture packets? I think if this version number is useless, I can try it myself |
Logging in via Twidere works, unless you get login challenge. If you do - you can use this python script to retrieve the token |
The official twitter key does work. I tried to use the HootSuite key (I found it on the Internet, it should be available), but I got 401. I am sure it is the enterprise version. Is it different from the personal version, and some headers need to be added. Also, should a newer version of twitter be used, so that the deprecation time will be extended later |
It was okay yesterday, but it is invalid today. I don’t know how it is on your side. |
I seem to find some regularity that not all accounts are available.
|
Like I said, the reason is that you are getting the login challenge. You need to use the Python script above in that case |
Hello, how can I contact you by email, I have many questions to ask you,
thank you very much
Torvin ***@***.***> 于2023年4月3日周一 06:58写道:
… 2. I don't know the reason
Like I said, the reason is that you are getting the login challenge. You
need to use the Python script above in that case
—
Reply to this email directly, view it on GitHub
<#1482 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJKVLWB3IBU76ZM6F6A4PDW7IAAPANCNFSM6AAAAAAURQB5C4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
The Python script has a url address that returns 302, you can read my comment in githu.io |
if it doesn't work anymore - that means something has changed yet again and you will have to find another way to login. either way it has nothing to do with this PR |
Any blocks to merging this now, @Tlaster ? From my perspective it's simple and brings the app back to functional. |
See my post here - #1475 (comment) but this doesn't seem to change anything any more in terms of allowing more access. Possibly an even newer version number is needed? |
You are right, everything is broken now for reasons unrelated to this PR - twitter simply shut down some endpoints that were used by Twidere (and other apps). Since this is project seems abandoned, the only viable solution now is to fork it and update the code to use new endpoints. There's not much point in merging this PR anymore 😞 |
Here is the real link: |
This change allows me to use Twidere again after the 3rd-party API ban. You just need to use the official Android consumer key and it works. XAuth works too.
I know that this project is not actively maintained, but please consider releasing this minor update 🙏
Potentially fixes #1478 (I haven't encountered it so couldn't test)