5 ms·
Helium are interesting, and there's a need for second sourcing, but also, i'm starting to think that the real problem is about creating percieved value for the
by petra 10y ago
Helium are interesting, and there's a need for second sourcing, but also, i'm starting to think that the real problem is about creating percieved value for the end customer, like i explained in my other comment:
https://news.ycombinator.com/item?id=14078560 https://news.ycombinator.com/item?id=14078560
I wonder what you, as a manufacturer think about it.
- joezydeco 10y agoIt's an interesting idea, and I've thought about it as well. My first objection would be that I wouldn't put some black box module from a company like Amazon or Google on my design. Too many issues about what's inside and other things like Google's tendency to follow the shiny and discontinue products for no published reasons. My idea was more along the lines of Amazon or Microsoft selling AWS and Azure-enabled hubs or concentrators that did all the backend lifting and presented a simple REST or MQTT interface on the local network for data ingestion. Then you could connect any 802.11 radio to it and send data over an encrypted channel without having to worry about the heavier layers about it (TLS, DNS, Certs, SAS tokens, endpoints, etc).
- petra 10y agoYes, the router path makes sense. In a way, it's modular security - if the customer cares about security - he should pay a bit more for the right router, if not - it's his decision. Btw, Amazon does some interesting stuff with AWS greengrass, including a router, it's quite similar to how you view it. And i'm sure they'll take of telling end users.
- joezydeco 10y agoYeah, greengrass looks interesting. At least until I saw this: Devices need to offer at least 128 MB of memory and an x86 or ARM CPU that runs at 1 GHz or more My devices run on Cortex-M0s. That's not going to work at all.