Re: Introducing a new HTTP response header for Carbon Emissions calculation

Lucas Pardue writes:

> Failure to provide client-side reporting risks creating a perverse
> incentive to push more work onto the client, which is probably worse from a
> net perspective.

Ohh, absolutely.

But it is tricker to implement because the significant client side
emissions are from JS which runs after the transaction is nominally
over, so the charge needs to be cached client-side and sent on the
next request, if any.

There is also the issue of how to prevent people from just 
charging 1 billion tons of CO2 to Exxon's website because they
feel like it...

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Wednesday, 12 April 2023 08:33:18 UTC