cucho

As with most things, the price is what a buyer is willing to pay. As for the mechanics, sell it through an escrow service. I’ve used Escrow.com in the past.

> Not sure how we arrived at the present title

It was me. Sorry, I didn’t mean to imply that Chris Olah co-authored the encyclical with the Pope. I just found it noteworthy that there was someone from the “industry” at the encyclical presentation on May 25, which I think is a first. Usually, they are all clergy or academics.

We are using LangGraph, which is quite low level, but has useful features like time travel, human in the loop capabilities (interruptions), flexibility on the paradigm.

Economic BCAs are typically handled by large eng firms like Arup, Jacobs, and WSP. However, the tricky task of modeling time savings (given that transport systems are complex) is often subcontracted to more specialized firms such as Steer.

Deloitte, KPMG, etc are usually more involved in writing the financial case (how to fund the project).

That's actually the standard model for evaluating transport projects: aggregating small time savings across millions of people.

You basically take those millions of saved hours and multiply them by a government-standard 'value of time' (roughly £15/hr in the UK). That usually makes up the bulk of the benefits, though they also price in things like safety (a prevented death is worth ~£2m), carbon, noise, etc.

IIRC, if you hit a Benefit-Cost Ratio of 2.0 or higher, the project is considered 'high value' and has a good shot at getting executed.

All good security measures, for sure, but the blog post you linked doesn’t mention anything about telemetry (ie request data sent to those *.gw.postman.com endpoints). As a user, it would be great to know exactly what data is sent to Postman servers (eg we send resolved query strings, we don’t send headers, etc), as well as to have an easy way to opt out of telemetry altogether.

At first glance, Google's e-signatures seems to check all the boxes for legally-binding electronic signatures: user consent to conduct business electronically, proper adoption of a signature symbol, and signed documents tamper-proof'd with a cryptographic signature.

(You'd be surprised how many e-signature platforms fail to meet the basic legal and jurisprudence standards for creating electronic signatures that can hold up in court)

I'm glad to see serious competition for 20-year-old dinosaurs like DocuSign, Adobe Sign (ex EchoSign), and Dropbox Sign (ex HelloSign). They've gone undisrupted for far too long.

Disclaimer: IANAL, but working at SignatureAPI.com I've been advised with the top e-signature lawyers in the US.