-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Add a webpage for unimplemented features #42
Comments
Added, available at /about/feature. Let me know if this is sufficient. |
Thank you! Just a last thing. It would be great to have a list of common features not implemented yet with their URL and redirect those URL to the about/feature page automatically. I think it makes more sense to implement it directly in Nitter, since the Nitter Project knows better what is implemented and what is not, instead of doing it in every other third party project. e.g: |
Alright, I can do that. I've found a bunch of weird Twitter features already but it's hard to keep track, I'll try to cover everything I know of. |
These are now covered: The /i/ wildcard covers these and potentially others I haven't found: |
Great job! Thank you! Maybe we should create a wiki page to list different Twitter endpoints and if they are supported or not. So everyone could contribute to list it. |
Hi!
When an user is trying to redirect a twitter link to an unimplemented feature, she/he is redirected to a 404 error.
That would be great if, instead, users could be redirected to a special webpage for unimplemented features, saying something like "Nitter is WIP. The feature you're trying to access is not currently supported but it's on our plan. You can check what is our TODO list here."
This way, third parties would not have to take care about which URL the user is trying to redirect and then they would not have to check all implemented features and how the project is growing day after day.
Finally, that would let the user know they are not facing a bug and that humans are working on the project. (You could use this same webpage to display informations like where to submit a bug, where to talk with the community arround Nitter, where to donate, etc.)
The text was updated successfully, but these errors were encountered: