ekingr

The wireless one has Bluetooth - which is the only way to go on iOS for now.

The description doesn't say if the keys are compatible with FIDO2 / Webauthn, which seem to be the new standard superseding FIDO (namely with password-less and multi-factor auth). It would be disappointing if not...

They do.

If you want an order of magnitude of how huge the drifts are, have a look at the construction of the EPR of Flamanville in France[1]: started in 2007 with an initial timeline of 5 years and budget of €3.3bn, it is still not completed as of today (they just announced targeting the end of 2018) and the current budget is over €10.5bn.

In the end, the complexity, criticality and sheer scale of these projects make them extremely hard to lead properly and any setback can have gigantic impacts.

[1] https://en.wikipedia.org/wiki/Flamanville_Nuclear_Power_Plan...

Not to have to accept the tracking cookies policy, I guess.

It is true that LBOs can injure companies - like what happened to Toys'R'Us bankruptcy after the Bain Cap & KKR buyout.

It is especially dangerous in times of inflated multiples like we are seeing these days, where PE valuations are kind of bubbling. The demand for M&A transactions is so much bigger than the supply that prices growth quicker than the underlying business value - making it usually harder to justify through profitability improvements.

Yet the whole PE process does bring benefits to the underlying industries is buys, especially by providing investment capacities to businesses that usually don't have enough, and also by professionalization and by introducing sophisticated management standards to the companies (eg. in terms of strategic thinking, reporting, optimization, pricing, etc.).

See previous discussion: https://news.ycombinator.com/item?id=14550060

The article explains in the "Cloudflare, Privacy and k-Anonymity" section how you can use k-Anonymity to query the API with (at least some) privacy, by just submit the first 5 characters of your password's hash.

> Far too often businesses define churn as no purchases after N days; typically N is a multiple of 7 or 30 days

I'm working for a strategy consulting firm, advising large retail clients. Even though we have looked at doing this kind of advanced modelling for churn metrics, we always end-up using the same kind of very basic rules of customer not purchasing within the last x days.

The reason is twofold: (1) it’s trivially easy to implement and explain, (2) at the end of the day using the complex method is not worth the effort. Because business-wise, there are many other external factors that are much more impactful than the modelling biais – like seasonality, variation by category of product, etc.

It all depends on the decisions those metrics are used for, but most of the time it’s not worth the pain.

And especially because of its flexibility (Young's modulus) - which is very similar to the bones' ones. That's why Ti alloys are preferred when a prosthesis needs to be anchored into a bone, like the stem part of a hip implant.

Any chance iOS Safari enables it once Apple opens its NFC APIs in 11?

In the same vein, for French translation, Linguee[1] uses many sources from websites of organisations that display official content in several languages (eg. the websites of the EU, of the Canadian Parliament...). The fact that it's official texts (eg. laws) makes it quite reliable.

[1] http://www.linguee.fr

Same here on my iPhone.

Much less environmental-friendly than the Odeillo solar furnace[1]...

[1] https://en.wikipedia.org/wiki/Odeillo_solar_furnace

https://keeweb.info/ is also very nice. It has a very convenient Dropbox (& co) integration.

As you say, the Azure Key Vault helps making things more secure (by allowing to control, log and revoke keys usage), but it does not help at all with the problem of API keys in the source code - it's just another set of keys that you need in your config.

Source interview: http://www.mljournal-digital.com/meleadershipjournal/october...

Actually, one of the safest option I have found to import/export from Excel without the encoding going wild is to just copy/paste TSV data, and treat it as UTF-8 in your programming language of choice.

In that specific case, they plan to close the only road that allows to cross the centre of Paris smoothly (no red light, can be driven in 4th/5th gear all the way). Even if the number of cars decreases a lot, since the only alternative path is streets that are full of traffic lights and already quite jammed, the remaining cars will pollute much more. I'm not sure that this will help decrease pollution in the mid-term.

Reminds me of a scandal with Tesco in London when they installed "anti-homeless" spikes in front of their stores. https://www.theguardian.com/society/2014/jun/12/tesco-spikes...

I'm wondering what's the benefit of using d3 here compared to Leaflet's build-in geoJson() function: http://leafletjs.com/examples/choropleth.html#basic-states-m...