(no title)
great_psy | 1 year ago
We already have an interface for agents, we call that an API. Why do we need to have AI click buttons, that eventually call an API. Just skip the middle layer and go straight to an API that does everything that system is capable of doing.
bberenberg|1 year ago
“Twitter doesn’t want to let me access via an API? That’s fine, my browser/agent will automatically automate what I want it to do for me in the UI.” Is a major shift in how we interface with other services.
rixed|1 year ago
gorgoiler|1 year ago
This goes for aria- labelled forms, but also for button operated doors, tactile surfaces, and information printed in plain and clear English.
Robots must love public buildings! Many doors are labelled with a bright green sign using the human word for door (“exit”), most signs and switches are labelled in human binary (braille) and the designers of the building go out of their way to replace lots of pesky steps with nice ramps instead.
preommr|1 year ago
End-user interfaces can be served ads, are intrinsically rate limited, and are often the main money source.
APIs make no ad revenue, can easily rack up expensive server costs, and are often a single third-party service that offer services to the rest of the customer base (bonus points for making you look bad if they implement a feature better).
necovek|1 year ago
But it's also why ad-blockers generally work.
solidasparagus|1 year ago
jackvalentine|1 year ago
RPA bridged the gap a bit for us.
ants_everywhere|1 year ago
unknown|1 year ago
[deleted]