I found this a couple months ago and it was an amazing resource (thanks dmitrygr)!
I ended up using atc1441's base station firmware[0] because it's a bit of a pain to actually pop open the case and get the programming pins on the Chroma 74
It's been a long while since I worked there, but IIRC one of the big issues at the time was that the symlink "support" couldn't actually work properly:
- some users want symlinks to be synced as symlinks (and they might not know it, old Apple file formats have internal symlinks), so their files got corrupted if they were accessed on another computer
- some users want the sync client to follow the symlink and copy all the files at the destination, which requires the client to listen to filesystem events for potentially the entire filesystem, which is no longer permitted in many cases
so, not exactly a vulnerability, but a mix of security and product issues.
I can't speak for Slack, but it's not unreasonable to believe that a single machine's available output bandwidth (~10-40Gbps) can be saturated during a deploy of ~GB to hundreds of machines. Pushing the package to S3 and fetching it back down lets the bandwidth get spread over more machines and over different network paths (e.g. in other data centers)
I ended up using atc1441's base station firmware[0] because it's a bit of a pain to actually pop open the case and get the programming pins on the Chroma 74
[0]https://github.com/atc1441/E-Paper_Pricetags