Pharaoh2

It was one of the few CI providers that supported MacOS.

Since iOS apps can only be legally built on apple hardware, if you were an iOS developer and didn't want to maintain your own mac minis, you knew about them and the few other providers.

Edit: s/comparable LTV/comparable ROI(~= LTV-CPI)

You will have equal ROI, with the LTV being slightly lower on android but so too will the acquisition cost... overall profit being the same.

This may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms.

And if you also going to launch in EU/Australia/Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app.

So the classical logic of implementing on iOS first doesn't really apply anymore. Now its more, implement first on the platform you are comfortable with but don't forget about the other platform because there is a equal amount of money to be made there...

PS: Data excludes low end iOS and android devices. (< SE, old iPads/iPods, old and cheap android devices). These devices have extremely low conversion on both platforms anyway.

Yep, that was the whole argument of the article... I do really agree with the article but at least we can agree on what the article is claiming...

He is talking about mining bitcoins, not buying bitcoins.

Most bitcoin hash rate comes from places with low energy costs... its just basic economics.

The only reason this arbitrage is present is because the value of bitcoins is higher than the cost to mine them at the moment. Since the capital investment required to setup a (reasonable large)mining farm is rather high, it is unknown if the investment will pay off over the long term. But a lot of people are betting it will.

That sounds horrible, squash -> rebase -> fast-forward merge... Much more easier to reason about the commits/changes.

Git bisect is really important in some cases and that needs all/most commits to be compilable..., especially big merge commits.

Unless you have a special reason to preserve all commits as they were made (eg. signed commits), in that case go with the linux model of small single responsibility merges that preferably have no conflicts...

Except that hitler video is now making money from the pepsi ad. And its not far fetched to say that pepsi is giving money to creators of that video and when pepsi exec find out that that is a thing, they will want to shut it down asap.

PR is not a logical thing because people aren't logical, they are emotional and in that context your logic doesn't mean anything...

Facts are lost in the world of marketing, all that matters is ctr and conversion. I wonder if we can do something about this?

Too late, enough businesses have screwed up the unsubscribe system that now I mark every mail as spam and let the spam filters take care of it.

I don't care if the unsubscribe links works or not, I already have a faster path.

100% because it depends on your TV not the device sending the signals, assuming the source device supports rec 2020 at all that is...

DV certs don't say anything about who the own the website. Just that the website is the URL you are trying to visit. Someone else could have registered the url and created the website, so checking the certificate chain doesn't prove anything.

EV certs on the other hand at least claim to verify who owns the website but even then I would be cautious.

Did you mean https://www.blog.google/?

HDMI 2.1 is 48 Gbits/s

How is it different from ImageOptim?

https://github.com/ImageOptim/ImageOptim

Also are you going to support and fix the frequent bugs that png optimizers run into with esoteric color space/alpha combinations beyond the best effort...?

If your service allows arbitrary url queries that a user can trigger then you should make sure that you only allow queries to publicly routable ip ranges anyway.

169.254.0.0/16 is link-local range which you should be flitering along with publicly routable ip ranges that might be very upset if you access them like .mil reserved ip ranges. Go as far to also only allow DNS names instead of arbitrary ip, keeping in mind dns names may resolve to non publicly routable ranges or ranges you may not wish to access. These are all standard dangers of making queries on a user's behalf.

Good list of ipv4 ranges you should not allow: https://github.com/robertdavidgraham/masscan/blob/master/dat...

You are getting downvoted because it's not a vulnerability.

It's well documented and very useful feature in aws and it also exists in gcloud, although gcloud documentation is not as good^1.

It only becomes a vulnerability if you don't read the documentation AND don't follow best practices^2.

I don't know if azure provides this feature.

^1 I use gcloud now and have used aws in the past.

^2 Don't run unknown code without proper sandboxing

Almost like a video camera running face recognition... which almost sound like a lot easier to do.

It's not really chrome's fault. Blame it on increased screen resolution, copious amounts of available ram and a requirement to prefer using less cpu than less ram. Which also has the nice effect of using less energy.

If you have ram and it is not being used, it is completely wasted, if you have cpu cycles and it is not being used you are just saving on battery and not over heating the laptop.

High gain directional antenna pointing at exactly the right direction

It would be awesome if HN automatically created a archived version using https://archive.org/ and added a archive link below the post like the web link.

The reason is very simple. The best way to learn about an event is to observe an event. One of the most important thing that NASA does is collect data. That data can then be analyzed in the future to mitigate or prevent future problems.

We have already beaten the turing test multiple times, each time making the test more complicated than how it was originally designed. We have now moved on to the supposedly better chinese room test.

I don't believe it. Unless you are running some 1999's 20gig hard drives and a i7-6700k with high speed ddr4 rams and use a ccache and gold linker, that is very very unlikely.

I am still unconvinced if NN provide any advantage over regular expressions in this domain since it's not a hard problem to solve. Also, the request needs to be rejected before the connection is made so the only data to work with is the HTTP request headers.

On an enterprise level, a better challenge to solve with NN would be to create a asic accelerated neural net hardware to filter packets/connections of IPS/IDS and firewall purpose with an extra ability of also possibly blocking advert.

Part of the requirement of adblock software is to inject itself into the request pipeline in realtime and reject ad requests while at the same time causing as small a stall as possible and also using the least amount of resources. NN's running inside a browser don't satisfy any of those criterias.

uBlock is working on creating neutered version of ad/tracking scripts so that the js think that they are loaded fine and are working but they don't do anything. They are called surrogate script and noscript already uses them.

https://github.com/gorhill/uBlock/blob/master/assets/ublock/...

In that case you use the backup codes that you had printed and put in a safe a register a new 2FA token.

All projects start that way, mostly because it very hard to invent a new noun for something. Some projects just get really popular and then get high on search rankings for that noun organically.