I assumed you might have been referring to the Payment Request API when you said "all major browsers support it" because that isn't true for ILP. Thanks for the

I assumed you might have been referring to the Payment Request API when you said "all major browsers support it" because that isn't true for ILP. Thanks for the correction on the acronym's meaning. You're right, Coil is a member of the W3C [members]. You're also right that W3C approval isn't necessarily necessary for something to become implemented. However, when I hear "the W3C is behind ILP" I (and I assume many others) interpret that to mean the W3C as a consortium has taken some step towards creating a standard, or even that the consortium has issued some statement that they hope to do so. I don't think that most people would interpret one of the W3C's 400+ members proposing something and putting it up on a domain they bought as the W3C being behind it. HTML5 is a great example of how tech becomes implemented and standardized in the modern era. HTML5 exists because Apple, Google, Mozilla, and Microsoft agreed on it (through the organization WHATWG) and then implemented it. HTML5 was implemented through an even more centralized process, I wouldn't call getting something pushed through by the major browser members something anyone can do just by putting up a good spec. I agree completely that a W3C spec isn't something people need before they can use the extension shim, of course. All I meant to respond to was your claim that browsers and the W3C were behind IPL. A company called Coil is behind IPL. [members]: https://www.w3.org/Consortium/Member/List https://www.w3.org/Consortium/Member/List