-
-
Notifications
You must be signed in to change notification settings - Fork 516
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
Some users' timelines show "Unsupported feature" page #814
Comments
@jackyzy823 thanks, but that breaks several routes like settings and search since timeline swallows them. I used your suggestion and added a fix that makes the routing order less important: 91c6d59 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Opening the page at https://nitter.net/intenttoship shows an "Unsupported feature" page instead of the expected user timeline/profile page.
The user's individual tweets can be opened, for example https://nitter.net/intenttoship/status/1636087416959258625 works - I first encountered the user through that individual tweet on another user's timeline RSS feed with no hint of anything being wrong.
I don't know much of Nim or the routing system used by Nitter, but I have a hunch this happens because the "/intent/?@i?" route in unsupported.nim maybe has a higher priority than the route that would show the user profile. I found some other cases with the user search that show the same behavior:
https://nitter.net/intentcompany
https://nitter.net/intentdatasci
However, this one does work:
https://nitter.net/Intent_blog
Seems like only lower case "intent" causes this. This proved out to work as a workaround: capitalize a letter in the "intent" part of account name, and the profile opens, as Twitter usernames apparently are case-insensitive. For example, the address https://nitter.net/Intenttoship works.
Looking at unsupported.nim, there's also the route "/login/?@i?", which made me suspect that usernames starting with "login" might also be affected, and this seems to be the case. For example https://nitter.net/logindotgov also causes the "Unsupported feature" page. Capitalizing the first letter (or any letter in "login" I suppose) shows the profile page, as with "intent" users. I did not try to check the other path patterns, as they didn't seem suspicious.
The text was updated successfully, but these errors were encountered: