Dan Lyke 23:07:43+0000 (2025-01-17)— twitter (1/0) facebook (0/0) flutterby (1/1) — Lat,Lon: (38.2508,-122.639)

If you are one of the single-digit people in the world who understands this, I am so, so sorry. document.querySelector("div[role='banner']:has(div > a[href='https://support.google.com/a/answer/33864'])").style.display="none";

Dan Lyke 18:24:46+0000 (2025-01-17)— twitter (1/0) facebook (0/0) flutterby (1/1) — Lat,Lon: (38.2517,-122.639)

I'm trying to debug why our password fill isn't working, and run into the "Boomerang" framework, and under features I see a list like: * Web browser client No plugins required! * Node.js command line client * WebCL support in progress Okay, but, like, what the fuck does this actually *do*? Besides frob the egos of middle management or something?

Dan Lyke 18:01:41+0000 (2025-01-17)— twitter (1/0) facebook (0/0) flutterby (1/1) — Lat,Lon: (38.2517,-122.639)

Whee: "Atmospheric CO2 rise now exceeding IPCC 1.5°C scenarios" https://www.metoffice.gov.uk/research/climate/seasonal-to-decadal/long-range/forecasts/co2-forecast-for-2025 Just imagine if we'd spent that $150B that's burning up in Southern California, or the ~$60B that Helene inflicted on North Carolina (>$80B total), or the... pre-emptively, rather than making the world worse.

Dan Lyke 17:25:21+0000 (2025-01-17)— twitter (1/0) facebook (0/0) flutterby (1/1)

In this age of dynamic languages which protect ourselves from raw pointers, and widget sets which manager their own string storage, how are people managing secure text, like passwords? Used to be we'd memset() out our passwords as soon as we were done with them, now... Do we just hope that the allocator overwrites them, that the garbage collector discards them, or do we just depend on memory protection keeping others from finding them?