-
Notifications
You must be signed in to change notification settings - Fork 74
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
MAL Scraper - additional information about series #425
Comments
@da3dsoul would love this ;-) |
Did I not have an issue for this? |
Guess not |
I didnt find any so I made it so it wont be forgotten ;-) |
MAL API is fun to work with, just ask @hidden4003. :) Well it can be a pain I'd prefer we use it over some third-party source. Also there are over a dozen issues related to MAL so we'll probably need a "main" issue for MAL. |
Throw it then and link this one there or make it project which have nice progress bar On September 19, 2016 3:18:31 PM GMT+02:00, ElementalCrisis [email protected] wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
omg! studio! licensor! we need this ! |
the question would be: we doing it inside shoko-server or via web-cache |
Inside |
you want to port jiken into c#, and maintain it ? wouldn't it be better to do it via web-cache ? so someone else would update it and we could contribute to jiken ?and if project would die we would replace it but leave web-cache structure intact ? |
It's already hosted, we don't need to |
so what data we got now added ? Studios ? |
Nothing. We're dropping MAL Support. We're going with AniList |
That's just the checklist, MAL has pretty much forced all third-parties devs to drop them. They completely removed their API and have no plans to bring it back as they are working on a "new" one that we should see sometime in the next millennia. |
MAL contain some information that AniDB is lacking
for example: Studio
We could add some additional info to ours databases
by utilizing API or simple scrapper
This could be done via CacheServer - as only once ever or by jmmserver when needed.
A cacheserver script could run and harvest those information and jmm would use those as input to avoid stressing out MAL servers - or if the API is working use that instead to free up Cache.
The text was updated successfully, but these errors were encountered: