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.
Well that's a technicality. There's no reason to base practical realities of Jan 1 2020 being the start of the "2020s" with the fact that Year 0 was missing.
> Those technicalities, however, don't change the fact that as a society, we seem to have collectively determined that decades begin in years ending in zero and end on years ending in nine.
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.
This is how I felt about Algolia's search when I first enabled it for our Vuepress site at https://developers.kloudless.com/guides/enterprise/ (the search bar at the very top). I assumed it had loaded some kind of index in memory via JavaScript since the XHR requests take < 30 ms (!) from my location in San Francisco, which is pretty much instant. That's faster than the delay between my keystrokes.
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.
Well it's likely the client/server time-zone mismatch was the cause here. It could be that everyone at AirAsia, or even the majority of passengers, saw the right dates, and this edge case was simply not considered.
Assuming a timezone mismatch, it wouldn't always show up because the date would have to cross a midnight boundary for the days to be different. Even if we assumed the servers used Malaysia time rather than UTC, that leaves 8 hours in a day where North American travelers could see the right day.
The lack of version control in Keep has come back to bite me in the past. I've switched to OneNote which provides more control over version history and deleted notes. It's the only Microsoft product I (knowingly?) use personally, but I've come to recommend it to family and friends instead of Evernote and alternatives like Keep.
We ended up implementing a REST API endpoint for SFTP to provide an easy way for web apps to transfer content without having to speak the FTP protocol: https://kloudless.com/products/file-storage/
I can see this being valuable for apps to get user content into S3 more efficiently from the server-side rather than funneling it through hosted servers. The one caveat is programmatic user management, which I'm sure is possible.
I'm not sure I understand the concern with integrity of OAuth 2.0 payloads. Sending the request over HTTPS already ensures that the request is not tampered with, and also guards against replay attacks.
Kloudless | Solutions Engineer | San Francisco area (Berkeley); Taipei, TW | Full-time | $130k-160k + equity (SF) | Series A stage
Kloudless’s unified APIs enable engineering teams to quickly integrate their applications with other software services: https://kloudless.com.
We’re looking for an experienced Solutions Engineer to serve as a technical resource during all stages of business development and lead advanced technical support for our customers.
Ideal candidates have strong DevOps experience with Linux systems, experience in a customer-facing role, familiarity with web application development and REST APIs, and are eager to join an early-stage company.
Kloudless is backed by some of Silicon Valley’s top investors including David Sacks (co-founder of PayPal and Yammer) and Tim Draper (investor in Box, Tesla, SpaceX).
We offer competitive salaries and benefits, including insurance plans, flexible paid time off, telecommuting, and snacks. Our team-wide activities include outings, lunches and dinners.
Well, there have been attempts to create single standards (e.g. CMIS, in the content management space). A lot of the time, enabling the right workflow for the integration to be useful involves providing capabilities that quickly diverge from any common standard that is agreed on. Tying together different business stacks involves a lot more than just establishing API endpoints for individual actions.
Having a single API reduces this inevitable maintenance overhead and swaps out some set of N integrations in favor of one other. There is the added benefit of having a resource (Kloudless, in this case) assist with enabling whichever use case the business is trying to solve for their users by providing the integrations.
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.