Skip to content
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

Add website status to README.md and index.json (incomplete) #169

Closed
wants to merge 1 commit into from

Conversation

bethropolis
Copy link
Contributor

this pr is based of issue #133

I added a file status.go which will perform the http request to check if the website is up and return 1 or 0 for each extension

I also added a column on the README table displaying "Ok" or "Down" based on the return status

finally the status for each extension is included in the index.json file that is saved

eg:

 //...
"package": "9animetv.to",
 "status": "1",
 "type": "bangumi",
// ...

current issues causing status 0

  1. Most extensions use an api service which mostly return a 403 page when you GET / example agedm.org

  2. Some extensions don't have a website url, or the url has an incorrect syntax eg. vod.api.json.collection18.js, com.freexcomic ...


@MiaoMint @OshekharO what would be a better way to do it?

this is what I can think of as opposed to manually or using the earlier one on test branch

in this one we could make //@website required and probably in api based extension ensure they point it to a working path then set the website url through the "Miru-Url" header or another description field can be added.

in the second one where we can mimic miru and just test the latest method, but i'm not sure if it's a better way

This are just my thoughts and views what do you think?

@OshekharO
Copy link
Member

You going with bachig suggestion?

@bethropolis
Copy link
Contributor Author

bethropolis commented Jan 18, 2024

You going with bachig suggestion?

yes, adding status to the README

@MiaoMint
Copy link
Member

It's a good idea, but there are too many situations to deal with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants