Saïd
/attempt #255 Options Cancel my attempt
I'm sure @neo773 has no trouble speaking for him/herself so there's absolutely no need for you @WcaleNieWolny to speak on their behalf.
@neo773 gracias 👍! @riderx I did some preliminary research and I have a few quick questions: 1. the response headers for requests to the https://api.capgo.app/updates endpoint includes this header: `CF-Cache-Status:...
To support resumable downloads you need 2 headers. The `Content-Length:` header is one piece. The other piece is the `Range:` header. There are 2 reasons why a new endpoint is...
> That is not true, capgo has a way longer validity due to redis caching the url lol 😂🤣! This was true just [2 weeks](https://github.com/Cap-go/capgo/blame/968e488b84461d98354ed510216356c0711e7892/supabase/functions/_utils/downloadUrl.ts#L4-L5) ago so not sure what...
@algora-pbc yes, I know but without @riderx's input, I can't really forge ahead. Martin is working on fixing issues with billing (which is of higher priority).
@neo773 I know, right 😁! (I also know that the founders of Algora keep an eye on the bot's email notifications too 😉).
@whizsid curious as to what blocking error(s) you met?
Hey @riderx Still open? I'm thinking I might want to take a stab at this ...
@riderx Great! I would like to _tenatively_ adopt the same approach proposed [above](https://github.com/Cap-go/capacitor-updater/issues/119#issuecomment-1434625848): > i am interested. if you would be comfortable, we can split the bounty into two tasks...