Re: Re:Predictive failures

Liste des GroupesRevenir à se design 
Sujet : Re: Re:Predictive failures
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.design
Date : 16. Apr 2024, 23:35:34
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uvmqve$15hl7$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
On 4/16/2024 12:43 PM, Edward Rawde wrote:
"Don Y" <blockedofcourse@foo.invalid> wrote in message
news:uvmjmt$140d2$1@dont-email.me...
On 4/16/2024 10:25 AM, Edward Rawde wrote:
Better to inform the individual who can get the replacement done when
the
tenant isn't even home.
>
So, a WiFi/BT link to <whatever>?  Now the simple smoke detector starts
suffering from feeping creaturism.  "Download the app..."
>
No thanks. I have the same view of cameras.
They won't be connecting outbound to a server anywhere in the world.
But the average user does not know that and just wants the pictures on
their
phone.
>
There is no need for a manufacturer to interpose themselves in such
"remote access".  Having the device register with a DDNS service
cuts out the need for the manufacturer to essentially provide THAT
service.
 Not for most users here.
They tried to put me on lsn/cgnat not long ago.
After complaining I was given a free static IPv4.
Most folks, here, effectively have static IPs -- even if not guaranteed
as such.  But, most also have AUPs that prohibit running their own servers
(speaking about consumers, not businesses).

