You posted that, and someone at Microsoft unwittingly twitched.
Clippy was useless.
But attaching a Clippy to a language model? Still nominally useless, but mindfully so!
It would be self-deprecating (un-deprecated???) humor for Microsoft, which would take the edge off of the often pushy and tone-deaf corporate look they continually and crassly paint themselves into by default.
And actually potentially useful as a branding touchstone: a visual and interface link across otherwise seemingly disparate model interfaces. Clearly delineating and bridging MS AI tools from all the other mixes of tools we are accumulating.
They could lean into the “clip” in Clippy with a side app for saving and organizing clippings and logs of notable interactions with any MS model, akin to a notes app. With features for compressing convos into compact topic cheat sheets (with retained sources & convos), lists and other helpful info gathering and leveraging tasks.
An ongoing accumulated compressed common core of context for both (hu)man and machine, er … Clippy.
The pre-clippy natural language help in MS word worked fine too. Chatbot interfaces that work fine are nothing new, it's just very few programs are complex and open-ended enough for them to be a reasonable UI -- but a full-featured word processor probably is
Agreed!
Compare https://gwern.net/fiction/clippy
That would be violating the second design principle:
"When robots and people coexist in the same spaces, the robots must not take away from people’s agency, particularly when the robots are failing, as inevitably they will at times."
With a physical robot, if it fails and freezes, it turns into a hazard.
With Clippy, it intrusively stops humans from being able to do what they are doing.
Especially the old 'suicide note' joke image... guess would be called a meme today.
its just that it outlived its welcome quickly, once i learned everything that i needed. the lesson to learn is i think about how to move from that guided experience into more power tools