narsil

It's helpful to filter out links to large content and downloadable assets from being traversed. For example, I assume you wouldn't care about downloading videos, images, and other assets that would otherwise use a large amount of data transfer and increase costs.

If the file type isn't clear, the response headers would still include the Content-Length for non-chunked downloads, and the Content-Disposition header may contain the file name with extension for assets meant to be downloaded rather than displayed on a page. Response headers can be parsed prior to downloading the entire body.

I am willing to chalk this up to an honest mistake considering "end-to-end" encryption as being from the client's end to the server, although that's not the accepted use of the term. This appears to be their explanation. I hope their marketing team fixes this now that it's been pointed out to them though.

I really hope the UX improves considerably and basic features actually function as expected. Notifications for new messages on OS X were broken for several months last year, for example, and notifications on Android are still hit-or-miss (literally "miss" when you miss a message for several hours!).

I see your point, but if a dependency package needs exact versions for its dependencies, I'd expect it to be specified in its package.json as well. If not, then I don't see why exact dependencies for the entire tree are needed.

Sure, if a package absolutely needs exact dependencies for its entire tree, it can check in the lock file, but I've not found this necessary in practice provided I use dependencies I trust , that follow semantic versioning.

But since the lockfile can be generated from the package.json, I still don't see a reason that the lockfile needs to be committed by a third-party contributor instead of being generated automatically post-merge, or by the repository maintainers during the course of normal development.

.. and to also de-duplicate files across users to avoid repeatedly storing the same file.

Nothing seems to indicate that the cameras are building personal profiles that persist across sessions. That would be hard to do anyway, requiring some kind of recognition technology or assistance tracking consumers beyond just that aisle all the way to the register.

It looks like they're tracking aggregate statistics at most.