D
Don Y
Guest
Why do most \"smart devices\" seem to (needlessly?) inject a
proxy into their communications with other devices?
Arguable needs could include:
- vendor wants to harvest usage information
- vendor wants to snoop (gain some advantage)
- vendor wants to act as a bastion host
- vendor wants to supply service enhancements (e.g., DDNS)
- vendor wants to keep device current (laughable)
The first two are clearly not value added to the consumer.
The third *could* represent value -- but there\'s no way
of empirically knowing if it is actually happening!
The fourth seems trite -- are those enhancements REALLY
necessary? (do you really need to be able to check to
see if your laundry is done while miles from home? Or,
would an alert that finds you on the other side of the
house be more typical -- handled locally)
The fifth could be empirically verified but I\'d wager
the number of updates pushed is pretty small. Esp if
you consider how often devices are \"no longer supported\".
Any other likely reasons?
proxy into their communications with other devices?
Arguable needs could include:
- vendor wants to harvest usage information
- vendor wants to snoop (gain some advantage)
- vendor wants to act as a bastion host
- vendor wants to supply service enhancements (e.g., DDNS)
- vendor wants to keep device current (laughable)
The first two are clearly not value added to the consumer.
The third *could* represent value -- but there\'s no way
of empirically knowing if it is actually happening!
The fourth seems trite -- are those enhancements REALLY
necessary? (do you really need to be able to check to
see if your laundry is done while miles from home? Or,
would an alert that finds you on the other side of the
house be more typical -- handled locally)
The fifth could be empirically verified but I\'d wager
the number of updates pushed is pretty small. Esp if
you consider how often devices are \"no longer supported\".
Any other likely reasons?