zlacker

[return to "A sane but bull case on Clawdbot / OpenClaw"]
1. baalim+xZ3[view] [source] 2026-02-04 16:25:13
>>brdd+(OP)
I'm a bit surprised that people need an LLM to automate things like this. Is the market really that large, to cause such a hype? I don't think I'm being "elitist" by having a calendar and a pen, am I..?

The one tangible usecase is perhaps booking things. But, personally, I don't mind paying 5-10% extra by going to a local store and speaking to a real person. Or perhaps intentionally buying ecological. Or whatever. What is life if you have a robot optimize everything you do? What is left?

◧◩
2. hackyh+lc4[view] [source] 2026-02-04 17:22:18
>>baalim+xZ3
IMHO the "killer app" aspect of OpenClaw (and similar) is that everything is now an API.

We think of chat apps, like WhatsApp, as being ways to communicate with people, which is a nice way of saying they are protocols. When you want something, you send a message, and you get an answer, just like with HTTP, except the endpoints have been controlled by meat. With OpenClaw, the meat is gone. Now you can send a message on WhatsApp to schedule a date with your spouse, their OpenClaw will respond with availability, they'll negotiate a time and place. We've replaced human communication with an ad-hoc, open-ended date-negotiation protocol, using English instead of JSON as a data-interchange format, and OpenClaw as the interface library.

You can say "make an appointment at my dentist" and even if your dentist doesn't have a website, the bot can call up and schedule an appointment. (I don't know if OpenClaw can do this now, but it seems inevitable.) In other words, the (human) receptionist is now an API that can be accessed programmatically.

[go to top]