It's unfeasible for some operating systems to have URLs directly fetched & stored in JSON. For example, URLs for macOS recover images expire after ~50 minutes, Windows URLs expire after 24 hours (which may have elapsed near the end of the day). Using docker images would add unnecessary bloat.
I propose adding an executable source type, which provides a URL to download an executable file from (e.g. a Windows/macOS downloader) alongside parameters to fetch the desired image through it & filenames expected after its completion. Frontends, such as quickget implementations, should always prompt the user before executing any file, due to the security risk.
Windows & macOS downloaders should probably be hosted within this repository; they should all be written in a language such as Golang or Rust to avoid external dependencies (such as Bash, Python, etc).
After a little bit of thought, these probably should be written in a language like Python instead. Otherwise, we'd have to cross compile them for every platform we want quickget to work on.
It's unfeasible for some operating systems to have URLs directly fetched & stored in JSON. For example, URLs for macOS recover images expire after ~50 minutes, Windows URLs expire after 24 hours (which may have elapsed near the end of the day). Using docker images would add unnecessary bloat.
I propose adding an executable source type, which provides a URL to download an executable file from (e.g. a Windows/macOS downloader) alongside parameters to fetch the desired image through it & filenames expected after its completion. Frontends, such as quickget implementations, should always prompt the user before executing any file, due to the security risk.
Windows & macOS downloaders should probably be hosted within this repository; they should all be written in a language such as Golang or Rust to avoid external dependencies (such as Bash, Python, etc).