Meta: Unifies API#605
Open
lissy93 wants to merge 11 commits into
Open
Conversation
- Re-wrote the API - It still includes all endpoints for programmatically fetching/querying awesome-privacy data - But now it also includes the enrichment endpoints, which the website, lib scripts and other places use to fetch more info about a given listing. Like GitHub, android trackers, privacy policy info, etc. - it uses Bun now. Previously it was a combination of Node and Python - Deployable from source, or with docker, or to the big evil cloudflare to run on workers
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Type
Misc
Changes
The awesome-privacy API exists to make browsing the list in a machine-readable format possible, and to add additional context to listings.
The data is used in two places:
Most of this API existed before. But it was a bunch of scattered Python scripts, living in random places. Not very consumable, maintainable or transparent. This PR refines is, and moves it into the repo.
This was done so that:
All data is for info purposes only. None of this data plays any part in decision making. Human review is always needed, and you should always do your own research.
Do not trust any of the data, it only gives a very narrow picture, of the most obvious stats for any given listing.
Supporting Material
N/A
Affiliation
N/A
Checklist