Most users wouldn't know DDNS from a banana, and will expect it to work out
of the box after installing the app on their phone.
There's no reason the app can't rely on DDNS.  Infineon used to make
a series of "power control modules" (think BSR/X10) for consumers.
You could talk to the "controller" -- placed on YOUR network -- directly.
No need to go THROUGH a third party (e.g., Infineon).
If you wanted to access those devices (through the controller) from
a remote location, the controller -- if you provided internet access
to it -- would register with a DDNS and you could access it through
that URL.
It is only recently that vendors have been trying to bake themselves into
their products.  Effectively turning their products into "rentals".
You can buy a smart IP camera that will recognize *people*!  For $30.
Plus $6/month -- forever!  (and, if you stop paying, you have a nice
high-tech-looking PAPERWEIGHT).
I rescued another (APC) UPS, recently.  I was excited that they FINALLY
had included the NIC in the basic model (instead of as an add-in card
as it has historically been supplied - at additional cost).
[I use the network access to log my power consumption and control the
power to attached devices without having to press power buttons]
Ah, but you can't *talk* to that NIC!  It exists so the UPS can talk to the
vendor!  Who will let you talk to them to get information about YOUR UPS.
So, you pay for a NIC that you can't use -- unless you agree to their
terms (I have no idea if there is a fee involved or if they just want
to spy on your usage and sell you batteries!)
In addition to the sleeze factor, it's also a risk.  Do you know what
the software in the device does?  Are you sure it is benevolent?  And,
not snooping your INTERNAL network (it's INSIDE your firewall)?  Maybe
just trying to sort out what sorts of hardware you have (for which they
could pitch additional products/services)?  Are you sure the product
(if benign) can't be hacked and act as a beachhead for some other
infestation?
And, what, exactly, am I *getting* for this risk that I couldn't get
with the "old style" NIC?

Date Sujet#  Auteur
15 Apr 24 * Predictive failures70Don Y
15 Apr 24 +* Re: Predictive failures27Martin Rid
16 Apr 24 i`* Re: Predictive failures26Don Y
16 Apr 24 i `* Re: Predictive failures25Edward Rawde
16 Apr 24 i  `* Re: Predictive failures24Don Y
16 Apr 24 i   +* Re: Predictive failures3Edward Rawde
16 Apr 24 i   i+- Re: Predictive failures1Edward Rawde
17 Apr 24 i   i`- Re: Predictive failures1legg
16 Apr 24 i   `* Re: Predictive failures20Edward Rawde
16 Apr 24 i    `* Re: Predictive failures19Don Y
16 Apr 24 i     +* Re: Predictive failures16Edward Rawde
16 Apr 24 i     i`* Re: Predictive failures15Don Y
16 Apr 24 i     i +* Re: Predictive failures13Edward Rawde
16 Apr 24 i     i i`* Re: Predictive failures12Don Y
17 Apr 24 i     i i `* Re: Predictive failures11Edward Rawde
17 Apr 24 i     i i  `* Re: Predictive failures10Don Y
17 Apr 24 i     i i   `* Re: Predictive failures9Edward Rawde
17 Apr 24 i     i i    `* Re: Predictive failures8Don Y
17 Apr 24 i     i i     `* Re: Predictive failures7Edward Rawde
17 Apr 24 i     i i      `* Re: Predictive failures6Don Y
17 Apr 24 i     i i       `* Re: Predictive failures5Edward Rawde
17 Apr 24 i     i i        `* Re: Predictive failures4Don Y
17 Apr 24 i     i i         `* Re: Predictive failures3Edward Rawde
17 Apr 24 i     i i          `* Re: Predictive failures2Don Y
17 Apr 24 i     i i           `- Re: Predictive failures1Edward Rawde
17 Apr 24 i     i `- Re: Predictive failures1Don Y
17 Apr 24 i     `* Re: Predictive failures2Liz Tuddenham
17 Apr 24 i      `- Re: Predictive failures1Don Y
15 Apr 24 +- Re: Predictive failures1john larkin
15 Apr 24 +* Re: Predictive failures11Joe Gwinn
16 Apr 24 i`* Re: Predictive failures10Joe Gwinn
16 Apr 24 i +* Re: Predictive failures7john larkin
16 Apr 24 i i`* Re: Predictive failures6Joe Gwinn
16 Apr 24 i i `* Re: Predictive failures5John Larkin
17 Apr 24 i i  +* Re: Predictive failures3Edward Rawde
17 Apr 24 i i  i`* Re: Predictive failures2John Larkin
17 Apr 24 i i  i `- Re: Predictive failures1Edward Rawde
17 Apr 24 i i  `- Re: Predictive failures1Joe Gwinn
16 Apr 24 i `* Re: Predictive failures2Phil Hobbs
16 Apr 24 i  `- Re: Predictive failures1Joe Gwinn
15 Apr 24 +* Re: Predictive failures8Edward Rawde
16 Apr 24 i`* Re: Predictive failures7Don Y
16 Apr 24 i +* Re: Predictive failures4Edward Rawde
16 Apr 24 i i+* Re: Predictive failures2Don Y
16 Apr 24 i ii`- Re: Predictive failures1Edward Rawde
16 Apr 24 i i`- Re: Predictive failures1Martin Brown
17 Apr 24 i `* Re: Predictive failures2Don Y
17 Apr 24 i  `- Re: Predictive failures1Don Y
16 Apr 24 +* Re: Predictive failures7Martin Brown
16 Apr 24 i+- Re: Predictive failures1Don Y
16 Apr 24 i`* Re: Predictive failures5Bill Sloman
16 Apr 24 i `* Re: Predictive failures4Edward Rawde
17 Apr 24 i  `* Re: Predictive failures3Edward Rawde
17 Apr 24 i   `* Re: Predictive failures2John Larkin
17 Apr 24 i    `- Re: Predictive failures1Edward Rawde
16 Apr 24 +* Re: Predictive failures8Don
16 Apr 24 i+* Re: Predictive failures3Edward Rawde
16 Apr 24 ii+- Re: Predictive failures1Don
16 Apr 24 ii`- Re: Predictive failures1Don Y
17 Apr 24 i+* Re: Predictive failures3john larkin
17 Apr 24 ii`* Re: Predictive failures2Don
17 Apr 24 ii `- Re: Predictive failures1Don
17 Apr 24 i`- Re: Predictive failures1Don Y
18 Apr 24 `* Re: Predictive failures7Buzz McCool
19 Apr 24  `* Re: Predictive failures6Don Y
19 Apr 24   +- Re: Predictive failures1Don Y
19 Apr 24   `* Re: Predictive failures4boB
19 Apr 24    `* Re: Predictive failures3Don Y
21 Apr 24     `* Re: Predictive failures2boB
21 Apr 24      `- Re: Predictive failures1Don Y

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal