nmjohn's comments

nmjohn | 2 months ago | on: Upcoming Changes to Let's Encrypt Certificates

> and paid for with your privacy (and probably your website user's privacy too)?

That's not really how ssl certs work - google isn't getting any information they wouldn't have otherwise had by issuing the ssl cert.

nmjohn | 2 years ago | on: Ruby's exceptional creatures

> And please don’t reply.

Respectfully, if you don't want discussion, why comment in the first place?

Commenting telling someone not to comment and then ending in telling them not to bother replying is confusing behavior to me for a discussion forum.

nmjohn | 2 years ago | on: Starship will attempt a launch this Friday

> it’s borderline treason and should be prosecuted that way.

Have words lost all meaning? This is the most absurd thing I've read all day.

(And I promise I'm not even remotely defending the absurd situations you're referring to.)

nmjohn | 2 years ago | on: Cloudflare API, dashboard, tunnels down

> was only 27 minutes...

I was affected by the tunnel outage. It was down for closer to 3 hours, not 27 minutes. (Their status page does accurately reflect this time)

nmjohn | 2 years ago | on: YouTube now blocking ad block

Not sure if ublock updated their blocking rules to bypass the block or youtube stopped the experiment - but starting yesterday, I'm no longer seeing any adblock warning which previously had started blocking me (as opposed to originally just nagging me to disable) from watching youtube videos.

I do wonder if the actual outcome of the experiment was increased rates of adblocking though - since every time it makes it into the news, more people are exposed to the idea it's even possible.

Aside, (cmd+l, cmd+c, cmd+shit+n, cmd+v, enter) is a pretty useful sequence to have muscle memory for to open the same page in incognito, which easily bypasses the block as well.

nmjohn | 2 years ago | on: The database servers powering Let's Encrypt (2021)

Yes, I was pointing out that many of their products have explicit limits.

But more importantly, the second link I posted shows how that despite being "unlimited" - it's not uncommon for hetzner to throttle / close your account if you go over unstated traffic limits.

nmjohn | 2 years ago | on: The database servers powering Let's Encrypt (2021)

You can not get actual unmetered 1gb/s for anywhere close to that. If you start pushing anywhere close to that much bandwidth, you will be throttled / have your account closed. For example, Hetzner caps your bandwidth at 20TB per month.

Additionally, if you are actually pushing close to that much traffic, you can negotiate guaranteed commit prices w/ AWS that are competitive (especially when you consider the quality of bandwidth. I can only get ~100 mb/s to my hetzner server because of how bad their peering is. I can easily saturate my 1GB connection to anywhere in AWS.)

---

(Having said that, this does only apply to egress via cloudfront. Things like charging for intra A-Z bandwidth within the same region is insane, and for many workloads may be surprisingly expensive.)

page 1