3 ms·
Dropbox apparently abandoned the project. Do you know what their takeaways were from trying to improve the JPEG storage? For example, was it worth it in the en
by staunton 1y ago
Dropbox apparently abandoned the project. Do you know what their takeaways were from trying to improve the JPEG storage?
For example, was it worth it in the end? Did they announce anything? Did they switch to another method or give up on the idea, or do we not know?
- lifthrasiir 1y agoDropbox apparently still uses Lepton or any successor internally, but the open source version is abandoned because it posed larger maintenance burden than internal projects.
- staunton 1y agoHas Dropbox said this anywhere? Or are you assuming it based on something like "this kind of project is very easy to maintain internally so there's no reason why they would have stopped using it"?
- lifthrasiir 1y agoAt least at the time of abandonment, Dropbox did say (emphasis mine): > While we did ensure that the reported vulnerabilities don’t affect our internal use of Lepton, we unfortunately don’t have the capacity to properly fix these and future issues in this public repo. As far as I know this is indeed the last known public mention of its use, but given that Lepton was already in use and dropping it would substantially increase its traffic, it is reasonable to assume that its use somehow continues to this day.
- Dylan16807 1y agoThat's pretty strange. If they're using it in a meaningful way, then they're applying it to arbitrary files, so they'd generally need fixes for almost all the bugs. So what resources would be lacking so badly that they give up on releasing?
- wakawaka28 1y agoIt could just be a lame excuse. Open sourcing with zero support would be better than not doing it. But I imagine that this seems valuable enough to keep secret, or at least not to pay money to polish up for external use.