This makes me want to never create a public service again.

Definitely get that. Being hammered by scrapers is a massive PITA (especially with latest aggressive AI crawlers). We focus primarily on allowing people to automate their existing workflows. For all hosted workflows we have rate limits to prevent mass scraping/affecting server workload in any real capacity. In fact, because we don't load js/html and hit endpoints directly I would guess that we consume less server resources in the end.

▲

doc_ick 4 hours ago | parent [-]

Oh no I’m not worried about the resources or rate limits.

If I’d make a mobile app and users simply use your automation service instead of my mobile app, I’d lose traffic/money/motivation to improve it.

If they run into issues from your service now it could make my app look bad while the error isn’t with the app.

See tailwind for an example tale.

	▲	an hour ago \| parent \| next [-]

	▲	alexblackwell_ 3 hours ago \| parent \| prev [-]
		The requests still route through your servers/the data still lives with you. Kampala is a powerful tool but I don't see people replacing the actual apps with it. Most of our customers use it for automating repetitive actions in legacy dashboards.