In case someone decides to put a malicious/stolen/broken mod on github, since we can't remove it from github, we need to filter these mods out of the mod browser
A blacklist file can be present in one the branches, can be as simple as one line per entry, like this:
owner/repo1 This mod has been blacklisted as it is known to damage other mods.
owner/repo2
owner/repo3 This mod belongs to another person. Only the original creator may upload their mod.
In this example I show an optional description, can be displayed in a "troubleshooting" page, where modders can go to check why their mod isn't appearing on the mod browser.
If SMM has a feature to download/update mods, it should probably respect this blacklist by default (potentially, let the user turn this feature off, after warning them), and maybe show the description so the user knows why this mod can't be installed/updated.
The app(s) (or rather the library) should download this blacklist on startup, parse it into a dictionary, and filter out any search results that match the listed repos
In case someone decides to put a malicious/stolen/broken mod on github, since we can't remove it from github, we need to filter these mods out of the mod browser
A blacklist file can be present in one the branches, can be as simple as one line per entry, like this:
In this example I show an optional description, can be displayed in a "troubleshooting" page, where modders can go to check why their mod isn't appearing on the mod browser.
If SMM has a feature to download/update mods, it should probably respect this blacklist by default (potentially, let the user turn this feature off, after warning them), and maybe show the description so the user knows why this mod can't be installed/updated.
The app(s) (or rather the library) should download this blacklist on startup, parse it into a dictionary, and filter out any search results that match the listed repos