Cron would be for a polling model. You can also have an interrupts/events model that triggers it on incoming information (eg. new email, WhatsApp, incoming bank payments etc).

I still don't see a way this wouldn't end up with my bank balance being sent to somewhere I didn't want.

▲

bpicolo an hour ago | parent | next [-]

Don't give it write permissions?

You could easily make human approval workflows for this stuff, where humans need to take any interesting action at the recommendation of the bot.

	▲	wavemode 3 minutes ago \| parent [-]
		The mere act of browsing the web is "write permissions". If I visit example.com/<my password>, I've now written my password into the web server logs of that site. So the only remaining question is whether I can be tricked/coerced into doing so.

▲

igravious an hour ago | parent | prev [-]

> I still don't see a way

1) don't give it access to your bank

2) if you do give it access don't give it direct access (have direct access blocked off and indirect access 2FA to something physical you control and the bot does not have access to)

---

agreed or not?

---

think of it like this -- if you gave a human power to drain you bank balance but put in no provision to stop them doing just that would that personal advisor of yours be to blame or you?