Open majora2007 opened 12 months ago
I have some thoughts about this i want to share.
If i understand this right you want to proxy the Metadata request to your own Server and implement a rate limit ? I would suggest if you do this, use the Kavita Instance of the user and the API Key of the Admin that activated that Setting, dont send that over to your own Server.
That sounds awful, cencorship bad. Thats why doing it over the Kavita Instance is better, then if a user would like to get metadata for a manga containing e.g. Sexual Violence it would only be on their server and never touch your network/server.
- I need to investigate some advanced settings with the feature, like blocking certain keywords from being saved. Ie) Sexual Violence is not a genre in my opinion and shouldn't be written to target.
- I may investigate a tag based system to help guide age ratings. Completely user customizable to have that written as there are no metadata sites with this present.
It would be really nice to have tags split into categories like mangadex does - format, genre, theme, and content warnings (suggestive, erotica, gore, sexual violence). Also, since some Anilist tags contain spoilers, there should be a way to hide/reveal them, and a default setting.
(Thinking about spoilers, I had a thought about an option to blur/replace unread chapter covers, since it often starts with first frame and it might reveal some things that volume covers do not).
This is targeted towards people that don't use Komf.
The idea is to provide a manual button to download metadata from AniList and update Kavita via the API (this will not save the data to ComicInfo).
Note: Even if community votes yes for this, it is still subject to being removed after testing. This would likely put enormous strain on hosting and may not be sustainable.
Notes for self: