News for hackers. Stuff that matters.
Re:NeverSSL by artursapek on Saturday November 02, 2019 @07:12PM (#21430774)
Bandwidth, maybe? That page is 53.8 KB total. $2k does seem high though.
Re:NeverSSL by maltalex on Saturday November 02, 2019 @07:36PM (#21430884)
A GB of outbound transfer on AWS costs about 0.09$.

If the page is 55KB, that means that a single GB is about 18K page loads, but let's make that 15K page loads due to various overhead.

To spend 2000$, you'd need to send about 22TB, which are about 330M page loads.

Re:NeverSSL by eatbitseveryday on Saturday November 02, 2019 @07:51PM (#21430958)
> To spend 2000$, you'd need to send about 22TB, which are about 330M page loads.

That equates to 330M/365d = ~900k loads per day.

> it's now grown to about 6 million hits per day, and that's just the traffic that makes it through to the landing page [0]

So he's paying a discount, even.

[0] http://neverssl.com/changes

Re:NeverSSL by ComputerGuru on Saturday November 02, 2019 @07:46PM (#21430925)
But that’s not accounting for gzip.
Re:NeverSSL by gruez on Saturday November 02, 2019 @08:23PM (#21431111)
This. Firefox's dev tools says 3.38KB transferred (including redirect and favicon). Taking that into account, it's closer to 5 billion page loads.
Re:NeverSSL by wincy on Saturday November 02, 2019 @09:44PM (#21431465)
Well if he’s getting 6 million a day that’s a little over 2 billion hits a year. Maybe he’s overprovisioned an AWS instance or something.
Re:NeverSSL by bbernoulli on Saturday November 02, 2019 @10:22PM (#21431642)
I think he's including the transfers from twitter in the 55kb (which is over 50k of it), which wouldn't cost him anything personally
Re:NeverSSL by PuffinBlue on Monday November 04, 2019 @05:33AM (#21440370)
Looks more like 2.7KB and then it loads some resources from Twitter to make up the rest of the size.
Re:NeverSSL by c22 on Saturday November 02, 2019 @07:29PM (#21430861)
When used "properly" it should take even less bandwidth.