api-specs
api-specs copied to clipboard
OpenPodcastAPI
Exclude gpodder from lychee
Since v2 (#105), Lychee-action automatically fails a PR if a link-check doesn't work. Probably a good thing, though we have one particular website that will often fail. Therefore excluding that website.
Doing via exclude argument rather than creating a .lychee-ignore file because (at this point) we're only excluding a single site (and adding a file is polluting more than helpful).
Deploy Preview for openpodcastapi ready!
| Name | Link |
|---|---|
| Latest commit | 3c06afb35b26ae384668d684b9b5b8c1f3a4b0c5 |
| Latest deploy log | https://app.netlify.com/sites/openpodcastapi/deploys/672766f87238cd0008ff0625 |
| Deploy Preview | https://deploy-preview-116--openpodcastapi.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
we have one particular website that will often fail
If this is the case and we don't have any reason to expect improvements or means to improve the situation, I'd say we should create a mirror and link to that. Because if the page isn't available on a regular base, why should we link there? Its not reliably useful to our users.
It's regularly offline but often still works. But you have a good point.
I just realised that the link only exists in our Readme file - not very prominent. A mirror is probably not worth it. I guess that (instead of adjusting lychee) we could:
- drop the link
- replace it with a link to archive.org's copy
- replace it with a link to the GitHub repo
Any preference?
@keunes Using archive.org was basically what I meant by "mirroring", I didn't want to host a mirror on our own. But I wasn't sure about the state of archive.org at the moment and didn't knew if there is already a copy there. But if there is, we should probably link there. Github would be also fine.
I think our project is heavily inspired by GPodder and dropping the link is something I wouldn't be comfortable with. I also think we should promote the link to our Website in order to appreciate their work :)
It seems the gpodder.net team have cleaned their database and upgraded the hardware, so their website is up most of the time again.