How so? The TV, being a Roku-enabled device (says so on the box!), reasonably expected me to have a Roku account. I could have plugged an ethernet cable into it to bypass WiFi, but my network router is not close enough for that, hence the WiFi access. It still would have wanted the Roku account because, well, it's a Roku TV, and that's its primary design goal. The account was "free" and didn't require giving them my first-born or my kidneys, so I was OK with that. I may actually try using Roku in the future, but for now it's just an unused feature of a device that functions as a suitable display for my DVR, otherwise. The vacuum, by contrast, is controlled from the smartphone app only (well, except for a single button on the top), and, also said so on the box. That, again, requires WiFi access. The vendor account I see as being mostly for scheduling and automated software updates rather than anything else (like spying on my vacuum buying habits), and, again I get to keep my kidneys. I see neither as being unfit or defective because both fulfill their functions (though the vacuum is getting a little uppity lately). I think that, with any modern technology, there is a level of expectation involved. This has changed over time, but lately wireless has come become commonplace to where vendors can reasonably expect/rely on customers to have it available for use. In their eyes, they are providing a better product and service in exchange for a little of your goodwill and network bandwidth. I have many other devices that use the network, both wired and wireless. That isn't a bad thing, after all, the network is there to be used, so why wouldn't I use it for my TV and vacuum? But, more to the point, needing network access isn't the problem or a defect-by-design. I think the real concern here is that IoT has had a rocky (nay infamous) start out of the gates that left many shaking their heads. It is frightening to hear about thousands of IoT devices being turned into an Army of the Undead. What we need is for vendors to stop rushing to market before thoroughly testing their products, but even that won't catch everything. Look at more mature network/computer products and see how they still fail in various ways. I expect IoT to get better over time. It just sucks that we, the consumers, are being boosted as "beta" testers.
"defective" isn't really accurate. "intrusive by design", maybe, but a defect implies a failure. This is not the case. These products work as designed. They just want access to my "private" resources (ie: access to my WiFi and, to some lesser extent, my "personal" account on "their" systems). But, it's a question of time and effort for me. It would take more time investment for me to return both items and then seek suitable replacements. In both cases, I don't really have the time to waste and their use of my "private" resources is, realistically, minimal and won't really give away any informationI I truely care about (though the vaccum does give away some aspects of the house floor plan, but no real details concerning accessing the house itself). So, these, at least, while annoying, aren't all that intrusive on my privacy. I can, if I want, simply block their access or, instead, retarget their access on to my Guest network rather than my internal network if I'm concerned about them scanning my network. But, thus far, I haven't seen any such behaviour from either device (nor any of the other, older "smart" devices I have, and that includes my cellphone). So, while annoying, their requirements are "acceptable" at the moment. I can't say that will be true of newer devices as they start to demand more and more of our personal info, but I'll cross that bridge when I get to it.
You joke, but my new TV demanded my WiFI password and a Roku account before it would do anything else! Heck, my new robot vacuum demanded WiFi and a vendor account too! I can easily see a toaster demanding the same. Just watch Red Dwarf some time and see how pushy a toaster can truely be!:)
Well as far as modem technology goes I've still got a classic 1200 baud Hayes modem; must be from the early 80s I would guess (perhaps older?)
Bah!
I still have my original Apple ][ with my original Hayes Micro-modem (110/300) with it's external Micro-coupler (a blue ribbon cable) and the Trend-Comm terminal software for it (running of my Corvus 5Mb (yes, megabyte) harddisk).
Now if I could just figure out how to connect it to my HDTV!:-)
Has anyone seen or used this:
http://www.jadeintegration.com/jackpc.php
I'm looking for some very small form-factor/low-power boards for some embedded work and stumbled upon this.
Slashdot Mirror
How so? The TV, being a Roku-enabled device (says so on the box!), reasonably expected me to have a Roku account. I could have plugged an ethernet cable into it to bypass WiFi, but my network router is not close enough for that, hence the WiFi access. It still would have wanted the Roku account because, well, it's a Roku TV, and that's its primary design goal. The account was "free" and didn't require giving them my first-born or my kidneys, so I was OK with that. I may actually try using Roku in the future, but for now it's just an unused feature of a device that functions as a suitable display for my DVR, otherwise.
The vacuum, by contrast, is controlled from the smartphone app only (well, except for a single button on the top), and, also said so on the box. That, again, requires WiFi access. The vendor account I see as being mostly for scheduling and automated software updates rather than anything else (like spying on my vacuum buying habits), and, again I get to keep my kidneys.
I see neither as being unfit or defective because both fulfill their functions (though the vacuum is getting a little uppity lately).
I think that, with any modern technology, there is a level of expectation involved. This has changed over time, but lately wireless has come become commonplace to where vendors can reasonably expect/rely on customers to have it available for use. In their eyes, they are providing a better product and service in exchange for a little of your goodwill and network bandwidth.
I have many other devices that use the network, both wired and wireless. That isn't a bad thing, after all, the network is there to be used, so why wouldn't I use it for my TV and vacuum? But, more to the point, needing network access isn't the problem or a defect-by-design.
I think the real concern here is that IoT has had a rocky (nay infamous) start out of the gates that left many shaking their heads. It is frightening to hear about thousands of IoT devices being turned into an Army of the Undead. What we need is for vendors to stop rushing to market before thoroughly testing their products, but even that won't catch everything. Look at more mature network/computer products and see how they still fail in various ways.
I expect IoT to get better over time. It just sucks that we, the consumers, are being boosted as "beta" testers.
"defective" isn't really accurate. "intrusive by design", maybe, but a defect implies a failure. This is not the case. These products work as designed. They just want access to my "private" resources (ie: access to my WiFi and, to some lesser extent, my "personal" account on "their" systems). But, it's a question of time and effort for me. It would take more time investment for me to return both items and then seek suitable replacements. In both cases, I don't really have the time to waste and their use of my "private" resources is, realistically, minimal and won't really give away any informationI I truely care about (though the vaccum does give away some aspects of the house floor plan, but no real details concerning accessing the house itself). So, these, at least, while annoying, aren't all that intrusive on my privacy. I can, if I want, simply block their access or, instead, retarget their access on to my Guest network rather than my internal network if I'm concerned about them scanning my network. But, thus far, I haven't seen any such behaviour from either device (nor any of the other, older "smart" devices I have, and that includes my cellphone). So, while annoying, their requirements are "acceptable" at the moment. I can't say that will be true of newer devices as they start to demand more and more of our personal info, but I'll cross that bridge when I get to it.
You joke, but my new TV demanded my WiFI password and a Roku account before it would do anything else! Heck, my new robot vacuum demanded WiFi and a vendor account too! I can easily see a toaster demanding the same. Just watch Red Dwarf some time and see how pushy a toaster can truely be! :)
I told him NOT to wear a Red Shirt today! -- Dr. McCoy
Well as far as modem technology goes I've still got a classic 1200 baud Hayes modem; must be from the early 80s I would guess (perhaps older?)
Bah!
I still have my original Apple ][ with my original Hayes Micro-modem (110/300) with it's external Micro-coupler (a blue ribbon cable) and the Trend-Comm terminal software for it (running of my Corvus 5Mb (yes, megabyte) harddisk).
Now if I could just figure out how to connect it to my HDTV! :-)
Has anyone seen or used this: http://www.jadeintegration.com/jackpc.php I'm looking for some very small form-factor/low-power boards for some embedded work and stumbled upon this.