Ironically enough, that's a platform choice: it's the tractor emoji glyph, U+1F69C. On lots of platforms it's red or yellow :-) (Not on desktop Firefox, which is where my screenshot came from in the blog post.) Switching to dark mode may help it be a little more visible for people who find it a problem? It's a good point, though...
Oh no, I wasn't talking about visibility. Just that a certain tractor company has a trademark on the green and yellow color scheme. And they win in court.
That's a fair point. I tend to think in prose rather than visually, so I don't have diagrams already, but it would have been a good idea to put together graphical things to go along with the post to make it a better explanation! Good suggestion. Are there drawings or diagrams that you think would have been particularly useful?
Yup. Shilling my own work here, https://kryogenix.org/code/the-ux-of-text-fusion/ is a talk which explicitly calls that out -- we can do better than this, and whoever works out how to deliver chat interfaces where you can't imagine the underlying nodejs commands will have people love their stuff. (And the answer certainly isn't "pretend to be a human", either, as you know; be a bot, be known to be a bot, and have people relate to you anyway. But now I'm just reiterating the talk.)
That would certainly be simpler, in that it just fits in to the existing password login, but I'm not sure it helps all that much here? Mainly because the point of this suggested approach is discoverability; your password manager can change your password without you having to manually do it. Most of the time, this doesn't apply; a password manager knows that such-and-such-a-site has such-and-such a username and a password, but it doesn't know how to actually log in with them, just that these are the values, and maybe these are some form fields on a particular URL to fill them into.
