-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: announcements/ changelogs endpoint #42
Comments
So how do the client (for example, the announcement patch in YouTube ReVanced) access the api if it has a CAPTCHA? If you set a variable at built time, wouldnt it also be scraped by decompiling the apk or just use sth like MITM + wireshark? |
To display Captcha, a traditional WebView component would be displayed that would complete the captcha. |
This comment was marked as off-topic.
This comment was marked as off-topic.
ReVanced/revanced-patches-template#1047 So Osu are saying that the client would have a CAPTCHA window once a day? why dont just rate-limit the client IP instead? |
@alexandreteles If possible, a specification could be released early for clients to mock the endpoints until it is available. Currently open: ReVanced/revanced-website#165 |
About
It is currently not possible to publish official announcements or changelogs.
Solution
Add the following endpoints:
Why
Additional context
It may be beneficial to authenticate this endpoint. The reason to do so would be so that it isn't scraped. Imagine the following scenario:
Someone forks ReVanced Manager. Now that they use our API endpoint, we will deliver announcements and changelogs on their fork. The same applies to the ReVanced website, which could consume them. Ideally, we display them on the website, which would act as the primary source of information. If the endpoint were not authenticated, some other website would use it. Instead, the idea is to host your own API to deliver them. ReVanced Website and ReVanced Manager would have a variable in the source code that can be set at the built time to authenticate against the endpoint. Adding a captcha to the endpoints may also be beneficial to prevent scraping. Further attempts are not necessary to protect the endpoints.
The text was updated successfully, but these errors were encountered: