> DO NOT RUN THIS VERSION OF NGROK (1.X) IN PRODUCTION I don't see that anywhere. Even if it is somewhere, it's not ironic. Ngrok is used for all sorts of stuf

> DO NOT RUN THIS VERSION OF NGROK (1.X) IN PRODUCTION I don't see that anywhere. Even if it is somewhere, it's not ironic. Ngrok is used for all sorts of stuff. Stream redirection to hosted services is a thing for ease of use to get going with play of a product. The point is that making it easy makes it public sometimes, which is fine if the use cases aren't arbitrary made up to justify a worrisome argument. It it very unlikely an agent is going to penetrate and exploit one of these cameras through such a service. Squirrels don't need to be secured. Other things do, so reconfigure! If you have a use case...a real one...then run this locally. The inventor and I are both privacy advocates. Your argument is cherry picked and overlooks the obvious on-premise use of a Raspberry Pi! :) In all seriousness, I get what you are talking about, but being adamant dog poop use cases must be secured is pointless. Seriously, if you have a secure use case for this it does NOT have to be streamed to some service. The service is there for squirrels, not secure deployments.