Release pushing chrome to the limits (and then some) · 9001/copyparty

there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-02-25)

recent important news

v1.16.15 (2025-02-25) fixed low-severity xss when uploading maliciously-named files
v1.15.0 (2024-09-08) changed upload deduplication to be default-disabled
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details

up2k: improve file-hashing speed on recent versions of google chrome e3e51fb
- speed increased from 319 to 513 MiB/s by default (but older chrome versions did 748...)
- read the commit message for the full story, but basically chrome has gotten gradually slower over the past couple versions (starting from v133) and this makes it slightly less bad again
- hashing speed can be further improved from 0.5 to 1.1 GiB/s by enabling the [wasm] option in the [⚙️] settings tab
  - this option can be made default-enabled with --nosubtle 137 but beware that this increases the chances of running into browser-bugs (foreshadowing...)
up2k: fix errorhandler for browser-bugs (oom and such) 49c7124
- because chrome-bug 383568268 is about to make a surprise return?!
#168 fix uploading into shares if path-based proxying is used 9cb93ae
#165 unconditionally heed --rp-loc 84f5f41
- the config-option for path-based proxying was ignored if the reverse-proxy was untrusted; this was confusing and not strictly necessary

#166 the nixos module was improved once more (thx @msfjarvis!) 48470f6 60fb120
added usage instructions to minimal-up2k.js, the up2k-ui simplifier 1d308ee
docker: improve feedback if config is bad or missing 28b63e5

this release was tested using an unreliable rdp connection through two ssh-jumphosts to a qemu win10 vm back home from the bergen-oslo night train wifi