{"id":5146,"date":"2017-03-12T11:26:56","date_gmt":"2017-03-12T16:26:56","guid":{"rendered":"https:\/\/rud.is\/b\/?p=5146"},"modified":"2018-03-10T07:54:15","modified_gmt":"2018-03-10T12:54:15","slug":"think-twice-before-using-ohmconnect","status":"publish","type":"post","link":"https:\/\/rud.is\/b\/2017\/03\/12\/think-twice-before-using-ohmconnect\/","title":{"rendered":"Think Twice Before Using Ohmconnect"},"content":{"rendered":"

I listen to @NPR throughout the day (on most days) and a story on Ohmconnect<\/a> piqued my interest (it aired 5 days prior to this post). The TLDR on Ohmconnect is that it ostensibly helps you save energy by making you more aware of consumption and can be enabled to control various bits of IoT you have in your abode to curtail wanton power usage.<\/p>\n

OK. So\u2026?<\/h3>\n

Such a service requires access to (possibly many) accounts and devices to facilitate said awareness and control. Now, it’s 2017 and there’s this thing called OAuth<\/a> that makes giving such access quite a bit safer than it was in the “old days” when you pretty much had to give your main username and password out to “connect” things.<\/p>\n

It \u2014 apparently \u2014\u00a0is not 2017 wherever Ohmconnect developers reside since they ask for your credentials to every service and integration you want enabled<\/strong>. Don’t believe me? Take a look:<\/p>\n\n\t\t