2026-09-27 23:36 UTC
@shriramk@mastodon.social As we both understand, a reservation website is a structured negotiation between three parties designed to minimize impact on staff, and provide for the whole lifcycle of the reservation. I use these too, especially if the restaurant expresses that preference, and I appreciate them.
It's not an "API" though, becasue all of the ones I have seen presume human agency on my part. Maybe I've over-indexed on the OAuth2 entity model tho. The flow is designed to NOT support automated agents, and they consider that abuse.
I'm sure noone in the fediverse would mistake a human being picking up the phone for an API, or use an API metaphor to rationalize abusing those humans. So let's talk about this hypothetical one call agent.
The agent making one robocall to a private entity without prior permission is still subject to FCC robocall complaints, caller-id requirements, and basic social norms. Without even getting into efficacy of the speech recognition/synthesis and reasoning, it bypasses the mitigations and controls of a website reservation system, if there is one, and is an unbalanced demand on human time.
That is to say, it is an entitled dickhead move. Not an innovation, or signal of missed oportunity. This was the point of my original commet, BTW.
This practice becomes a DDOS when a sufficient, but relatively small, number of hypothetical entitled dickheads pull the host(ess) into a running gun-battle armed only with caller-id and "Thank you for calling, please hold". 8^)
Replies (0)
No replies.