News for hackers. Stuff that matters.

A comment on Automate Public Certificates Lifecycle Management via RFC 8555 (ACME). Parent comment

Re:Automate Public Certificates Lifecycle Management via RFC... by throwaway81523 on Tuesday April 12, 2022 @01:02AM (#30998817)
More like: first they become the dominant acme provider, then the other ones go away so they are the only one left, and then they have you where they want you.
[ Parent | on HN ]
Re:Automate Public Certificates Lifecycle Management via RFC... by tobltobs on Tuesday April 12, 2022 @02:24AM (#30999290)
They have you where they want, you are willing to pay, ... but the close down the service anyway with a three months notice.
[ Parent | on HN ]
Re:Automate Public Certificates Lifecycle Management via RFC... by pdkl95 on Tuesday April 12, 2022 @05:19AM (#31000334)
> first they become the dominant acme provider

The traditional way a big tech company becomes the dominant provider is to embrace an open interoperable protocol to minimize the friction of switching from another provider. Later, when they have captured enough of the market, they extend the protocol to gradually reduce the de facto interoperability with other providers to increase the friction of switching to any other provider.

https://en.wikipedia.org/wiki/Embrace%2C_extend%2C_and_extin...

[ Parent | on HN ]