ketch

The article has answers

> It seems that the original author

> - Briefly added the authorization token to their source code

> - Ran the source code (Python script), which got compiled into a .pyc binary with the auth token

> - Removed the authorization token from the source code, but didn’t clean the .pyc

> - Pushed both the clean source code and the unclean .pyc binary into the docker image

This would also break the current approach for responsive emails.

Usually the default/desktop styles are already compiled and inlined, then a style tag with media query selectors is used in the `head` to improve readability for mobile devices.

SEEKING WORK | Montréal, QC, Canada or Remote

Senior full-stack developer with a degree in graphic design, specializing in helping teams deliver beautiful, accessible, and performant web products.

Immediate availability for short to medium term projects.

Services offered:

- Full-stack web development

- Branding & identity design

- Product proof-of-concept/MVP design & development

Skills: TypeScript, NodeJS, React, WebComponents, HTML, CSS, WebComponents, SQL UX/UI design

---

More details and contact info at https://ketch.co

Maybe not as hard-science heavy as you are looking for, but I found this article to be an approachable overview of potential methods https://www.orbuch.com/carbon-removal/

I'm pretty sure Garmin and Polar are pretty capable of fending for themselves, and I hope that by extension the smaller devs will be able to defend themselves more easily. But I agree on your second point