Jackett: [REQ] https://milkie.cc/milk/General2019
New tracker request
bumjrah
All 6 comments
semi-private.
not compatible with cardigann processor, as it generated search results dynamically with js.
requires a c# indexer.
garfield69
on 1 Jun 2019
@garfield69 Could you possibly look at this again, for search it looks like we can use https://milkie.cc/browse?query=&pi=0&ps=50 and https://milkie.cc/browse?query=ubuntu&categories=6&&pi=0&ps=50
for searching. I may be wrong, but I think that allows us to use the cardigann processor? (Or does the login using JS rule it out to begin with? It looks like it does a POST to https://milkie.cc/api/v1/auth/sessions to get a login token)
Sytanek
on 19 Aug 2019
if you login to milkie with your chrome browser directly, and open the development tools page and click on the network tab, you can test this for yourself.
so perform your search on milkie then click on the network entry generated.
take a look at response tab and you will not see html containing the results, but just a short document
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Milkie</title>
<base href="/">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" type="image/png" href="favicon.png">
<link rel="stylesheet" href="styles.41f55174c965a802e527.css"></head>
<body>
<app-root class="mat-typography"></app-root>
<script type="text/javascript" src="runtime.18fb13c69522f7d0c4b7.js"></script><script type="text/javascript" src="polyfills.5156d16a69af74b9d8c1.js"></script><script type="text/javascript" src="main.ab1676a1f0fb1a5659b9.js"></script></body>
</html>
there is nothing for the cardigann processor to process :-(
everything you see on the browser screen is created by js dynamically after the html base page is returned.
garfield69
on 19 Aug 2019
@garfield69 I'm not familiar with Jackett at all to be completely honest, but many of our users would like to have Jackett support. Could you please tell me what exactly needs to be done and if there's anything we can do on our end to make it easier?
milkiecc
on 10 Apr 2020
TBH, I don't think there is much you can do from your end ATM.
We should be able to support milkiecc with a Jackett indexer written in C#
ATM the issue is one of resources.
There are only two C# devs that regularly contribute, and both are extremely busy right now.
I specialise in writing Jackett indexer in yaml (which has a more simpler structure) but has constraints such as only being able to process HTML that does not use JS post processing).
But a C# Jackett indexer has not such constraints.
Right now, it just a matter of waiting for a C# to volunteer to code up an indexer.
garfield69
on 10 Apr 2020
Jackett 0.16.96
garfield69
on 21 Apr 2020
Related issues
Eisa01
路
3Comments
annomatik
路
3Comments
suisuneko
路
4Comments
ohmaxx
路
3Comments
STX2k
路
3Comments
Most helpful comment
if you login to milkie with your chrome browser directly, and open the development tools page and click on the network tab, you can test this for yourself.
so perform your search on milkie then click on the network entry generated.
take a look at response tab and you will not see html containing the results, but just a short document
there is nothing for the cardigann processor to process :-(
everything you see on the browser screen is created by js dynamically after the html base page is returned.