VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel...
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> I have chunking working in a test environment
<HebaruSan[m]> Using the 'dropzone' client component
<HebaruSan[m]> Installed via browserify
<Darklight[m]> I'll test by setting low timeouts and speed limited upload speed when I have the time
<HebaruSan[m]> Well it'll be a little while yet, I finished the update page but create is in progress
<Darklight[m]> This doesn't break the API upload right? Or does it add a new api enpoint?
<HebaruSan[m]> I think I can make it compatible
<Darklight[m]> I'd recommend just adding a new api endpoint if unsure
<Darklight[m]> That way peoples curl scripts don't break ;)
<HebaruSan[m]> But if someone wants to upload huge mods via curl scripts over dialup...
<HebaruSan[m]> Uncaught ReferenceError: repsonse is not defined 🤦‍♂️
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]