Figma is a work tool only and I'm disappointed by its MCP tooling which feels late and behind where it should be, I just feel forced to use Figma Make which stays in their walled garden without practical utility and connections to my actual codebases

I sometimes like having my content editorialized. Some of the LLM writing tropes are ok to me—I'd delete them if I added this prompt to my instructions (but I wouldn't). But my editorial preferences—the sense of voice and tone I want the LLM to make—are rarely these tropes. Instead, I have a positive prompt of the angles I do enjoy.

However, what is cloying about these tropes for many is that they're becoming empty words. Instead of tack-sharp summaries or reductions to simple understanding, the model is spilling extra tokens for minimal value—I don't need to read "it's not X, it's Y" for the n-th time today. I'd really prefer tighter, more succinct reading that actually directly quotes sources (which modern models rarely do to avoid copyright traps).

Pure grid cycling is also frowned on by some utilities.

I have 2 EVs (Tesla and BMW), an electric oven, and a homelab rack (but no HVAC), and my usage was 34.4 MWh last year — with 100% from Solar and Powerwall.

This isn't always the patient's choice—my insurance/PBM (CVS Caremark) dropped coverage for the GLP-1 that I was taking (Zepbound) and had several rounds of prior-authorization shenanigans over a few months before they approved the previous-generation GLP-1, Wegovy. Now I've had to start the ramp-up of a different medication again, which hurt and stalled progress. Evil.

Would be cool to read more!

I think the telltale for me that makes me count as heavily AI-assisted is the lack of inclusion of real, inline examples of actual fares & their restrictions. I know I've seen them broken down before in other content. But not once here was there a full readout of an actual fare bucket & its rules. I think a human writer would have been tempted to include even one of those as an artifact, but an AI as a topic reviewer/summarizer/collator won't unless explicitly instructed.

Try opening a HEIC or AV1 or something on a machine that doesn't natively support it down to the OS-level, and you're in for a bad time. This stuff needs to work everywhere—in every app, in the OS shell for quick-looking at files, in APIs, on Linux, etc. If a codec does not function at that level, it is not functional for wider use and should not be a default for any platform.

> By being pedantic about the formatting, BlastDoor is protecting the recipient from an exploit that would abuse that type of issue.

So, not impossible, but less likely than you think

This has the potential to damage safety-critical sensors used in backup cameras or autonomous vehicles—and, obviously, inflicts damage on personal property like smartphones.

Volvo even states online that their sensors can damage cameras: https://www.volvocars.com/uk/support/car/ex90/article/47d2c9...