What a fascinating deep dive. 2x with sphere mapping is my favourite - it starts to take on a sort of pointillism-like quality which gives all the objects (or maybe my brain) a sort of understanding of their texture.
Could be a very useful way to do some overnight tasks using spare RAM. Possibly things like LLM-based categorisation, labelling, data cleansing. That's what comes to mind for me anyway.
Nope. I specifically excluded LLM wrappers, which I think is a fair qualification for a "first useful software at scale". If it turns out that LLMs can produce useful things that aren't LLM wrappers, then maybe later we can evaluate whether LLM wrappers are worthwhile. But if LLM wrappers are only used to produce other LLM wrappers, which are used to produce other LLM wrappers, it's merely indicative of a pyramid scheme wherein people are trying to sell you on hype because they can't sell you anything that actually produces utility in the real world (browsers, compilers, IDEs, production databases, music production software, photo editing software, Excel, viable Discord replacement, any of the reasons people used computers as tools to accomplish things).
On the note of Microsoft specifically, they've shipped a critical OS-destroying bug every month for several months straight now, and people seem to be generally in agreement that Windows 11 has only been going further and further downhill. I have literally not seen a single person with a positive opinion on anything W11 or associated programs have done in the last 6 months. Which does not create a compelling case for translating LLM wrapper into real-world useful code.
I haven't tried it, but I think you could keep the full transcript by running a pre-compact hook (on Claude Code) to save your entire conversation history to a file.
I agree that rejecting valid non-Latin characters in valid contexts is user-hostile, but I should be clearer about scope: this is specifically about machine-readable identifiers (slugs, handles, ENS names) where the character set is intentionally restricted, not display names or user-facing text.
The approach there should be what wongarsu describes below (imo), to style the UI so official accounts are visually distinct (badges, colour, etc.) rather than policing the character set.
namespace-guard is deliberately opinionated for the slug/handle case where you've already decided the output should be ASCII-safe. If your use case is broader than that, confusables detection without rejection is the right call.
Thanks Josh - putting this article out there has pushed me to sharpen a lot of my thinking which hopefully should come across in my more recent work. I've updated the article to scope the NFKC recommendation to identifiers and added a note crediting your correction. Thanks for catching it.
thanks. I am not a frequent tmux user, and always find myself forget about the basic commands after what the hotkey is. So this deadly simple stuff may be useful for those not want to spend too much time but have to use tmux.
Of course Google can restrict how their API is accessed. But locking paid accounts with no warning, no explanation email, and no functioning support path while continuing to charge $249/month is a different problem entirely. A reasonable enforcement process would have been a warning email, grace period to stop using the tool, then restriction.
What an awful way to lose trust, locking out their users but billing them all the same.
Their "API" isn't what's being accessed here. As far as I understand it's using their subscription account oauth token in some third party app that's the issue here.
It is basically impossible to disallow the token to work that way on a technical level. It would be akin to trying to trying to set up a card scanner that can deny a valid card depending on who is holding it. The only way to prevent it from working is analyzing usage patterns/details/etc in some form or fashion. Similar to stationing a guard as a second check on people whose cards scan as valid.
Google have always done this if they suspect you’ve broken TOS, if anything this is better than usual because usually you lose your Gmail and YouTube accounts too with no human to talk to about it.
I was using Antigravity the proper way, but why would I risk my account using this subpar software? OpenClaw and Opencode literally obfuscate the API call exactly like Antigravity calls it. Do you really trust Google to only catch misuse using this dragnet?
