Electron

Users debated whether Dane and DNSSEG would better limit certificate authority power, while others argued that those systems would make it harder to remove a compromised top-level domain operator.

Commenters also criticized the fragmented revocation process, especially the need to update Go, Rust, Python, Electron, Curl, and embedded devices separately.

Overall, users saw the incident as proof that browser revocation worked better than the wider certificate ecosystem.

Title, Upcoming Critical PHP Security Release, CVE-2026109-618 and CVE-2026109-619.

We integrate with partners of ours instead.

And that's always an important thing is, what's the complexity of the sale? Even to this day, our test automation sale is a more complex sale than our primary product, our management layer sale, because you've got to do so much more testing and verification of what you're doing like we can sell our test management requirements planning tool to anyone but to test automation does it work to test my specific app with its specific user interface maybe it's oracle maybe it's sap maybe it's something we wrote 10 years ago in vb maybe it's something using you know swing or jwt maybe it's a brand new node app depending what it is, Electron app, you know, we can test a variety of these things, but it's more complex technical sale, takes longer, more objections, more naysayers, more reasons they can say no.

So we generally want to lead with our management product first, get that as our first sale, and then we cross sell our other more technical products of sort of fact.

And For us, that's worked better as a go-to market.