I could change the way that new files are downloaded - at the moment the user types the pfb code into the box and if it is not there it downloads.
However for very large files, eg 7a6a, this takes ages. It could even blow the file server budget for the free tier.
I could instead provide a list of all the available already downloaded files and the user could choose one or "request" a new one. They could then come back and check if it exists later, it would downl;oad asynchronously, possibly go into a requests list qith a status "pending" "downloaded" or "rejected on size" perhaps.
I could change the way that new files are downloaded - at the moment the user types the pfb code into the box and if it is not there it downloads. However for very large files, eg 7a6a, this takes ages. It could even blow the file server budget for the free tier. I could instead provide a list of all the available already downloaded files and the user could choose one or "request" a new one. They could then come back and check if it exists later, it would downl;oad asynchronously, possibly go into a requests list qith a status "pending" "downloaded" or "rejected on size" perhaps.